[JBoss-dev] jboss-3.2-testsuite build.226 Build Fixed
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 mapping for boolean in finder wrong (added type-mapping for MAXDB) Unit Tests: (1848) Total Errors and Failures: (0)All Tests Passed Modifications since last build:(first 50 of 4)1.39.2.59modifiedaloubyanskyserver/src/etc/conf/default/standardjbosscmp-jdbc.xml[JBAS-1504] type mapping for boolean in finder wrong (added type-mapping for MAXDB)1.1.2.2.2.8modifieddimitrisbuild/docs/readme.htmlno message1.5.4.2modifieddimitristransaction/src/main/org/jboss/tm/LocalId.javaJBAS-2892, bring LocalId from 4.x to overcome serialization problem, the class is not really used here1.27.2.26modifiedtdieslerjboss.net/build.xmlUpdate to new version convention
Re: [JBoss-dev] minOccurs=0 not being used
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 unresolvedElementHandler is null then the element will be skipped. Scott M Stark wrote: So how does this: xs:any minOccurs=0 maxOccurs=unbounded processContents=lax/ compare to the previous: xs:any minOccurs=0 maxOccurs=unbounded / which should be processContents=strict? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexey Loubyansky Sent: Monday, March 06, 2006 3:27 AM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] minOccurs=0 not being used It's fixed now. Thanks. Scott M Stark wrote: http://jira.jboss.com/jira/browse/JBXB-56 is an issue that describes a simple testcase in head that shows this behavior. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] minOccurs=0 not being used
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 resolved for the element. If not then - if there is unresolvedElementHandler set on the WildcardBinding then it will be used to process the element - if unresolvedElementHandler is null then the element will be skipped. Scott M Stark wrote: So how does this: xs:any minOccurs=0 maxOccurs=unbounded processContents=lax/ compare to the previous: xs:any minOccurs=0 maxOccurs=unbounded / which should be processContents=strict? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexey Loubyansky Sent: Monday, March 06, 2006 3:27 AM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] minOccurs=0 not being used It's fixed now. Thanks. Scott M Stark wrote: http://jira.jboss.com/jira/browse/JBXB-56 is an issue that describes a simple testcase in head that shows this behavior. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] minOccurs=0 not being used
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(); resolver.addSchemaInitializer(urn:jboss:simplejavabean:1.0, si); resolver.addSchemaLocation(urn:jboss-test:xmbean:2.0, xml/mbeanserver/jboss_xmbean_2_0.xsd); I'm expecting that both the urn:jboss-test:xmbean:2.0 and urn:jboss:simplejavabean:1.0 namespaces can be handled. The urn:jboss:simplejavabean:1.0 has a code centric SchemaBinding while the urn:jboss-test:xmbean:2.0 has a SchemaBinding derived from the jboss_xmbean_2_0.xsd annotations. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexey Loubyansky Sent: Tuesday, March 07, 2006 3:28 AM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] minOccurs=0 not being used 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 resolved for the element. If not then - if there is unresolvedElementHandler set on the WildcardBinding then it will be used to process the element - if unresolvedElementHandler is null then the element will be skipped. Scott M Stark wrote: So how does this: xs:any minOccurs=0 maxOccurs=unbounded processContents=lax/ compare to the previous: xs:any minOccurs=0 maxOccurs=unbounded / which should be processContents=strict? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexey Loubyansky Sent: Monday, March 06, 2006 3:27 AM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] minOccurs=0 not being used It's fixed now. Thanks. Scott M Stark wrote: http://jira.jboss.com/jira/browse/JBXB-56 is an issue that describes a simple testcase in head that shows this behavior. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=1216 42 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720; dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] minOccurs=0 not being used
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(); JavaBeanSchemaInitializer si = new JavaBeanSchemaInitializer(); resolver.addSchemaInitializer(urn:jboss:simplejavabean:1.0, si); resolver.addSchemaLocation(urn:jboss-test:xmbean:2.0, xml/mbeanserver/jboss_xmbean_2_0.xsd); I'm expecting that both the urn:jboss-test:xmbean:2.0 and urn:jboss:simplejavabean:1.0 namespaces can be handled. The urn:jboss:simplejavabean:1.0 has a code centric SchemaBinding while the urn:jboss-test:xmbean:2.0 has a SchemaBinding derived from the jboss_xmbean_2_0.xsd annotations. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexey Loubyansky Sent: Tuesday, March 07, 2006 3:28 AM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] minOccurs=0 not being used 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 resolved for the element. If not then - if there is unresolvedElementHandler set on the WildcardBinding then it will be used to process the element - if unresolvedElementHandler is null then the element will be skipped. Scott M Stark wrote: So how does this: xs:any minOccurs=0 maxOccurs=unbounded processContents=lax/ compare to the previous: xs:any minOccurs=0 maxOccurs=unbounded / which should be processContents=strict? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexey Loubyansky Sent: Monday, March 06, 2006 3:27 AM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] minOccurs=0 not being used It's fixed now. Thanks. Scott M Stark wrote: http://jira.jboss.com/jira/browse/JBXB-56 is an issue that describes a simple testcase in head that shows this behavior. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=1216 42 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720; dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] minOccurs=0 not being used
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- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexey Loubyansky Sent: Tuesday, March 07, 2006 7:50 AM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] minOccurs=0 not being used 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(); JavaBeanSchemaInitializer si = new JavaBeanSchemaInitializer(); resolver.addSchemaInitializer(urn:jboss:simplejavabean:1.0, si); resolver.addSchemaLocation(urn:jboss-test:xmbean:2.0, xml/mbeanserver/jboss_xmbean_2_0.xsd); I'm expecting that both the urn:jboss-test:xmbean:2.0 and urn:jboss:simplejavabean:1.0 namespaces can be handled. The urn:jboss:simplejavabean:1.0 has a code centric SchemaBinding while the urn:jboss-test:xmbean:2.0 has a SchemaBinding derived from the jboss_xmbean_2_0.xsd annotations. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] javax.sql.ConnectionPoolDataSource in jca layer
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 Inc. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head-jdk-matrix Build Failed
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: /services/cruisecontrol/work/scripts/build-jboss-common.xml:64: Exit code: 1 See compile.log in Build Artifacts for details.Date of build:03/07/2006 17:13:17Time to build:16 minutes 57 secondsLast changed:03/07/2006 16:36:00Last log entry:Move the org.jboss.util.xml.Dom2Sax class to org.jboss.xb.util.Dom2Sax Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(first 50 of 48)1.2deletedstarksmcommon/src/main/org/jboss/util/xml/Dom2Sax.javaMove the org.jboss.util.xml.Dom2Sax class to org.jboss.xb.util.Dom2Sax1.26modifiedstarksmwebservice/src/main/org/jboss/ws/jaxb/JAXBMarshallerImpl.javaMove the org.jboss.util.xml.Dom2Sax class to org.jboss.xb.util.Dom2Sax1.41modifiedbillejb3/src/resources/ejb3-interceptors-aop.xmlfixes1.3deletedstarksmcommon/src/main/org/jboss/util/stream/AppendObjectOutputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/AppendingObjectOutputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/AutoResetObjectOutputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/NullInputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/NullOutputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/ObjectOutputStreamAdapter.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/Printable.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.6modifiedstarksmcommon/src/main/org/jboss/util/stream/Streams.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.40modifiedbillejb3/src/resources/ejb3-interceptors-aop.xmlremove unnecessary log.info and changed to log.debug1.7modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ConsumerEndpoint.javaRenamed message delegates to message proxies1.15modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/DeliveryRunnable.javaRenamed message delegates to message proxies1.25modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerConsumerEndpoint.javaRenamed message delegates to message proxies1.5modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/advised/ConsumerAdvised.javaRenamed message delegates to message proxies1.6modifiedtimfoxjms/src/main/org/jboss/jms/server/remoting/JMSWireFormat.javaRenamed message delegates to message proxies1.4modifiedtimfoxjms/src/main/org/jboss/messaging/core/plugin/SimpleMessageReference.javaRenamed message delegates to message proxies1.5deletedtimfoxjms/tests/src/org/jboss/test/messaging/jms/MessageDelegateTest.javaRenamed message delegates to message proxies1.15modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/ReferencingTest.javaRenamed message delegates to message proxies1.23modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/TemporaryDestinationTest.javaRenamed message delegates to message proxies1.4modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/WireFormatTest.javaRenamed message delegates to message proxies1.15modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/message/JMSExpirationHeaderTest.javaRenamed message delegates to message proxies1.28modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/message/MessageTest.javaRenamed message delegates to message proxies1.21modifiedtimfoxjms/src/main/org/jboss/jms/client/JBossConnectionConsumer.javaRenamed message delegates to message proxies1.37modifiedtimfoxjms/src/main/org/jboss/jms/client/JBossSession.javaRenamed message delegates to message proxies1.8modifiedtimfoxjms/src/main/org/jboss/jms/client/container/AsfAspect.javaRenamed message delegates to message proxies1.9modifiedtimfoxjms/src/main/org/jboss/jms/client/container/FactoryAspect.javaRenamed message delegates to message
[JBoss-dev] no dependency error message
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 error message though. No message, nothing...However, if I manually go to the ServiceController through the JMX-Console I do see the correct message when invoking listIncompletelyDeployed() [ObjectName: jboss.j2ee:service=EJB3,ear=JiraTestApp.ear,jar=JiraTestEJB.jar,name=JiraTestInnerBean State: NOTYETINSTALLED I Depend On: persistence.units:unitName=jiratest ] What's up here? Any ideas? -- Bill Burke Chief Architect JBoss Inc. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] no dependency error message
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: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] no dependency error message 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 error message though. No message, nothing...However, if I manually go to the ServiceController through the JMX-Console I do see the correct message when invoking listIncompletelyDeployed() [ObjectName: jboss.j2ee:service=EJB3,ear=JiraTestApp.ear,jar=JiraTestEJB.jar,name=Jir aTestInnerBean State: NOTYETINSTALLED I Depend On: persistence.units:unitName=jiratest ] What's up here? Any ideas? -- Bill Burke Chief Architect JBoss Inc. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head-jdk-matrix Build Failed
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: /services/cruisecontrol/work/scripts/build-jboss-common.xml:64: Exit code: 1 See compile.log in Build Artifacts for details.Date of build:03/07/2006 18:22:36Time to build:21 minutes 42 secondsLast changed:03/07/2006 18:02:57Last log entry:Add the xerces classpath Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(first 50 of 48)1.4modifiedstarksmmbeans/build.xmlAdd the xerces classpath1.1addedstarksmcommon/src/main/org/jboss/xb/util/Dom2Sax.javaMove the org.jboss.util.xml.Dom2Sax class to org.jboss.xb.util.Dom2Sax1.2deletedstarksmcommon/src/main/org/jboss/util/xml/Dom2Sax.javaMove the org.jboss.util.xml.Dom2Sax class to org.jboss.xb.util.Dom2Sax1.26modifiedstarksmwebservice/src/main/org/jboss/ws/jaxb/JAXBMarshallerImpl.javaMove the org.jboss.util.xml.Dom2Sax class to org.jboss.xb.util.Dom2Sax1.41modifiedbillejb3/src/resources/ejb3-interceptors-aop.xmlfixes1.3deletedstarksmcommon/src/main/org/jboss/util/stream/AppendObjectOutputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/AppendingObjectOutputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/AutoResetObjectOutputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/NullInputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/NullOutputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/ObjectOutputStreamAdapter.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/Printable.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.6modifiedstarksmcommon/src/main/org/jboss/util/stream/Streams.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.40modifiedbillejb3/src/resources/ejb3-interceptors-aop.xmlremove unnecessary log.info and changed to log.debug1.7modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ConsumerEndpoint.javaRenamed message delegates to message proxies1.15modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/DeliveryRunnable.javaRenamed message delegates to message proxies1.25modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerConsumerEndpoint.javaRenamed message delegates to message proxies1.5modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/advised/ConsumerAdvised.javaRenamed message delegates to message proxies1.6modifiedtimfoxjms/src/main/org/jboss/jms/server/remoting/JMSWireFormat.javaRenamed message delegates to message proxies1.4modifiedtimfoxjms/src/main/org/jboss/messaging/core/plugin/SimpleMessageReference.javaRenamed message delegates to message proxies1.5deletedtimfoxjms/tests/src/org/jboss/test/messaging/jms/MessageDelegateTest.javaRenamed message delegates to message proxies1.15modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/ReferencingTest.javaRenamed message delegates to message proxies1.23modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/TemporaryDestinationTest.javaRenamed message delegates to message proxies1.4modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/WireFormatTest.javaRenamed message delegates to message proxies1.15modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/message/JMSExpirationHeaderTest.javaRenamed message delegates to message proxies1.28modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/message/MessageTest.javaRenamed message delegates to message proxies1.21modifiedtimfoxjms/src/main/org/jboss/jms/client/JBossConnectionConsumer.javaRenamed message delegates to message proxies1.37modifiedtimfoxjms/src/main/org/jboss/jms/client/JBossSession.javaRenamed message delegates to message proxies1.8modifiedtimfoxjms/src/main/org/jboss/jms/client/container/AsfAspect.javaRenamed message delegates to message
[JBoss-dev] jboss-head-jdk-matrix Build Failed
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: /services/cruisecontrol/work/scripts/build-jboss-common.xml:64: Exit code: 1 See compile.log in Build Artifacts for details.Date of build:03/07/2006 19:01:45Time to build:19 minutes 27 secondsLast changed:03/07/2006 18:37:07Last log entry:changes access from private to protected to allow subclasses to usesome utility methods/variables. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(first 50 of 51)1.50modifiedstalepaop/src/main/org/jboss/aop/instrument/Instrumentor.javachanges access from private to protected to allow subclasses to usesome utility methods/variables.1.38modifiedstalepaop/src/main/org/jboss/aop/instrument/MethodExecutionTransformer.javachanges access from private to protected to allow subclasses to usesome utility methods/variables.1.4modifiedstarksmmbeans/build.xmlAdd the xerces classpath1.1addedstarksmcommon/src/main/org/jboss/xb/util/Dom2Sax.javaMove the org.jboss.util.xml.Dom2Sax class to org.jboss.xb.util.Dom2Sax1.2deletedstarksmcommon/src/main/org/jboss/util/xml/Dom2Sax.javaMove the org.jboss.util.xml.Dom2Sax class to org.jboss.xb.util.Dom2Sax1.26modifiedstarksmwebservice/src/main/org/jboss/ws/jaxb/JAXBMarshallerImpl.javaMove the org.jboss.util.xml.Dom2Sax class to org.jboss.xb.util.Dom2Sax1.41modifiedbillejb3/src/resources/ejb3-interceptors-aop.xmlfixes1.3deletedstarksmcommon/src/main/org/jboss/util/stream/AppendObjectOutputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/AppendingObjectOutputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/AutoResetObjectOutputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/NullInputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/NullOutputStream.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/ObjectOutputStreamAdapter.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.3deletedstarksmcommon/src/main/org/jboss/util/stream/Printable.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.6modifiedstarksmcommon/src/main/org/jboss/util/stream/Streams.javaDrop the Constants and use of ThrowableHandler to break util/streams package cycle and get rid of the unused io stream classes.1.40modifiedbillejb3/src/resources/ejb3-interceptors-aop.xmlremove unnecessary log.info and changed to log.debug1.7modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ConsumerEndpoint.javaRenamed message delegates to message proxies1.15modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/DeliveryRunnable.javaRenamed message delegates to message proxies1.25modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerConsumerEndpoint.javaRenamed message delegates to message proxies1.5modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/advised/ConsumerAdvised.javaRenamed message delegates to message proxies1.6modifiedtimfoxjms/src/main/org/jboss/jms/server/remoting/JMSWireFormat.javaRenamed message delegates to message proxies1.4modifiedtimfoxjms/src/main/org/jboss/messaging/core/plugin/SimpleMessageReference.javaRenamed message delegates to message proxies1.5deletedtimfoxjms/tests/src/org/jboss/test/messaging/jms/MessageDelegateTest.javaRenamed message delegates to message proxies1.15modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/ReferencingTest.javaRenamed message delegates to message proxies1.23modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/TemporaryDestinationTest.javaRenamed message delegates to message proxies1.4modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/WireFormatTest.javaRenamed message delegates to message proxies1.15modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/message/JMSExpirationHeaderTest.javaRenamed message delegates to message proxies1.28modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/message/MessageTest.javaRenamed message
Re: [JBoss-dev] no dependency error message
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 and didn't get the error message anymore. What I think I'll do is look for the top DI and add the registered mbean to it. The SARDeployer will try to create/start DI.mbeans if they exist, but the code seems to check to make sure it hasn't already been called. Scott M Stark wrote: 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: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] no dependency error message 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 error message though. No message, nothing...However, if I manually go to the ServiceController through the JMX-Console I do see the correct message when invoking listIncompletelyDeployed() [ObjectName: jboss.j2ee:service=EJB3,ear=JiraTestApp.ear,jar=JiraTestEJB.jar,name=Jir aTestInnerBean State: NOTYETINSTALLED I Depend On: persistence.units:unitName=jiratest ] What's up here? Any ideas? -- Bill Burke Chief Architect JBoss Inc. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jbossretro-testsuite Build Completed With Testsuite Errors
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: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build:03/07/2006 21:36:03Time to build:7 minutes 2 secondsLast changed:03/06/2006 15:09:55Last log entry:Revert the reentrant lock stuff to backport concurrent utiland remove tests that don't have coverage. Unit Tests: (1233) Total Errors and Failures: (5)unknownorg.jboss.test.concurrent.ReentrantLockTesttestPrivilegedThreadFactoryorg.jboss.test.concurrent.ExecutorsTesttestHasQueuedThreadsorg.jboss.test.concurrent.SemaphoreTesttestGetQueueLengthorg.jboss.test.concurrent.SemaphoreTesttestGetQueuedThreadsorg.jboss.test.concurrent.SemaphoreTest Modifications since last build:(first 50 of 166)1.2deletedadriansrc/test/org/jboss/test/concurrent/LockSupportTest.javaRevert the reentrant lock stuff to backport concurrent utiland remove tests that don't have coverage.1.4deletedadriansrc/test/org/jboss/test/concurrent/ReentrantReadWriteLockTest.javaRevert the reentrant lock stuff to backport concurrent utiland remove tests that don't have coverage.1.2deletedadriansrc/test/org/jboss/test/concurrent/ThreadTest.javaRevert the reentrant lock stuff to backport concurrent utiland remove tests that don't have coverage.1.3modifiedadriansrc/test/org/jboss/test/concurrent/SemaphoreTest.javaProvide more information than "UnexpectedException"1.8modifiedadrianthirdparty/javassist/lib/javassist.jarRemove the signature fixing.We need something a bit more robust.1.3modifiedadriansrc/test/org/jboss/test/concurrent/ReentrantReadWriteLockTest.javaWork around unweaved stuff in the ReentrantReadWriteLock test1.4modifiedadriansrc/test/org/jboss/test/concurrent/JSR166TestCase.javaExclude tests for UncaughtExceptionHandler1.2modifiedadriansrc/test/org/jboss/test/concurrent/SemaphoreTest.javaRemove tests for semaphore operations with multiple permitssince backport concurrent util doesn't support these operations.1.7modifiedadrianthirdparty/javassist/lib/javassist.jarAdd the ability to change the signature of a constant pool methodref entry.This is useful for JDK5 to 1.4 mapping, e.g.java.lang.String.clone()Ljava.lang.String; - java.lang.String.clone()Ljava.lang.Object;Apply this for ReentrantLock.read/writeLock()1.6modifiedadrianthirdparty/javassist/lib/javassist.jarUse the version of javassist that handles no parameter annotations properly.1.2modifiedadriansrc/test/org/jboss/test/concurrent/ThreadPoolExecutorTest.javaComment out tests that use non-existant api1.2modifiedadriansrc/test/org/jboss/test/concurrent/ThreadPoolExecutorSubclassTest.javaComment out tests that use non-existant api1.2modifiedadriansrc/test/org/jboss/test/concurrent/TreeSetTest.javaComment out tests that use non-existant apiSimulate pollFirst/Last used by this test.1.2modifiedadriansrc/test/org/jboss/test/concurrent/TreeMapTest.javaComment out tests that use non-existant api1.2modifiedadriansrc/test/org/jboss/test/concurrent/TimeUnitTest.javaComment out tests that use non-existant api1.1addedadriansrc/test/org/jboss/test/concurrent/RunnableScheduledFuture.javaInclude non-existant api in org.jboss.test.concurrent1.1addedadriansrc/test/org/jboss/test/concurrent/RunnableFuture.javaInclude non-existant api in org.jboss.test.concurrent1.3modifiedadriansrc/test/org/jboss/test/concurrent/JSR166TestCase.javaComment out non-existant test1.2modifiedrcampbellsrc/test/org/jboss/test/concurrent/ReentrantReadWriteLockTest.javaJBAS-2814 - remove tests of non java 5 methods1.2modifiedrcampbellsrc/test/org/jboss/test/concurrent/LinkedListTest.javaJBAS-2814 - remove tests of non java 5 methods1.2modifiedrcampbellsrc/test/org/jboss/test/concurrent/JSR166TestCase.javaJBAS-2814 - removed tests for classes not present in jdk51.2deletedrcampbellsrc/test/org/jboss/test/concurrent/LinkedBlockingDequeTest.javaJBAS-2814 - removed tests for classes not present in jdk51.2deletedrcampbellsrc/test/org/jboss/test/concurrent/TreeSubMapTest.javaJBAS-2814 - removed tests for classes not present in jdk51.2deletedrcampbellsrc/test/org/jboss/test/concurrent/TreeSubSetTest.javaJBAS-2814 - removed tests for classes not present in jdk51.1addedrcampbellsrc/test/org/jboss/test/concurrent/JSR166TestCase.javaJBAS-2814: Initial import of jsr166 tck. Currently excluded from build since it has dependencies not available in jdk5.1.1addedrcampbellsrc/test/org/jboss/test/concurrent/LinkedBlockingDequeTest.javaJBAS-2814: Initial import of jsr166 tck. Currently excluded from build since it has dependencies not available in
[JBoss-dev] concurrent-testsuite Build Completed With Testsuite Errors
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: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build:03/07/2006 21:43:10Time to build:7 minutes 20 secondsLast changed:02/21/2006 05:34:26Last log entry:Build concurrent with JDK1.4 Unit Tests: (1707) Total Errors and Failures: (1)testPrivilegedThreadFactory.ExecutorsTest Modifications since last build:(first 50 of 1)1.3modifiedadrian/.classpathBuild concurrent with JDK1.4
[JBoss-dev] jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
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: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:96: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:212: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build:03/07/2006 21:51:17Time to build:3 minutes 14 secondsLast changed:03/07/2006 15:39:58Last log entry:forgot to add the controller name in the second portal servlet of core Unit Tests: (109) Total Errors and Failures: (2)org.jboss.portal.test.server.parameters.ParametersTestSuiteorg.jboss.portal.test.server.servlet.ServletTestSuite Modifications since last build:(first 50 of 1428)1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/MarkupType.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/MissingParametersFault.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/ModelDescription.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/ModelTypes.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/ModifyRegistration.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/NamedString.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/Online.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/OperationFailedFault.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/PerformBlockingInteraction.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/PersonName.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/PortletContext.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled
RE: [JBoss-dev] no dependency error message
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 error message 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 and didn't get the error message anymore. What I think I'll do is look for the top DI and add the registered mbean to it. The SARDeployer will try to create/start DI.mbeans if they exist, but the code seems to check to make sure it hasn't already been called. Scott M Stark wrote: 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: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] no dependency error message 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 error message though. No message, nothing...However, if I manually go to the ServiceController through the JMX-Console I do see the correct message when invoking listIncompletelyDeployed() [ObjectName: jboss.j2ee:service=EJB3,ear=JiraTestApp.ear,jar=JiraTestEJB.jar,name=Jir aTestInnerBean State: NOTYETINSTALLED I Depend On: persistence.units:unitName=jiratest ] What's up here? Any ideas? -- Bill Burke Chief Architect JBoss Inc. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors
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: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build:03/07/2006 21:54:51Time to build:35 minutes 1 secondLast changed:03/07/2006 13:38:30Last log entry:Fixed a problem with LocalSyncHandlers being created for remotely initiated GTXs Unit Tests: (1377) Total Errors and Failures: (1)testTxCollectionRemoveorg.jboss.cache.aop.loader.FileCacheLoaderAopTest Modifications since last build:(first 50 of 21)1.34modifiedmsurtanisrc/org/jboss/cache/interceptors/TxInterceptor.javaFixed a problem with LocalSyncHandlers being created for remotely initiated GTXs1.33modifiedmsurtanisrc/org/jboss/cache/interceptors/TxInterceptor.javaAdded error message for null tx entry1.7modifiedmsurtanidocs/TreeCache/en/modules/mgmt_information.xmlJBCACHE-4891.17modifiedmsurtanidocs/faq/en/master.xmlJBCACHE-4891.16modifiedbwangdocs/faq/en/master.xmlupd1.13modifiedbwangdocs/TreeCacheAop/en/master.xmlUPD fpr 1.3 release1.5modifiedbwangdocs/TreeCacheAop/en/modules/api.xmlUPD fpr 1.3 release1.4modifiedbwangdocs/TreeCacheAop/en/modules/appendix.xmlUPD fpr 1.3 release1.7modifiedbwangdocs/TreeCacheAop/en/modules/architecture.xmlUPD fpr 1.3 release1.4modifiedbwangdocs/TreeCacheAop/en/modules/configuration.xmlUPD fpr 1.3 release1.8modifiedbwangdocs/TreeCacheAop/en/modules/instrumentation.xmlUPD fpr 1.3 release1.8modifiedbwangdocs/TreeCacheAop/en/modules/introduction.xmlUPD fpr 1.3 release1.6modifiedbwangdocs/TreeCacheAop/en/modules/jbossaop.xmlUPD fpr 1.3 release1.8modifiedbwangdocs/TreeCacheAop/en/modules/term.xmlUPD fpr 1.3 release1.1addedbwangdocs/design/CollectionRefactoring.txtadded for 2.0, perhaps1.32modifiedmsurtanisrc/org/jboss/cache/interceptors/TxInterceptor.javaRolled back fix - broke too many things1.31modifiedmsurtanisrc/org/jboss/cache/interceptors/TxInterceptor.javaFixed bug in removing tx stuff when an exception occurs when committing1.12modifiedmsurtanidocs/Changelog.txtAdded changelog1.84modifiedmsurtani/build.xmlJBCACHE-4871.83modifiedrrajasekaran/build.xmlUpdated Version to Beta11.7modifiedbwangtests/functional/org/jboss/cache/aop/loader/CacheLoaderTestsBase.javaJBCACHE-477 Created to illustrate this problem.
Re: [JBoss-dev] no dependency error message
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 Behalf Of Bill Burke Sent: Tuesday, March 07, 2006 5:09 PM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] no dependency error message 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 and didn't get the error message anymore. What I think I'll do is look for the top DI and add the registered mbean to it. The SARDeployer will try to create/start DI.mbeans if they exist, but the code seems to check to make sure it hasn't already been called. Scott M Stark wrote: 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: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] no dependency error message 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 error message though. No message, nothing...However, if I manually go to the ServiceController through the JMX-Console I do see the correct message when invoking listIncompletelyDeployed() [ObjectName: jboss.j2ee:service=EJB3,ear=JiraTestApp.ear,jar=JiraTestEJB.jar,name=Jir aTestInnerBean State: NOTYETINSTALLED I Depend On: persistence.units:unitName=jiratest ] What's up here? Any ideas? -- Bill Burke Chief Architect JBoss Inc. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] drop dead date for 4.0.4?
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 extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] drop dead date for 4.0.4?
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 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 extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors
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: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build:03/07/2006 22:49:04Time to build:71 minutes 28 secondsLast changed:12/31/2005 20:37:24Last log entry:JBREM-272:Added tests for (clientPool != null) and (threadPool != null) in cleanup. Unit Tests: (287) Total Errors and Failures: (2)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(java_serialization)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(jboss_serialization) Modifications since last build:(first 50 of 2128)1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutClientTest.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutServerTest.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutTestCase.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/ComplexObject.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvocationHandler.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestServer.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestServerImpl.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TransporterTestCase.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/SSLInvokerConstants.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerClientTest.javaJBREM-235 - added new lgpl headers.1.8modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerTestCase.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerClientTest.javaJBREM-235 - added new lgpl headers.1.7modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-235 - added new lgpl headers.1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerTestCase.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleClient.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleServer.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/keepalive/TimeoutClientTest.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/keepalive/TimeoutServerTest.javaJBREM-235 - added new lgpl headers.1.7modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-270:Replaced "," with ""1.6modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-270:Replaced "," with ""1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-253 - changed to use coyote connector by default instead of http server invoker. Also adding many fixes so now only ssl related http tests are failing within the tests suite.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/.truststoreJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many
Re: [JBoss-dev] jboss-head-jdk-matrix Build Failed
I know :( [EMAIL PROTECTED] wrote: View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060307203159 BUILD FAILED Ant Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-common.xml:64: Exit code: 1 See compile.log in Build Artifacts for details. Date of build:03/07/2006 20:31:59 Time to build:21 minutes 9 seconds Last changed:03/07/2006 20:22:56 Last log entry:add manually deployed mbeans to top level DI so that error message is printed out on dependency errors
