View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050315060110Lbuild.436

BUILD COMPLETE -  build.436
Date of build: 03/15/2005 06:01:10
Time to build: 28 minutes 48 seconds
Last changed: 03/15/2005 01:53:05
Last log entry: Fix attachments on the return path (JBWS-146)

 Unit Tests: (0)  Total Errors and Failures: (0)
 

 Modifications since last build:  (38)
1.1.2.8modifiednihilitytestsuite/src/main/org/jboss/test/webservice/attachment/AttachmentProxyTestCase.javaFix attachments on the return path (JBWS-146)
1.1.2.2modifiednihilityjaxrpc/src/main/org/jboss/axis/encoding/DefaultTypeMappingImpl.javaFix attachments on the return path (JBWS-146)
1.1.2.2modifiednihilityjaxrpc/src/main/org/jboss/axis/wsdl/toJava/Utils.javaFix attachments on the return path (JBWS-146)
1.3.6.1deletedstarksmvaria/src/main/org/jboss/tools/Boot.javano message
1.2.6.1modifiedejorttestsuite/src/main/org/jboss/test/jbossmq/test/UIL2ConnectionUnitTestCase.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.
1.4.6.2modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/msgs/ReceiveRequestMsg.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.
1.4.6.1modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/ServerSocketManagerHandler.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.
1.3.6.2modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILClientIL.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.
1.3.6.1modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILClientILService.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.
1.3.6.1modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILServerILFactory.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.
1.5.6.3modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILServerILService.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.
1.3.6.1modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILClientIL.javaAdd the missing serialVersionUID
1.1.2.3modifiedejortconnector/src/resources/dtd/jboss-ds_1_5.dtd[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it with<share-prepared-statements>true</share-prepared-statements>in your -ds.xml
1.10.4.1modifiedejortconnector/src/resources/xa-rar/META-INF/ra.xml[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it with<share-prepared-statements>true</share-prepared-statements>in your -ds.xml
1.12.4.1modifiedejortconnector/src/resources/local-rar/META-INF/ra.xml[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it with<share-prepared-statements>true</share-prepared-statements>in your -ds.xml
1.22.2.4modifiedejortconnector/src/resources/stylesheets/ConnectionFactoryTemplate.xsl[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it with<share-prepared-statements>true</share-prepared-statements>in your -ds.xml
1.6.4.3modifiedejortconnector/src/main/org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnection.java[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it with<share-prepared-statements>true</share-prepared-statements>in your -ds.xml
1.16.2.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnectionFactory.java[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it with<share-prepared-statements>true</share-prepared-statements>in your -ds.xml
1.2.4.3modifiedejortconnector/src/main/org/jboss/resource/adapter/jdbc/CachedPreparedStatement.java[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it with<share-prepared-statements>true</share-prepared-statements>in your -ds.xml
1.4.6.1modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/msgs/ReceiveRequestMsg.java[JBAS-1578] - Trim the ReceiveRequestMsg when sending the reply.
1.24.2.5modifiedejorttestsuite/.classpathFix the eclipe build
1.15.6.3modifiedejortconsole/.classpathFix the eclipse build
1.17.2.5modifiedejortvaria/.classpathFix the eclipse build
1.7.6.2modifiedejortjms/.classpathFix the eclipse build
1.12.2.5modifiedejortremoting/.classpathFix the eclipse build
1.12.4.3modifiedejortcache/.classpathFix the eclipse build
1.7.6.1modifiedanddsystem/src/main/org/jboss/system/ServiceMBean.javaJBAS-1577: white-space in ServiceMBean EVENT types, removed
1.117.2.7modifiedstarksmserver/src/etc/conf/default/jboss-service.xmlShow the ScanEnabled attribute in the URLDeploymentScanner explicitly with its default value of true.
1.29.2.1modifiedejortmessaging/src/main/org/jboss/mq/pm/jdbc2/PersistenceManager.java[JBAS-1583] - JMS_TRANSACTIONS - primary key violationThe calculation of the max txid should be done before the incomplete transactions are rolled back.
1.5.4.2modifiedanddsystem/src/main/org/jboss/system/ListenerServiceMBeanSupport.javaNew Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.
1.1.2.1modifiedanddsystem/src/main/org/jboss/system/NotificationFilterFactory.javaNew Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.
1.3.4.1modifiedanddsystem/src/main/org/jboss/system/ListenerServiceMBean.javaNew Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.
1.2.4.2modifiedanddsystem/src/resources/dtd/jboss-subscription.dtdNew Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.
1.2.6.1modifiedejortmessaging/src/etc/server/examples/deploy/null-persistence-service.xml[JBAS-1582] - NPM - example delegate persistence manager is wrong, attribute name should be DelegatePM
1.6.2.1modifiedejortmessaging/src/main/org/jboss/mq/sm/jdbc/JDBCStateManager.java[JBAS-1581] - JDBC StateManager - CREATE_TABLES_ON_STARTUP is wrongThe config now accepts both CREATE_TABLES_ON_STARTUP andCREATE_TABLES_ON_START_UP (for backwards compatibility)
1.1.4.2modifiedosdchicagovaria/src/main/org/jboss/jaxr/juddi/JUDDIService.javaChange the log level to "debug" from "warn" for the DB initialization process.
1.117.2.6modifiedstarksmserver/src/etc/conf/default/jboss-service.xmlShow the ScanEnabled attribute in the URLDeploymentScanner explicitly with its default value of true.
1.1.2.7modifiedstarksmbuild/docs/readme.htmlInclude the release notes summary in the the readme.

Reply via email to