[
https://issues.apache.org/jira/browse/TOMEE-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dev Null 52 updated TOMEE-1978:
-------------------------------
Environment: Mac OS Sierra, Java 1.8.0_25, Eclipse Neon, Maven TomEE Plugin
7.0.2 (was: Mac OS Sierra, )
Priority: Major (was: Trivial)
Description:
I am using TommEE org.apache.tomee.maven plugin version 7.0.2 to a seperate
TomEE 7.0.2 JVM process ( not embedded within Eclipse ). I am used to
tomcat7:deploy task. However equivalent tomee:deploy fails.
1. If I use as-is, it complains with message:
The parameters 'path' for goal
org.apache.tomee.maven:tomee-maven-plugin:7.0.2:deploy are missing or invalid.
2. If I provide a path it fails with message:
Caused by: org.apache.openejb.OpenEJBException: Creating application failed:
/LOCAL_FS_PATH/Eclipse/workspace/jee-examples/target/jeeexamples##0.0.1:
addChild: Child name '/jeeexamples##0.0.1' is not unique.
My webapps directory is empty. I had initial difficulties with deployment but I
was able to deploy a tomee.war and able to proceed. Not sure if it helps, but I
have added following based on posts to system.properties ( I dont know all the
implications yet but I have added to go past while I learn more ). Not sure if
I am contributing to the problem.
system.properties
===============
tomee.remote.support = true
tomee.serialization.class.whitelist =
tomee.serialization.class.blacklist =
org.codehaus.groovy.runtime.,org.apache.commons.collections.functors.,org.apache.xalan,java.lang.Process
openejb.system.apps = true
## tomee.version=7.0.2
<plugin>
<groupId>org.apache.tomee.maven</groupId>
<artifactId>tomee-maven-plugin</artifactId>
<version>${tomee.version}</version>
<configuration>
<tomeeVersion>${tomee.version}</tomeeVersion>
<tomeeClassifier>plus</tomeeClassifier>
<tomeeHttpPort>${tomee.port}</tomeeHttpPort>
</configuration>
</plugin>
was:
I have been trying for couple of days to have a trivial MDB example working to
listen on ActiveMQ Queue on default port. I am using TomEE 7.0.2.
I tried first using an embedded Active MQ 5.2.0 broker, then moved it as a
stand alone process using activemq-maven-plugin plugin to rule out Active MQ
out as a variable.I tried MDB with annotation using activation config, without
annotation but no avail. Examples online vary and none of them appear to work.
I am able to send to the Queue using a seperate Servlet and able to validate
then but not able to read.
Also I am seeing very strange Auto-linking resource-ref logs whereby I see
injections for Beans that do not have those instances/types defined -- so very
confused.
Plain JMS and EJB worked like a charm on JEE. Using Maven
META-INF/beans.xml ( empty )
META-INF/ejb-jar.xml ( MDB and basic EJB descriptor )
WEB-INF/resources.xml (ConnectionFactory and Queue definition pointing to
localhost ActiveMQ on default port ).
WEB-INF/web.xml ( empty )
Please help if possible.
Component/s: (was: TomEE Core Server)
TomEE Maven Plugin
> JEE WAR not getting deployed with tomee-maven-plugin 7.0.2
> ----------------------------------------------------------
>
> Key: TOMEE-1978
> URL: https://issues.apache.org/jira/browse/TOMEE-1978
> Project: TomEE
> Issue Type: Documentation
> Components: TomEE Maven Plugin
> Affects Versions: 7.0.2
> Environment: Mac OS Sierra, Java 1.8.0_25, Eclipse Neon, Maven TomEE
> Plugin 7.0.2
> Reporter: Dev Null 52
>
> I am using TommEE org.apache.tomee.maven plugin version 7.0.2 to a seperate
> TomEE 7.0.2 JVM process ( not embedded within Eclipse ). I am used to
> tomcat7:deploy task. However equivalent tomee:deploy fails.
> 1. If I use as-is, it complains with message:
> The parameters 'path' for goal
> org.apache.tomee.maven:tomee-maven-plugin:7.0.2:deploy are missing or invalid.
> 2. If I provide a path it fails with message:
> Caused by: org.apache.openejb.OpenEJBException: Creating application failed:
> /LOCAL_FS_PATH/Eclipse/workspace/jee-examples/target/jeeexamples##0.0.1:
> addChild: Child name '/jeeexamples##0.0.1' is not unique.
> My webapps directory is empty. I had initial difficulties with deployment but
> I was able to deploy a tomee.war and able to proceed. Not sure if it helps,
> but I have added following based on posts to system.properties ( I dont know
> all the implications yet but I have added to go past while I learn more ).
> Not sure if I am contributing to the problem.
> system.properties
> ===============
> tomee.remote.support = true
> tomee.serialization.class.whitelist =
> tomee.serialization.class.blacklist =
> org.codehaus.groovy.runtime.,org.apache.commons.collections.functors.,org.apache.xalan,java.lang.Process
> openejb.system.apps = true
> ## tomee.version=7.0.2
> <plugin>
> <groupId>org.apache.tomee.maven</groupId>
> <artifactId>tomee-maven-plugin</artifactId>
> <version>${tomee.version}</version>
> <configuration>
>
> <tomeeVersion>${tomee.version}</tomeeVersion>
> <tomeeClassifier>plus</tomeeClassifier>
>
> <tomeeHttpPort>${tomee.port}</tomeeHttpPort>
> </configuration>
> </plugin>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
