Skip to main content

Source code revision

svn

summary: Change various Sniffers to set up correct list of container modules. They are now setting up required fragments as well, but I think that's not a bullet proof idea
revision: 53462
author: Sahoo
date: 2012-04-11 02:02:02 UTC (2 years)
message: Change various Sniffers to set up correct list of container modules.
They are now setting up required fragments as well, but I think that's not a bullet proof idea
, as some other bad module could have caused the host to be resolved without the fragment.
I have seen this happening for weld-osgi-bundle. That's why we are unable to rely on Sniffer
setting up fragments; instead we provision the fragments at bootstrap time. We could have
avoided it if we know how to select fragments of a host while deploying a host. Our attempt to
write a two-pass Obr resolver was futile.
Change Path Actions
M trunk/main/appserver/persistence/gf-jpa-connector/src/main/java/org/glassfish/persistence/jpaconnector/JPASniffer.java
M trunk/main/appserver/web/gf-web-connector/src/main/java/org/glassfish/web/sniffer/WebSniffer.java
M trunk/main/appserver/web/gf-weld-connector/src/main/java/org/glassfish/weld/connector/WeldSniffer.java
M trunk/main/appserver/web/gf-weld-connector/src/main/java/org/glassfish/weld/connector/WeldUtils.java
 
 
Close
loading
Please Confirm
Close