Hi All,
I am upgrading an application from Karaf 3.0.3 to 4.0.1 and facing an
strange JPA related issue.
As it mentioned in the email title, the JPA related bundle is waiting for
JPA namespace handler.
I can see that "Aries JPA Blueprint" version 2.1.0 is started successfully
but it is registeri
Hi Mohammad,
it sounds like a bug in Aries JPA Blueprint.
I gonna create the Jira and fix that.
Regards
JB
On 09/02/2015 12:19 PM, Mohammad Shamsi wrote:
Hi All,
I am upgrading an application from Karaf 3.0.3 to 4.0.1 and facing an
strange JPA related issue.
As it mentioned in the email tit
Hi JB,
May I have the issue number, if it is already created?
Meanwhile is there any workaround for this problem? (other than downgrading
Aries version)
Thanks,
Mohammad Shamsi
On Wed, 2 Sep 2015 at 13:18 Jean-Baptiste Onofré wrote:
> Hi Mohammad,
>
> it sounds like a bug in Aries JPA Bluep
Mohammad, things changed slightly in karaf 4.
Check this page: http://aries.apache.org/modules/jpaproject.html.
--
View this message in context:
http://karaf.922171.n3.nabble.com/Bundle-is-waiting-for-namespace-handlers-http-aries-apache-org-xmlns-jpa-v1-0-0-tp4042275p4042371.html
Sent from t
Hi Ellirael,
Thanks for the hint.
Using the new approach, annotation based EntityManager, the startup was
successful.
Cheers,
On Mon, 7 Sep 2015 at 12:13 ellirael wrote:
> Mohammad, things changed slightly in karaf 4.
>
> Check this page: http://aries.apache.org/modules/jpaproject.html.
>
>
>
Does this mean that now it is *mandatory *to define the persistence unit per
annotation, and it is no longer possible to define it in the blueprint file?
Is this a bug of a feature? Or, in other words, does it make sense to open a
Jira for Aries if I want to get the blueprint.xml mechanism back (t
Hi Jochen,
yes this is correct. Aries JPA 2 only uses the annotations.
In addition I am currently working on a new Aries Transaction 3 that
will then also only use the jta 1.2 annotations.
This means that the whole JPA/JTA setup will then be based on the
standard set of annotations. The advan
does that imply you only can use the annotations, and rely on a generated
blueprint.xml?
2015-09-16 11:05 GMT+02:00 Christian Schneider :
> Hi Jochen,
>
> yes this is correct. Aries JPA 2 only uses the annotations.
> In addition I am currently working on a new Aries Transaction 3 that will
> the
It sounds good, and it's what I leverage in karaf-boot (with the @jpa
annotation which creates the persistence.xml for you).
Regards
JB
On 09/16/2015 11:05 AM, Christian Schneider wrote:
Hi Jochen,
yes this is correct. Aries JPA 2 only uses the annotations.
In addition I am currently working
The @PersistenceContext, @PersistenceUnit and @Transactional annotations
are evaluated at runtime. So they work with hand written xml as well as
with the
generated one.
The CDI annotions are evaluated at compile time to create the blueprint
xml using the maven-blueprint-plugin. So to use these
Hello Christian,
ok, then my expectation was wrong, that the mechanisms to use annotations or
definitions in xml always exist in parallel, and one can use the one or the
other.
So if up to now one decided to use the blueprint.xml file since annotations
were still in experimental state, it is not
It could make sense to keep "backward" compatibility with both
annotation and XML elements.
I will chat with Christian about that.
Regards
JB
On 09/16/2015 04:50 PM, jochenw wrote:
Hello Christian,
ok, then my expectation was wrong, that the mechanisms to use annotations or
definitions in xm
Your are not wrong Aries JPA 2 and Aries transaction 3 will be
annotation only.
You will only have the enable elements in the xml. This was announced
quite a while ago on the dev list.
In fact the disruptive nature is why both are major versions.
The JPA and JTA annotations are not related in a
Ok, thanks, Christian, for the detailed explanation. I got the idea. Looks
fair enough to me to stay with the 1.x version for keeping the xml
definitions, and then to move towards annotations with the new versions.
You might think about adding your explanation to the Aries docu. It's not so
easy t
I wasn't aware of this fact, and I find it rather disturbing.
Till now I was under the impression that the maven-blueprint-plugin was
just another complementary way of creating the blueprint.xml
Not a replacement. Especially since those annotations are just build-time
and not runtime annotations an
Slightly different aspect (don't know whether I should open a new thread, but
it is related to this one): with Karaf 4.0.1, I tried to use JPA 1.0.4
instead of 2.1.0 - to start with, since switching to annotations will take
some time.
However, the transaction feature 1.3.0 seems not to work with J
It is the plan to also provide jpa and jta 1.x for karaf 4.
The problem here is that I forgot to also add the coordinator bundle to
the transaction feature. When it is used together with jpa 2 the problem
does not show so I missed this.
Can you open an issue for it?
Christian
On 17.09.2015 0
I have done some tests. The problem is indeed the coordinator bundle.
Normally there should be an error message when installing the
transaction feature as transaction.blueprint needs the coordinator. I
think this is a bug in the feature service. Probably this is the reason
that I did not spot t
Yes, this works, I have already tried this. I filed a Jira anyways:
KARAF-3998.
Best Regards,
Jochen
cschneider wrote
> I have done some tests. The problem is indeed the coordinator bundle.
> Normally there should be an error message when installing the
> transaction feature as transaction.bl
19 matches
Mail list logo
