[
http://issues.ops4j.org/browse/PAXURL-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11990#action_11990
]
Roman Roelofsen commented on PAXURL-34:
---------------------------------------
Sure, this would be helpful...
In case of WAR files this was "easily" (at least compared to EJB) accomplished
by using the pax-web and the Jetty HTTP server. Jetty implements the full
Servlet spec and provides this functionality via a rich API.
But EAR files and EJBs are a totally different beast. You will not only need
JTA but also JNDI, JPA, JAX-WS, etc. EJBs also imply a certain thread behavior.
Before we can talk about supporting this in PAX URL, we need the
Jetty-equivalent for EJBs. I guess the best shot here is currently easybeans
but I haven't used it though... Also I am not sure which role PAX URL would
play here if the deployment unit is already an EJB and an EJB container is
already available.
> Supporting of .EAR for Java EE Applications
> -------------------------------------------
>
> Key: PAXURL-34
> URL: http://issues.ops4j.org/browse/PAXURL-34
> Project: Pax URL
> Issue Type: New Feature
> Reporter: Miroslav Nachev
> Assignee: Alin Dreghiciu
>
> It will be very helpful if one existing Java EE Application can be started in
> OSGi environment. The best way will be if one EJB can be represented as one
> OSGi Bundle and JTA is supported.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
