February 2010 - jboss-dev-forums - Jboss List Archives

[EJB Development] New message: "Problem in sar and ear class loading"

by simulex inc

JBoss development, A new message was posted in the thread "Problem in sar and ear class loading": http://community.jboss.org/message/523805#523805 Author : simulex inc Profile : http://community.jboss.org/people/simulex Message: -------------------------------------------------------------- I have ejb[UserBean] which saves the user details to the database. The EJB project is dependent on hibernate and I had to provide its own class-loader in jboss-web.xml. [UserData.ear] I want to invoke this bean when the user logs in to the JBoss Portal.For this I created a Listener and registered it using jboss-service.xml. The class (UserLoginEventListener) implements PortalEventListener and listens for the UserAuthenticationEvent. I have the jar for the ejb in the lib folder sar/lib. [LoginEvent.sar] When I try to invoke the ejb from UserLoginEventListener, I get the ClassCastException. I understand this is because the UserBean is loaded by two class-loaders(one from the .ear and other from .sar) . If I try to remove the ejb jar (expecting that it will find the bean class from ear loader) I get NoClassDefFoundError. In the jboss-service.xml(for .sar), if I specify class-loader, then it fails to deploy the sar as now it doenst find JBossServiceModelMBean class which is required to register the service. Is there a way that I can share the class-loader for .sar and for .ear so that the ejb class will be loaded only once avoiding ClassCastException? Or is there a better way to do it? Thanks. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/523805#523805

14 years, 2 months

1
0
0 / 0

[Clustering Development] New message: "Re: 503 Service Temporarily Unavailable error when I kill a"

by Naveen Jakkamsetti

JBoss development, A new message was posted in the thread "503 Service Temporarily Unavailable error when I kill a node": http://community.jboss.org/message/523769#523769 Author : Naveen Jakkamsetti Profile : http://community.jboss.org/people/naveenj Message: -------------------------------------------------------------- Hi bb, Did you manage to solve this? I too have the same error, but I am still far from it. I am not even able to route traffic from Apache to JBoss. I have posted it @ http://community.jboss.org/thread/147477?tstart=0 Any help will be appreciated. Thanks. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/523769#523769

14 years, 2 months

1
0
0 / 0

[EJB 3.0 Development] New message: "Re: Externalizing Scope: Resolving EJB References and Endpoints"

by Andrew Rubinger

JBoss development, A new message was posted in the thread "Externalizing Scope: Resolving EJB References and Endpoints": http://community.jboss.org/message/523758#523758 Author : Andrew Rubinger Profile : http://community.jboss.org/people/ALRubinger Message: -------------------------------------------------------------- I've always wondered about this anyway. Because injection of a SFSB makes little sense; it can timeout and become dead. Better to inject an EJB-compatible "Home"-type thing. So a vendor-specific extension for us is what this sounds like. Confirm we're on the same page now? The other points about resolving references for injection is another concern entirely; an external resolver w/ minimal dependencies. S, ALR -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/523758#523758

14 years, 2 months

1
0
0 / 0

[EJB 3.0 Development] New message: "Re: Externalizing Scope: Resolving EJB References and Endpoints"

by Carlo de Wolf

JBoss development, A new message was posted in the thread "Externalizing Scope: Resolving EJB References and Endpoints": http://community.jboss.org/message/523755#523755 Author : Carlo de Wolf Profile : http://community.jboss.org/people/wolfc Message: -------------------------------------------------------------- Exactly, were it not that EJB 3 beans don't have a home. So we need to bind an orphanage for Weld to adopt EJB 3 beans. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/523755#523755

14 years, 2 months

1
0
0 / 0

[JCA Development] New message: "Re: Management of configuration properties inside ra.xml"

by Vicky Kak

JBoss development, A new message was posted in the thread "Management of configuration properties inside ra.xml": http://community.jboss.org/message/523753#523753 Author : Vicky Kak Profile : http://community.jboss.org/people/vickyk Message: -------------------------------------------------------------- Sounds ok, I was also going to suggest you take a look at the jboss.jca:* MBeans for retrieving the required information. It seems that you are overriding the -ds.xml which will make the -ds.xml to survice the server restart. I will take a look at the code whenever I get some free time -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/523753#523753

