June 2008 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Re: trunk Ejb3Deployment is incompatible with jbossas trunk

by scott.stark＠jboss.org

Ok, my poms/thirdparty say its CR9, but my build might be out of sync. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157146#4157146 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157146

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: trunk Ejb3Deployment is incompatible with jbossas trunk

by alesj

It means you're using JBossXB.2.0.0.CR8 instead of 9. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157141#4157141 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157141

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: trunk Ejb3Deployment is incompatible with jbossas trunk

by scott.stark＠jboss.org

I don't see this once I updated the metadata-deployer-beans.xml, but I do see: | Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Attribute is not bound: element owner {http://java.sun.com/xml/ns/persistence}property, attribute name | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:193) | at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153) | at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:191) | at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:165) | at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132) | at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118) | at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:128) | | <?xml version="1.0" encoding="UTF-8"?> | <persistence xmlns="http://java.sun.com/xml/ns/persistence" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" | version="1.0"> | <persistence-unit name="bookingDatabase"> | <provider>org.hibernate.ejb.HibernatePersistence</provider> | <jta-data-source>java:/bookingDatasource</jta-data-source> | <properties> | <property name="hibernate.hbm2ddl.auto" value="create-drop"/> | <property name="hibernate.show_sql" value="true"/> |  | <property name="hibernate.cache.provider_class" value="org.hibernate.cache.HashtableCacheProvider"/> | <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup"/> | </properties> | </persistence-unit> | </persistence> | It looks like the name attribute should be mapped correctly based on the PersistenceUnitMetaData annotations: | @XmlElementWrapper(name="properties") | @JBossXmlMapEntry(name="property") | @JBossXmlMapKeyAttribute(name="name") | @JBossXmlMapValueAttribute(name="value") | public void setProperties(Map<String, String> properties) | { | this.properties = properties; | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157137#4157137 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157137

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: DeploymentScopeBaseName from JAR prepending JNDI Name

by alesj

"alesj" wrote : "scott.stark(a)jboss.org" wrote : I see Ales has added back in a hack to check the deployment unit suffix for ".ear" to get the jboss-seam-dvd application to work. | | | That was Carlo. But it was a good hack. :-) We at least saw that we're on the right path with making Seam run in AS5. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157135#4157135 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157135

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: DeploymentScopeBaseName from JAR prepending JNDI Name

by alesj

"scott.stark(a)jboss.org" wrote : I see Ales has added back in a hack to check the deployment unit suffix for ".ear" to get the jboss-seam-dvd application to work. | That was Carlo. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157130#4157130 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157130

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: trunk Ejb3Deployment is incompatible with jbossas trunk

by scott.stark＠jboss.org

Can you verify if the tests are running against a server with the 74354 rev change that adds the org.jboss.metadata.jpa.spec.PersistenceMetaData mapping to server/src/etc/deployers/metadata-deployer-beans.xml? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157129#4157129 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157129

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: DeploymentScopeBaseName from JAR prepending JNDI Name

by scott.stark＠jboss.org

"wolfc" wrote : This is becoming ugly. | A deployment scope was meant to denote a JavaEEApplication (/ EAR) and thus it implements it as such. If the usage has changed we should at least disconnect DeploymentScope from JavaEEApplication. | Its a resolution context/api now. Is the JavaEEApplication still useful? "wolfc" wrote : | Furthermore the determination of whether there is an EAR or not appears to be broken. As the jboss-seam-dvd application gets deployed with a deployment scope with a null base name. I'll have to see why that is. I see Ales has added back in a hack to check the deployment unit suffix for ".ear" to get the jboss-seam-dvd application to work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157127#4157127 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157127

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JBPAPP-864/EJBTHREE-1109 - clustered home proxies

by galder.zamarreno＠jboss.com

"bstansberry(a)jboss.com" wrote : "galder.zamarreno(a)jboss.com" wrote : I think it might have been possible to retrieve the proxy factory by looking it up in JNDI and the calling any of the createProxies accordingly. I have the feeling that this solution would have indirectly gone through the Dispatcher as well. | | Yes, it would go through the dispatcher as well. But that becomes an internal detail of how the proxy factory works, and doesn't leak into StatefulContainer. | | I'm not advocating changing this for 4.x, as the usage of dispatcher is not going to change. :) But for trunk, think about it a bit. Ok, I think you've got a point there. I'll leave it as it is for 4.x and rethink it for trunk. Thanks for the feedback :)) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157121#4157121 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157121

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by dimitris＠jboss.org

I'll put back our implementation while adding a missing feature: http://jira.jboss.com/jira/browse/JBCOMMON-56 If there are other problems, we'll see then. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157111#4157111 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157111

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by anil.saldhana＠jboss.com

1) After AS5 start, why is there a consistent scan of console-mgr.sar and jbossws.sar only? 2) Dimitris, what are you planning to do? Override some method in FileUrlConnection? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157106#4157106 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157106

16 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums June 2008