I've got an EAR deployment with multiple JARs - each JAR contains its own
Spring context via jboss-spring.xml files. The challenge I'm facing is that I
want my main application to be able to instantiate Spring beans from these
child contexts.
Now, I haven't a lot of experience with Spring,
Thanks for your response Marius. I've tried context.getParentBeanFactory(),
and it returns a null reference when called against the child context.
I wonder if this has anything to do with me using the
SpringApplicationContextDeployer instead of the default BeanFactory one?
Either way, I'll
I've updated the mbean declaration in jboss-service.xml and it's working fine
now.
Thank you!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4239492#4239492
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4239492
Thanks for the response! Unfortunately, I'm doing something wrong as I'm still
not able to get the deployer working.
I've downloaded the spring-deployer.zip and extracted the
jboss-spring-jdk5.deployer directory from inside it to my JBoss deploy/
directory.
Inside the extracted deployer
I'm trying to install the Spring deployer into JBoss 4.2.3.GA.
The installation instructions on the wiki state to copy the
jboss-spring-jdk5.deployer directory into the JBoss deploy/ directory, but I
don't see this available for download on the Sourceforge page here:
I've made some progress on this issue.
By adding logging for the WebappClassLoader, I am able to see where the failure
is. Depending on which JARs I'm missing, the errors are more or less obvious -
here is an obvious one, where commons-beanutils is missing:
| 2009-03-25 11:09:33,033 DEBUG
Thanks for your response Peter.
I did check the log files, but there was no additional information to work
with. Perhaps there's a specific class/package I can add a log appender for,
to see the reason for the failed deployment?
I'll keep tinkering with it - in the meantime, hopefully someone
Hello,
I'm trying to learn SEAM, and am having trouble deploying my SEAM web
application EAR on JBoss 4.2.3.GA. This is not a SEAM question, though! This
question is about learning to diagnose web application deployment problems in
general.
Because the deployment error with my SEAM app
This is exactly what I wanted. Thanks so much for your help!
I see I no longer need to specify the 'name' in the @Stateless attribute
either. This is my Global JNDI Namespace before and after the change:
Before:
| @Stateless(name=TestEJB)
| @Remote(IPing.class)
|
| +-
Hello,
When accessing one of several EJBs in my EAR through JNDI, the JNDI names are
'ear-name/ejb-name/local'. I can customize ejb-name portion through the
@Stateless(name=) attribute, but I cannot find a way to change the ejb-name
part without renaming my EAR file, and I don't want to do
Correction, I cannot find a way to change the ear-name part without renaming
my ear, not ejb-name.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4178654#4178654
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4178654
piliana,
I'm having the same issue connecting a .NET client to JBoss. Could you
please specify what you had to do to resolve this in .NET? (I couldn't find a
way to PM or e-mail you about this.)
Your help would be greatly appreciated!
-David
View the original post :
12 matches
Mail list logo
