Darryl Miles [http://community.jboss.org/people/dlmiles] created the discussion
"Re: AS6 & Snowdrop2 multiple queries" To view the discussion, visit: http://community.jboss.org/message/594497#594497 -------------------------------------------------------------- First thanks for your reply. 1) Yes I agree from looking at the spring.deploy codebase (and testing by creating deliberate failure scenarios, like using the wrong label) that the parent/child must be getting setup at the time that code runs. But accoridng to my code inside the WAR which uses JNDI and examines the WAR ApplicationContext those settings do not stick, something is nulling the parent/parentBeanFactory out. I create this WAR code after my posting to this thread, so I shall paste the code and output in a new reply shortly. 2) Through trial-and-error/testing I found that the spring.deploy does not look inside the WAR. It was my understanding the JBoss VFS could see descriptors nested inside a mix of dirs/JARs, so JARs inside JARs are transparent from a scan for a valid deployment descritpor and for spring this means my WEB-INF/spring-context/warApplicationContext-spring.xml _SHOULD_ match and spring.deploy should see it. But my testing indicates that even so it does not attempt to deploy it. In some ways I am not expecting to but I could not see how it was being skipped. My EAR has an exploded EJB and WAR directory which makes it even more apparent, since even without JBoss VFS code a file-scan would find it. So getting back to the question "Should a certain naming convention not be used" ? This means the file $JBOSS_HOME/server/default/my.domain.ear/my.domain.war/WEB-INF/classes/spring-context-warApplicationContext-spring.xml being a filre on the filesystem I would have expected it to be found by the spring.deployer. Since I know the Instantiaion(false) does not work. I wondered why it was being missed by the JBoss VFS code, if it is meant to be able to see descriptors from inside nested deloyments. This would make using /WEB-INF/classes/spring-context/warApplicationContext-spring.xml a _BAD_ choice of filename. Changing the -spring.xml would be a good chocie. However it appears to make no difference, since it is never looked at by spring.deployer so why is this ? 3) I'd like to come back to this point at a later date. After establishing my better understanding of the other points. 4) beanRefContext.xml I need to understand this better, I have not been using it in any projects I've created so far. 5) This is easy to observe, simply prepend the BeanFactory(label) with spring/ making it BeanFactory(spring/label) this used to bind to JNDI hierarchically. I'll try to knock out a simple EAR for JIRA later this week. Last) http://docs.redhat.com/docs/en-US/JBoss_Web_Framework_Kit/1.1/html/Snowdrop_Sportsclub_Example/index.html http://docs.redhat.com/docs/en-US/JBoss_Web_Framework_Kit/1.1/html/Snowdrop_Sportsclub_Example/index.html this looks to be a relevant URL. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/594497#594497] Start a new discussion in Snowdrop at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2082]
_______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
