[Installation, Configuration & DEPLOYMENT] - Re: JBoss5 CR1 and org.jboss.xb.binding.JBossXBException
by jimmycallaghan
OK, so I turned logging up to DEBUG on all org.jboss so that I could get more information out of the server.log as I deploy. I removed all of the applications and deployed just this one to reproduce the error and ensure that I'm not looking at a different app. This is the bit of interest:
12:03:39,465 DEBUG [JBossXBDeployerHelper] Parsing file: ZipEntryHandler(a)10127346[path=webs/10.mpee.local.20080702.1257.ear/META-INF/persistence.xml context=file:/home/jim/messaging-platform/jboss-5.0.0.CR1/server/custom1/deploy/ real=vfszip:/home/jim/messaging-platform/jboss-5.0.0.CR1/server/custom1/deploy/webs/10.mpee.local.20080702.1257.ear/META-INF/persistence.xml] for type: class org.jboss.metadata.jpa.spec.PersistenceMetaData
| 12:03:39,466 DEBUG [SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@153505d, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
| 12:03:39,467 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
| 12:03:39,467 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
| 12:03:39,467 DEBUG [SaxJBossXBParser] http://apache.org/xml/features/xinclude/fixup-language set to: false
| 12:03:39,467 DEBUG [SaxJBossXBParser] http://apache.org/xml/features/xinclude/fixup-base-uris set to: false
| 12:03:39,467 DEBUG [SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
| 12:03:39,467 DEBUG [SaxJBossXBParser] http://apache.org/xml/features/validation/schema set to: true
| 12:03:39,467 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
| 12:03:39,467 DEBUG [SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@153505d, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
| 12:03:39,472 DEBUG [JBossEntityResolver] Cannot resolve [publicID=,systemID=persistence]
| 12:03:39,472 DEBUG [JBossEntityResolver] Cannot resolve [publicID=null,systemID=]
| 12:03:39,473 DEBUG [PersistenceUnitParsingDeployer] Error during deploy: vfszip:/home/jim/messaging-platform/jboss-5.0.0.CR1/server/custom1/deploy/webs/10.mpee.local.20080702.1257.ear
| org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/jim/messaging-platform/jboss-5.0.0.CR1/server/custom1/deploy/webs/10.mpee.local.20080702.1257.ear
I've opened up the EAR and looked at the persistence.xml file and can see that the relevant code is in it. I'm wondering if this is down to the location of my persistence.xml file. I know that in JBoss4 there were problems when the persistence.xml was in the META-INF directory of the EAR instead of the META-INF directory in the jar that held the entities. I'll investigate this possibility as well.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162029#4162029
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162029
17 years, 4 months
[Installation, Configuration & DEPLOYMENT] - JBoss5CR1- Changes to nested deployments redeploys the entir
by jaikiran
Operating System : Windows 2003
Java version : Sun Java 1.5
JBoss version : JBoss - 5 CR1
I have an (exploded) EAR which contains an jar file (for EJB3 artifacts) and a war file. The EAR, the jar and the war are all exploded:
ZEJB3Persistence.ear
| |
| |
| |--- META-INF
| | |
| | |--- application.xml
| | |--- jboss-app.xml
| |
| |
| |--- myapp_ejb3.jar (ejb module)
| | |
| | |--- META-INF
| | | |
| | | |--- persistence.xml
| |
| |
| |--- myapp.jar (java module)
| |
| |--- myapp.war (war module)
|
The application.xml contents are as follows:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <application>
| <display-name>MyEJB3</display-name>
| <module>
| <web>
| <web-uri>myapp.war</web-uri>
| <context-root>/EJB3Persistence</context-root>
| </web>
| </module>
| <module>
| <ejb>myapp_ejb3.jar</ejb>
| </module>
| <module>
| <java>myapp.jar</java>
| </module>
|
| </application>
The jboss-app.xml for classloader configuration:
<jboss-app>
| <loader-repository>
| org.myapp:loader=EJB3PersistenceClassloader
| <loader-repository-config>
| java2ParentDelegation=false
| </loader-repository-config>
| </loader-repository>
|
|
| </jboss-app>
|
Now when i "touch" the *persistence.xml* file, which belongs to myapp_ejb3.jar (inside the EAR), the entire (EAR) application redeploys.
Is this expected? As far as i know, changes to only application.xml should have triggered the redeployment.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162027#4162027
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162027
17 years, 4 months
[Microcontainer] - Partial override of MapValue not working
by wolfc
Given the following code:
@MapValue(keyClass=String.class, value={}, valueClass=String.class)
| public void setDefaultPersistenceProperties(Properties p)
| {
| this.defaultPersistenceProperties = p;
| }
With the following override:
<bean name="PersistenceUnitDeployer" class="org.jboss.jpa.deployers.PersistenceUnitDeployer">
| <property name="defaultPersistenceProperties">
| <map>
| <entry>
| <key>hibernate.transaction.manager_lookup_class</key>
| <value>org.hibernate.transaction.JBossTransactionManagerLookup</value>
| </entry>
| </map>
| </property>
| </bean>
I still get: java.lang.IllegalArgumentException: Unable to determine type for value: hibernate.transaction.manager_lookup_class
Why is that?
(It also struck me as weird that MapValue.value is mandatory.)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162019#4162019
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162019
17 years, 4 months