14 years, 2 months

1
0
0 / 0

[JCA Development] New message: "Re: Management of configuration properties inside ra.xml"

by Ramesh Reddy

JBoss development, A new message was posted in the thread "Management of configuration properties inside ra.xml": http://community.jboss.org/message/523729#523729 Author : Ramesh Reddy Profile : http://community.jboss.org/people/rareddy Message: -------------------------------------------------------------- Yes, to support my usecase, no in a generic framework, but this trick can be applied to any connection factory with little work. All the Connection Factories expose a JMX interface in the JBoss AS, using those you can see what properties are inside a Connection Factory or Data Source. When exposing a "template" for those connection factories, read the these properties and inject them into the template metadata which will be exposed through the profile service to any management applications like JOPR. When writing the template do the reverse, but write the properties that are from "ra.xml" as "config-property" in the "-ds.xml" file. If you are interested see the code here.. http://anonsvn.jboss.org/repos/teiid/branches/JCA/jboss-integration/src/m... and look for template info stuff here.. http://anonsvn.jboss.org/repos/teiid/branches/JCA/build/kit-jboss-contain... a sample ra.xml file here.. http://anonsvn.jboss.org/repos/teiid/branches/JCA/connectors/connector-jd... Thanks. Ramesh.. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/523729#523729

14 years, 2 months

1
0
0 / 0

[EJB 3.0 Development] New message: "Re: Externalizing Scope: Resolving EJB References and Endpoints"

by Andrew Rubinger

JBoss development, A new message was posted in the thread "Externalizing Scope: Resolving EJB References and Endpoints": http://community.jboss.org/message/523727#523727 Author : Andrew Rubinger Profile : http://community.jboss.org/people/ALRubinger Message: -------------------------------------------------------------- I see what you're saying now. Weld needs to defer SFSB removal. But they don't need a hook to the Container at all. They can do: EJBHome home = context.lookup("MyEJB/home"); EJBObject object = home.create(); // Do stuff, then later: home.remove(object.getHandle()); Then you don't need Endpoint at all.. S, ALR. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/523727#523727

14 years, 2 months

1
0
0 / 0

[EJB 3.0 Development] New message: "Re: Externalizing Scope: Resolving EJB References and Endpoints"

by Pete Muir

JBoss development, A new message was posted in the thread "Externalizing Scope: Resolving EJB References and Endpoints": http://community.jboss.org/message/523724#523724 Author : Pete Muir Profile : http://community.jboss.org/people/petemuir Message: -------------------------------------------------------------- BTW the reason we need to hold this reference beyond creation is to allow us to request the EJB is removed at a later date. CDI can do this because it actively manages the lifecycle of a bean - for example a session scoped bean has a well defined point at which it is destroyed (when the http session ends) - and needs to request that the EJB container removes the EJB. As the session is a passivating scope, and can be replicated, we also need to hold this reference across passivation. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/523724#523724

14 years, 2 months

1
0
0 / 0

[EJB 3.0 Development] New message: "Re: Externalizing Scope: Resolving EJB References and Endpoints"

by Andrew Rubinger

JBoss development, A new message was posted in the thread "Externalizing Scope: Resolving EJB References and Endpoints": http://community.jboss.org/message/523722#523722 Author : Andrew Rubinger Profile : http://community.jboss.org/people/ALRubinger Message: -------------------------------------------------------------- How to Home Interfaces give Weld a hook to the Container/Endpoint which is safely replicable in a cluster? S, ALR -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/523722#523722

14 years, 2 months

1
0
0 / 0

[JCA Development] New message: "Re: Management of configuration properties inside ra.xml"

by Vicky Kak

JBoss development, A new message was posted in the thread "Management of configuration properties inside ra.xml": http://community.jboss.org/message/523719#523719 Author : Vicky Kak Profile : http://community.jboss.org/people/vickyk Message: -------------------------------------------------------------- Did you manage to get things working? -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/523719#523719

14 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums February 2010