I probably need to clarify what you mean.
A DB 'view' can be treated like a DB 'table' though. You can annotate it the same way. What you will miss with a view is foreign keys so you will need to manually specify joins if you need them (@JoinColumn etc).
Plus some views are not updatable... I have plans for a @SqlUpdate, @SqlInsert @SqlDelete where you can specify statements or stored procs for insert, update delete. I haven't done this yet though... but that would give you explicit control when persisting a bean based on a DB view.
Is that what you are meaning/ looking for?