[Design of POJO Server] - Re: VFS isLeaf() vs isDirectory()/isFile()
by scott.stark@jboss.org
This makes more sense to me, although I still don't believe isArchive is sufficiently different from isLeaf == false to warrant an attribute. Its essentially isLeaf == false + a suffix pattern to indicate this is a special non-leaf. The suggested change of the VFScanner defines such a special non-leaf such that only archives can contain deployable content. Its not clear that the vfs really has sufficient knowledge of a non-leaf to make this distinction. Examples include:
- jars referenced via Class-Path manifest references are not to be considered as deployments.
- we need to support a virtual war/ejb-jar that is directory, that does not have to end in .war/.jar, containing war/ejb-jar contents.
I think we need a basic vfs notion, and an attributed vfs notion where the attributed vfs is a result of metadata coming from the structural analysis. In the attributed vfs I can ask is a non-leaf a deployment container or not.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974879#3974879
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974879
17 years, 7 months
[Design of POJO Server] - Re: Updating docs
by adrian@jboss.org
I'm not talking about the default datasource
java:/DefaultDS
I'm talking about the default resource-ref binding
(or its annotation equivalent)
| <resource-ref>
| <res-ref-name>jdbc/DataSource</res-ref-name>
| <jndi-name>java:/DefaultDS</jndi-name>
| </resource-ref>
|
which can be set at any level and would get "merged" into the ENC.
This could be set at the server scope.
The same thing happens with
1) Class annotation at the class scope
2) XML overrides at the instance scope (if you assume instance
generically means bean instance for POJOs or EJB container of EJB
deployments)
The user still wants to know:
1) What is the ENC for this instance (merged).
2) Where are these values configured in my deployments (what they actually change) which can affect multiple instances depending on the scope.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974876#3974876
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974876
17 years, 7 months