[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3779) Error while reading JPA XML file: META-INF/orm.xml when using SMPC with Seam Remoting
7:15 a.m.
Error while reading JPA XML file: META-INF/orm.xml when using SMPC with Seam Remoting
-------------------------------------------------------------------------------------
Key: JBSEAM-3779
URL: https://jira.jboss.org/jira/browse/JBSEAM-3779
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.1.CR1
Environment: Microsoft Windows XP Professional SP3
JBoss 4.3.2.GA
Reporter: Andreas Eriksson
Assignee: Shane Bryzak
When I package my EAR with the Seam Remoting JAR the orm.xml (contains my entity listener,
i.e. EntitySecurityListener) JPA configuration file cannot be parsed.
I also had to add the gwt-servlet dependency to in order to escape exception messages
during deploy (even though I'm not using GWT).
See attached Maven project (README.TXT inside) and stacktrace.txt.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:17 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3779) Error while reading JPA XML file: META-INF/orm.xml when using SMPC with Seam Remoting
[
https://jira.jboss.org/jira/browse/JBSEAM-3779?page=com.atlassian.jira.pl...
]
Andreas Eriksson updated JBSEAM-3779:
-------------------------------------
Attachment: seam-remoting-test.zip
Maven project
Error while reading JPA XML file: META-INF/orm.xml when using SMPC
with Seam Remoting
-------------------------------------------------------------------------------------
Key: JBSEAM-3779
URL: https://jira.jboss.org/jira/browse/JBSEAM-3779
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.1.CR1
Environment: Microsoft Windows XP Professional SP3
JBoss 4.3.2.GA
Reporter: Andreas Eriksson
Assignee: Shane Bryzak
Attachments: seam-remoting-test.zip, stacktrace.txt
When I package my EAR with the Seam Remoting JAR the orm.xml (contains my entity
listener, i.e. EntitySecurityListener) JPA configuration file cannot be parsed.
I also had to add the gwt-servlet dependency to in order to escape exception messages
during deploy (even though I'm not using GWT).
See attached Maven project (README.TXT inside) and stacktrace.txt.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:17 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3779) Error while reading JPA XML file: META-INF/orm.xml when using SMPC with Seam Remoting
[
https://jira.jboss.org/jira/browse/JBSEAM-3779?page=com.atlassian.jira.pl...
]
Andreas Eriksson updated JBSEAM-3779:
-------------------------------------
Attachment: stacktrace.txt
stacktrace
Error while reading JPA XML file: META-INF/orm.xml when using SMPC
with Seam Remoting
-------------------------------------------------------------------------------------
Key: JBSEAM-3779
URL: https://jira.jboss.org/jira/browse/JBSEAM-3779
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.1.CR1
Environment: Microsoft Windows XP Professional SP3
JBoss 4.3.2.GA
Reporter: Andreas Eriksson
Assignee: Shane Bryzak
Attachments: seam-remoting-test.zip, stacktrace.txt
When I package my EAR with the Seam Remoting JAR the orm.xml (contains my entity
listener, i.e. EntitySecurityListener) JPA configuration file cannot be parsed.
I also had to add the gwt-servlet dependency to in order to escape exception messages
during deploy (even though I'm not using GWT).
See attached Maven project (README.TXT inside) and stacktrace.txt.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:12 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3779) Error while reading JPA XML file: META-INF/orm.xml when using SMPC with Seam Remoting
[
https://jira.jboss.org/jira/browse/JBSEAM-3779?page=com.atlassian.jira.pl...
]
Pete Muir closed JBSEAM-3779.
-----------------------------
Resolution: Rejected
JIRA is not for support
Error while reading JPA XML file: META-INF/orm.xml when using SMPC
with Seam Remoting
-------------------------------------------------------------------------------------
Key: JBSEAM-3779
URL: https://jira.jboss.org/jira/browse/JBSEAM-3779
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.1.CR1
Environment: Microsoft Windows XP Professional SP3
JBoss 4.3.2.GA
Reporter: Andreas Eriksson
Assignee: Shane Bryzak
Attachments: seam-remoting-test.zip, stacktrace.txt
When I package my EAR with the Seam Remoting JAR the orm.xml (contains my entity
listener, i.e. EntitySecurityListener) JPA configuration file cannot be parsed.
I also had to add the gwt-servlet dependency to in order to escape exception messages
during deploy (even though I'm not using GWT).
See attached Maven project (README.TXT inside) and stacktrace.txt.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:25 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3779) Error while reading JPA XML file: META-INF/orm.xml when using SMPC with Seam Remoting
[
https://jira.jboss.org/jira/browse/JBSEAM-3779?page=com.atlassian.jira.pl...
]
Andreas Eriksson commented on JBSEAM-3779:
------------------------------------------
Okay, so I modified the JBoss Seam Hello World remoting example shipped with the JBoss
Seam 2.1.1.CR1 release and it complains on not being able to parse the components.xml.
What did I do?
1. Added the entity manager factory configuration to the components.xml
2. Added a persistence.xml (copied from the contactlist example)
3. Injected the entity manager to the HelloAction
Stacktrace:
java.lang.RuntimeException: error while reading /WEB-INF/components.xml
at
org.jboss.seam.init.Initialization.initComponentsFromXmlDocument(Initialization.java:230)
at org.jboss.seam.init.Initialization.create(Initialization.java:133)
at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3856)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4361)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:790)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:770)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.apache.catalina.core.StandardContext.init(StandardContext.java:5312)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeployer.java:301)
at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:104)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy44.start(Unknown Source)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at
org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at
org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:87)
at
org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy45.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Caused by: org.dom4j.DocumentException: org.dom4j.DocumentFactory Nested exception:
org.dom4j.DocumentFactory
at org.dom4j.io.SAXReader.read(SAXReader.java:484)
at org.dom4j.io.SAXReader.read(SAXReader.java:343)
at org.jboss.seam.util.XML.getRootElement(XML.java:24)
at
org.jboss.seam.init.Initialization.initComponentsFromXmlDocument(Initialization.java:226)
... 92 more
Still not a bug?
Apparently your SAX reader goes bananas....
Error while reading JPA XML file: META-INF/orm.xml when using SMPC
with Seam Remoting
-------------------------------------------------------------------------------------
Key: JBSEAM-3779
URL: https://jira.jboss.org/jira/browse/JBSEAM-3779
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.1.CR1
Environment: Microsoft Windows XP Professional SP3
JBoss 4.3.2.GA
Reporter: Andreas Eriksson
Assignee: Shane Bryzak
Attachments: seam-remoting-test.zip, stacktrace.txt
When I package my EAR with the Seam Remoting JAR the orm.xml (contains my entity
listener, i.e. EntitySecurityListener) JPA configuration file cannot be parsed.
I also had to add the gwt-servlet dependency to in order to escape exception messages
during deploy (even though I'm not using GWT).
See attached Maven project (README.TXT inside) and stacktrace.txt.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5882
days inactive
5882
days old
4 comments
2 participants
participants (2)
-
Andreas Eriksson (JIRA) -
Pete Muir (JIRA)