[
https://issues.apache.org/jira/browse/TOMEE-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147908#comment-14147908
]
jieryn commented on TOMEE-1361:
-------------------------------
Frankly speaking, the tricks employed to work around OpenJPA deficiencies cause
a lot of headaches for my team that already had existing dependencies on
org.apache.openjpa:openjpa and then to have to work around
org.apache.openejb.patch:openjpa is a pain in Maven. Then our use of Arquillian
with TomEE Embedded mode is generally met with disgust or told not to use it at
all by TomEE development. It's a huge amount of work over here to migrate with
all these land mines, and generally out of date/broken documentation on top of
everything else. Getting the 20-40 hours to do the migration and document all
the breakage and rule out some likely user errors (probably caused by lack of
doc) and create projects which demonstrate the problem external to my projects
.... it's huge.
> tomee-m-p automatic reload leaves previously deployed @Path JAX-RS resources
> undeployed
> ---------------------------------------------------------------------------------------
>
> Key: TOMEE-1361
> URL: https://issues.apache.org/jira/browse/TOMEE-1361
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Maven Plugin
> Reporter: jieryn
>
> I am running a web application via tomee:run:1.6.0.2 and have a dependency on
> another module packaging=war which contains @Path JAX-RS resouces. When I
> make a change to the current module's index.html page, e.g., the overlayed
> JAX-RS resources are not available after tomee automatically reloads itself.
> This is a huge problem for developer productivity.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
