View results here -> http://tck2.jboss.com/cc/buildresults/jboss-head?log=log20040506141114Lbuild.125

BUILD COMPLETE -  build.125
Date of build: 05/06/2004 14:11:14
Time to build: 13 minutes 6 seconds
Last changed: 05/06/2004 13:56:25
Last log entry: This is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.

 Unit Tests: (0)
No Tests Run
This project doesn't have any tests
 

 Modifications since last build:  (106)
1.2deletedejortjmx/src/main/org/jboss/mx/util/BinaryComparisonQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/OrQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/SingleValueExpSupport.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/AndQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/AnySubStringQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/BetweenQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/BinaryOpValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/BooleanValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/ClassAttributeValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/FinalSubStringQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/InQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/InitialSubStringQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/MatchQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/NotQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/NumberValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/QualifiedAttributeValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2modifiedejortjmx/src/main/org/jboss/mx/util/QueryExpSupport.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.2deletedejortjmx/src/main/org/jboss/mx/util/ValueExpSupport.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.4modifiedejortjmx/src/main/javax/management/ClassAttributeValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.1addedejortjmx/src/main/javax/management/NumericValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.5modifiedejortjmx/src/main/javax/management/Query.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.8modifiedejortjmx/src/main/javax/management/AndQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.8modifiedejortjmx/src/main/javax/management/AttributeValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.1addedejortjmx/src/main/javax/management/BinaryRelQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.3modifiedejortjmx/src/main/javax/management/BooleanValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.8modifiedejortjmx/src/main/javax/management/InQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.8modifiedejortjmx/src/main/javax/management/NotQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.8modifiedejortjmx/src/main/javax/management/OrQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.8modifiedejortjmx/src/main/javax/management/StringValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.8modifiedejortjmx/src/main/javax/management/BetweenQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.9modifiedejortjmx/src/main/javax/management/BinaryOpValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.9modifiedejortjmx/src/main/javax/management/MatchQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.4modifiedejortjmx/src/main/javax/management/QualifiedAttributeValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eehandler/Handler.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eehandler/HandlerBean.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eehandler/HandlerTestCase.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eehandler/TestHandler.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eesimple/Hello.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eesimple/HelloBean.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eesimple/HelloClientBean.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eesimple/HelloHome.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eesimple/HelloJavaBean.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eesimple/HelloWs.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eesimple/HelloWsClientApp.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eesimple/HelloWsClientServlet.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eesimple/SimpleClientTestCase.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eesimple/SimpleEJBTestCase.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eesimple/SimpleJSETestCase.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eecomplex/Complex1Bean.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eecomplex/Complex1Home.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eecomplex/Complex1Ws.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eecomplex/Complex1WsClientServlet.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eecomplex/ComplexEJBTestCase.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eecomplex/ComplexJSETestCase.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eecomplex/ComplexSer1.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eecomplex/ComplexSer2.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/main/org/jboss/test/ws4ee/ws4eecomplex/Complex1.javaadd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eesimple/WEB-INF/web-secure.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eesimple/WEB-INF/web.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eesimple/WEB-INF/webservices.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eesimple-client/META-INF/HelloClient.wsdladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eesimple-client/META-INF/HelloMapping.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eesimple-client/META-INF/application-client.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eesimple-client/META-INF/application.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eesimple-client/META-INF/ejb-jar.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eesimple-client/META-INF/jboss-client.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eesimple-client/WEB-INF/web.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eesimple/META-INF/Hello.wsdladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eesimple/META-INF/HelloMapping.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eesimple/META-INF/ejb-jar.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eesimple/META-INF/webservices.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eecomplex/WEB-INF/web.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eehandler/META-INF/Handler.wsdladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eehandler/META-INF/HandlerMapping.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eehandler/META-INF/ejb-jar.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eehandler/META-INF/webservices.xmladd ws4ee tests
1.363modifiedtdieslertestsuite/build.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eecomplex/META-INF/Complex1.wsdladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eecomplex/META-INF/Complex1Mapping.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eecomplex/META-INF/ejb-jar.xmladd ws4ee tests
1.1addedtdieslertestsuite/src/resources/ws4ee/ws4eecomplex/META-INF/webservices.xmladd ws4ee tests
1.1addedtdieslerwebservice/src/resources/schema/j2ee_jaxrpc_mapping_1_1.xsd+ add support handlers in port-component+ verify corresponding SEI+ add schema files
1.1addedtdieslerwebservice/src/resources/schema/j2ee_web_services_1_1.xsd+ add support handlers in port-component+ verify corresponding SEI+ add schema files
1.1addedtdieslerwebservice/src/resources/schema/j2ee_web_services_client_1_1.xsd+ add support handlers in port-component+ verify corresponding SEI+ add schema files
1.2modifiedtdieslerwebservice/src/main/org/jboss/webservice/server/InvokerProviderEJB.java+ add support handlers in port-component+ verify corresponding SEI+ add schema files
1.1addedtdieslerwebservice/src/resources/schema/j2ee_1_4.xsd+ add support handlers in port-component+ verify corresponding SEI+ add schema files
1.1addedtdieslerwebservice/src/main/org/jboss/webservice/metadata/PortComponentHandlerMetaData.java+ add support handlers in port-component+ verify corresponding SEI+ add schema files
1.2modifiedtdieslerwebservice/src/main/org/jboss/webservice/metadata/PortComponentMetaData.java+ add support handlers in port-component+ verify corresponding SEI+ add schema files
1.3modifiedtdieslerwebservice/src/main/org/jboss/webservice/metadata/WebserviceDescriptionMetaData.java+ add support handlers in port-component+ verify corresponding SEI+ add schema files
1.7modifiedtdieslerwebservice/src/main/org/jboss/webservice/metadata/WebservicesFactory.java+ add support handlers in port-component+ verify corresponding SEI+ add schema files
1.2modifiedtdieslerwebservice/src/main/org/jboss/webservice/metadata/WebservicesMetaData.java+ add support handlers in port-component+ verify corresponding SEI+ add schema files
1.3modifiedtdieslerwebservice/samples/server-web/resources/WEB-INF/web.xml+ add support handlers in port-component+ verify corresponding SEI+ add schema files
1.4modifiedtdieslerwebservice/samples/client-appl/resources/META-INF/application-client.xml+ add support handlers in port-component+ verify corresponding SEI+ add schema files
1.322modifiedtdieslerbuild/build.xmlreactivate jboss-net.sar
1.24modifiedtdieslerserver/src/etc/conf/default/log4j.xmladd org.jboss.webservice
1.2deletedtdieslerserver/src/resources/schema/j2ee_jaxrpc_mapping_1_1.xsdsupport handler in service-ref
1.2deletedtdieslerserver/src/resources/schema/j2ee_web_services_1_1.xsdsupport handler in service-ref
1.2deletedtdieslerserver/src/resources/schema/j2ee_web_services_client_1_1.xsdsupport handler in service-ref
1.25modifiedtdieslerserver/src/main/org/jboss/metadata/WebMetaData.javasupport handler in service-ref
1.64modifiedtdieslerserver/src/main/org/jboss/metadata/BeanMetaData.javasupport handler in service-ref
1.9modifiedtdieslerserver/src/main/org/jboss/metadata/ClientMetaData.javasupport handler in service-ref
1.2deletedtdieslerserver/src/main/org/jboss/metadata/HandlerMetaData.javasupport handler in service-ref
1.1addedtdieslerserver/src/main/org/jboss/metadata/InitParamMetaData.javasupport handler in service-ref
1.1addedtdieslerserver/src/main/org/jboss/metadata/PortComponentRefMetaData.javasupport handler in service-ref
1.1addedtdieslerserver/src/main/org/jboss/metadata/ServiceRefHandlerMetaData.javasupport handler in service-ref
1.7modifiedtdieslerserver/src/main/org/jboss/metadata/ServiceRefMetaData.javasupport handler in service-ref

Reply via email to