[JBoss-dev] jboss-4.0 build.454 Build Fixed

Tue, 29 Mar 2005 06:41:40 -0800

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

BUILD COMPLETE -  build.454
Date of build: 03/29/2005 08:21:11
Time to build: 47 minutes 38 seconds
Last changed: 03/29/2005 07:14:20
Last log entry: Add the personsAge field

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

 Modifications since last build:  (58)
1.1.32.1modifiedstarksmtestsuite/src/main/org/jboss/test/cts/interfaces/CtsCmp.javaAdd the personsAge field
1.3.2.11modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaAnother fix for JBAS-1622
1.15.4.3modifiedstarksmtestsuite/src/resources/cts/META-INF/ejb-jar.xmlAdd the personsAge field
1.7.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/cts/ejb/CtsCmpBean.javaAdd the personsAge field
1.12.6.1modifiedanddsystem/src/main/org/jboss/system/server/ServerInfo.javaJBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really.
1.5.2.6modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaFixed sm getString message
1.3.2.10modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaJBAS-1622 findSessions api wasn't correct
1.3.2.8modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaJBAS-1622 findSessions api wasn't correct
1.406.2.48modifiedovidiuftestsuite/build.xmltests-clustering-all-stacks generates different test report sets for each stack configuration
1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-coyote.jar- Update to Tomcat 5.5.9.
1.5.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-http.jar- Update to Tomcat 5.5.9.
1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-util.jar- Update to Tomcat 5.5.9.
1.1.2.5modifiedremmthirdparty/apache-tomcat55/naming-resources.jar- Update to Tomcat 5.5.9.
1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-cgi.renametojar- Update to Tomcat 5.5.9.
1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-default.jar- Update to Tomcat 5.5.9.
1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-invoker.jar- Update to Tomcat 5.5.9.
1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-ssi.renametojar- Update to Tomcat 5.5.9.
1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-webdav.jar- Update to Tomcat 5.5.9.
1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-ajp.jar- Update to Tomcat 5.5.9.
1.1.2.5modifiedremmthirdparty/apache-tomcat55/jasper-runtime.jar- Update to Tomcat 5.5.9.
1.1.2.5modifiedremmthirdparty/apache-tomcat55/jasper-compiler.jar- Update to Tomcat 5.5.9.
1.1.2.4modifiedremmthirdparty/apache-tomcat55/jasper-compiler-jdt.jar- Update to Tomcat 5.5.9.
1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina-manager.jar- Update to Tomcat 5.5.9.
1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina-optional.jar- Update to Tomcat 5.5.9.
1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina.jar- Update to Tomcat 5.5.9.
1.2.2.5modifiedremmthirdparty/apache-tomcat55/README- Update to Tomcat 5.5.9.
1.2.8.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsMessageConsumer.java[JBAS-1604] - Make a start on the JMSRA trace logging
1.10.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSession.java[JBAS-1604] - Make a start on the JMSRA trace logging
1.11.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.java[JBAS-1604] - Make a start on the JMSRA trace logging
1.8.2.1modifiedstarksmserver/src/main/org/jboss/tm/usertx/client/ClientUserTransaction.javaUse the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.
1.8.6.1modifiedejortconnector/src/main/org/jboss/resource/deployment/RARDeployment.java[JBAS-1446] - Add trace logging for rar deployment operations
1.3.4.2modifiedejortconnector/src/main/org/jboss/resource/deployment/ActivationSpecFactory.java[JBAS-1446] - Add trace logging to activation spec construction
1.1.2.3modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObject.java[JBAS-1446] - Add TRACE logging to AdminObject construction.
1.1.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObjectFactory.java[JBAS-1446] - Add TRACE logging to AdminObject construction.
1.1.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/dlq/GenericDLQHandler.javaSource code tidyup
1.1.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/DLQHandler.javaSource code tidyup
1.2.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/JmsServerSession.javaSource code tidyup
1.1.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/dlq/AbstractDLQHandler.javaSource code tidyup
1.1.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObject.javaSource code tidyup
1.2.6.1modifiedejortconnector/src/main/org/jboss/resource/deployment/DummyResourceAdapter.javaSource code tidyup
1.11.2.1modifiedejortconnector/src/main/org/jboss/resource/deployment/RARDeployer.javaSource code tidyup
1.3.4.1modifiedejortconnector/src/main/org/jboss/resource/deployment/ResourceAdapterFactory.javaSource code tidyup
1.3.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/ResourceAdapterObjectModelFactory.javaSource code tidyup
1.5.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsLocalTransaction.javaSource code tidyup
1.5.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsResourceAdapter.javaSource code tidyup
1.11.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.javaSource code tidyup
1.9.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsConnectionFactoryImpl.javaSource code tidyup
1.7.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsConnectionRequestInfo.javaSource code tidyup
1.10.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSession.javaSource code tidyup
1.11.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsManagedConnectionFactory.javaSource code tidyup
1.6.6.3modifiedstarksmremoting/src/main/org/jboss/remoting/transport/socket/SocketServerInvoker.javaUpdate the accept catch to handle Throwables. Part of (JBAS-1559) Check all serverSocket accept threads.
1.4.6.1modifiedstarksmserver/src/main/org/jboss/logging/Log4jSocketServer.javaUpdate the accept catch to handle Throwables. Part of (JBAS-1559) Check all serverSocket accept threads.
1.10.2.3modifiedstarksmserver/src/main/org/jboss/invocation/pooled/server/PooledInvoker.javaUpdate the accept catch to handle Throwables. Part of (JBAS-1559) Check all serverSocket accept threads.
1.3.2.3modifiedstarksmtestsuite/src/main/org/jboss/test/web/test/FormAuthUnitTestCase.javaAccess the resource without attempting a login to validate that the session is valid and that any caching on the server is working as expected.
1.406.2.47modifiedstarksmtestsuite/build.xmlInclude all deploy/jms content recursively in the jacc test configuration
1.1.4.3modifiedstarksmtomcat/src/main/org/jboss/web/tomcat/security/JaccAuthorizationRealm.java- If there is no JACC Subject context handler data when the resource permission check is made, check to see if the request principal is a JBossGenericPrincipal that encapsulates the authenticated user. This is needed for FORM-AUTH which caches the authenticated user as part of the session context and does not reauthenticate to the Realm. Resolves (JBAS-1592) JaccAuthorizationRealm always returns false on subsequent requests.- Fix a problem with the migration to tomcat 5.5.x that broke the isUserInRole call for the JACC Realm.
1.10.2.8modifiedstarksmtomcat/src/main/org/jboss/web/tomcat/security/JBossSecurityMgrRealm.javaChange the roleMap to a mapping from the caller principal to the GenericPrincipal rather than just the caller's roles.
1.3.4.3modifiedstarksmtomcat/src/main/org/jboss/web/tomcat/security/JBossGenericPrincipal.javaKeep the original Set<Princpal> of the user roles in addition to the role names.

Reply via email to