No, I haven't.  I'll have to look into how to do that.

Joe

Alasdair Nottingham wrote:
Have you tried setting the system packages extra to export javax.transaction and javax.transaction.xa at version 1.1?

Alasdair

On 4 Mar 2010, at 22:46, Joe Bohn <[email protected]> wrote:

Thank you Alasdair.  Yep, that does the trick.


Now I just have to get past the transaction issues.

I can get the transaction manager to start correctly by including the geronimo-jta_1.1_spec-1.1.1.jar in the Xbootclasspath but something still isn't right when I actually attempt to use a container managed transaction via the blueprint declarative transaction support. It seems that something isn't being registered correctly.

I get this error:
Caused by: javax.persistence.TransactionRequiredException: No JTA transaction services implementation is currently available. As a result the JPA container cannot integrate with JTA transactions. at org.apache.aries.jpa.container.context.transaction.impl.JTAPersistenceContextRegistry.getCurrentPersistenceContext(JTAPersistenceContextRegistry.java:96) at org.apache.aries.jpa.container.context.transaction.impl.JTAEntityManager.getPersistenceContext(JTAEntityManager.java:73) at org.apache.aries.jpa.container.context.transaction.impl.JTAEntityManager.persist(JTAEntityManager.java:220) at org.apache.aries.samples.ariestrader.persist.jpa.TradeJpaCm.createQuote(TradeJpaCm.java:449)
       ... 31 more
java.lang.RuntimeException: javax.persistence.TransactionRequiredException: No JTA transaction services implementation is currently available. As a result the JPA container cannot integrate with JTA transactions. at org.apache.aries.samples.ariestrader.persist.jpa.TradeJpaCm.createQuote(TradeJpaCm.java:458)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


Joe


Alasdair Nottingham wrote:
Hi,
I've committed a fix that should solve this problem.
Alasdair
On 4 March 2010 18:33, Alasdair Nottingham <[email protected]> wrote:
Hi,

I didn't think you were terse (well maybe for 1 second :), I just
wanted to make sure in the context of the email you sent that people
were aware I was looking into it.

Thanks
Alasdair

On 4 March 2010 18:06, Joe Bohn <[email protected]> wrote:
Hi Alasdair,

Thanks. I'm sorry if my note sounded a little terse and you thought I was complaining about the jndi issue (or even the transaction issue for that
matter).  That was not what I intended to convey.

My note was more driven by confusion related to transaction support. I just
confirmed (at least as far as I understand how to do) that AriesTrader
transaction support was working prior to the recent changes. However, I've heard comments that it should not have been working. And so I was trying to get a better understanding of why it was working before and if the recent
changes (which now require adding the geronimo jta spec to the
Xbootclasspath) were really necessary.

The jndi change was really just mentioned because you can't get far enough in AriesTrader to see transaction working unless you also revert the jndi change locally which will let you get far enough to see it working with the
former transaction code.


Joe



Alasdair Nottingham wrote:
Joe,

I'm going to look at why the JNDI failure is occurring this evening.

Alasdair

On 4 March 2010 17:50, Joe Bohn <[email protected]> wrote:
.... but not anymore with the recent changes in jndi and transaction.

I understand that the transaction changes were necessitated by the belief
that they were necessary.  However, I can confirm that declarative
transactions were working in AriesTrader before the recent changes. So
I'm
a bit confused if these changes were really necessary.

If you want to see this running for yourself you must do the following:

1) Revert the jndi changes that are causing the lookup to fail for
TradeServicesManager ( rev. 918571 and 917809)
2) Revert the Transaction Manager changes that are causing the
transaction.manager bundle to fail to start (rev. 918977).

Once you revert those 3 changes locally you can get AriesTrader working
again.


--
Joe




--
Joe



--
Alasdair Nottingham
[email protected]



--
Joe



--
Joe

Reply via email to