Paul Spencer,
Thanks for your good help and detailed description, samples.
As you say, NO Real Value For Jarkarta REST implementation is .
I'm developing new REST Development Standards.
So I'd like to reduce additional work to change in the future.
It will be good references For New Standards.
Jeongpil An,
For what it is worth, below is a simplified and sanitized version of my REST
environment under Karaf 4.4.3. Note the REST endpoint and the API
implementation are in different bundles, as I used the same REST application
for many bundles.
Although thus is not a Jararta
Hello again !
After reading the code of pax-transx-tm-geronimo I think the issue
perhaps comes from the detected presence of the spring-tx exported
packages when the TM is instantiated : the code seems to protect
itself against missing classes to provide a PTM only when the
spring-tx classes are
Hello.
I'm going to check my XA configuration, but our tests seem to confirm
it works : our JMS and JDBC configurations are all based on factories
with pax-XXX-config, with pooling and XA features, and we have no
custom blueprints to set them...
In parallel I've found some interesting evidence
Hi Ephemeris,
First thing to notice, are you aiming to use XA transactions with JMS / JDBC?
As far as I know only the pax jdbc aries pool and transactionmanager support
this.
The following setup is for Karaf 4.2.6 / ActiveMQ 5.15.9 / Camel 2.24.1 and is
proven in years of production.
Basic
Hello Maurice.
I attach a description of our features stack, starting with low level
resource management, then framework and common features, and finally
an application feature example.
The transaction feature is pulled by a common "foo-base", and used in
some of our application bundles that
Thanks for your good comments, Grzegorz Grzybek.
Using your comments, I'll try again and post the result.
Regards
Jeongpil An (call ajp)
2023년 4월 12일 (수) 오후 3:01, Grzegorz Grzybek 님이 작성:
> Hello
>
> Karaf 4.4.3 uses Pax Web 8 and Pax Web, while not containing any Karaf
> features related to
Hello
Karaf 4.4.3 uses Pax Web 8 and Pax Web, while not containing any Karaf
features related to JaxRS, provides integration tests using aries-jaxrs
(OSGi CMPN specification implementation).
The Jetty-based test:
