I'm curious if there are any hooks into the handling of runtime exceptions that
propagate up through an EJB. The default behavior is to rollback a transaction
and log the error. What I would like to be able to do is add my own custom
logging here to add additional information on errors.
Let
Hi, can you or anyone else elaborate more on what causes this or where to look
to fix this? Getting it with same configuration as original poster.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047682#4047682
Reply to the post :
http://www.jboss.com/index.h
Thanks for the help guys. Turns out it was because I was using the jbossws
that was installed with jboss-4.0.5.GA, which i believe is version 1.0.3. I
guess jaxb bindings were not supported until a later version, because I
installed 1.2.1.GA and everything worked as expected.
However, I have
Thanks for writing back.
That's actually the first technique I tried which also did not seem to work.
Here is an example of a my web service bean:
| @Stateless(name="VerificationWs")
| @WebService(
| name="VerificationWs",
| targetNamespace = VerificationWsBean.DEFAULT_NS)
|
Hi,
I just upgraded to using jax-ws with my ejb 3.0 beans, and its working fine.
The classes used by my web service are being mapped to a shema with a
targetNamespace reflected by their package name. Because I'm trying to
recreate an exact copy of my old web services I would like to define the
Please, all i need to know from anyone who is successfully using ehcache with
ejb 3.0 right now, where did you put the ehcache.jar file, and where also did
you put the ehcache.xml file?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4044710#4044710
Reply to
Woops - technically i made a mistake. I think it was actually I who put
ehcache.jar into the server/default/lib folder; but that doesn't change the
basis of the classloader issue I am having.
I put the ehcache jar into that directory because that is where the hibernate
jars are, and if i put
Hi, i just upgraded to 4.0.5.GA with ejb3 support, and I deployed my ear file
with ehcache.xml in the ear root. However i get the error that ehcache.xml is
not found and that it is defaulting to
/server/default/lib/ehcache-1.2.jar/ehcache-failsafe.xml.
So it looks like ehcache is now bundled