Solved! Go to Solution.
Views, including spatial views, are DBMS creatures.
That is to say, they exist in a particular relational database
by virtue of SQL
and are not supported in file geodatabases.
Layer files saved on disk are the analogous file geodatabase entities (sort of).
So, you can either export (and optionaly, reproject) your spatial views
as individual file gdb feature classes, or
export (and optionaly, reproject) your source feature class
and recreate the views as feature layers, saving the layers to disk.
If your spatial view is accessing data from several tables in the DBMS
then recreating it in a file geodatabase might be complicated.