[JBoss-dev] Thread pooling etc.
I hate to bring this up, given the trouble I've caused recently, but it's been on my mind... Given the weird behavior of EDU.oswego.cs.dl.util.concurrent.PooledExecutor to queue rather than create new threads, wouldn't it be better to replace it with something else that needs less idle threads. I bring this up, given that typically the servers I operate with run around 300-500 threads each, about 60-70% of them JBoss's. It seems like (and this isn't without vigorous proof) that the java.util.concurrent thread pool for JDK 1.5 is superior to the concurrent library in current use. Here is a link to a back-port for JDK 1.4: http://www.mathcs.emory.edu/dcl/util/backport-util-concurrent/ --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Moving sequenceNumber from ServiceMBeanSupport to JBossNotificationBroadcasterSupport
Currently we have sequenceNumber as private in ServiceMBeanSupport, with
mbeans extending this baseclass to use
getNextNotificationSequenceNumber() to get sequence numbers when
emitting notifcations:
/** Sequence number for jmx notifications we send out. */
private SynchronizedLong sequenceNumber = new SynchronizedLong(0);
protected long getNextNotificationSequenceNumber()
{
return sequenceNumber.increment();
}
I have a usecase where I want the Mbean to let a 3rd class it creates to
use the mbean's broadcasting capability, by passing a
JBossNotificationBroadcasterSupport, which is the baseclass of
ServiceMbeanSupport. The 3rd class currently can use
JBossNotificationBroadcasterSupport.sendNotification(), but it doesn't
have access to the getNextNotificationSequenceNumber().
It seems to me, a lot more natural to move the
getNextNotificationSequenceNumber() in the
JBossNotificationBroadcasterSupport baseclass and make it public (like
all the other methods in JBossNotificationBroadcasterSupport), thus
enabling 3rd helper classes to emit notifications on behalf of the
mbean.
I think this change is compatible with mbeans extending
ServiceMBeanSupport. Otherwise, getNextNotificationSequenceNumber()
could stay in place, but be changed to public.
Any thoughts, objections?
---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head-jdk-matrix build.558 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050901184259Lbuild.558 BUILD COMPLETE - build.558Date of build: 09/01/2005 18:42:59Time to build: 18 minutes 35 secondsLast changed: 09/01/2005 14:23:44Last log entry: Reverted to previous snapshot of javassist 3.1 RC1 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last builds: (first 50 of 19)1.30modifiedkkhanaop/src/main/org/jboss/aop/AOPClassPool.javaReverted to previous snapshot of javassist 3.1 RC11.8modifiedgenmanmessaging/src/main/org/jboss/mq/AcknowledgementRequest.javaRevert accident change in AcknowledgementRequest, the default upon constructionshould be NACK. And every StringBuffer is sacred.1.23modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/AbstractMetaDataBuilder.javaFix wrappedParameters with primitives1.14modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/TypesMetaData.javaFix wrappedParameters with primitives1.21modifiedtdieslerwebservice/src/main/org/jboss/ws/server/WebServiceDeployerJSE.javaFix wrappedParameters with primitives1.4modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/TypeMappingMetaData.javaAdd qname-scope element1.6modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/OperationMetaData.javaAdd more tracing1.20modifiedtdieslerwebservice/src/main/org/jboss/ws/server/WebServiceDeployerJSE.javaUse annotation class loader for building meta data1.22modifiedkkhanaop/docs/reference/reference/en/modules/running.xml*** empty log message ***1.29modifiedkkhanaop/src/main/org/jboss/aop/AOPClassPool.javaChanges to work with javassist RC1 proper1.22modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/AbstractMetaDataBuilder.javaDerrive TypeMappingMetaData from xsModel contained simpleTypes1.13modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/TypesMetaData.javaDerrive TypeMappingMetaData from xsModel contained simpleTypes1.3modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/TypeMappingMetaData.javaprotect agains invali qname-scope1.4modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/wsdl/WSDLDefinitionsFactory.javachange log level1.8modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/AttributeBinding.javaadded QName to element and attribute bindings1.9modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/ElementBinding.javaadded QName to element and attribute bindings1.10modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/SchemaBinding.javaadded QName to element and attribute bindings1.15modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/TypeBinding.javaadded QName to element and attribute bindings1.25modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.javaadded QName to element and attribute bindings
[JBoss-dev] jboss-4.0-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050901163322 BUILD FAILEDAnt Error Message: build timeoutDate of build: 09/01/2005 16:33:22Time to build: Last changed: 09/01/2005 10:14:32Last log entry: merge server controller tasks in to 4.0 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last builds: (first 50 of 7536)1.28.2.4modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/ServiceObjectFactory.javaSync webservices with HEAD.Fix samples build.1.1.2.8modifiedjgreenewebservice/src/main/org/jboss/webservice/client/Stub.javaPackage prefix SSL transport properties1.2.2.3modifiedtdieslerwebservice/src/resources/jboss-ws4ee.sar/META-INF/axis-server-config.xmlRemove Axis version service1.1.2.7modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/Stub.javaBackward compatibility for client timeout1.1.2.6modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/Stub.javajavadoc1.1.2.5modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/Stub.javaAdd support for transport properties1.4.2.11modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/PortProxy.javaAdd support for transport properties1.10.2.9modifiedtdieslerwebservice/src/main/org/jboss/webservice/ServiceDeployerEJB.javaFix: JBWS-3091.4.2.10modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/PortProxy.javaFix CTS failures that use doc/lit unwrapping.1.20.2.11modifiedtdieslerwebservice/src/main/org/jboss/webservice/server/InvokerProvider.javaFix CTS failures that use doc/lit unwrapping.1.6.2.9modifiedtdieslerwebservice/src/main/org/jboss/webservice/encoding/ser/MetaDataTypeDesc.javaSupport unwrapping of document style parameters on the server side.1.20.2.10modifiedtdieslerwebservice/src/main/org/jboss/webservice/server/InvokerProvider.javaSupport unwrapping of document style parameters on the server side.1.4.4.3modifiedtdieslerwebservice/src/main/org/jboss/webservice/server/ServiceEndpointInterceptor.javaSupport unwrapping of document style parameters on the server side.1.9.2.6modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/CallImpl.javaSupport unwrapping of document style parameters on the server side.1.4.2.9modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/PortProxy.javaSupport unwrapping of document style parameters on the server side.1.1.2.9modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/BeanXMLMetaData.javaSupport unwrapping of document style parameters on the server side.1.40.2.24modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/ServiceDescription.javaSupport unwrapping of document style parameters on the server side.1.8.2.14modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/TypeMappingDescription.javaSupport unwrapping of document style parameters on the server side.1.22.2.10modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/WSDDGenerator.javaSupport unwrapping of document style parameters on the server side.1.4.2.4modifiedtdieslerwebservice/src/main/org/jboss/webservice/server/JBossRPCInvocation.javaSupport doc style parameter wrapping, first cut.1.1.2.8modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/BeanXMLMetaData.javaUse DOMUtils from jboss.util1.40.2.23modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/ServiceDescription.javaUse DOMUtils from jboss.util1.8.2.13modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/TypeMappingDescription.javaUse DOMUtils from jboss.util1.1.4.2deletedtdieslerwebservice/src/main/org/jboss/webservice/util/DOMUtils.javaUse DOMUtils from jboss.util1.8.2.6modifiedtdieslerwebservice/src/main/org/jboss/webservice/server/ServiceEndpointServlet.javaUse the same ServiceEndpointID param name as in jbossws1.7.4.3modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/ServiceFactoryImpl.javaSupport multiple wsdl service elements as long as they have a single port1.40.2.22modifiedbillwebservice/src/main/org/jboss/webservice/deployment/ServiceDescription.javamove org.jboss.xml to org.jboss.xb1.22.2.9modifiedbillwebservice/src/main/org/jboss/webservice/deployment/WSDDGenerator.javamove org.jboss.xml to org.jboss.xb1.17.2.3modifiedbillwebservice/src/main/org/jboss/webservice/metadata/WebservicesFactory.javamove org.jboss.xml to org.jboss.xb1.7.4.2modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/ServiceFactoryImpl.javasync ws4ee metadata with head1.28.2.3modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/ServiceObjectFactory.javasync ws4ee metadata with head1.6.2.4modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/ServiceReferenceable.javasync ws4ee metadata with head1.40.2.21modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/ServiceDescription.javasync ws4ee metadata with he
Re: [JBoss-dev] EJB3 question
I think you have to do jndi lookups for other ejbs, no? I don't think the specifications define how to reference remote EJBs. Francisco Reverbel wrote: Can an EJB3 have ejb-refs that refer to EJB3 components deployed in other servers? I am migrating some DTM recovery tests to EJB3. These are the relevant DD elements: StatelessFooCallerBean org.jboss.test.recover.interfaces.StatelessFooCaller org.jboss.test.recover.bean.StatelessFooCallerBean Stateless Container ejb/Foo1 Session org.jboss.test.recover.interfaces.StatelessFoo foo1 ejb/Foo2 Session org.jboss.test.recover.interfaces.StatelessFoo foo2 ... StatelessFooCallerBean StatelessFooCaller ejb/Foo1 jnp://@HOST2@:1099/StatelessFoo ejb/Foo2 jnp://@HOST3@:1099/StatelessFoo I get an incomplete deployment for the referencing EJB3 because JBoss expects Foo1 and Foo2 to be deployed in the same server as the referencing EJB3. It sets up a dependency from the referencing EJB3 to Foo1/Foo2: --- MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:service=EJB3,name=StatelessFooCallerBean State: NOTYETINSTALLED I Depend On: jboss.j2ee:service=EJB3,name=ejb/Foo1 jboss.j2ee:service=EJB3,name=ejb/Foo2 --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.j2ee:service=EJB3,name=ejb/Foo1 State: NOTYETINSTALLED Depends On Me: jboss.j2ee:service=EJB3,name=StatelessFooCallerBean Regards, Francisco --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development -- Bill Burke Chief Architect JBoss Inc. --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0-jdk-matrix build.360 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050901161327Lbuild.360 BUILD COMPLETE - build.360Date of build: 09/01/2005 16:13:27Time to build: 17 minutes 30 seconds Unit Tests: (0) Total Errors and Failures: (0) Modifications since last builds: (first 50 of 0)
[JBoss-dev] jboss-head-jdk-matrix Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050901130131 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-common.xml:158: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-common.xml:43: Exit code: 1 See compile.log in Build Artifacts for details.Date of build: 09/01/2005 13:01:31Time to build: 7 minutes 5 secondsLast changed: 09/01/2005 12:40:34Last log entry: Add more tracing Unit Tests: (0) Total Errors and Failures: (0) Modifications since last builds: (first 50 of 13)1.6modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/OperationMetaData.javaAdd more tracing1.20modifiedtdieslerwebservice/src/main/org/jboss/ws/server/WebServiceDeployerJSE.javaUse annotation class loader for building meta data1.22modifiedkkhanaop/docs/reference/reference/en/modules/running.xml*** empty log message ***1.29modifiedkkhanaop/src/main/org/jboss/aop/AOPClassPool.javaChanges to work with javassist RC1 proper1.22modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/AbstractMetaDataBuilder.javaDerrive TypeMappingMetaData from xsModel contained simpleTypes1.13modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/TypesMetaData.javaDerrive TypeMappingMetaData from xsModel contained simpleTypes1.3modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/TypeMappingMetaData.javaprotect agains invali qname-scope1.4modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/wsdl/WSDLDefinitionsFactory.javachange log level1.8modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/AttributeBinding.javaadded QName to element and attribute bindings1.9modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/ElementBinding.javaadded QName to element and attribute bindings1.10modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/SchemaBinding.javaadded QName to element and attribute bindings1.15modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/TypeBinding.javaadded QName to element and attribute bindings1.25modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.javaadded QName to element and attribute bindings
[JBoss-dev] jboss-head-jdk-matrix Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050901134842 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-common.xml:158: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-common.xml:43: Exit code: 1 See compile.log in Build Artifacts for details.Date of build: 09/01/2005 13:48:42Time to build: 7 minutes 41 secondsLast changed: 09/01/2005 13:27:48Last log entry: Fix wrappedParameters with primitives Unit Tests: (0) Total Errors and Failures: (0) Modifications since last builds: (first 50 of 17)1.23modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/AbstractMetaDataBuilder.javaFix wrappedParameters with primitives1.14modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/TypesMetaData.javaFix wrappedParameters with primitives1.21modifiedtdieslerwebservice/src/main/org/jboss/ws/server/WebServiceDeployerJSE.javaFix wrappedParameters with primitives1.4modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/TypeMappingMetaData.javaAdd qname-scope element1.6modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/OperationMetaData.javaAdd more tracing1.20modifiedtdieslerwebservice/src/main/org/jboss/ws/server/WebServiceDeployerJSE.javaUse annotation class loader for building meta data1.22modifiedkkhanaop/docs/reference/reference/en/modules/running.xml*** empty log message ***1.29modifiedkkhanaop/src/main/org/jboss/aop/AOPClassPool.javaChanges to work with javassist RC1 proper1.22modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/AbstractMetaDataBuilder.javaDerrive TypeMappingMetaData from xsModel contained simpleTypes1.13modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/TypesMetaData.javaDerrive TypeMappingMetaData from xsModel contained simpleTypes1.3modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/TypeMappingMetaData.javaprotect agains invali qname-scope1.4modifiedtdieslerwebservice/src/main/org/jboss/ws/metadata/wsdl/WSDLDefinitionsFactory.javachange log level1.8modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/AttributeBinding.javaadded QName to element and attribute bindings1.9modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/ElementBinding.javaadded QName to element and attribute bindings1.10modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/SchemaBinding.javaadded QName to element and attribute bindings1.15modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/TypeBinding.javaadded QName to element and attribute bindings1.25modifiedaloubyanskycommon/src/main/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.javaadded QName to element and attribute bindings
[JBoss-dev] jboss-4.0-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050901131340 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-common.xml:208: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-common.xml:84: Exit code: 1 See compile-build.log in Build Artifacts for details.Date of build: 09/01/2005 13:13:40Time to build: 9 minutes 0 secondsLast changed: 09/01/2005 10:14:32Last log entry: merge server controller tasks in to 4.0 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last builds: (first 50 of 7536)1.28.2.4modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/ServiceObjectFactory.javaSync webservices with HEAD.Fix samples build.1.1.2.8modifiedjgreenewebservice/src/main/org/jboss/webservice/client/Stub.javaPackage prefix SSL transport properties1.2.2.3modifiedtdieslerwebservice/src/resources/jboss-ws4ee.sar/META-INF/axis-server-config.xmlRemove Axis version service1.1.2.7modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/Stub.javaBackward compatibility for client timeout1.1.2.6modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/Stub.javajavadoc1.1.2.5modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/Stub.javaAdd support for transport properties1.4.2.11modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/PortProxy.javaAdd support for transport properties1.10.2.9modifiedtdieslerwebservice/src/main/org/jboss/webservice/ServiceDeployerEJB.javaFix: JBWS-3091.4.2.10modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/PortProxy.javaFix CTS failures that use doc/lit unwrapping.1.20.2.11modifiedtdieslerwebservice/src/main/org/jboss/webservice/server/InvokerProvider.javaFix CTS failures that use doc/lit unwrapping.1.6.2.9modifiedtdieslerwebservice/src/main/org/jboss/webservice/encoding/ser/MetaDataTypeDesc.javaSupport unwrapping of document style parameters on the server side.1.20.2.10modifiedtdieslerwebservice/src/main/org/jboss/webservice/server/InvokerProvider.javaSupport unwrapping of document style parameters on the server side.1.4.4.3modifiedtdieslerwebservice/src/main/org/jboss/webservice/server/ServiceEndpointInterceptor.javaSupport unwrapping of document style parameters on the server side.1.9.2.6modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/CallImpl.javaSupport unwrapping of document style parameters on the server side.1.4.2.9modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/PortProxy.javaSupport unwrapping of document style parameters on the server side.1.1.2.9modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/BeanXMLMetaData.javaSupport unwrapping of document style parameters on the server side.1.40.2.24modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/ServiceDescription.javaSupport unwrapping of document style parameters on the server side.1.8.2.14modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/TypeMappingDescription.javaSupport unwrapping of document style parameters on the server side.1.22.2.10modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/WSDDGenerator.javaSupport unwrapping of document style parameters on the server side.1.4.2.4modifiedtdieslerwebservice/src/main/org/jboss/webservice/server/JBossRPCInvocation.javaSupport doc style parameter wrapping, first cut.1.1.2.8modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/BeanXMLMetaData.javaUse DOMUtils from jboss.util1.40.2.23modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/ServiceDescription.javaUse DOMUtils from jboss.util1.8.2.13modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/TypeMappingDescription.javaUse DOMUtils from jboss.util1.1.4.2deletedtdieslerwebservice/src/main/org/jboss/webservice/util/DOMUtils.javaUse DOMUtils from jboss.util1.8.2.6modifiedtdieslerwebservice/src/main/org/jboss/webservice/server/ServiceEndpointServlet.javaUse the same ServiceEndpointID param name as in jbossws1.7.4.3modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/ServiceFactoryImpl.javaSupport multiple wsdl service elements as long as they have a single port1.40.2.22modifiedbillwebservice/src/main/org/jboss/webservice/deployment/ServiceDescription.javamove org.jboss.xml to org.jboss.xb1.22.2.9modifiedbillwebservice/src/main/org/jboss/webservice/deployment/WSDDGenerator.javamove org.jboss.xml to org.jboss.xb1.17.2.3modifiedbillwebservice/src/main/org/jboss/webservice/metadata/WebservicesFactory.javamove org.jboss.xml to org.jboss.xb1.7.4.2modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/ServiceFactoryImpl.javasync ws4ee metadata with head1.28.2.3modifiedtdieslerwebservice/src/main/org/jboss/webservice/client/ServiceObjectFactory.javasync ws4ee metadata wi
[JBoss-dev] jboss-4.0-jdk-matrix Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050901124601 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-common.xml:158: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-common.xml:43: Exit code: 1 See compile.log in Build Artifacts for details.Date of build: 09/01/2005 12:46:01Time to build: 8 minutes 35 seconds Unit Tests: (0) Total Errors and Failures: (0) Modifications since last builds: (first 50 of 0)
