× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



My understanding is that the WebSphere annotation processor will
only process injection requests for types defined in the Java EE
spec (Servlet, Listener, etc). To process injection annotations for
JSF, apparently an injection provider can be written for Mojarra
to handle those requests. We're not looking at EJB yet (probably
not until Java EE 6 -- EJB 3.1 drops the complexity level to just
about POJO), so I haven't really spent much time on it. Someone
posted on the Mojarra forum the other day about an injection
provider.
________________________________________
From: web400-bounces@xxxxxxxxxxxx [web400-bounces@xxxxxxxxxxxx] On Behalf Of James Perkins [jrperkinsjr@xxxxxxxxx]
Sent: Wednesday, April 21, 2010 4:35 PM
To: Java Programming on and around the iSeries / AS400; Web Enabling the AS400 / iSeries
Subject: [WEB400] Container Mange Persistence

I'll apologize up front for the cross post, but I'm not sure which
list would be most appropriate for this question. It could be a Java
problem, or a problem/set-up issue with WAS.

The environment:
I have WebSphere Application Server 6.1 installed with the EJB 3.0
feature pack on an IBM i at 5.4. I have a enterprise application (EAR)
that contains a web application (WAR), an EJB client, the EJB 3.0
implementation and a JPA library. I'm packing/building this
application with maven.

The problem:
Everything installs with no errors. I have a utility Java class that
looks up the EJB because it appears you can't inject an EJB into a JSF
managed bean with the feature pack. The issue is the EJB has an
EntityManager that should be getting injected, but it's not. I printed
a listing of the context "java:comp/env" where the persistence context
should be stored and nothing is there. I have worked around this by
managing the entities myself, but I don't want to leave it like this
if I don't have to.

So, my question is has anybody else had any issues similar to this? I
guess also, has anybody successfully deployed a JPA application on WAS
6.1 that does container managed persistence?

Thanks in advance,
--
James R. Perkins
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.