Tim,
Regarding <jnlp-document>, if you commit it now and gets added to the nighlty build, will a new version of that module also also be available via update tool witth the changes you made?
Regarding the app-client and classpath. First of all, thank for the clarification as i though that all EAR modules wehere visible to each other and seems not to be the spec.
I must though that it was a theoritically not the most correct design. I was quiet convenient to add the whole ejb project to the app-client class path for several reasons.
1. You didn't need to create a second "xxx-ejb-client Java SE classlibrary" project for the remote interfaces.
2. If the remote interfaces export an entity in one of the methods. Means that all your entites have to be in this new "xxx-ejb-client Java SE classlibrary" as well.
3. Having put the entities in this new project, means that you manually have to add another line to your persistence.xml file pointing to the "xxx-ejb-client Java SE classlibrary" as it is this one having the entities now.
I know there are small things and that the actual design of the application looks better like this... but I am just talking from the point of view of convenience.
What I still don't understand is why does GlassFishs APT tool scan all jars in the app-client's class path (as per its manigest) file if it is only the app client main class that receives dependency injection.
Why does it need to scan all jars in the class path?
Pablo.
[Message sent by forum member 'pablopina']
http://forums.java.net/jive/thread.jspa?messageID=479294