[jira] [Commented] (TOMEE-1720) tomee as a maven dependency
[
https://issues.apache.org/jira/browse/TOMEE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171131#comment-15171131
]
Matthew Broadhead commented on TOMEE-1720:
--
how do i specify plus (or plume) in maven? i tried the following but it didn't
work. omitting the classifier works but doesn't compile. first error is
ManagedBean annotation not found
{code:xml}
org.apache.openejb
apache-tomee
1.7.3
provided
plus
{code}
> tomee as a maven dependency
> ---
>
> Key: TOMEE-1720
> URL: https://issues.apache.org/jira/browse/TOMEE-1720
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 1.7.3
>Reporter: Matthew Broadhead
>
> Currently my projects in eclipse have the TomEE server runtime include on the
> build path. this works fine but it is not very portable and upgrading
> requires changing the build path for every project rather than changing the
> version number in the pom.xml.
> Is it possible to include TomEE using Maven? I tried adding
> {code:xml}
>
> org.apache.openejb
> tomee-plume-webapp
> 1.7.3
>
> {code}
> but it gives "Missing artifact
> org.apache.openejb:tomee-plume-webapp:jar:1.7.3"
> I have tried the tomee-maven-plugin but I prefer to be able to stop and start
> the server from eclipse and also the debugger is easier to set up. Also
> eclipse starts all the projects together and integrates them. (I suppose if
> tomee-maven-plugin is capable of all this I could try it again)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TOMEE-1720) tomee as a maven dependency
[
https://issues.apache.org/jira/browse/TOMEE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171127#comment-15171127
]
Romain Manni-Bucau commented on TOMEE-1720:
---
did you try: org.apache.tomee:apache-tomee:${tomee.version}:zip:plus?
> tomee as a maven dependency
> ---
>
> Key: TOMEE-1720
> URL: https://issues.apache.org/jira/browse/TOMEE-1720
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 1.7.3
>Reporter: Matthew Broadhead
>
> Currently my projects in eclipse have the TomEE server runtime include on the
> build path. this works fine but it is not very portable and upgrading
> requires changing the build path for every project rather than changing the
> version number in the pom.xml.
> Is it possible to include TomEE using Maven? I tried adding
> {code:xml}
>
> org.apache.openejb
> tomee-plume-webapp
> 1.7.3
>
> {code}
> but it gives "Missing artifact
> org.apache.openejb:tomee-plume-webapp:jar:1.7.3"
> I have tried the tomee-maven-plugin but I prefer to be able to stop and start
> the server from eclipse and also the debugger is easier to set up. Also
> eclipse starts all the projects together and integrates them. (I suppose if
> tomee-maven-plugin is capable of all this I could try it again)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (TOMEE-1717) OpenWebBeans 1.6.3
[ https://issues.apache.org/jira/browse/TOMEE-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved TOMEE-1717. --- Resolution: Fixed > OpenWebBeans 1.6.3 > -- > > Key: TOMEE-1717 > URL: https://issues.apache.org/jira/browse/TOMEE-1717 > Project: TomEE > Issue Type: Dependency upgrade >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 7.0.0-M2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1671) Ensure Joda Time notice is added
[ https://issues.apache.org/jira/browse/TOMEE-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1671: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure Joda Time notice is added > > > Key: TOMEE-1671 > URL: https://issues.apache.org/jira/browse/TOMEE-1671 > Project: TomEE > Issue Type: Task >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht > Fix For: 1.7.4, 7.0.0-M3 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1311) Ensure full support of JSR 346 Contexts and Dependency Injection for Java EE 1.1
[ https://issues.apache.org/jira/browse/TOMEE-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1311: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure full support of JSR 346 Contexts and Dependency Injection for Java EE > 1.1 > > > Key: TOMEE-1311 > URL: https://issues.apache.org/jira/browse/TOMEE-1311 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Ensure full support of JSR 346 Contexts and Dependency Injection for Java EE > 1.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1308) Ensure full support of JSR-340 Java Servlet 3.1
[ https://issues.apache.org/jira/browse/TOMEE-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1308: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure full support of JSR-340 Java Servlet 3.1 > --- > > Key: TOMEE-1308 > URL: https://issues.apache.org/jira/browse/TOMEE-1308 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Ensure full support of JSR-340 Java Servlet 3.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1305) Ensure full support of JSR-344 JavaServer Faces 2.2
[ https://issues.apache.org/jira/browse/TOMEE-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1305: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure full support of JSR-344 JavaServer Faces 2.2 > --- > > Key: TOMEE-1305 > URL: https://issues.apache.org/jira/browse/TOMEE-1305 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Ensure full support of JSR-344 JavaServer Faces 2.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1291) Example Moviefun updated to servlet 3.1 and bootstrap 3.2.0
[ https://issues.apache.org/jira/browse/TOMEE-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1291: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Example Moviefun updated to servlet 3.1 and bootstrap 3.2.0 > --- > > Key: TOMEE-1291 > URL: https://issues.apache.org/jira/browse/TOMEE-1291 > Project: TomEE > Issue Type: Improvement >Reporter: Helio Frota >Priority: Trivial > Labels: patch > Fix For: 7.0.0, 7.0.0-M3 > > Attachments: TOMEE-1291.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1316) Ensure full support of JSR-343 Java Message Service 2.0
[ https://issues.apache.org/jira/browse/TOMEE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1316: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure full support of JSR-343 Java Message Service 2.0 > --- > > Key: TOMEE-1316 > URL: https://issues.apache.org/jira/browse/TOMEE-1316 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Ensure full support of JSR-343 Java Message Service 2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1309) Ensure full support of JSR-250 Common Annotations for Java Platform 1.1
[ https://issues.apache.org/jira/browse/TOMEE-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1309: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure full support of JSR-250 Common Annotations for Java Platform 1.1 > --- > > Key: TOMEE-1309 > URL: https://issues.apache.org/jira/browse/TOMEE-1309 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Ensure full support of JSR-250 Common Annotations for Java Platform 1.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1286) Intermittent test failure org.apache.openejb.itest.legacy.LegacyClientTest
[ https://issues.apache.org/jira/browse/TOMEE-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1286: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Intermittent test failure org.apache.openejb.itest.legacy.LegacyClientTest > -- > > Key: TOMEE-1286 > URL: https://issues.apache.org/jira/browse/TOMEE-1286 > Project: TomEE > Issue Type: Task >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Intermittent test failure org.apache.openejb.itest.legacy.LegacyClientTest -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1313) Ensure full support of JSR-322 Java EE Connector Architecture 1.7
[ https://issues.apache.org/jira/browse/TOMEE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1313: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure full support of JSR-322 Java EE Connector Architecture 1.7 > - > > Key: TOMEE-1313 > URL: https://issues.apache.org/jira/browse/TOMEE-1313 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Ensure full support of JSR-322 Java EE Connector Architecture 1.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1412) Extra unversioned context displayed when using parallel deployment
[ https://issues.apache.org/jira/browse/TOMEE-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1412: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Extra unversioned context displayed when using parallel deployment > -- > > Key: TOMEE-1412 > URL: https://issues.apache.org/jira/browse/TOMEE-1412 > Project: TomEE > Issue Type: Test >Affects Versions: 1.7.1 > Environment: Amazon Linux, latest version > LMDE, latest version > Java 7 update 67 >Reporter: Felipe Jaekel >Priority: Minor > Labels: test > Fix For: 1.7.4, 7.0.0-M3 > > > When using parallel deployment, TomEE 1.7.1 displays an additional > unversioned context in manager and webaccess applications. Another detail is > that on manager the undeploy option is disabled for this unversioned context. > This doesn't happen on a regular Tomcat 7.0.55. > I haven't found any actual problems, but as i'm not using TomEE in production > yet, my tests were limited, so I would appreciate some investigation if this > can impact on session routing somehow. > Sample: > https://dl.dropboxusercontent.com/u/66737052/mavenproject%23%2320140924-1600.war > https://dl.dropboxusercontent.com/u/66737052/mavenproject%23%2320140924-1615.war > Thanks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1287) Intermittent test failure org.apache.openejb.server.ssh.SSHServerTest
[ https://issues.apache.org/jira/browse/TOMEE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1287: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Intermittent test failure org.apache.openejb.server.ssh.SSHServerTest > - > > Key: TOMEE-1287 > URL: https://issues.apache.org/jira/browse/TOMEE-1287 > Project: TomEE > Issue Type: Task >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Intermittent test failure org.apache.openejb.server.ssh.SSHServerTest -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1662) Ensure dangling JMS connections are closed on shutdown
[ https://issues.apache.org/jira/browse/TOMEE-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1662: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure dangling JMS connections are closed on shutdown > -- > > Key: TOMEE-1662 > URL: https://issues.apache.org/jira/browse/TOMEE-1662 > Project: TomEE > Issue Type: Improvement >Affects Versions: 7.0.0, 1.7.2 > Environment: NA >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht > Fix For: 1.7.4, 7.0.0-M3 > > Original Estimate: 4h > Remaining Estimate: 4h > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1318) Drop or deprecate EJB Entity Beans Support
[ https://issues.apache.org/jira/browse/TOMEE-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1318: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Drop or deprecate EJB Entity Beans Support > -- > > Key: TOMEE-1318 > URL: https://issues.apache.org/jira/browse/TOMEE-1318 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Drop or deprecate EJB Entity Beans Support -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1304) Ensure full support of JSR-245 JavaServer Pages 2.2
[ https://issues.apache.org/jira/browse/TOMEE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1304: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure full support of JSR-245 JavaServer Pages 2.2 > --- > > Key: TOMEE-1304 > URL: https://issues.apache.org/jira/browse/TOMEE-1304 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Ensure full support of JSR-245 JavaServer Pages 2.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1465) org.apache.openejb.util.PropertyPlaceHolderHelper.PropertiesLookup caches properties
[
https://issues.apache.org/jira/browse/TOMEE-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romain Manni-Bucau updated TOMEE-1465:
--
Fix Version/s: (was: 7.0.0-M2)
7.0.0-M3
> org.apache.openejb.util.PropertyPlaceHolderHelper.PropertiesLookup caches
> properties
>
>
> Key: TOMEE-1465
> URL: https://issues.apache.org/jira/browse/TOMEE-1465
> Project: TomEE
> Issue Type: Bug
>Affects Versions: 1.7.1, 7.0.0-M1
>Reporter: Andy Gumbrecht
>Assignee: Andy Gumbrecht
> Fix For: 1.7.4, 7.0.0-M3
>
>
> org.apache.openejb.util.PropertyPlaceHolderHelper.PropertiesLookup should not
> cache SystemInstance.get().getProperties() as this leads to race conditions
> and rare test failures where test order is not guaranteed. The following
> illustrates the issue.
> SystemInstance.get().setProperty("PropertyPlaceHolderTest1", "bob");
> final String bob =
> PropertyPlaceHolderHelper.simpleValue("j${PropertyPlaceHolderTest1}");
> SystemInstance.get().setProperty("PropertyPlaceHolderTest1", "sally");
> final String sally =
> PropertyPlaceHolderHelper.simpleValue("j${PropertyPlaceHolderTest1}");
> sally == "bob" <-- As PropertiesLookup is using cached properties from first
> call.
> Calling PropertyPlaceHolderHelper .reset() on
> SystemInstance.get().setProperty() calls could be an option, but would force
> a loader dep on core, or moving PropertyPlaceHolderHelper to loader could be
> an option if it does not break anything.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TOMEE-1302) Support JSR 236 - Concurrency Utilities for Java EE
[ https://issues.apache.org/jira/browse/TOMEE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1302: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Support JSR 236 - Concurrency Utilities for Java EE > --- > > Key: TOMEE-1302 > URL: https://issues.apache.org/jira/browse/TOMEE-1302 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Support JSR 236 - Concurrency Utilities for Java EE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1306) Ensure full support of JSR-341 Expression Language 3.0
[ https://issues.apache.org/jira/browse/TOMEE-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1306: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure full support of JSR-341 Expression Language 3.0 > -- > > Key: TOMEE-1306 > URL: https://issues.apache.org/jira/browse/TOMEE-1306 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Ensure full support of JSR-341 Expression Language 3.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1622) TomEE SystemInstance unsafely iterates over the System.getProperties()
[ https://issues.apache.org/jira/browse/TOMEE-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1622: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > TomEE SystemInstance unsafely iterates over the System.getProperties() > -- > > Key: TOMEE-1622 > URL: https://issues.apache.org/jira/browse/TOMEE-1622 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.2 > Environment: Linux >Reporter: Kasun Gajasinghe > Fix For: 1.7.4, 7.0.0-M3 > > > This is discussed @tomee-dev > http://tomee-openejb.979440.n4.nabble.com/TomEE-SystemInstance-unsafely-iterates-over-the-System-getProperties-td4675732.html > We've been seeing the following exception [2] in an instance where we have > extended TomEE 1.7.2. We have debugged the issue, and it seems to have > occurred since TomEE iterate over the System.getProperties() hashtable [1]. > It's possible that other threads might be using the system properties which > could lead to ConcurrentModificationException. > Best way fix thing would to create a clone of the system properties, and use > that clone to iterate. There are issues reported for unsafe iterating of > system properties in other projects as seen in [3]. > Can we get this fixed in TomEE 1.7.3? > [1] > https://github.com/apache/tomee/blob/tomee-1.7.x/container/openejb-loader/src/main/java/org/apache/openejb/loader/SystemInstance.java#L71 > [2] > org.apache.openejb.loader.LoaderRuntimeException: Failed to create default > instance of SystemInstance > at org.apache.openejb.loader.SystemInstance.reset(SystemInstance.java:280) > at org.apache.openejb.loader.SystemInstance.(SystemInstance.java:265) > ... 9 more > Caused by: java.util.ConcurrentModificationException > at java.util.Hashtable$Enumerator.next(Hashtable.java:1167) > at org.apache.openejb.loader.SystemInstance.(SystemInstance.java:71) > at org.apache.openejb.loader.SystemInstance.reset(SystemInstance.java:277) > ... 10 more > [3] > https://bugs.eclipse.org/bugs/show_bug.cgi?id=469706 > https://liquibase.jira.com/browse/CORE-2104 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1300) Support JSON JSR 353 - Java API for JSON Processing (JSON-P)
[ https://issues.apache.org/jira/browse/TOMEE-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1300: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Support JSON JSR 353 - Java API for JSON Processing (JSON-P) > > > Key: TOMEE-1300 > URL: https://issues.apache.org/jira/browse/TOMEE-1300 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Support JSON JSR 353 - Java API for JSON Processing (JSON-P) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1683) Tests for JAX-RS Webservice based on EJBContainerRunner work in OpenEJB 4.7.3 but not in 7.0.0-M1
[ https://issues.apache.org/jira/browse/TOMEE-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1683: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Tests for JAX-RS Webservice based on EJBContainerRunner work in OpenEJB 4.7.3 > but not in 7.0.0-M1 > - > > Key: TOMEE-1683 > URL: https://issues.apache.org/jira/browse/TOMEE-1683 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 7.0.0-M1 > Environment: MacOS-10.11.2 / Linux (Ubuntu 14.04 LTS) - Maven 3.3.9 - > Java 8 (Oracle, 1.8.0-b66) >Reporter: Martin Wiesner > Labels: maven, test > Fix For: 7.0.0-M3 > > > I got a couple of JUnit Tests (> 200) based on > @RunWith(EJBContainerRunner.class) annotation which stopped working when > codebase is updated to use/run with TomEE/OpenEJB 7.0.0-M1. > I reproduced this on several projects and build a minimal example that shows > that the given Test passes with OpenEJB 4.7.3 and TomEE 1.7.3 (or: 1.7.2) but > not when we use "7.0.0-M1". The pom.xml of the example project has commented > lines for the older variant in order to quickly switch the environment. > Demo Project is available for download here: > https://download.mi.hs-heilbronn.de/tomee/ejb-container-runner-demo-ws.zip > As it seems, the environment launched via "@EJBContainerRunner" does not > start/expose the JAX-RS annotated webservice endpoint so clients can send > requests. Again, in 4.7.3/1.7.3 this worked like a charm. When we run the > project via maven goal "tomee:run" the endpoint is exposed and clients can > successfully send requests and receive HTTP 20x codes as a reply. > Maybe [~rmannibucau] could have a look at it? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1638) tomee:exec on Windows produces invalid tomee.zip due to backslash directory separators
[ https://issues.apache.org/jira/browse/TOMEE-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1638: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > tomee:exec on Windows produces invalid tomee.zip due to backslash directory > separators > -- > > Key: TOMEE-1638 > URL: https://issues.apache.org/jira/browse/TOMEE-1638 > Project: TomEE > Issue Type: Bug > Components: TomEE Maven Plugin >Affects Versions: 1.7.2 > Environment: Windows >Reporter: David Eaves >Priority: Minor > Fix For: 1.7.4, 7.0.0-M3 > > Attachments: ExecRunner.java.patch, Zips.java, Zips.java.patch, > ZipsTest.java > > > The tomee:exec target produces an invalid tomee.zip file within the > standalone jar when run under Windows. This prevents the standalone jar from > being run under Linux. > This issue is caused by the use of platform directory separators in the Zip > entry names rather than forward slashes. See section 4.4.17 at > https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT > The offending code is in org.apache.openejb.maven.plugin.util.Zips. I have > produced a fix and tested this stand-alone, but not in the context of the > plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1321) Drop or deprecate Java EE Application Deployment 1.2
[ https://issues.apache.org/jira/browse/TOMEE-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1321: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Drop or deprecate Java EE Application Deployment 1.2 > > > Key: TOMEE-1321 > URL: https://issues.apache.org/jira/browse/TOMEE-1321 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Drop or deprecate Java EE Application Deployment 1.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1315) Ensure full support of JSR-907 JavaTM Transaction API 1.2
[ https://issues.apache.org/jira/browse/TOMEE-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1315: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure full support of JSR-907 JavaTM Transaction API 1.2 > - > > Key: TOMEE-1315 > URL: https://issues.apache.org/jira/browse/TOMEE-1315 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Ensure full support of JSR-907 JavaTM Transaction API 1.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1301) Support JSR 352 - Batch Applications for the Java Platform
[ https://issues.apache.org/jira/browse/TOMEE-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1301: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Support JSR 352 - Batch Applications for the Java Platform > -- > > Key: TOMEE-1301 > URL: https://issues.apache.org/jira/browse/TOMEE-1301 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Support JSR 352 - Batch Applications for the Java Platform -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1314) Ensure full support of JSR-338 Java Persistence 2.1
[ https://issues.apache.org/jira/browse/TOMEE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1314: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure full support of JSR-338 Java Persistence 2.1 > --- > > Key: TOMEE-1314 > URL: https://issues.apache.org/jira/browse/TOMEE-1314 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Ensure full support of JSR-338 Java Persistence 2.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1319) Drop or deprecate JAX-RPC 1.1 Support
[ https://issues.apache.org/jira/browse/TOMEE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1319: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Drop or deprecate JAX-RPC 1.1 Support > - > > Key: TOMEE-1319 > URL: https://issues.apache.org/jira/browse/TOMEE-1319 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Drop or deprecate JAX-RPC 1.1 Support -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1323) Ensure full support of JSR-919 JavaMail 1.5
[ https://issues.apache.org/jira/browse/TOMEE-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1323: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure full support of JSR-919 JavaMail 1.5 > --- > > Key: TOMEE-1323 > URL: https://issues.apache.org/jira/browse/TOMEE-1323 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Ensure full support of JSR-919 JavaMail 1.5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1461) Need a machine global mechanism for 'get next available port' to prevent 'address in use' issues
[ https://issues.apache.org/jira/browse/TOMEE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1461: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Need a machine global mechanism for 'get next available port' to prevent > 'address in use' issues > > > Key: TOMEE-1461 > URL: https://issues.apache.org/jira/browse/TOMEE-1461 > Project: TomEE > Issue Type: Improvement >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Minor > Fix For: 1.7.4, 7.0.0-M3 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1455) for resource local pu try to guess if datasource is configured in persistence unit properties
[ https://issues.apache.org/jira/browse/TOMEE-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1455: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > for resource local pu try to guess if datasource is configured in persistence > unit properties > - > > Key: TOMEE-1455 > URL: https://issues.apache.org/jira/browse/TOMEE-1455 > Project: TomEE > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 1.7.4, 7.0.0-M3 > > > Note: it still needs openejb.force-unit-type=true if no [non-]jta-data-source > is configured to stay spec compliant -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1320) Drop or deprecate JAXR 1.0
[ https://issues.apache.org/jira/browse/TOMEE-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1320: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Drop or deprecate JAXR 1.0 > -- > > Key: TOMEE-1320 > URL: https://issues.apache.org/jira/browse/TOMEE-1320 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Drop or deprecate JAXR 1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1303) Support JSR-299 - CDI Portable Extensions
[ https://issues.apache.org/jira/browse/TOMEE-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1303: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Support JSR-299 - CDI Portable Extensions > - > > Key: TOMEE-1303 > URL: https://issues.apache.org/jira/browse/TOMEE-1303 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Support JSR-299 - CDI Portable Extensions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1312) Ensure full support of JSR-345 Enterprise JavaBeans 3.2
[ https://issues.apache.org/jira/browse/TOMEE-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1312: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure full support of JSR-345 Enterprise JavaBeans 3.2 > > > Key: TOMEE-1312 > URL: https://issues.apache.org/jira/browse/TOMEE-1312 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Ensure full support of JSR-345 Enterprise JavaBeansTM 3.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1666) Remove BootstrapTransformer once work is done - no need to see all classes + disable by default web scanning in org.apache.openejb.persistence.PersistenceBootstrap#bootst
[ https://issues.apache.org/jira/browse/TOMEE-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1666: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Remove BootstrapTransformer once work is done - no need to see all classes + > disable by default web scanning in > org.apache.openejb.persistence.PersistenceBootstrap#bootstrap > - > > Key: TOMEE-1666 > URL: https://issues.apache.org/jira/browse/TOMEE-1666 > Project: TomEE > Issue Type: Improvement >Affects Versions: 7.0.0-M1 >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Minor > Fix For: 7.0.0-M3 > > > Cutting web scanning is for performance reason and is very rarely needed > Removing the transformer avoids few potential classloading runtime issues in > some env. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1310) Ensure full support of JSR-318 Interceptors 1.1
[ https://issues.apache.org/jira/browse/TOMEE-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1310: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure full support of JSR-318 Interceptors 1.1 > --- > > Key: TOMEE-1310 > URL: https://issues.apache.org/jira/browse/TOMEE-1310 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Ensure full support of JSR-318 Interceptors 1.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1547) Use application classloader for resources defined in resources.xml
[
https://issues.apache.org/jira/browse/TOMEE-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romain Manni-Bucau updated TOMEE-1547:
--
Fix Version/s: (was: 7.0.0-M2)
7.0.0-M3
> Use application classloader for resources defined in resources.xml
> --
>
> Key: TOMEE-1547
> URL: https://issues.apache.org/jira/browse/TOMEE-1547
> Project: TomEE
> Issue Type: Improvement
>Affects Versions: 1.7.1
>Reporter: Jonathan Gallimore
>Assignee: Jonathan Gallimore
> Fix For: 1.7.4, 7.0.0-M3
>
>
> Resources can be defined in applications using META-INF/resources.xml. This
> is a useful feature, but because resources are created very early on in
> deployment the final classloader for the application is not available.
> I know I can manually specify a specific jar or classpath, but I specifically
> want the resources I define to be loaded using the same classpath the
> application uses.
> So, for example, if I have an EJB jar in an EAR, and the EJB jar contains a
> POJO called HelloBean, the following should load the resource from the
> application classloader:
>
>
>property1 value1
>property2 value2
>
>
> Currently this fails with a class not found error, due to the following in
> org.apache.openejb.assembler.classic.Assembler.createResource(ResourceInfo):
> ClassLoader loader = Thread.currentThread().getContextClassLoader();
> boolean customLoader = false;
> try {
> if (serviceInfo.classpath != null && serviceInfo.classpath.length
> > 0) {
> final URL[] urls = new URL[serviceInfo.classpath.length];
> for (int i = 0; i < serviceInfo.classpath.length; i++) {
> urls[i] = serviceInfo.classpath[i].toURL();
> }
> loader = new URLClassLoaderFirst(urls, loader);
> customLoader = true;
> }
> } catch (final MalformedURLException e) {
> throw new OpenEJBException("Unable to create a classloader for "
> + serviceInfo.id, e);
> }
> Object service = serviceRecipe.create(loader);
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TOMEE-1628) tomee.sh start registering MBean problem
[ https://issues.apache.org/jira/browse/TOMEE-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1628: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > tomee.sh start registering MBean problem > - > > Key: TOMEE-1628 > URL: https://issues.apache.org/jira/browse/TOMEE-1628 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 1.7.2 >Reporter: Gurkan Erdogdu > Fix For: 7.0.0-M3 > > Attachments: TOMEE_1628.patch > > > Whenever you run the tomee.sh start from bin/ directory you get the following > exceptions in the log files. The problem is that registering MBean failes > because of there is no default constructor in > JMXReloadableEntityManagerFactory and TransactionManagerMBean classes. In > fact, transaction manager and entity manager factories are already registered > to MBean server but these exceptions gives wrong message to the user. > Therefore, it is reasonable to register these MBeans under application object > names. > I attached the code that fixes the exception problem. > Here is the exception when you start tomee.sh start: > SEVERE: the mbean > org.apache.openejb.assembler.classic.ReloadableEntityManagerFactory$JMXReloadableEntityManagerFactory > can't be registered because it can't be instantiated > java.lang.InstantiationException: > org.apache.openejb.assembler.classic.ReloadableEntityManagerFactory$JMXReloadableEntityManagerFactory > at java.lang.Class.newInstance(Class.java:364) > at > org.apache.openejb.assembler.classic.Assembler.deployMBean(Assembler.java:1428) > at > org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:950) > at > org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:658) > at > org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:549) > at > org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:445) > at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150) > at org.apache.openejb.OpenEJB.init(OpenEJB.java:298) > at org.apache.openejb.server.Server.init(Server.java:65) > at org.apache.openejb.server.Main.initServer(Main.java:154) > at org.apache.openejb.server.Main.main(Main.java:128) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.cli.MainImpl.main(MainImpl.java:148) > at org.apache.openejb.cli.Bootstrap.main(Bootstrap.java:106) > Aug 30, 2015 12:02:19 AM org.apache.openejb.assembler.classic.Assembler > deployMBean > INFO: Deployed > MBean(openejb.user.mbeans:application=openejb-core-4.7.3-SNAPSHOT,group=org.apache.openejb.assembler.monitoring,name=JMXDeployer) > Aug 30, 2015 12:02:31 AM org.apache.openejb.assembler.classic.Assembler > deployMBean > SEVERE: the mbean > org.apache.openejb.resource.GeronimoTransactionManagerFactory$TransactionManagerMBean > can't be registered because it can't be instantiated > java.lang.InstantiationException: > org.apache.openejb.resource.GeronimoTransactionManagerFactory$TransactionManagerMBean > at java.lang.Class.newInstance(Class.java:364) > at > org.apache.openejb.assembler.classic.Assembler.deployMBean(Assembler.java:1428) > at > org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:950) > at > org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:658) > at > org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:549) > at > org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:445) > at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150) > at org.apache.openejb.OpenEJB.init(OpenEJB.java:298) > at org.apache.openejb.server.Server.init(Server.java:65) > at org.apache.openejb.server.Main.initServer(Main.java:154) > at org.apache.openejb.server.Main.main(Main.java:128) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.cli.MainImpl.main(MainImpl.java:148) > at org.apache.openejb.cli.Bootstrap.main(Bootstrap.java:106) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TOMEE-1307) Ensure full support of JSR-339 The Java API for RESTful Web Services 2.0 (JAX-RS)
[ https://issues.apache.org/jira/browse/TOMEE-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1307: -- Fix Version/s: (was: 7.0.0-M2) 7.0.0-M3 > Ensure full support of JSR-339 The Java API for RESTful Web Services 2.0 > (JAX-RS) > - > > Key: TOMEE-1307 > URL: https://issues.apache.org/jira/browse/TOMEE-1307 > Project: TomEE > Issue Type: Task >Affects Versions: 7.0.0 >Reporter: Andy Gumbrecht > Fix For: 7.0.0, 7.0.0-M3 > > > Ensure full support of JSR-339 The Java API for RESTful Web Services 2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TOMEE-1720) tomee as a maven dependency
[
https://issues.apache.org/jira/browse/TOMEE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171122#comment-15171122
]
Matthew Broadhead commented on TOMEE-1720:
--
ok. commons-codec:commons-codec:1.9 is another one that needs to be added
manually
> tomee as a maven dependency
> ---
>
> Key: TOMEE-1720
> URL: https://issues.apache.org/jira/browse/TOMEE-1720
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 1.7.3
>Reporter: Matthew Broadhead
>
> Currently my projects in eclipse have the TomEE server runtime include on the
> build path. this works fine but it is not very portable and upgrading
> requires changing the build path for every project rather than changing the
> version number in the pom.xml.
> Is it possible to include TomEE using Maven? I tried adding
> {code:xml}
>
> org.apache.openejb
> tomee-plume-webapp
> 1.7.3
>
> {code}
> but it gives "Missing artifact
> org.apache.openejb:tomee-plume-webapp:jar:1.7.3"
> I have tried the tomee-maven-plugin but I prefer to be able to stop and start
> the server from eclipse and also the debugger is easier to set up. Also
> eclipse starts all the projects together and integrates them. (I suppose if
> tomee-maven-plugin is capable of all this I could try it again)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TOMEE-1720) tomee as a maven dependency
[
https://issues.apache.org/jira/browse/TOMEE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171044#comment-15171044
]
Romain Manni-Bucau commented on TOMEE-1720:
---
No cause we switch it to keep tomcat api and avoid conflicts during packaging
of the distribution.
> tomee as a maven dependency
> ---
>
> Key: TOMEE-1720
> URL: https://issues.apache.org/jira/browse/TOMEE-1720
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 1.7.3
>Reporter: Matthew Broadhead
>
> Currently my projects in eclipse have the TomEE server runtime include on the
> build path. this works fine but it is not very portable and upgrading
> requires changing the build path for every project rather than changing the
> version number in the pom.xml.
> Is it possible to include TomEE using Maven? I tried adding
> {code:xml}
>
> org.apache.openejb
> tomee-plume-webapp
> 1.7.3
>
> {code}
> but it gives "Missing artifact
> org.apache.openejb:tomee-plume-webapp:jar:1.7.3"
> I have tried the tomee-maven-plugin but I prefer to be able to stop and start
> the server from eclipse and also the debugger is easier to set up. Also
> eclipse starts all the projects together and integrates them. (I suppose if
> tomee-maven-plugin is capable of all this I could try it again)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
buildbot success in on tomee-trunk-ubuntu-jvm8
The Buildbot has detected a restored build on builder tomee-trunk-ubuntu-jvm8 while building tomee. Full details are available at: https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/223 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: hemera_ubuntu Build Reason: The SingleBranchScheduler scheduler named 'on-tomee-trunk-ubuntu-jvm8-commit' triggered this build Build Source Stamp: [branch master] 5689b25ac70a243c4d838962e068856f889ea87f Blamelist: Romain manni-Bucau Build succeeded! Sincerely, -The Buildbot
[jira] [Commented] (TOMEE-1720) tomee as a maven dependency
[
https://issues.apache.org/jira/browse/TOMEE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170989#comment-15170989
]
Matthew Broadhead commented on TOMEE-1720:
--
thanks that works. should javaee-api be included in tomee-plume-webapp?
> tomee as a maven dependency
> ---
>
> Key: TOMEE-1720
> URL: https://issues.apache.org/jira/browse/TOMEE-1720
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 1.7.3
>Reporter: Matthew Broadhead
>
> Currently my projects in eclipse have the TomEE server runtime include on the
> build path. this works fine but it is not very portable and upgrading
> requires changing the build path for every project rather than changing the
> version number in the pom.xml.
> Is it possible to include TomEE using Maven? I tried adding
> {code:xml}
>
> org.apache.openejb
> tomee-plume-webapp
> 1.7.3
>
> {code}
> but it gives "Missing artifact
> org.apache.openejb:tomee-plume-webapp:jar:1.7.3"
> I have tried the tomee-maven-plugin but I prefer to be able to stop and start
> the server from eclipse and also the debugger is easier to set up. Also
> eclipse starts all the projects together and integrates them. (I suppose if
> tomee-maven-plugin is capable of all this I could try it again)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TOMEE-1720) tomee as a maven dependency
[
https://issues.apache.org/jira/browse/TOMEE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170981#comment-15170981
]
Romain Manni-Bucau commented on TOMEE-1720:
---
Yes, you need org.apache.tomee:javaee-api:7.0 in scope providee for all api
related artifacts.
> tomee as a maven dependency
> ---
>
> Key: TOMEE-1720
> URL: https://issues.apache.org/jira/browse/TOMEE-1720
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 1.7.3
>Reporter: Matthew Broadhead
>
> Currently my projects in eclipse have the TomEE server runtime include on the
> build path. this works fine but it is not very portable and upgrading
> requires changing the build path for every project rather than changing the
> version number in the pom.xml.
> Is it possible to include TomEE using Maven? I tried adding
> {code:xml}
>
> org.apache.openejb
> tomee-plume-webapp
> 1.7.3
>
> {code}
> but it gives "Missing artifact
> org.apache.openejb:tomee-plume-webapp:jar:1.7.3"
> I have tried the tomee-maven-plugin but I prefer to be able to stop and start
> the server from eclipse and also the debugger is easier to set up. Also
> eclipse starts all the projects together and integrates them. (I suppose if
> tomee-maven-plugin is capable of all this I could try it again)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
buildbot failure in on tomee-trunk-ubuntu
The Buildbot has detected a new failure on builder tomee-trunk-ubuntu while building tomee. Full details are available at: https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/240 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: hemera_ubuntu Build Reason: The SingleBranchScheduler scheduler named 'on-tomee-trunk-ubuntu-commit' triggered this build Build Source Stamp: [branch master] 5689b25ac70a243c4d838962e068856f889ea87f Blamelist: Romain manni-Bucau BUILD FAILED: failed test Sincerely, -The Buildbot
[jira] [Commented] (TOMEE-1720) tomee as a maven dependency
[
https://issues.apache.org/jira/browse/TOMEE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170979#comment-15170979
]
Matthew Broadhead commented on TOMEE-1720:
--
i changed it to
{code:xml}
org.apache.openejb
tomee-plume-webapp
1.7.3
pom
provided
{code}
but i get error
{noformat}
The type javax.el.ELException cannot be resolved. It is indirectly referenced
from required .class files
{noformat}
> tomee as a maven dependency
> ---
>
> Key: TOMEE-1720
> URL: https://issues.apache.org/jira/browse/TOMEE-1720
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 1.7.3
>Reporter: Matthew Broadhead
>
> Currently my projects in eclipse have the TomEE server runtime include on the
> build path. this works fine but it is not very portable and upgrading
> requires changing the build path for every project rather than changing the
> version number in the pom.xml.
> Is it possible to include TomEE using Maven? I tried adding
> {code:xml}
>
> org.apache.openejb
> tomee-plume-webapp
> 1.7.3
>
> {code}
> but it gives "Missing artifact
> org.apache.openejb:tomee-plume-webapp:jar:1.7.3"
> I have tried the tomee-maven-plugin but I prefer to be able to stop and start
> the server from eclipse and also the debugger is easier to set up. Also
> eclipse starts all the projects together and integrates them. (I suppose if
> tomee-maven-plugin is capable of all this I could try it again)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TOMEE-1721) no module (webapp here) webservices can lead to NPE
[ https://issues.apache.org/jira/browse/TOMEE-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1721: -- Affects Version/s: 7.0.0-M1 > no module (webapp here) webservices can lead to NPE > --- > > Key: TOMEE-1721 > URL: https://issues.apache.org/jira/browse/TOMEE-1721 > Project: TomEE > Issue Type: Bug >Affects Versions: 7.0.0-M1 >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 7.0.0-M2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TOMEE-1721) no module (webapp here) webservices can lead to NPE
[ https://issues.apache.org/jira/browse/TOMEE-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved TOMEE-1721. --- Resolution: Fixed Fix Version/s: (was: 7.0.0-M1) 7.0.0-M2 > no module (webapp here) webservices can lead to NPE > --- > > Key: TOMEE-1721 > URL: https://issues.apache.org/jira/browse/TOMEE-1721 > Project: TomEE > Issue Type: Bug >Affects Versions: 7.0.0-M1 >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 7.0.0-M2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
tomee git commit: TOMEE-1721 moduleId is supposed nullable, not path
Repository: tomee
Updated Branches:
refs/heads/master 9505fdc1a -> 5689b25ac
TOMEE-1721 moduleId is supposed nullable, not path
Project: http://git-wip-us.apache.org/repos/asf/tomee/repo
Commit: http://git-wip-us.apache.org/repos/asf/tomee/commit/5689b25a
Tree: http://git-wip-us.apache.org/repos/asf/tomee/tree/5689b25a
Diff: http://git-wip-us.apache.org/repos/asf/tomee/diff/5689b25a
Branch: refs/heads/master
Commit: 5689b25ac70a243c4d838962e068856f889ea87f
Parents: 9505fdc
Author: Romain manni-Bucau
Authored: Sun Feb 28 10:03:26 2016 +0100
Committer: Romain manni-Bucau
Committed: Sun Feb 28 10:03:26 2016 +0100
--
.../main/java/org/apache/tomee/webservices/TomcatWsRegistry.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
http://git-wip-us.apache.org/repos/asf/tomee/blob/5689b25a/tomee/tomee-webservices/src/main/java/org/apache/tomee/webservices/TomcatWsRegistry.java
--
diff --git
a/tomee/tomee-webservices/src/main/java/org/apache/tomee/webservices/TomcatWsRegistry.java
b/tomee/tomee-webservices/src/main/java/org/apache/tomee/webservices/TomcatWsRegistry.java
index b33976f..e16c983 100644
---
a/tomee/tomee-webservices/src/main/java/org/apache/tomee/webservices/TomcatWsRegistry.java
+++
b/tomee/tomee-webservices/src/main/java/org/apache/tomee/webservices/TomcatWsRegistry.java
@@ -454,7 +454,7 @@ public class TomcatWsRegistry implements WsRegistry {
private final String path;
private final int hash;
-public Key(final String moduleId, final String path) {
+public Key(final String path, final String moduleId) {
this.moduleId = moduleId;
this.path = path;
this.hash = 31 * (moduleId != null ? moduleId.hashCode() : 0) +
path.hashCode();
[jira] [Created] (TOMEE-1721) no module (webapp here) webservices can lead to NPE
Romain Manni-Bucau created TOMEE-1721: - Summary: no module (webapp here) webservices can lead to NPE Key: TOMEE-1721 URL: https://issues.apache.org/jira/browse/TOMEE-1721 Project: TomEE Issue Type: Bug Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 7.0.0-M1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
