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

[Deployers on JBoss (Deployers/JBoss)] - EAR Dependency

by vickyk

Can we have a dependency feature between the EAR's ? Right now we can have the dependency defined in the jee modules but does not yet exist at the EAR level . I have seen many of the users asking for such feature , can you initiate the discussion about it ? Here is the related JIRA http://jira.jboss.com/jira/browse/JBAS-3654 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157255#4157255 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157255

16 years, 3 months

1
0
0 / 0

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

by alesj

"wolfc" wrote : I think it must be moved out to a separate JPA deployer, which does persistence deployment for ear, war and jar. | Current PersistenceMetaDataUnitDeployer (or whatever its name is) already knows how to do this for all different artifact types. To handle war's WEB-INF/classes/META-INF, it's the WARStructure that also defines that directory as possible metadata location. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157235#4157235 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157235

16 years, 3 months

1
0
0 / 0

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

by wolfc

I think it must be moved out to a separate JPA deployer, which does persistence deployment for ear, war and jar. This should not be done in AS trunk, it should happen in a new project. In trunk there should be a switch to turn off persistence deployments, which should then be picked up by the new JPA deployer. That allows for a gradual transition. The interesting integration point will be the persistence unit injection facilitator. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157228#4157228 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157228

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

Its jbossxb that could be reporting more info like the element namespace or lack there of. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157224#4157224 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157224

16 years, 3 months

1
0
0 / 0

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

by ALRubinger

That's the piece I was looking for, thanks. Who should I talk to regarding a better error message (even something as simple as "Could not deploy; no XSD or DTD on [file] was declared" would do)? S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157222#4157222 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157222

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

Since the persistence_1_0.xsd schema specifically declares a targetNamespace, the descriptors will have to match it to validate. The persistence_1_0.xsd docs say the persistence namespace must be used as well: "persistence_1_0.xsd" wrote : | Persistence configuration files must indicate | the persistence schema by using the persistence namespace: | | http://java.sun.com/xml/ns/persistence | | and indicate the version of the schema by | using the version element as shown below: | | <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"> | ... | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157221#4157221 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157221

16 years, 3 months

1
0
0 / 0

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

by ALRubinger

EJB3 Persistence Spec 6.2.1 has samples that do not include a DTD or XSD declaration. Section 7.1.1 is a bit vauge as to whether the descriptor requires this information: anonymous wrote : When the container finds a persistence.xml file, it processes the persistence unit definitions that it contains. The container must validate the persistence.xml file against the persistence_1_0.xsd schema and report any validation errors. In any case, we'll need a more friendly error message to give the bean provider some sense of why the deployment failed. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157220#4157220 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157220

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

Its definitely required for the previous javaee descriptors where there are multiple versions, so I don't see this as much of a requirement. The reason the simple persistence key is not working is that when the PersistenceMetaData is resolved, its jaxb @XmlRootElement declares a namespace that does not match the empty namespace used by the descriptor. In general proper namespaces are needed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157218#4157218 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157218

16 years, 3 months

1
0
0 / 0

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

by ALRubinger

Should it be a requirement that a DTD/XSD is specified? Great practice, but an imposition to place upon our users. If yes, I'll fix all the tests and also the NCDFE. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157217#4157217 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157217

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

Ok, the problem is that there is no schemaLocation to map to the persistence_1_0.xsd key, and I guess the persistence key is only being used if the descriptor declares a DTD. | <?xml version="1.0" encoding="UTF-8"?> | <persistence> | <persistence-unit name="tempdb"> | <jta-data-source>java:/DefaultDS</jta-data-source> | <properties> | <property name="hibernate.hbm2ddl.auto" value="create-drop"/> | </properties> | </persistence-unit> | </persistence> | If I change it to use the correct namespace: | <?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="tempdb"> | <jta-data-source>java:/DefaultDS</jta-data-source> | <properties> | <property name="hibernate.hbm2ddl.auto" value="create-drop"/> | </properties> | </persistence-unit> | </persistence> | it deploys without any errors, but still reports 6 errors, still related to the security NCDFE: | Testcase: testOneToMany took 0.498 sec | Caused an ERROR | org/jboss/security/plugins/SecurityContextAssociation | java.lang.NoClassDefFoundError: org/jboss/security/plugins/SecurityContextAssociation | at org.jboss.ejb3.security.SecurityActions$4.run(SecurityActions.java:287) | at org.jboss.ejb3.security.SecurityActions$4.run(SecurityActions.java:285) | at java.security.AccessController.doPrivileged(Native Method) | at org.jboss.ejb3.security.SecurityActions.getSecurityContext(SecurityActions.java:283) | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157215#4157215 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157215

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