[JBoss Seam] - "could not discover transaction" despite transaction-managem
by cba2
I have set <core:init transaction-management-enabled="false"/> in components.xml but I still get errors like the following:
10:51:04,521 ERROR [Contexts] could not discover transaction status
Should I disable seam transaction management somewhere else as well or is this rather a (minor) Seam bug?
>From Contexts.java (package org.jboss.seam.contexts):
| boolean transactionActive = false;
| try
| {
| transactionActive = Transaction.instance().isActive();
| }
| catch (Exception e)
| {
| log.error("could not discover transaction status");
| }
| if (transactionActive)
| {
| //in calls to MDBs and remote calls to SBs, the
| //transaction doesn't commit until after contexts
| //are destroyed, so pre-emptively flush here:
| getBusinessProcessContext().flush();
| }
|
I suspect Transaction.instance() is just null (because there is simply no transaction) which triggers an NPE. But since the logged error includes no stack trace I cannot be sure...
FYI: I use Seam2.0.0.BETA1 on plain Tomcat 5.5. I use spring for the whole persistence layer which is also why I would like to completely disable Seam transaction management.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081604#4081604
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081604
18 years, 7 months
[JBossWS] - how to return an empty http response instead of soapmessage
by kukeltje
Hi,
I'm implementing an ebMS 2.0 Message Service Handler with JBossWS 2.0.0 and related frameworks. According to the ebMS 2.0 spec, In all cases a soapmessage is received and in many cases a soapmessage has to be returned. Therefor I choose the 'message' way of communicating. However in some cases an empty response (no soapmessage, just an http 200 ok) has to be returned. First thing I tried was returning 'null' hoping that would do the trick. Unfortunately it didn't.
I can do several things now
- do not use the 'message' way but start using the source
- try something with a soaphandler by e.g. setting the messagecontext to null
- return a basic soapmessage and write a servletfilter that deletes this if it encounters it
The first option would result in to much coding (imo), the second might not work and the last one doesn't feel 'right'
Does anybody have a different suggestion?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081601#4081601
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081601
18 years, 7 months