WAS is not an option, as we run an embedded approach where we may have
several instances each serving their own purpose and port. This is to
each instance to inherit things from the launching process.
It doesn't inject? That is interesting, as the injection mechanism is
managed by JSF so it should be available in JSF pages. Perhaps WAS isn't
fully Servlet 2.5 API compliant?
Jetty runs quite nicely in PASE. You essentially just need to start QSH,
to the jetty-X.Y folder and run "java -jar start.jar". We need a custom
launcher to pick up the configuration and pass it to Jetty, so I looked up
on the documentation for embedding Jetty, and got it working quite nicely,
but there is a lot of things you need to figure out yourself. We were
specially interested in having a central slf4j configuration which required
some tinkering with classloaders, as well as JNDI for centralized, pooled
and preconfigured org.ibm.access.AS400 objects, which has worked reasonably
We would like to migrate from a Servlet 2.5 API baseline to a Java EE 6 Web
profile baseline, and the way to do that these days is to embed Glassfish,
perhaps even in an OSGi container to emulate the library list.
Hence my interest in getting this to run natively.
This is the Java Programming on and around the IBM i (JAVA400-L) mailing
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.