View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060307032512Lbuild.226
BUILD COMPLETE-build.226Date of build:03/07/2006 03:25:12Time to build:49 minutes 54 secondsLast changed:03/06/2006 09:36:40Last log entry:[JBAS-1504] type
In case of strict, all elements must be present in the SchemaBinding.
In case of lax, if element binding is found in the SchemaBinding then it
is used. If not then
- if there is unresolvedElementHandler set on the WildcardBinding then
it will be used to process the element
- if
Alexey Loubyansky wrote:
In case of strict, all elements must be present in the SchemaBinding.
In a SchemaBinding that can be resolved.
In case of lax, if element binding is found in the SchemaBinding
then it is used.
The above, of course, implies that the SchemaBinding was successfully
So I'm not understanding what triggers a SchemaBindingInitializer to be
loaded. For a configuration of a marshaller such as the following:
DefaultSchemaResolver resolver = new DefaultSchemaResolver();
JavaBeanSchemaInitializer si = new JavaBeanSchemaInitializer();
There must be a resolvable XSD for urn:jboss:simplejavabean:1.0.
Scott M Stark wrote:
So I'm not understanding what triggers a SchemaBindingInitializer to be
loaded. For a configuration of a marshaller such as the following:
DefaultSchemaResolver resolver = new DefaultSchemaResolver();
Then I don't see the point of the SchemaBindingInitializer. An XSD is
simply mapped to a SchemaBinding via the XsdBinder class, what I want is
to bypass the XSD and just tell the binding layer here is how to handle
the urn:jboss:simplejavabean:1.0 namespace elements.
-Original Message-
Related to this user forum question:
http://www.jboss.com/index.html?module=bbop=viewtopict=78545
how does ConnectionPoolDataSource fit into the jca layer? Is a separate
pool implementation that wraps this needed or what?
Scott Stark
VP Architecture Technology
JBoss
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060307171317
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line:
I'm deploying an EAR that contains an EJB3 bean. The EJB3Deployer
creates and registers an MBean that manages the deployment of the
EJB3Container using the servicecontroller manually
The problem:
The EJB3 container's mbean depends on an MBean that does not exist. I
do not get a deployment
URLDeploymentScanner.scan calls MainDeployer.checkIncompleteDeployments
to validate unsatisfied dependencies on each scan so check that.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Tuesday, March 07, 2006 3:17 PM
To:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060307182236
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060307190145
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line:
What I found was that unless the *top* DeploymentInfo has the unready
mbean listed in its member variable DeploymentInfo.mbeans, then there
is no error message printed.
So, I added the created mbeans to the EAR's DI.mbeans variable and got
the error message. Then I jarred the EAR in a .jar
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossretro-testsuite?log=log20060307213603
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jbossretro-testsuite.xml:75: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/concurrent-testsuite?log=log20060307214310
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-concurrent-testsuite.xml:73: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.4-testsuite?log=log20060307215117
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-portal.xml:70: The following error occurred while executing this line:
The deployment check should be traversing the nested dependency state
then.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Tuesday, March 07, 2006 5:09 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] no dependency
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060307215451
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line:
why doesn't the scanner just listIncompleteDeployments() after a scan
that involved a new deployment or a redeploy?
Scott M Stark wrote:
The deployment check should be traversing the nested dependency state
then.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
How long do I have to get EJB3 changes into Branch_4_0 before 4.0.4 goes
out? The 17th? Or sooner?
Thanks
--
Bill Burke
Chief Architect
JBoss Inc.
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that
Or latter.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Tuesday, March 07, 2006 8:11 PM
To: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] drop dead date for 4.0.4?
How long do I have to get EJB3 changes into Branch_4_0
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060307224904
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line:
I know :(
[EMAIL PROTECTED] wrote:
View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060307203159
BUILD FAILED
Ant Error
23 matches
Mail list logo
