Debug EJB3 component
by Roman Kasianenko
Hello, everybody.
I am developing web-application that needs to access EJB3 component that
is deployed to JBoss AS.
This bean uses few 3rd party libs, that are packed into the same jar as
bean is, under "/lib" path.
In the JBoss console i see message:
[EJBContainer] STARTED EJB: nuntia.ejb.CRFacadeBean ejbName: CRFacadeBean
So, it looks like bean is deployed successfully.
From web-app (from struts action actually) i try to get bean instance
as follows:
Properties properties = new Properties();
properties.setProperty("java.naming.factory.initial",
"org.jnp.interfaces.NamingContextFactory");
properties.setProperty("java.naming.factory.url.pkgs",
"org.jboss.naming:org.jnp.interfaces");
properties.setProperty("java.naming.provider.url", "localhost:1099");
CRFacade crFacade = (CRFacade) new
InitialContext(properties).lookup("CRFacadeBean/local");
Here, CRFacade is @Local interface, and CRFacadeBean is an
implementation class.
Instance seems to be successfully created (i see that while debugging),
but as soon as first of its methods is called, i got an
InvocationTargetException:
[PropertiesFactoryBean] Loading properties file from class path resource
[alfresco/domain/hibernate-cfg.properties]
So it seems that there's some problem either in bean or in the way how
libs are loaded (PropertiesFactoryBean class is actually part of
spring.jar that is one of the libs i'm bundling with my bean's jar).
Note, that class does his job well when used standalone (not as bean).
So, i would like to debug bean to find out what the reason of failure
is. I'm using Eclipse and JBossIDE, my project is configured properly,
sources are attached to the classes, and i can navigate throuhg them,
but still, i can't catch breakpoint that is set in the body of
constructor of my bean, so it seems like debugging is not working this
way...
And, finally, questions:
1) do i pack/deploy my EJB3 component correctly?
2) is there any way to debug deployed EJB3 component?
P.S. I am new to EJB3, so sorry for dumb questions (if any) ;)
Thanks in advance!
Cheers,
R. Kasianenko
16 years, 8 months
Webservice integration broken again!
by Adrian
I think we should ban the entire webservices team from the appserver
project and repository.jboss.com until they learn that breaking the
build every week is not acceptable! :-)
thirdparty:
[unzip]
Expanding: /home/ejort/jboss-head/thirdparty/jboss/jbossws/lib/jbossws50-deployer.zip into /home/ejort/jboss-head/build/output/jboss-5.0.0.Beta2/server/all/deployers/jbossws.deployer
[unjar]
Expanding: /home/ejort/jboss-head/thirdparty/jboss/jbossws/lib/jbossws50.sar into /home/ejort/jboss-head/build/output/jboss-5.0.0.Beta2/server/all/deploy/jbossws.sar
[unjar]
Expanding: /home/ejort/jboss-head/thirdparty/jboss/jbossws/lib/jbossws-client.jar into /home/ejort/jboss-head/build/output/jboss-5.0.0.Beta2/bin
BUILD FAILED
/home/ejort/jboss-head/build/build.xml:306: The following error occurred
while executing this line:
/home/ejort/jboss-head/build/build.xml:666: The following error occurred
while executing this line:
/home/ejort/jboss-head/build/build-distr.xml:1843: Error while
expanding /home/ejort/jboss-head/thirdparty/jboss/jbossws/lib/jbossws-client.jar
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
16 years, 8 months
RE: [jboss-dev] Re: Plan for JBossAS 4.2.0.CR1 - Your Help isNeeded
by Adrian
Get off my thread with your Dillonisms. :-)
Be
On Mon, 2007-01-29 at 07:43 -0600, Sacha Labourey wrote:
> Also, I think we should re-organize the deploy folder, possibly with
> something in that vein:
>
>
> Deploy
> /system
> /TX
> /jbossjca-service.xml
> /jboss-local-jdbc.rar
> /jboss-xa-jdbc.rar
> /JMS
> (like it is today)
> /management
> (like it is today)
> /Timers
> /ejb2-timer-service.xml
> /quartz-ra.rar
> /schedule-manager-service.xml
> /scheduler-service.xml
> /JBossWeb
> /JBossWS
> /Remoting
> /http-invoker.war
> /jmx-remoting.sar
> /apps
> /jmx-console.war
> /web-console.war
>
> Etc.
>
>
> The current deploy folder is such a mess...
>
> BTW, we could argue we need the same thing for the lib folder i.e.
> lib/system lib/apps (or lib/user)
>
> > -----Original Message-----
> > From: Adrian Brock
> > Sent: lundi, 29. janvier 2007 14:37
> > To: JBoss.org development list
> > Cc: Dimitris Andreadis; jboss-as(a)redhat.com; The Core
> > Subject: Re: [jboss-dev] Re: Plan for JBossAS 4.2.0.CR1 -
> > Your Help isNeeded
> >
> > Here's another suggested change to the default configurations for JCA:
> > http://www.jboss.com/index.html?module=bb&op=viewtopic&p=40077
> 77#4007777
> >
> > We should enable all the useful features that are available
> > by default rather than just having a basic config and requiring
> > users to figure out how to configure them.
> >
> > The most important is the transaction query timeout
> > for sql queries
> >
> > <set-tx-query-timeout/>
> >
> > Which will avoid the FAQs about hanging database connections
> > providing the sql driver supports it. :-)
> >
> > > On Wed, 2007-01-24 at 10:15 -0600, Dimitris Andreadis wrote:
> > > > Hi folks,
> > > >
> > > > We are shooting for Feb/26th for JBossAS 4.2.0.CR1, which
> > is only 4.5
> > > > weeks away. As a consequence:
> >
> > --
> > xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Adrian Brock
> > Chief Scientist
> > JBoss, a division of Red Hat
> > xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >
> >
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
16 years, 8 months
RE: [jboss-dev] Re: Plan for JBossAS 4.2.0.CR1 - Your Help isNeeded
by Jason T. Greene
I have seen users ask for this before. Except they usually ask for an
empty deploy folder that only contains *their* deployments.
On Mon, 2007-01-29 at 07:43 -0600, Sacha Labourey wrote:
> Also, I think we should re-organize the deploy folder, possibly with
> something in that vein:
>
>
> Deploy
> /system
> /TX
> /jbossjca-service.xml
> /jboss-local-jdbc.rar
> /jboss-xa-jdbc.rar
> /JMS
> (like it is today)
> /management
> (like it is today)
> /Timers
> /ejb2-timer-service.xml
> /quartz-ra.rar
> /schedule-manager-service.xml
> /scheduler-service.xml
> /JBossWeb
> /JBossWS
> /Remoting
> /http-invoker.war
> /jmx-remoting.sar
> /apps
> /jmx-console.war
> /web-console.war
>
> Etc.
>
>
> The current deploy folder is such a mess...
>
> BTW, we could argue we need the same thing for the lib folder i.e.
> lib/system lib/apps (or lib/user)
>
> > -----Original Message-----
> > From: Adrian Brock
> > Sent: lundi, 29. janvier 2007 14:37
> > To: JBoss.org development list
> > Cc: Dimitris Andreadis; jboss-as(a)redhat.com; The Core
> > Subject: Re: [jboss-dev] Re: Plan for JBossAS 4.2.0.CR1 -
> > Your Help isNeeded
> >
> > Here's another suggested change to the default configurations for JCA:
> > http://www.jboss.com/index.html?module=bb&op=viewtopic&p=40077
> 77#4007777
> >
> > We should enable all the useful features that are available
> > by default rather than just having a basic config and requiring
> > users to figure out how to configure them.
> >
> > The most important is the transaction query timeout
> > for sql queries
> >
> > <set-tx-query-timeout/>
> >
> > Which will avoid the FAQs about hanging database connections
> > providing the sql driver supports it. :-)
> >
> > > On Wed, 2007-01-24 at 10:15 -0600, Dimitris Andreadis wrote:
> > > > Hi folks,
> > > >
> > > > We are shooting for Feb/26th for JBossAS 4.2.0.CR1, which
> > is only 4.5
> > > > weeks away. As a consequence:
> >
> > --
> > xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Adrian Brock
> > Chief Scientist
> > JBoss, a division of Red Hat
> > xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >
> >
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Jason T. Greene
Senior Software Engineer
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
16 years, 8 months