Hi Ed,
I hope that the resource library contract spec will support scenarios where resources can be loaded from outside the filesystem or classpath, e.g. from any InputStream (JCR node, database, etc).
The use case I have in mind is where an end user uploads resources as part of a template/resource contract and later assigns the template/resource contract to one or more JSF views at runtime.
Is this possible in the current spec?
Regards,
Ian
--
Ian Hlavats - JSF Consultant
Author, JSF 1.2 Components (Packt)
http://www.jsftoolbox.com - Dreamweaver JSF Plugins
http://www.twitter.com/ianhlavats
On Nov 9, 2012, at 11:11 PM, Edward Burns <edward.burns_at_oracle.com> wrote:
> SECTION: Packaging Resource Library Contracts
>
> We must specify how the resourceLibraryContract is packaged. In JSF
> 2.0, we introduced a special directory in the webapp root, resources,
> and classpath area, META-INF/resources, for holding resources. I
> suggest we introduce a new directory in the webapp root, contracts, and
> classpath area, META-INF/contracts, and say that anything in there is
> taken to be a resource library contract. This directory is called
> CONTRACT_ROOT for discussion.
>
> If people are worried about JSF taking ownership of that name, we can
> introduce a context-param that lets the name be modified. I'm not
> worried about that, though.