[jboss-dev-forums] [Design of POJO Server] - Re: Java EE inter-module accessibility for Web Beans

[alesj]

"pete.muir at jboss.org" wrote : 
  | Yes it is - and tbh I didn't expect much more complex for JBoss AS as it uses a very flat classloading structure.
  | 
This is what we currently have.
But this can easily change once we have proper jboss-classloading.xml files to limit public API exposure, ...

"pete.muir at jboss.org" wrote : 
  | * using an ejb-jar not deployed inside the app, but deployed at the top level
  | 
You mean we should be able to track external EJBs and add them as accessible BDA?

How does this again play with all listed BDAs and circularity problem?
e.g. if I list it in one WB app Deployment/BDAs, I them must exclude it in another (its original app) ...

"pete.muir at jboss.org" wrote : 
  | * using extensions defined in manifest.mf http://java.sun.com/javase/6/docs/technotes/guides/jar/jar.html#Main%20Attributes[/url] and [url]http://java.sun.com/javase/6/docs/technotes/guides/extensions/spec.html
  | 
This looks like normal manifest lib listing, and is already supported - while building classpath.
Hence it should already be included in the recent new impl.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246669#4246669

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4246669