[jira] [Updated] (TOMEE-1868) Prevent hot deployment of "filepart" archives
[ https://issues.apache.org/jira/browse/TOMEE-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1868: -- Description: Dropping an application war into webapps sometimes deploys the partially extracted war file with the [appname].filepart and then [appname]. This obviously breaks both deployments and the only solution is to delete both, wait for the undeploy, and then redeploy. This is to do with the transfer over scp - the extension is either '.filepart' or '.partial'. was:Dropping an application war into webapps sometimes deploys the partially extracted war file with the [appname].filepart and then [appname]. This obviously breaks both deployments and the only solution is to delete both, wait for the undeploy, and then redeploy. > Prevent hot deployment of "filepart" archives > - > > Key: TOMEE-1868 > URL: https://issues.apache.org/jira/browse/TOMEE-1868 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.4, 7.0.1 >Reporter: Andy Gumbrecht >Priority: Major > Fix For: 7.0.5, 1.7.6 > > > Dropping an application war into webapps sometimes deploys the partially > extracted war file with the [appname].filepart and then [appname]. This > obviously breaks both deployments and the only solution is to delete both, > wait for the undeploy, and then redeploy. > This is to do with the transfer over scp - the extension is either > '.filepart' or '.partial'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1985) SessionBean ejbCreate invoked potentially twice
[
https://issues.apache.org/jira/browse/TOMEE-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Gumbrecht updated TOMEE-1985:
--
Fix Version/s: (was: 1.7.5)
1.7.6
> SessionBean ejbCreate invoked potentially twice
> ---
>
> Key: TOMEE-1985
> URL: https://issues.apache.org/jira/browse/TOMEE-1985
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 1.7.4, 7.0.2
>Reporter: David Blevins
>Assignee: David Blevins
> Fix For: 7.0.5, 1.7.6
>
>
> When an EJB 2.x style Stateless session bean implements the
> {{javax.ejb.SessionBean}} interface, the "ejbCreate" method is invoked twice
> if the method signature is {{public void ejbCreate()}}
> If the method signature is {{public void ejbCreateObject()}} or otherwise has
> a suffix as is allowed in the EJB spec, it is only invoked once as intended.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (TOMEE-1868) Prevent hot deployment of "filepart" archives
[ https://issues.apache.org/jira/browse/TOMEE-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1868: -- Fix Version/s: (was: 1.7.5) 1.7.6 > Prevent hot deployment of "filepart" archives > - > > Key: TOMEE-1868 > URL: https://issues.apache.org/jira/browse/TOMEE-1868 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.4, 7.0.1 >Reporter: Andy Gumbrecht > Fix For: 7.0.5, 1.7.6 > > > Dropping an application war into webapps sometimes deploys the partially > extracted war file with the [appname].filepart and then [appname]. This > obviously breaks both deployments and the only solution is to delete both, > wait for the undeploy, and then redeploy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2091) NetworkUtilTest
[ https://issues.apache.org/jira/browse/TOMEE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2091: -- Fix Version/s: (was: 1.7.5) 1.7.6 > NetworkUtilTest > --- > > Key: TOMEE-2091 > URL: https://issues.apache.org/jira/browse/TOMEE-2091 > Project: TomEE > Issue Type: Bug > Components: TomEE Build >Affects Versions: 1.7.4, 7.0.3 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 7.0.5, 1.7.6 > > > This test seems to fail occasionally: > Running org.apache.openejb.util.NetworkUtilTest > Exception in thread "test-thread-20" java.lang.AssertionError: Got a > duplicate port with ten seconds > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.openejb.util.NetworkUtilTest$1.run(NetworkUtilTest.java:68) > at java.lang.Thread.run(Thread.java:745) > Machine safe port list = [1025, 1026, 1027, 1028, 1029, 1030, 1031, 1032, > 1033, 1034, 1035, 1036, 1037, 1038, 1039, 1040, 1041, 1042, 1043, 1044] > Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.305 sec > <<< FAILURE! - in org.apache.openejb.util.NetworkUtilTest > testNext(org.apache.openejb.util.NetworkUtilTest) Time elapsed: 15.019 sec > <<< FAILURE! > java.lang.AssertionError > at > org.apache.openejb.util.NetworkUtilTest.testNext(NetworkUtilTest.java:82) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2112) Update Taglibs, WSS4J, Jansi and OpenSAML
[ https://issues.apache.org/jira/browse/TOMEE-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2112: -- Fix Version/s: (was: 1.7.5) 1.7.6 > Update Taglibs, WSS4J, Jansi and OpenSAML > - > > Key: TOMEE-2112 > URL: https://issues.apache.org/jira/browse/TOMEE-2112 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 1.7.4 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore >Priority: Minor > Fix For: 1.7.6 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1867) Investigate FileNotFoundException warning
[ https://issues.apache.org/jira/browse/TOMEE-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1867: -- Fix Version/s: (was: 1.7.5) 1.7.6 > Investigate FileNotFoundException warning > - > > Key: TOMEE-1867 > URL: https://issues.apache.org/jira/browse/TOMEE-1867 > Project: TomEE > Issue Type: Task >Affects Versions: 1.7.4 > Environment: Windows >Reporter: Andy Gumbrecht >Priority: Trivial > Fix For: 7.0.5, 1.7.6 > > > Only a warning, but wondering why this broken path is generated: > 2016-07-15 11:00:35 WARN FileZippedJarVisitor:74 - HHH015010: Unable to find > file (ignored): > file:/C:/Integration/workspace/project/project-service-impl/jar:file:/C:/repository/com/company/division/app/app-service-impl/1.2.3/app-service-impl-1.2.3.jar!/META-INF/persistence.xml > java.io.FileNotFoundException: > C:\Integration\workspace\project\project-service-impl\jar:file:\C:\repository\com\company\division\app\app-service-impl\1.2.3\app-service-impl-1.2.3.jar!\META-INF\persistence.xml > (Die Syntax für den Dateinamen, Verzeichnisnamen oder die > Datenträgerbezeichnung ist falsch) > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.(ZipFile.java:215) > at java.util.zip.ZipFile.(ZipFile.java:145) > at java.util.jar.JarFile.(JarFile.java:154) > at java.util.jar.JarFile.(JarFile.java:91) > at > org.hibernate.ejb.packaging.FileZippedJarVisitor.doProcessElements(FileZippedJarVisitor.java:70) > at > org.hibernate.ejb.packaging.AbstractJarVisitor.getMatchingEntries(AbstractJarVisitor.java:149) > at > org.hibernate.ejb.packaging.NativeScanner.getClassesInJar(NativeScanner.java:128) > at > org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:488) > at > org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:862) > at > org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:607) > at > org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:75) > at > org.apache.openejb.assembler.classic.EntityManagerFactoryCallable.call(EntityManagerFactoryCallable.java:64) > at > org.apache.openejb.assembler.classic.ReloadableEntityManagerFactory.createDelegate(ReloadableEntityManagerFactory.java:116) > at > org.apache.openejb.assembler.classic.ReloadableEntityManagerFactory.(ReloadableEntityManagerFactory.java:102) > at > org.apache.openejb.assembler.classic.PersistenceBuilder.createEntityManagerFactory(PersistenceBuilder.java:154) > at > org.apache.openejb.assembler.classic.Assembler.loadPersistenceUnits(Assembler.java:985) > at > org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:744) > at > org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:680) > at > org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:676) > at > org.apache.openejb.testing.ApplicationComposers.before(ApplicationComposers.java:830) > at > org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:984) > at > org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2034) Upgrade to latest OpenJPA-2.4.2
[ https://issues.apache.org/jira/browse/TOMEE-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2034: -- Fix Version/s: (was: 1.7.5) 1.7.6 > Upgrade to latest OpenJPA-2.4.2 > --- > > Key: TOMEE-2034 > URL: https://issues.apache.org/jira/browse/TOMEE-2034 > Project: TomEE > Issue Type: Task > Components: TomEE Core Server >Affects Versions: 1.7.4 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.7.6 > > > We currently ship an older OpenJPA-2.4.0 version. This should get updated for > the 1.7.5 release. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1399) Potential NPE in Assembler
[ https://issues.apache.org/jira/browse/TOMEE-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1399: -- Fix Version/s: (was: 7.0.4) 7.0.5 > Potential NPE in Assembler > -- > > Key: TOMEE-1399 > URL: https://issues.apache.org/jira/browse/TOMEE-1399 > Project: TomEE > Issue Type: Bug >Affects Versions: 7.0.0 >Reporter: Daniel Kasmeroglu >Priority: Minor > Fix For: 7.0.5 > > Attachments: tomee-1399.patch > > > There is a test whether _AppContext_ is _null_ or not. But it's dereferenced > ahead of this test so a _null_ value would still cause an NPE. > See: > https://kasisoft.com/stash/projects/TOMEE/repos/tomee/commits/d0b85235aacd0a39559abcab677438c056e8aa81 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2107) Upgrade CXF
[ https://issues.apache.org/jira/browse/TOMEE-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2107: -- Fix Version/s: (was: 7.0.4) 7.0.5 > Upgrade CXF > --- > > Key: TOMEE-2107 > URL: https://issues.apache.org/jira/browse/TOMEE-2107 > Project: TomEE > Issue Type: Dependency upgrade > Components: TomEE Core Server >Affects Versions: 7.0.4 >Reporter: Daniel Cunha >Priority: Minor > Fix For: 7.0.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1868) Prevent hot deployment of "filepart" archives
[ https://issues.apache.org/jira/browse/TOMEE-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1868: -- Fix Version/s: (was: 7.0.4) 7.0.5 > Prevent hot deployment of "filepart" archives > - > > Key: TOMEE-1868 > URL: https://issues.apache.org/jira/browse/TOMEE-1868 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.4, 7.0.1 >Reporter: Andy Gumbrecht > Fix For: 1.7.5, 7.0.5 > > > Dropping an application war into webapps sometimes deploys the partially > extracted war file with the [appname].filepart and then [appname]. This > obviously breaks both deployments and the only solution is to delete both, > wait for the undeploy, and then redeploy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1315: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Ensure full support of JSR-907 JavaTM Transaction API 1.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1943) Tomee blows up when it finds tags in beans.xml which it doesn't know
[ https://issues.apache.org/jira/browse/TOMEE-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1943: -- Fix Version/s: (was: 7.0.4) 7.0.5 > Tomee blows up when it finds tags in beans.xml which it doesn't know > > > Key: TOMEE-1943 > URL: https://issues.apache.org/jira/browse/TOMEE-1943 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 1.7.4, 7.0.1 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 7.0.5 > > > We blow up heavily if we find a tag in e.g. beans.xml which we don't know. > This is really sad since OWB has additional tags since many years and Weld > also has them. > A hardcoded 'ignore' hack got added for Weld, but not for OWB. > We must only log out a warning if we detect a tag or attribute we don't know, > but must not blow up. This really limits us. > There is a simple trick to work around this: > @XmlAnyElement(lax = true) > private List unknownElements; > + log out those values manually afterwards. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1320: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Drop or deprecate JAXR 1.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1316: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Ensure full support of JSR-343 Java Message Service 2.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1525) tomee.bat complains about 'input line too long' when deploying big projects
[ https://issues.apache.org/jira/browse/TOMEE-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1525: -- Fix Version/s: (was: 7.0.4) 7.0.5 > tomee.bat complains about 'input line too long' when deploying big projects > --- > > Key: TOMEE-1525 > URL: https://issues.apache.org/jira/browse/TOMEE-1525 > Project: TomEE > Issue Type: Bug >Affects Versions: 7.0.0 > Environment: Windows. >Reporter: Mark Struberg > Fix For: 7.0.5 > > > tomee.bat complains about 'input line too long' when deploying big projects > This comes from using -cp on the command to start the jvm. But if there are > too many classpath entries then the commandline exceeds the limit of 8k. > We should use the environment variable CLASSPATH instead. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1313: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Ensure full support of JSR-322 Java EE Connector Architecture 1.7 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1378) @Override annotations should be used wherever necessary
[ https://issues.apache.org/jira/browse/TOMEE-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1378: -- Fix Version/s: (was: 7.0.4) 7.0.5 > @Override annotations should be used wherever necessary > --- > > Key: TOMEE-1378 > URL: https://issues.apache.org/jira/browse/TOMEE-1378 > Project: TomEE > Issue Type: Improvement >Reporter: Daniel Kasmeroglu >Priority: Minor > Fix For: 7.0.5 > > Attachments: override.patch > > > Overriding methods should be annotated with _@Override_ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1305: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Ensure full support of JSR-344 JavaServer Faces 2.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1314: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Ensure full support of JSR-338 Java Persistence 2.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1300: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Support JSON JSR 353 - Java API for JSON Processing (JSON-P) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1636) BrokerXmlConfig xbean:file: does not accept a relative path
[ https://issues.apache.org/jira/browse/TOMEE-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1636: -- Fix Version/s: (was: 7.0.4) 7.0.5 > BrokerXmlConfig xbean:file: does not accept a relative path > --- > > Key: TOMEE-1636 > URL: https://issues.apache.org/jira/browse/TOMEE-1636 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.2 > Environment: NA >Reporter: Andy Gumbrecht > Fix For: 7.0.5 > > > BrokerXmlConfig xbean:file:conf/activemq.xml resolves to the TomEE bin > directory. > BrokerXmlConfig xbean:file:../conf/activemq.xml fails. > TomEE should parse and resolve the file path as XBean seems to not use a > canonical path to reference this file. > Possibly worth creating an xbean-spring issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1397) Invalid web.xml in example project
[ https://issues.apache.org/jira/browse/TOMEE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1397: -- Fix Version/s: (was: 7.0.4) 7.0.5 > Invalid web.xml in example project > -- > > Key: TOMEE-1397 > URL: https://issues.apache.org/jira/browse/TOMEE-1397 > Project: TomEE > Issue Type: Bug >Affects Versions: 7.0.0 >Reporter: Daniel Kasmeroglu >Priority: Minor > Fix For: 7.0.5 > > Attachments: tomee-1397.patch > > > The _web.xml_ specifies the value _Transactional_ for a > _persistence-context-type_ which is incorrect as it should be _Transaction_ . > The corresponding commit on my local git could be found on: > * > https://kasisoft.com/stash/projects/TOMEE/repos/tomee/commits/88315131c9b804fe166c2a909cd749768ab45eef -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1307: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Ensure full support of JSR-339 The Java API for RESTful Web Services 2.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1310: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Ensure full support of JSR-318 Interceptors 1.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1417) [TEST] Incorrect test function PropertiesTest assertTest
[
https://issues.apache.org/jira/browse/TOMEE-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Gumbrecht updated TOMEE-1417:
--
Fix Version/s: (was: 7.0.4)
7.0.5
> [TEST] Incorrect test function PropertiesTest assertTest
>
>
> Key: TOMEE-1417
> URL: https://issues.apache.org/jira/browse/TOMEE-1417
> Project: TomEE
> Issue Type: Improvement
>Affects Versions: 7.0.0
>Reporter: Daniel Kasmeroglu
>Priority: Trivial
> Fix For: 7.0.5
>
>
> The helper function _PropertiesTest$assertProperties_ contains an invalid
> comparison for a different property:
> {code:java}
> if (expectedValue != expectedValue && (expectedValue == null ||
> !expectedValue.equals(actual))) {
> ...
> }
> {code}
> The comparison *expectedValue != expectedValue* obviously always returns
> false so the contained code will never be executed.
> Furthermore the only use cases of this function returns at it's entry due to
> the fact that the supplied parameters are always equal.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1291: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > Attachments: TOMEE-1291.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1286: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Intermittent test failure org.apache.openejb.itest.legacy.LegacyClientTest -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1312: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Ensure full support of JSR-345 Enterprise JavaBeansTM 3.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2110) DefaultContextService missing like default resource.
[ https://issues.apache.org/jira/browse/TOMEE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2110: -- Fix Version/s: (was: 7.0.4) 7.0.5 > DefaultContextService missing like default resource. > > > Key: TOMEE-2110 > URL: https://issues.apache.org/jira/browse/TOMEE-2110 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 7.0.4 >Reporter: Daniel Cunha > Fix For: 7.0.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1287: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Intermittent test failure org.apache.openejb.server.ssh.SSHServerTest -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1308: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Ensure full support of JSR-340 Java Servlet 3.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1614) Netbeans Tomcat Plugin Integration Does Not Detected TomeeStarted
[ https://issues.apache.org/jira/browse/TOMEE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1614: -- Fix Version/s: (was: 7.0.4) 7.0.5 > Netbeans Tomcat Plugin Integration Does Not Detected TomeeStarted > - > > Key: TOMEE-1614 > URL: https://issues.apache.org/jira/browse/TOMEE-1614 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 1.7.3 > Environment: Ubuntu 14 LTS Netbeans latest release >Reporter: Nuno G. de M >Priority: Minor > Fix For: 7.0.5 > > > Download the latest TOMEE Plume snapshot release. > http://repository.apache.org/content/groups/snapshots/org/apache/openejb/apache-tomee/1.7.3-SNAPSHOT/ > After that, open your netbeans and on the Services tab add a new Server of > type Tomcat or TOMEE. > Point to the folder where the snapshort tar.gz got extracted. > Setup a user with the proper rights to administer tomee. > for example > roles="tomcat,tomee-admin,manager-gui,manager-script,admin" username="admin"/> > Now click start on the tomee server. > Tomee quickly starts, but the plugin stays active forever stating: > Waiting for tomcat to start. > After a while the plugin will show an alert stating that the server failed to > start. > The server started fine. > NOTE: > THe netbeans tomee plugin has a second bug that should be filed under a > different bug report. > Which is, when you deploy an application that breaks during deployment, an > infinite loop of tomcat trying to repdeploy the broken application will take > place. > I am leting you know of this second as right now I do not have the > opprotunity to make you a sample application to reproduce the problem, and > therefore will not open a bug report. > Kindest regards. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1395) Invalid package in example: simple-mdb-with-descriptor
[ https://issues.apache.org/jira/browse/TOMEE-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1395: -- Fix Version/s: (was: 7.0.4) 7.0.5 > Invalid package in example: simple-mdb-with-descriptor > -- > > Key: TOMEE-1395 > URL: https://issues.apache.org/jira/browse/TOMEE-1395 > Project: TomEE > Issue Type: Bug >Affects Versions: 7.0.0 >Reporter: Daniel Kasmeroglu >Priority: Minor > Fix For: 7.0.5 > > Attachments: tomee-1395.patch > > > Just an invalid package name. A corresponding diff can be found here: > https://kasisoft.com/stash/projects/TOMEE/repos/tomee/commits/e8f8d08b5733bd93a090fe2ff9e5dbe7f95f817e -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1666: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > 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.4.14#64029)
[jira] [Updated] (TOMEE-1419) [CQ] Removal and cleanup of redundant and unnecessary expressions
[
https://issues.apache.org/jira/browse/TOMEE-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Gumbrecht updated TOMEE-1419:
--
Fix Version/s: (was: 7.0.4)
7.0.5
> [CQ] Removal and cleanup of redundant and unnecessary expressions
> -
>
> Key: TOMEE-1419
> URL: https://issues.apache.org/jira/browse/TOMEE-1419
> Project: TomEE
> Issue Type: Improvement
>Affects Versions: 7.0.0
>Reporter: Daniel Kasmeroglu
>Priority: Minor
> Fix For: 7.0.5
>
>
> The codebase currently contains several needless expressions like f.e.
> {code:java}
> File f = ...
> if(f.exists() && f.isFile()) { -> if(f.isFile()) {
>...
> }
> {code}
> {code:java}
> URLS.uri(module.getModuleId()) -> module.getModuleUri()
> {code}
> There are many more examples which I won't list here. These should be cleaned
> up.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (TOMEE-1908) Proxy for JCA connections does not implement interface
[ https://issues.apache.org/jira/browse/TOMEE-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1908: -- Fix Version/s: (was: 7.0.4) 7.0.5 > Proxy for JCA connections does not implement interface > -- > > Key: TOMEE-1908 > URL: https://issues.apache.org/jira/browse/TOMEE-1908 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 7.0.0, 7.0.1 >Reporter: Kilian Matt >Assignee: Romain Manni-Bucau > Labels: patch-available > Fix For: 7.0.5 > > Attachments: AutoConnectionTrackerTest.java, TOMEE-1908.patch > > > When the connection implementation of a JCA resource adapter does not contain > any implements clauses in the class declaration, the proxy will not implement > any interfaces. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1683: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > 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.4.14#64029)
[jira] [Updated] (TOMEE-1697) javamail: sending email fails
[
https://issues.apache.org/jira/browse/TOMEE-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Gumbrecht updated TOMEE-1697:
--
Fix Version/s: (was: 7.0.4)
7.0.5
> javamail: sending email fails
> -
>
> Key: TOMEE-1697
> URL: https://issues.apache.org/jira/browse/TOMEE-1697
> Project: TomEE
> Issue Type: Bug
>Affects Versions: 1.7.3
> Environment: Linux (Ubuntu 14.04.3 LTS), Oracle Java 1.8.0_66
>Reporter: Tamás Greguss
> Fix For: 7.0.5
>
>
> Sending email fails. javamail's Transport.send(...) function throws an
> exception. The same code works fine with previous versions of TomEE which
> includes javamail 1.8.3. But TomEE 1.7.3 upgraded to javamail 1.9.0-alpha2
> which does not work well.
> If in TomEE 1.7.3 lib folder I change the content of
> geronimo-javamail_1.4_mail-1.9.0-alpha-2.jar file to the previous
> geronimo-javamail_1.4_mail-1.8.3.jar, it also works well.
> Here is the code that works fine with sendmail 1.8.3 in TomEE 1.7.1 but fails
> with sendmail.1.9.0-alpha2 in TomEE 1.7.3:
> (This is a low level code only. But using apache commons email library which
> uses java.mail in the background, also fails.)
> {code:title=MailSender.java|borderStyle=solid}
> public static void SendWithGMailSSL( String email_to, String subject, String
> text, String email_from, final String senderuser, final String senderpass ) {
> Properties props = new Properties();
> props.put("mail.smtp.host", "smtp.gmail.com");
> props.put("mail.smtp.socketFactory.port", "465");
> props.put("mail.smtp.socketFactory.class",
> "javax.net.ssl.SSLSocketFactory");
> props.put("mail.smtp.auth", "true");
> props.put("mail.smtp.port", "465");
> Session session;
> try {
> session = Session.getInstance(props, new
> javax.mail.Authenticator() {
> @Override
> protected PasswordAuthentication
> getPasswordAuthentication() {
> return new PasswordAuthentication(senderuser,
> senderpass);
> }
> });
> } catch (Exception e) {
> throw new RuntimeException(e);
> }
> try {
> Message message = new MimeMessage(session);
> message.setFrom(new InternetAddress(email_from));
> message.setRecipients(Message.RecipientType.TO,
> InternetAddress.parse(email_to));
> message.setSubject(subject);
> message.setText(text);
> Transport.send(message);
> //System.out.println("e-mail sending done.");
> } catch (MessagingException e) {
> throw new RuntimeException(e);
> }
> }
> {code}
> The calling of Transport.send(message) throws an exception:
> {noformat}
> javax.mail.SendFailedException: Send failure (javax.mail.MessagingException:
> Connection error (java.io.IOException: Error connecting to smtp.gmail.com,
> 465))
> at javax.mail.Transport.send(Transport.java:163)
> at javax.mail.Transport.send(Transport.java:48)
> at com.gbit.lib.GBITMail.SendWithGMailSSL(GBITMail.java:136)
> at com.gbit.lib.GBITMail.SendMail(GBITMail.java:103)
> at
> com.gbit.efoglalo.test.UnitTestMB.testSendingEmailOld(UnitTestMB.java:503)
> at
> com.gbit.efoglalo.test.UnitTestMB$$OwbNormalScopeProxy0.testSendingEmailOld(com/gbit/efoglalo/test/UnitTestMB.java)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.apache.el.parser.AstValue.invoke(AstValue.java:278)
> at
> org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:273)
> at
> org.apache.myfaces.view.facelets.el.ContextAwareTagMethodExpression.invoke(ContextAwareTagMethodExpression.java:96)
> at
> javax.faces.event.MethodExpressionActionListener.processAction(MethodExpressionActionListener.java:88)
> at javax.faces.event.ActionEvent.processListener(ActionEvent.java:51)
> at
> javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:420)
> at javax.faces.component.UICommand.broadcast(UICommand.java:103)
> at javax.faces.component.UIViewRoot._broadcastAll(UIViewRoot.java:1041)
> at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:289)
> at javax.faces.component.UIViewRoot._process(UIViewRoot.java:1415)
> at
> javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:765)
> at
>
[jira] [Updated] (TOMEE-1985) SessionBean ejbCreate invoked potentially twice
[
https://issues.apache.org/jira/browse/TOMEE-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Gumbrecht updated TOMEE-1985:
--
Fix Version/s: (was: 7.0.4)
7.0.5
> SessionBean ejbCreate invoked potentially twice
> ---
>
> Key: TOMEE-1985
> URL: https://issues.apache.org/jira/browse/TOMEE-1985
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 1.7.4, 7.0.2
>Reporter: David Blevins
>Assignee: David Blevins
> Fix For: 1.7.5, 7.0.5
>
>
> When an EJB 2.x style Stateless session bean implements the
> {{javax.ejb.SessionBean}} interface, the "ejbCreate" method is invoked twice
> if the method signature is {{public void ejbCreate()}}
> If the method signature is {{public void ejbCreateObject()}} or otherwise has
> a suffix as is allowed in the EJB spec, it is only invoked once as intended.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (TOMEE-2091) NetworkUtilTest
[ https://issues.apache.org/jira/browse/TOMEE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2091: -- Fix Version/s: (was: 7.0.4) 7.0.5 > NetworkUtilTest > --- > > Key: TOMEE-2091 > URL: https://issues.apache.org/jira/browse/TOMEE-2091 > Project: TomEE > Issue Type: Bug > Components: TomEE Build >Affects Versions: 1.7.4, 7.0.3 >Reporter: Jonathan Gallimore >Assignee: Jonathan Gallimore > Fix For: 1.7.5, 7.0.5 > > > This test seems to fail occasionally: > Running org.apache.openejb.util.NetworkUtilTest > Exception in thread "test-thread-20" java.lang.AssertionError: Got a > duplicate port with ten seconds > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.openejb.util.NetworkUtilTest$1.run(NetworkUtilTest.java:68) > at java.lang.Thread.run(Thread.java:745) > Machine safe port list = [1025, 1026, 1027, 1028, 1029, 1030, 1031, 1032, > 1033, 1034, 1035, 1036, 1037, 1038, 1039, 1040, 1041, 1042, 1043, 1044] > Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.305 sec > <<< FAILURE! - in org.apache.openejb.util.NetworkUtilTest > testNext(org.apache.openejb.util.NetworkUtilTest) Time elapsed: 15.019 sec > <<< FAILURE! > java.lang.AssertionError > at > org.apache.openejb.util.NetworkUtilTest.testNext(NetworkUtilTest.java:82) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1323: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Ensure full support of JSR-919 JavaMail 1.5 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1318: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Drop or deprecate EJB Entity Beans Support -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2044) threadPool-queue (in ServicePool) from ejbd-Service is never processed
[ https://issues.apache.org/jira/browse/TOMEE-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2044: -- Fix Version/s: (was: 7.0.4) 7.0.5 > threadPool-queue (in ServicePool) from ejbd-Service is never processed > --- > > Key: TOMEE-2044 > URL: https://issues.apache.org/jira/browse/TOMEE-2044 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 1.7.4 > Environment: FreeBSD 10.3-STABLE amd64 > openjdk8-8.131.11 >Reporter: Lars Herschke > Fix For: 7.0.5 > > > If you have many requests to your ejbd-service the queue from the threadPool > in ServicePool.java is filled. This queue is never processed depending on > your server config. If you have only ejbd-service enabled and the services > admin, ejbds and httpejbd are disabled all is fine. If you have two or more > of these services enabled the issue could occur. The reason is the following. > KeepAliveServer.java has the following line to get the queue. > final ServicePool incoming = > SystemInstance.get().getComponent(ServicePool.class); > SystemInstance.java hold components in a HahMap with the class type as key. > On server-startup the above named services are initalized in > ServiceManager.manage(...). This method instances new ServicePool for this > services. Each ServicePool-instance calls in his constructor > SystemInstance.get().setComponent(ServicePool.class, this);. > Every other call of setComponent replace the old entry in the components > HashMap. So KeepAliveServer gets always the queue of the last initalized > service. > Workaround: > Use only one of the four above named services > or > set threadsCore for your services at least as high, that the queue is never > used. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1867) Investigate FileNotFoundException warning
[ https://issues.apache.org/jira/browse/TOMEE-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1867: -- Fix Version/s: (was: 7.0.4) 7.0.5 > Investigate FileNotFoundException warning > - > > Key: TOMEE-1867 > URL: https://issues.apache.org/jira/browse/TOMEE-1867 > Project: TomEE > Issue Type: Task >Affects Versions: 1.7.4 > Environment: Windows >Reporter: Andy Gumbrecht >Priority: Trivial > Fix For: 1.7.5, 7.0.5 > > > Only a warning, but wondering why this broken path is generated: > 2016-07-15 11:00:35 WARN FileZippedJarVisitor:74 - HHH015010: Unable to find > file (ignored): > file:/C:/Integration/workspace/project/project-service-impl/jar:file:/C:/repository/com/company/division/app/app-service-impl/1.2.3/app-service-impl-1.2.3.jar!/META-INF/persistence.xml > java.io.FileNotFoundException: > C:\Integration\workspace\project\project-service-impl\jar:file:\C:\repository\com\company\division\app\app-service-impl\1.2.3\app-service-impl-1.2.3.jar!\META-INF\persistence.xml > (Die Syntax für den Dateinamen, Verzeichnisnamen oder die > Datenträgerbezeichnung ist falsch) > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.(ZipFile.java:215) > at java.util.zip.ZipFile.(ZipFile.java:145) > at java.util.jar.JarFile.(JarFile.java:154) > at java.util.jar.JarFile.(JarFile.java:91) > at > org.hibernate.ejb.packaging.FileZippedJarVisitor.doProcessElements(FileZippedJarVisitor.java:70) > at > org.hibernate.ejb.packaging.AbstractJarVisitor.getMatchingEntries(AbstractJarVisitor.java:149) > at > org.hibernate.ejb.packaging.NativeScanner.getClassesInJar(NativeScanner.java:128) > at > org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:488) > at > org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:862) > at > org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:607) > at > org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:75) > at > org.apache.openejb.assembler.classic.EntityManagerFactoryCallable.call(EntityManagerFactoryCallable.java:64) > at > org.apache.openejb.assembler.classic.ReloadableEntityManagerFactory.createDelegate(ReloadableEntityManagerFactory.java:116) > at > org.apache.openejb.assembler.classic.ReloadableEntityManagerFactory.(ReloadableEntityManagerFactory.java:102) > at > org.apache.openejb.assembler.classic.PersistenceBuilder.createEntityManagerFactory(PersistenceBuilder.java:154) > at > org.apache.openejb.assembler.classic.Assembler.loadPersistenceUnits(Assembler.java:985) > at > org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:744) > at > org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:680) > at > org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:676) > at > org.apache.openejb.testing.ApplicationComposers.before(ApplicationComposers.java:830) > at > org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:984) > at > org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1401) Invalid module lookup of OpenEJBDeploymentManager
[ https://issues.apache.org/jira/browse/TOMEE-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1401: -- Fix Version/s: (was: 7.0.4) 7.0.5 > Invalid module lookup of OpenEJBDeploymentManager > - > > Key: TOMEE-1401 > URL: https://issues.apache.org/jira/browse/TOMEE-1401 > Project: TomEE > Issue Type: Bug >Affects Versions: 7.0.0 >Reporter: Daniel Kasmeroglu > Fix For: 7.0.5 > > Attachments: tomee-1401.patch > > > There is an error in the following methods: > * getAvailableModules > * getRunningModules > * getNonRunningModules > The error makes the parameter _moduleType_ useless as it's basically ignored. > I suspect that this is the result of an incomplete refactoring attempt. > See: > https://kasisoft.com/stash/projects/TOMEE/repos/tomee/commits/b10129e0f66277e003c7ed9f5912faf1f4c65b78 > Apart from that these methods are basically all equal so they could be > combined into a single method (I didn't do that to keep the diff readable). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1319: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Drop or deprecate JAX-RPC 1.1 Support -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1461: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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: 7.0.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] Andy Gumbrecht updated TOMEE-1302: -- Fix Version/s: (was: 7.0.4) 7.0.5 > 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.5 > > > Support JSR 236 - Concurrency Utilities for Java EE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1945) extract TomEEEmbeddedSingleRunner logic in org.apache.tomee.embedded.TomEEEmbeddedApplicationRunner
[
https://issues.apache.org/jira/browse/TOMEE-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Gumbrecht updated TOMEE-1945:
--
Fix Version/s: (was: 7.0.4)
7.0.5
> extract TomEEEmbeddedSingleRunner logic in
> org.apache.tomee.embedded.TomEEEmbeddedApplicationRunner
> ---
>
> Key: TOMEE-1945
> URL: https://issues.apache.org/jira/browse/TOMEE-1945
> Project: TomEE
> Issue Type: New Feature
>Reporter: Romain Manni-Bucau
>Assignee: Romain Manni-Bucau
> Fix For: 7.0.5
>
>
> Goal is to ensure this is reusable not only for tests:
> {code:java}
> @Application
> @Classes(context = "app")
> public class MyApp {
> public static void main(final String[] args) {
> TomEEEmbeddedApplicationRunner.run(new MyApp(), args);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (TOMEE-1416) [CQ] Removal of unnecessary null checks.
[ https://issues.apache.org/jira/browse/TOMEE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1416: -- Fix Version/s: (was: 7.0.4) 7.0.5 > [CQ] Removal of unnecessary null checks. > > > Key: TOMEE-1416 > URL: https://issues.apache.org/jira/browse/TOMEE-1416 > Project: TomEE > Issue Type: Improvement >Affects Versions: 7.0.0 >Reporter: Daniel Kasmeroglu >Priority: Minor > Fix For: 7.0.5 > > > There are several locations where variables are definitely _null_ or _not > null_ . These locations should be cleaned up. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-1618) Replace three register maps in Container in favour of one
[ https://issues.apache.org/jira/browse/TOMEE-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1618: -- Fix Version/s: (was: 7.0.4) 7.0.5 > Replace three register maps in Container in favour of one > - > > Key: TOMEE-1618 > URL: https://issues.apache.org/jira/browse/TOMEE-1618 > Project: TomEE > Issue Type: Improvement > Components: TomEE Core Server >Affects Versions: 7.0.0 >Reporter: Alex >Assignee: Alex >Priority: Trivial > Labels: newbie > Fix For: 7.0.5 > > > The class org.apache.tomee.embedded.Container currently uses three internal > ly managed maps to register following information: > moduleIds, appContexts and appInfos. > The key used in each of the map is the name of the application. > The suggested improvement is to introduce a multimap. I think however, it > would be cleaner to define an inner class that can hold the information > above, and have one map that maps the name to an instance of this class. > Drawback is an extra null check, but overall I think this better. > Additionally, this class does not have many unittests so I'd like to add > those as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOMEE-2129) CXF 3.1.13
[ https://issues.apache.org/jira/browse/TOMEE-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht resolved TOMEE-2129. --- Resolution: Fixed > CXF 3.1.13 > -- > > Key: TOMEE-2129 > URL: https://issues.apache.org/jira/browse/TOMEE-2129 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 7.0.3 >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht > Fix For: 7.0.4 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2129) CXF 3.1.13
[ https://issues.apache.org/jira/browse/TOMEE-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2129 started by Andy Gumbrecht. - > CXF 3.1.13 > -- > > Key: TOMEE-2129 > URL: https://issues.apache.org/jira/browse/TOMEE-2129 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 7.0.3 >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht > Fix For: 7.0.4 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2129) CXF 3.1.13
Andy Gumbrecht created TOMEE-2129: - Summary: CXF 3.1.13 Key: TOMEE-2129 URL: https://issues.apache.org/jira/browse/TOMEE-2129 Project: TomEE Issue Type: Dependency upgrade Affects Versions: 7.0.3 Reporter: Andy Gumbrecht Assignee: Andy Gumbrecht Fix For: 7.0.4 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2128) Axiom 1.2.20
Andy Gumbrecht created TOMEE-2128: - Summary: Axiom 1.2.20 Key: TOMEE-2128 URL: https://issues.apache.org/jira/browse/TOMEE-2128 Project: TomEE Issue Type: Dependency upgrade Affects Versions: 7.0.3 Reporter: Andy Gumbrecht Assignee: Andy Gumbrecht Priority: Trivial Fix For: 7.0.4 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOMEE-2128) Axiom 1.2.20
[ https://issues.apache.org/jira/browse/TOMEE-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht resolved TOMEE-2128. --- Resolution: Fixed > Axiom 1.2.20 > > > Key: TOMEE-2128 > URL: https://issues.apache.org/jira/browse/TOMEE-2128 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 7.0.3 >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Trivial > Fix For: 7.0.4 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOMEE-2127) Xalan 2.7.2
[ https://issues.apache.org/jira/browse/TOMEE-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht resolved TOMEE-2127. --- Resolution: Fixed > Xalan 2.7.2 > --- > > Key: TOMEE-2127 > URL: https://issues.apache.org/jira/browse/TOMEE-2127 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 7.0.3 >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Trivial > Fix For: 7.0.4 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2127) Xalan 2.7.2
Andy Gumbrecht created TOMEE-2127: - Summary: Xalan 2.7.2 Key: TOMEE-2127 URL: https://issues.apache.org/jira/browse/TOMEE-2127 Project: TomEE Issue Type: Dependency upgrade Affects Versions: 7.0.3 Reporter: Andy Gumbrecht Assignee: Andy Gumbrecht Priority: Trivial Fix For: 7.0.4 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2121) Add system property 'openejb.deployer.repository' to ProvisioningUtil
[ https://issues.apache.org/jira/browse/TOMEE-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2121: -- Description: Add system property 'openejb.deployer.repository' and 'openejb.deployer.snapshots.repository' to ProvisioningUtil to allow override of the hard coded repositories. 7.x has a new impl, but legacy still needs this. was: Add system property 'openejb.deployer.repository' to ProvisioningUtil to allow override of the hard coded repositories. 7.x has a new impl, but legacy still needs this. > Add system property 'openejb.deployer.repository' to ProvisioningUtil > - > > Key: TOMEE-2121 > URL: https://issues.apache.org/jira/browse/TOMEE-2121 > Project: TomEE > Issue Type: New Feature >Affects Versions: 1.7.4, 7.0.3 >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Minor > Fix For: 1.7.5, 7.0.4 > > > Add system property 'openejb.deployer.repository' and > 'openejb.deployer.snapshots.repository' to ProvisioningUtil to allow override > of the hard coded repositories. > 7.x has a new impl, but legacy still needs this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOMEE-2121) Add system property 'openejb.deployer.repository' to ProvisioningUtil
[ https://issues.apache.org/jira/browse/TOMEE-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht resolved TOMEE-2121. --- Resolution: Done > Add system property 'openejb.deployer.repository' to ProvisioningUtil > - > > Key: TOMEE-2121 > URL: https://issues.apache.org/jira/browse/TOMEE-2121 > Project: TomEE > Issue Type: New Feature >Affects Versions: 1.7.4, 7.0.3 >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Minor > Fix For: 1.7.5, 7.0.4 > > > Add system property 'openejb.deployer.repository' and > 'openejb.deployer.snapshots.repository' to ProvisioningUtil to allow override > of the hard coded repositories. > 7.x has a new impl, but legacy still needs this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2121) Add system property 'openejb.deployer.repository' to ProvisioningUtil
[ https://issues.apache.org/jira/browse/TOMEE-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2121: -- Description: Add system property 'openejb.deployer.repository' to ProvisioningUtil to allow override of the hard coded repositories. 7.x has a new impl, but legacy still needs this. was: Add system property 'openejb.deployer.repository' to ProvisioningUtil to allow override of the hard coded repositories. 7.x has a new impl. > Add system property 'openejb.deployer.repository' to ProvisioningUtil > - > > Key: TOMEE-2121 > URL: https://issues.apache.org/jira/browse/TOMEE-2121 > Project: TomEE > Issue Type: New Feature >Affects Versions: 1.7.4, 7.0.4 >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Minor > Fix For: 1.7.5 > > > Add system property 'openejb.deployer.repository' to ProvisioningUtil to > allow override of the hard coded repositories. > 7.x has a new impl, but legacy still needs this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2121) Add system property 'openejb.deployer.repository' to ProvisioningUtil
[ https://issues.apache.org/jira/browse/TOMEE-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2121: -- Affects Version/s: 7.0.4 > Add system property 'openejb.deployer.repository' to ProvisioningUtil > - > > Key: TOMEE-2121 > URL: https://issues.apache.org/jira/browse/TOMEE-2121 > Project: TomEE > Issue Type: New Feature >Affects Versions: 1.7.4, 7.0.4 >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Minor > Fix For: 1.7.5 > > > Add system property 'openejb.deployer.repository' to ProvisioningUtil to > allow override of the hard coded repositories. > 7.x has a new impl. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2121) Add system property 'openejb.deployer.repository' to ProvisioningUtil
[ https://issues.apache.org/jira/browse/TOMEE-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2121: -- Description: Add system property 'openejb.deployer.repository' to ProvisioningUtil to allow override of the hard coded repositories. 7.x has a new impl. was:Add system property 'openejb.deployer.repository' to ProvisioningUtil to allow override of the hard coded repositories > Add system property 'openejb.deployer.repository' to ProvisioningUtil > - > > Key: TOMEE-2121 > URL: https://issues.apache.org/jira/browse/TOMEE-2121 > Project: TomEE > Issue Type: New Feature >Affects Versions: 1.7.4 >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Minor > Fix For: 1.7.5 > > > Add system property 'openejb.deployer.repository' to ProvisioningUtil to > allow override of the hard coded repositories. > 7.x has a new impl. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2121) Add system property 'openejb.deployer.repository' to ProvisioningUtil
[ https://issues.apache.org/jira/browse/TOMEE-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2121: -- Affects Version/s: (was: 7.0.3) > Add system property 'openejb.deployer.repository' to ProvisioningUtil > - > > Key: TOMEE-2121 > URL: https://issues.apache.org/jira/browse/TOMEE-2121 > Project: TomEE > Issue Type: New Feature >Affects Versions: 1.7.4 >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Minor > Fix For: 1.7.5 > > > Add system property 'openejb.deployer.repository' to ProvisioningUtil to > allow override of the hard coded repositories -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2121) Add system property 'openejb.deployer.repository' to ProvisioningUtil
[ https://issues.apache.org/jira/browse/TOMEE-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2121: -- Fix Version/s: (was: 7.0.4) > Add system property 'openejb.deployer.repository' to ProvisioningUtil > - > > Key: TOMEE-2121 > URL: https://issues.apache.org/jira/browse/TOMEE-2121 > Project: TomEE > Issue Type: New Feature >Affects Versions: 1.7.4 >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Minor > Fix For: 1.7.5 > > > Add system property 'openejb.deployer.repository' to ProvisioningUtil to > allow override of the hard coded repositories -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2121) Add system property 'openejb.deployer.repository' to ProvisioningUtil
[ https://issues.apache.org/jira/browse/TOMEE-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2121: -- Description: Add system property 'openejb.deployer.repository' to ProvisioningUtil to allow override of the hard coded repositories (was: Add system property 'org.apache.openejb.loader.repository' to ProvisioningUtil to allow override of the hard coded repositories) > Add system property 'openejb.deployer.repository' to ProvisioningUtil > - > > Key: TOMEE-2121 > URL: https://issues.apache.org/jira/browse/TOMEE-2121 > Project: TomEE > Issue Type: New Feature >Affects Versions: 1.7.4, 7.0.3 >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Minor > Fix For: 1.7.5, 7.0.4 > > > Add system property 'openejb.deployer.repository' to ProvisioningUtil to > allow override of the hard coded repositories -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2121) Add system property 'org.apache.openejb.loader.repository' to ProvisioningUtil
[ https://issues.apache.org/jira/browse/TOMEE-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2121 started by Andy Gumbrecht. - > Add system property 'org.apache.openejb.loader.repository' to ProvisioningUtil > -- > > Key: TOMEE-2121 > URL: https://issues.apache.org/jira/browse/TOMEE-2121 > Project: TomEE > Issue Type: New Feature >Affects Versions: 1.7.4, 7.0.3 >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Minor > Fix For: 1.7.5, 7.0.4 > > > Add system property 'org.apache.openejb.loader.repository' to > ProvisioningUtil to allow override of the hard coded repositories -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066119#comment-16066119 ] Andy Gumbrecht commented on TOMEE-2078: --- [~ivanjunckes], I'll attempt to reapply the patch and stage them for review tonight. > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: mobbing.pdf, tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066117#comment-16066117 ] Andy Gumbrecht commented on TOMEE-2078: --- You made absolutely no attempt to work with me on this ticket [~romain.manni-bucau], so there was nothing to give up on. Actually deleting or resetting someone else's work in progress in a staging environment within minutes of the the commit is something other people just don't do. Not in OSS, or any other working environment. You do it consistently to myself and others. That is not called working with someone, rather actively against them. The result of this ticket should have been a staged site for others to review, under a vote - That is what the staging is for. You do not get to dictate on, only suggest and vote on, points of contention. To claim I don't care about TomEE working is obviously just you clutching at straws simply to make an insult, that statement is simply ridiculous, does not make sense and is not fact based. If I break the build I always ensure it is fixed or revert in my own time, to claim anything else is also a lie pertaining to an insult void of fact. You are perfectly legitimate in pointing out that a build is broken to any contributor, but never to simply overwrite or trash the work. That is what you consistently do, and it makes it impossible for the contributor to fix it when you do that. I have to admit that I do give up, as do most others, when you hijack an issue, which is very nearly every time. Just look at this issue - You made it a hostile environment within one minute, and we're supposed to be here for fun. Why should I invest one second of my time? And before you say it, you didn't and shouldn't need to invest one second of your time to a ticket that was in progress by someone else unless you're invited to do so. This would be called the review process. The buildbot provides the evidence as to how often the build is broken, by who, and when it is fixed. But in this case we're even only talking about a staging environment. The difference is that you felt it your right to trash peoples work in progress. You don't mean to be arrogant when you do that I'm sure, but I am telling you it is, and it must stop. I have never in my entire life willingly or actively trashed work done by others, and fully understand that the build gets broken and people need time to fix it <-- This is the issue here and you need to address it. You must allow people to breath on this project or you will surround yourself with friction. That cannot be a nice feeling? The work will continue on this ticket as is until the review process is complete. I do not expect any more interference from you until we request your review of the staging site. You can continue to play ping pong on this thread, as I'm sure you will. This is my last comment to you on it at least. You trashed a work in progress by others. Whereby others would never dream of trashing your or anyone else's work. > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: mobbing.pdf, tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2079) Escalate this story ticket as an example to Apache.org of the current state of mobbing on the TomEE project.
[ https://issues.apache.org/jira/browse/TOMEE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2079 started by Andy Gumbrecht. - > Escalate this story ticket as an example to Apache.org of the current state > of mobbing on the TomEE project. > > > Key: TOMEE-2079 > URL: https://issues.apache.org/jira/browse/TOMEE-2079 > Project: TomEE > Issue Type: Sub-task >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (TOMEE-2080) Reapply patch and review on staging when mobbing issues have been resolved
[ https://issues.apache.org/jira/browse/TOMEE-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht reassigned TOMEE-2080: - Assignee: Andy Gumbrecht > Reapply patch and review on staging when mobbing issues have been resolved > -- > > Key: TOMEE-2080 > URL: https://issues.apache.org/jira/browse/TOMEE-2080 > Project: TomEE > Issue Type: Sub-task >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2080) Reapply patch and review on staging when mobbing issues have been resolved
Andy Gumbrecht created TOMEE-2080: - Summary: Reapply patch and review on staging when mobbing issues have been resolved Key: TOMEE-2080 URL: https://issues.apache.org/jira/browse/TOMEE-2080 Project: TomEE Issue Type: Sub-task Reporter: Andy Gumbrecht -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-2078: -- Attachment: mobbing.pdf Record of mobbing to prevent deletion. > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: mobbing.pdf, tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOMEE-2079) Escalate this story ticket as an example to Apache.org of the current state of mobbing on the TomEE project.
Andy Gumbrecht created TOMEE-2079: - Summary: Escalate this story ticket as an example to Apache.org of the current state of mobbing on the TomEE project. Key: TOMEE-2079 URL: https://issues.apache.org/jira/browse/TOMEE-2079 Project: TomEE Issue Type: Sub-task Reporter: Andy Gumbrecht Assignee: Andy Gumbrecht Priority: Critical -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065733#comment-16065733 ] Andy Gumbrecht commented on TOMEE-2078: --- You polluted the contribution yourself by suffocating the work on it by your utterly arrogant actions. You were NOT assigned this ticket. You arrogantly hijacked it while I was in the process of fixing/working it. The 'target' directory was not previously ignored, a very common and simple to resolve error. You simply did this to destroy the community effort for your own very selfish needs, which I fail to understand because I could NEVER delete some's work without asking, EVER! You simply have no empathy for other people whatsoever and actively seek to provoke a negative environment or response - arrogantly trashing other peoples work without asking will ALWAYS invoke an angry response. You either enjoy this response, or do not have it in you to learn this simple thing. I believe you have an obvious ulterior motive for this given your conflict of interests. You make unfounded slanderous claims of blindly applying patches because you are arrogant. I spent over an hour with Ivan in a screenshare, that's not blind. Your attitude is blind. > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065605#comment-16065605 ] Andy Gumbrecht commented on TOMEE-2078: --- I was pushing it to stage for others to review. Not just the one man show. > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065508#comment-16065508 ] Andy Gumbrecht edited comment on TOMEE-2078 at 6/27/17 10:28 PM: - Thanks Ivan - This is a nice improvement was (Author: andyg): Thanks Ivan - This is nice improvement > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065580#comment-16065580 ] Andy Gumbrecht commented on TOMEE-2078: --- No Romain. This ticket was flagged, and with your usual arrogance you just trash other peoples work. I was in the process of reviewing it. Pushing to stage is perfectly valid. This is simply not acceptable. > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065581#comment-16065581 ] Andy Gumbrecht commented on TOMEE-2078: --- I will be escalating this incident. > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065574#comment-16065574 ] Andy Gumbrecht commented on TOMEE-2078: --- On what planet is this acceptable? > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065571#comment-16065571 ] Andy Gumbrecht commented on TOMEE-2078: --- This ticket is in progress, and I was working on it. How dare you! > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065559#comment-16065559 ] Andy Gumbrecht edited comment on TOMEE-2078 at 6/27/17 10:12 PM: - [~romain.manni-bucau] did you seriously just overwrite my commit? was (Author: andyg): [~romain.manni-bucau] did you seriously just my commit? > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065559#comment-16065559 ] Andy Gumbrecht commented on TOMEE-2078: --- [~romain.manni-bucau] did you seriously just my commit? > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065508#comment-16065508 ] Andy Gumbrecht commented on TOMEE-2078: --- Thanks Ivan - This is nice improvement > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht reassigned TOMEE-2078: - Assignee: Andy Gumbrecht > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (TOMEE-2078) TomEE Website Improvements
[ https://issues.apache.org/jira/browse/TOMEE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2078 started by Andy Gumbrecht. - > TomEE Website Improvements > -- > > Key: TOMEE-2078 > URL: https://issues.apache.org/jira/browse/TOMEE-2078 > Project: TomEE > Issue Type: Improvement >Reporter: Ivan Junckes Filho >Assignee: Andy Gumbrecht >Priority: Minor > Attachments: tomee_site_improvements_patch.patch > > > This patch aims to make the website more clear. It adds a section called > Documentation and also several changes with improvements on the descriptions, > content structure etc. > This is an initial commit, I would like to keep working on changes to better > the website. It is on my list to also write a Getting Started with TomEE, > that is why we still don't have this section. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOMEE-1874) Do not inject CDI if the application is being undeployed
[ https://issues.apache.org/jira/browse/TOMEE-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht resolved TOMEE-1874. --- Resolution: Fixed Fix Version/s: 7.0.3 1.7.5 Close before drain. Remove WebBeans context after bean undeploy in Assembler. > Do not inject CDI if the application is being undeployed > > > Key: TOMEE-1874 > URL: https://issues.apache.org/jira/browse/TOMEE-1874 > Project: TomEE > Issue Type: Bug >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Minor > Fix For: 1.7.5, 7.0.3 > > > Somewhere around StatelessInstanceManager.createInstance there should be > check a check to see if the application is being undeployed. > The following stacktrace snippet is written to the logs multiple times during > an undeploy, as the pool tries to fill. > at > org.apache.webbeans.util.InjectionExceptionUtil.throwUnsatisfiedResolutionException(InjectionExceptionUtil.java:60) > at > org.apache.webbeans.container.InjectionResolver.getInjectionPointBean(InjectionResolver.java:250) > at > org.apache.webbeans.inject.AbstractInjectable.inject(AbstractInjectable.java:76) > at > org.apache.webbeans.inject.InjectableField.doInjection(InjectableField.java:65) > at > org.apache.webbeans.portable.InjectionTargetImpl.injectFields(InjectionTargetImpl.java:208) > at > org.apache.webbeans.portable.InjectionTargetImpl.inject(InjectionTargetImpl.java:194) > at > org.apache.webbeans.portable.InjectionTargetImpl.inject(InjectionTargetImpl.java:184) > at > org.apache.openejb.cdi.CdiEjbBean$EjbInjectionTargetImpl.inject(CdiEjbBean.java:388) > at org.apache.openejb.BeanContext.inject(BeanContext.java:1660) > at org.apache.openejb.BeanContext.newInstance(BeanContext.java:1489) > at > org.apache.openejb.core.stateless.StatelessInstanceManager.createInstance(StatelessInstanceManager.java:207) > at > org.apache.openejb.core.stateless.StatelessInstanceManager.access$200(StatelessInstanceManager.java:72) > at > org.apache.openejb.core.stateless.StatelessInstanceManager$StatelessSupplier.create(StatelessInstanceManager.java:151) > at > org.apache.openejb.core.stateless.StatelessInstanceManager$StatelessSupplier.create(StatelessInstanceManager.java:127) > at org.apache.openejb.util.Pool$Replace.run(Pool.java:847) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (TOMEE-1874) Do not inject CDI if the application is being undeployed
[ https://issues.apache.org/jira/browse/TOMEE-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht reassigned TOMEE-1874: - Assignee: Andy Gumbrecht > Do not inject CDI if the application is being undeployed > > > Key: TOMEE-1874 > URL: https://issues.apache.org/jira/browse/TOMEE-1874 > Project: TomEE > Issue Type: Bug >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Minor > > Somewhere around StatelessInstanceManager.createInstance there should be > check a check to see if the application is being undeployed. > The following stacktrace snippet is written to the logs multiple times during > an undeploy, as the pool tries to fill. > at > org.apache.webbeans.util.InjectionExceptionUtil.throwUnsatisfiedResolutionException(InjectionExceptionUtil.java:60) > at > org.apache.webbeans.container.InjectionResolver.getInjectionPointBean(InjectionResolver.java:250) > at > org.apache.webbeans.inject.AbstractInjectable.inject(AbstractInjectable.java:76) > at > org.apache.webbeans.inject.InjectableField.doInjection(InjectableField.java:65) > at > org.apache.webbeans.portable.InjectionTargetImpl.injectFields(InjectionTargetImpl.java:208) > at > org.apache.webbeans.portable.InjectionTargetImpl.inject(InjectionTargetImpl.java:194) > at > org.apache.webbeans.portable.InjectionTargetImpl.inject(InjectionTargetImpl.java:184) > at > org.apache.openejb.cdi.CdiEjbBean$EjbInjectionTargetImpl.inject(CdiEjbBean.java:388) > at org.apache.openejb.BeanContext.inject(BeanContext.java:1660) > at org.apache.openejb.BeanContext.newInstance(BeanContext.java:1489) > at > org.apache.openejb.core.stateless.StatelessInstanceManager.createInstance(StatelessInstanceManager.java:207) > at > org.apache.openejb.core.stateless.StatelessInstanceManager.access$200(StatelessInstanceManager.java:72) > at > org.apache.openejb.core.stateless.StatelessInstanceManager$StatelessSupplier.create(StatelessInstanceManager.java:151) > at > org.apache.openejb.core.stateless.StatelessInstanceManager$StatelessSupplier.create(StatelessInstanceManager.java:127) > at org.apache.openejb.util.Pool$Replace.run(Pool.java:847) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (TOMEE-1897) CdiResourceProvider masks critical error in InjectionException
[ https://issues.apache.org/jira/browse/TOMEE-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht resolved TOMEE-1897. --- Resolution: Fixed > CdiResourceProvider masks critical error in InjectionException > -- > > Key: TOMEE-1897 > URL: https://issues.apache.org/jira/browse/TOMEE-1897 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 1.7.4, 7.0.1 > Environment: NA >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Critical > Fix For: 1.7.5, 7.0.3 > > > openejb-cxf-rs: > /org/apache/openejb/server/cxf/rs/CdiResourceProvider.java:277 > The InjectionException details should be propagated or logged. Currently the > WebApplicationException contains no information on the underlying error., > making error tracing very difficult -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (TOMEE-1897) CdiResourceProvider masks critical error in InjectionException
[ https://issues.apache.org/jira/browse/TOMEE-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-1897 started by Andy Gumbrecht. - > CdiResourceProvider masks critical error in InjectionException > -- > > Key: TOMEE-1897 > URL: https://issues.apache.org/jira/browse/TOMEE-1897 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 1.7.4, 7.0.1 > Environment: NA >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Critical > Fix For: 1.7.5, 7.0.3 > > > openejb-cxf-rs: > /org/apache/openejb/server/cxf/rs/CdiResourceProvider.java:277 > The InjectionException details should be propagated or logged. Currently the > WebApplicationException contains no information on the underlying error., > making error tracing very difficult -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (TOMEE-1897) CdiResourceProvider masks critical error in InjectionException
[ https://issues.apache.org/jira/browse/TOMEE-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht reassigned TOMEE-1897: - Assignee: Andy Gumbrecht > CdiResourceProvider masks critical error in InjectionException > -- > > Key: TOMEE-1897 > URL: https://issues.apache.org/jira/browse/TOMEE-1897 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 1.7.4, 7.0.1 > Environment: NA >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Critical > Fix For: 1.7.5, 7.0.3 > > > openejb-cxf-rs: > /org/apache/openejb/server/cxf/rs/CdiResourceProvider.java:277 > The InjectionException details should be propagated or logged. Currently the > WebApplicationException contains no information on the underlying error., > making error tracing very difficult -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TOMEE-1999) MySQL DataSource definitions require that 'user' is provided rather than 'userName'
Andy Gumbrecht created TOMEE-1999: - Summary: MySQL DataSource definitions require that 'user' is provided rather than 'userName' Key: TOMEE-1999 URL: https://issues.apache.org/jira/browse/TOMEE-1999 Project: TomEE Issue Type: Improvement Components: TomEE Core Server Affects Versions: 7.0.2 Reporter: Andy Gumbrecht Priority: Minor Would be an improvement if TomEE attempts to set both 'user' & 'userName'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TOMEE-1897) CdiResourceProvider masks critical error in InjectionException
[ https://issues.apache.org/jira/browse/TOMEE-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411464#comment-15411464 ] Andy Gumbrecht commented on TOMEE-1897: --- Sure, the current propagated error is: WARN org.apache.cxf.jaxrs.impl.WebApplicationExceptionMapper - javax.ws.rs.WebApplicationException In this instance the actual underlying error finally tracked down on site was: javax.enterprise.inject.CreationException: java.lang.NoSuchMethodError ... on a Hystrix wrapper. It was hard to track down. So at least one should be logged as severe, as this causes a complete failure at application level. > CdiResourceProvider masks critical error in InjectionException > -- > > Key: TOMEE-1897 > URL: https://issues.apache.org/jira/browse/TOMEE-1897 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 1.7.4, 7.0.1 > Environment: NA >Reporter: Andy Gumbrecht >Priority: Critical > Fix For: 1.7.5, 7.0.2 > > > openejb-cxf-rs: > /org/apache/openejb/server/cxf/rs/CdiResourceProvider.java:277 > The InjectionException details should be propagated or logged. Currently the > WebApplicationException contains no information on the underlying error., > making error tracing very difficult -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TOMEE-1897) CdiResourceProvider masks critical error in InjectionException
Andy Gumbrecht created TOMEE-1897: - Summary: CdiResourceProvider masks critical error in InjectionException Key: TOMEE-1897 URL: https://issues.apache.org/jira/browse/TOMEE-1897 Project: TomEE Issue Type: Bug Components: TomEE Core Server Affects Versions: 7.0.1, 1.7.4 Environment: NA Reporter: Andy Gumbrecht Priority: Critical Fix For: 1.7.5, 7.0.2 openejb-cxf-rs: /org/apache/openejb/server/cxf/rs/CdiResourceProvider.java:277 The InjectionException details should be propagated or logged. Currently the WebApplicationException contains no information on the underlying error., making error tracing very difficult -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TOMEE-1874) Do not inject CDI if the application is being undeployed
Andy Gumbrecht created TOMEE-1874: - Summary: Do not inject CDI if the application is being undeployed Key: TOMEE-1874 URL: https://issues.apache.org/jira/browse/TOMEE-1874 Project: TomEE Issue Type: Bug Reporter: Andy Gumbrecht Priority: Minor Somewhere around StatelessInstanceManager.createInstance there should be check a check to see if the application is being undeployed. The following stacktrace snippet is written to the logs multiple times during an undeploy, as the pool tries to fill. at org.apache.webbeans.util.InjectionExceptionUtil.throwUnsatisfiedResolutionException(InjectionExceptionUtil.java:60) at org.apache.webbeans.container.InjectionResolver.getInjectionPointBean(InjectionResolver.java:250) at org.apache.webbeans.inject.AbstractInjectable.inject(AbstractInjectable.java:76) at org.apache.webbeans.inject.InjectableField.doInjection(InjectableField.java:65) at org.apache.webbeans.portable.InjectionTargetImpl.injectFields(InjectionTargetImpl.java:208) at org.apache.webbeans.portable.InjectionTargetImpl.inject(InjectionTargetImpl.java:194) at org.apache.webbeans.portable.InjectionTargetImpl.inject(InjectionTargetImpl.java:184) at org.apache.openejb.cdi.CdiEjbBean$EjbInjectionTargetImpl.inject(CdiEjbBean.java:388) at org.apache.openejb.BeanContext.inject(BeanContext.java:1660) at org.apache.openejb.BeanContext.newInstance(BeanContext.java:1489) at org.apache.openejb.core.stateless.StatelessInstanceManager.createInstance(StatelessInstanceManager.java:207) at org.apache.openejb.core.stateless.StatelessInstanceManager.access$200(StatelessInstanceManager.java:72) at org.apache.openejb.core.stateless.StatelessInstanceManager$StatelessSupplier.create(StatelessInstanceManager.java:151) at org.apache.openejb.core.stateless.StatelessInstanceManager$StatelessSupplier.create(StatelessInstanceManager.java:127) at org.apache.openejb.util.Pool$Replace.run(Pool.java:847) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TOMEE-1868) Prevent hot deployment of "filepart" archives
Andy Gumbrecht created TOMEE-1868: - Summary: Prevent hot deployment of "filepart" archives Key: TOMEE-1868 URL: https://issues.apache.org/jira/browse/TOMEE-1868 Project: TomEE Issue Type: Bug Affects Versions: 7.0.1, 1.7.4 Reporter: Andy Gumbrecht Fix For: 1.7.5, 7.0.2 Dropping an application war into webapps sometimes deploys the partially extracted war file with the [appname].filepart and then [appname]. This obviously breaks both deployments and the only solution is to delete both, wait for the undeploy, and then redeploy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TOMEE-1867) Investigate FileNotFoundException warning
Andy Gumbrecht created TOMEE-1867: - Summary: Investigate FileNotFoundException warning Key: TOMEE-1867 URL: https://issues.apache.org/jira/browse/TOMEE-1867 Project: TomEE Issue Type: Task Affects Versions: 1.7.4 Environment: Windows Reporter: Andy Gumbrecht Priority: Trivial Fix For: 1.7.5, 7.0.2 Only a warning, but wondering why this broken path is generated: 2016-07-15 11:00:35 WARN FileZippedJarVisitor:74 - HHH015010: Unable to find file (ignored): file:/C:/Integration/workspace/project/project-service-impl/jar:file:/C:/repository/com/company/division/app/app-service-impl/1.2.3/app-service-impl-1.2.3.jar!/META-INF/persistence.xml java.io.FileNotFoundException: C:\Integration\workspace\project\project-service-impl\jar:file:\C:\repository\com\company\division\app\app-service-impl\1.2.3\app-service-impl-1.2.3.jar!\META-INF\persistence.xml (Die Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch) at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.(ZipFile.java:215) at java.util.zip.ZipFile.(ZipFile.java:145) at java.util.jar.JarFile.(JarFile.java:154) at java.util.jar.JarFile.(JarFile.java:91) at org.hibernate.ejb.packaging.FileZippedJarVisitor.doProcessElements(FileZippedJarVisitor.java:70) at org.hibernate.ejb.packaging.AbstractJarVisitor.getMatchingEntries(AbstractJarVisitor.java:149) at org.hibernate.ejb.packaging.NativeScanner.getClassesInJar(NativeScanner.java:128) at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:488) at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:862) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:607) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:75) at org.apache.openejb.assembler.classic.EntityManagerFactoryCallable.call(EntityManagerFactoryCallable.java:64) at org.apache.openejb.assembler.classic.ReloadableEntityManagerFactory.createDelegate(ReloadableEntityManagerFactory.java:116) at org.apache.openejb.assembler.classic.ReloadableEntityManagerFactory.(ReloadableEntityManagerFactory.java:102) at org.apache.openejb.assembler.classic.PersistenceBuilder.createEntityManagerFactory(PersistenceBuilder.java:154) at org.apache.openejb.assembler.classic.Assembler.loadPersistenceUnits(Assembler.java:985) at org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:744) at org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:680) at org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:676) at org.apache.openejb.testing.ApplicationComposers.before(ApplicationComposers.java:830) at org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:984) at org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (TOMEE-1860) Potential NPE with DBCP if a shared connection is closed
[
https://issues.apache.org/jira/browse/TOMEE-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371713#comment-15371713
]
Andy Gumbrecht edited comment on TOMEE-1860 at 7/11/16 9:54 PM:
Added
{code:java}
try{...}finally{_close = true;}
{code}
else the connection is not flagged.
Also added a null check in the isClosed method.
Updated test.
was (Author: andyg):
Added try{...}finally{_close = true;} else the connection is not flagged.
Also added a null check in the isClosed method.
Updated test.
> Potential NPE with DBCP if a shared connection is closed
>
>
> Key: TOMEE-1860
> URL: https://issues.apache.org/jira/browse/TOMEE-1860
> Project: TomEE
> Issue Type: Bug
>Reporter: Romain Manni-Bucau
>Assignee: Romain Manni-Bucau
> Fix For: 1.7.5, 7.0.2
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TOMEE-1860) Potential NPE with DBCP if a shared connection is closed
[
https://issues.apache.org/jira/browse/TOMEE-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371713#comment-15371713
]
Andy Gumbrecht commented on TOMEE-1860:
---
Added try{...}finally{_close = true;} else the connection is not flagged.
Also added a null check in the isClosed method.
Updated test.
> Potential NPE with DBCP if a shared connection is closed
>
>
> Key: TOMEE-1860
> URL: https://issues.apache.org/jira/browse/TOMEE-1860
> Project: TomEE
> Issue Type: Bug
>Reporter: Romain Manni-Bucau
>Assignee: Romain Manni-Bucau
> Fix For: 1.7.5, 7.0.2
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (TOMEE-1799) Java 8 : java.lang.IllegalArgumentException: Comparison method violates its general contract!
[ https://issues.apache.org/jira/browse/TOMEE-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht resolved TOMEE-1799. --- Resolution: Fixed Assignee: Andy Gumbrecht > Java 8 : java.lang.IllegalArgumentException: Comparison method violates its > general contract! > - > > Key: TOMEE-1799 > URL: https://issues.apache.org/jira/browse/TOMEE-1799 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.4, 7.0.0-M3 > Environment: Java 8 >Reporter: Andy Gumbrecht >Assignee: Andy Gumbrecht >Priority: Blocker > Fix For: 7.0.0, 1.7.5 > > > java.lang.IllegalArgumentException: Comparison method violates its general > contract! > at java.util.TimSort.mergeLo(TimSort.java:777) > at java.util.TimSort.mergeAt(TimSort.java:514) > at java.util.TimSort.mergeCollapse(TimSort.java:439) > at java.util.TimSort.sort(TimSort.java:245) > at java.util.Arrays.sort(Arrays.java:1512) > at java.util.ArrayList.sort(ArrayList.java:1454) > at java.util.Collections.sort(Collections.java:175) > at > org.apache.openejb.config.AutoConfig.firstMatching(AutoConfig.java:1997) > Following list reproduces the issue. Will provide a test and fix later. > def-monitor-internal/jdbc/appmgr-jta > jdbc/appmgr-jta > def-monitor-internal/jdbc/erp_global-jta > jdbc/erp_global-jta > def-monitor-internal/jdbc/catalog-jta > jdbc/catalog-jta > def-monitor-internal/jdbc/erp-jta > jdbc/erp-jta > def-monitor-internal/jdbc/ghi-jta > jdbc/ghi-jta > def-monitor-internal/jdbc/usr-jta > jdbc/usr-jta > def-monitor-internal/jdbc/email-jta > jdbc/email-jta > def-monitor-internal/jdbc/webcode-jta > jdbc/webcode-jta > def-monitor-internal/jdbc/webcode-download-jta > jdbc/webcode-download-jta > def-monitor-internal/jdbc/countrydata-jta > jdbc/countrydata-jta > def-monitor-internal/jdbc/clipsafe-jta > jdbc/clipsafe-jta > def-monitor-internal/jdbc/hazmat-jta > jdbc/hazmat-jta > def-monitor-internal/jdbc/waab-refapp-jta > jdbc/waab-refapp-jta > appmgr/jdbc/appmgr-jta > jdbc/appmgr-jta > appmgr/jdbc/erp_global-jta > jdbc/erp_global-jta > appmgr/jdbc/catalog-jta > jdbc/catalog-jta > appmgr/jdbc/erp-jta > jdbc/erp-jta > appmgr/jdbc/ghi-jta > jdbc/ghi-jta > appmgr/jdbc/usr-jta > jdbc/usr-jta > appmgr/jdbc/email-jta > jdbc/email-jta > appmgr/jdbc/webcode-jta > jdbc/webcode-jta > appmgr/jdbc/webcode-download-jta > jdbc/webcode-download-jta > appmgr/jdbc/countrydata-jta > jdbc/countrydata-jta > appmgr/jdbc/clipsafe-jta > jdbc/clipsafe-jta > appmgr/jdbc/hazmat-jta > jdbc/hazmat-jta > appmgr/jdbc/waab-refapp-jta > jdbc/waab-refapp-jta > abc-catalog-opq-uvw-jkl-web/jdbc/appmgr-jta > jdbc/appmgr-jta > abc-catalog-opq-uvw-jkl-web/jdbc/erp_global-jta > jdbc/erp_global-jta > abc-catalog-opq-uvw-jkl-web/jdbc/catalog-jta > jdbc/catalog-jta > abc-catalog-opq-uvw-jkl-web/jdbc/erp-jta > jdbc/erp-jta > abc-catalog-opq-uvw-jkl-web/jdbc/ghi-jta > jdbc/ghi-jta > abc-catalog-opq-uvw-jkl-web/jdbc/usr-jta > jdbc/usr-jta > abc-catalog-opq-uvw-jkl-web/jdbc/email-jta > jdbc/email-jta > abc-catalog-opq-uvw-jkl-web/jdbc/webcode-jta > jdbc/webcode-jta > abc-catalog-opq-uvw-jkl-web/jdbc/webcode-download-jta > jdbc/webcode-download-jta > abc-catalog-opq-uvw-jkl-web/jdbc/countrydata-jta > jdbc/countrydata-jta > abc-catalog-opq-uvw-jkl-web/jdbc/clipsafe-jta > jdbc/clipsafe-jta > abc-catalog-opq-uvw-jkl-web/jdbc/hazmat-jta > jdbc/hazmat-jta > abc-catalog-opq-uvw-jkl-web/jdbc/waab-refapp-jta > jdbc/waab-refapp-jta > abc-catapp-product-rest-web/jdbc/appmgr-jta > jdbc/appmgr-jta > abc-catapp-product-rest-web/jdbc/erp_global-jta > jdbc/erp_global-jta > abc-catapp-product-rest-web/jdbc/catalog-jta > jdbc/catalog-jta > abc-catapp-product-rest-web/jdbc/erp-jta > jdbc/erp-jta > abc-catapp-product-rest-web/jdbc/ghi-jta > jdbc/ghi-jta > abc-catapp-product-rest-web/jdbc/usr-jta > jdbc/usr-jta > abc-catapp-product-rest-web/jdbc/email-jta > jdbc/email-jta > abc-catapp-product-rest-web/jdbc/webcode-jta > jdbc/webcode-jta > abc-catapp-product-rest-web/jdbc/webcode-download-jta > jdbc/webcode-download-jta > abc-catapp-product-rest-web/jdbc/countrydata-jta > jdbc/countrydata-jta > abc-catapp-product-rest-web/jdbc/clipsafe-jta > jdbc/clipsafe-jta > abc-catapp-product-rest-web/jdbc/hazmat-jta > jdbc/hazmat-jta > abc-catapp-product-rest-web/jdbc/waab-refapp-jta > jdbc/waab-refapp-jta > abc-checkout-uvw-jkl-web/jdbc/appmgr-jta > jdbc/appmgr-jta > abc-checkout-uvw-jkl-web/jdbc/erp_global-jta > jdbc/erp_global-jta > abc-checkout-uvw-jkl-web/jdbc/catalog-jta > jdbc/catalog-jta > abc-checkout-uvw-jkl-web/jdbc/erp-jta > jdbc/erp-jta > abc-checkout-uvw-jkl-web/jdbc/ghi-jta > jdbc/ghi-jta > abc-checkout-uvw-jkl-web/jdbc/usr-jta > jdbc/usr-jta > abc-checkout-uvw-jkl-web/jdbc/email-jta >
