[jboss-user] [JCA/JBoss] - Re: XATransaction resource enlisted as LocalTransaction

2007-11-25 Thread nlmarco
I think we found the solution ourselves: Our *-ds.xml files (e.g. this one) were missing the element: After adding it, it looks now much better :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107595#4107595 Reply to the post : http://www.jboss.com/index

[jboss-user] [JCA/JBoss] - XATransaction resource enlisted as LocalTransaction

2007-11-25 Thread nlmarco
Hello *, I've a problem with a RA: Even though the ra.xml says XATransaction my resource seems to be handled as if it was only local-tx, which leads to exceptions: 2007-11-24 22:01:18,165 WARN [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.transaction.arjunacore.enlistst

[jboss-user] [Security & JAAS/JBoss] - Re: stick authentication info to EJB handle?

2007-08-01 Thread nlmarco
Yabbadabbado!!! It's working again!!! My client-interceptor checks now, whether the returned Proxy is already tagged with other user-data. If yes, I clone it via serialization and deserialization. The user thus gets a clone which is tagged correctly and everything seems to work fine. But this

[jboss-user] [Security & JAAS/JBoss] - Re: stick authentication info to EJB handle?

2007-08-01 Thread nlmarco
After some further investigation, I saw sth. very interesting: | EjbOfPartnerHome home1 = EjbOfPartnerUtil.getHome(getInitCtxProps(partner1)); | EjbOfPartner ejbOfPartner1 = home1.create(); | EjbOfPartnerHome home2 = EjbOfPartnerUtil.getHome(getInitCtxProps(partner2)); | EjbOfPartner ejb

[jboss-user] [Security & JAAS/JBoss] - stick authentication info to EJB handle?

2007-07-30 Thread nlmarco
Hello *, in our use case, quite a few EJB methods (mostly of stateless session beans) need to communicate with many EJBs on different servers (some on the same server, but then mostly still as different user). Therefore, we want to stick the authentication info to the EJBs, making code like thi

[jboss-user] [EJB 3.0] - Re: Create timer -

2007-06-16 Thread nlmarco
Hello wolfc, thanks a lot for your quick and very helpful reply!!! It works! I know that it's bad to turn on this option, but I need it for a development system (when we'll go productive, there will be solely xa-resources). For other readers browsing this thread, here a short summary: I edited

[jboss-user] [EJB 3.0] - Re: Create timer -

2007-06-13 Thread nlmarco
"wolfc" wrote : [...] It is possible to set a property in the transaction service to allow multiple one phase resources, but that could lead to transaction problems. [...] Hello wolfc, I upgraded from 4.0.4.GA to 4.2.0.GA and I now have the same problem. After having read your response, I start

[jboss-user] [JBoss jBPM] - Re: Fork + Join

2006-12-18 Thread nlmarco
Hello Tom, thanks a lot for your quick reply! I built a test case and hope you can either tell me what I'm doing wrong or fix the bug in jBPM ;-) This is my test process definition: http://www.nightlabs.de/~marco/jbpm/2006-12-18.00/processimage.jpg Here is a little test application (incl. the

[jboss-user] [JBoss jBPM] - Fork + Join

2006-12-11 Thread nlmarco
Hello *, I've got a question about Fork+Join behaviour: When the root token enters the Fork, it creates a new child token for every outgoing transition. That's exactly what I expected according to the docs and my intuition. When these child tokens enter the Join, however, they don't end there,

[jboss-user] [Messaging, JMS & JBossMQ] - Re: Transactional sending of a message with XA queue?

2006-08-01 Thread nlmarco
Hello genman, thanks a lot for the clarification! After some further research, I stumbled over http://www.odi.ch/weblog/posting.php?posting=210 Your hint and that document in conjunction with http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQDB solved my problem. Now, it seems to be worki

[jboss-user] [Messaging, JMS & JBossMQ] - Transactional sending of a message with XA queue?

2006-08-01 Thread nlmarco
Hello *, I would like to achieve the following behaviour: A session bean's method is called within a transaction and sends a message to a queue. The message should, however, not be delivered before the transaction is complete, because otherwise the data in my database is not yet visible to my