[JBoss-dev] jboss-cache build.204 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache?log=log20060222064405Lbuild.204 BUILD COMPLETE-build.204Date of build:02/22/2006 06:44:05Time to build:19 secondsLast changed:02/22/2006 01:10:10Last log entry:[JBCACHE-448] Add ability to get previous cache version for interop testing from repository Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(first 50 of 79)1.125modifiedbstansberrysrc/org/jboss/cache/TreeCache.java[JBCACHE-456] Disable setting FetchStateAtStartup; include cache loader fetchpersistent state in determining whether to do an initial state transfer1.25modifiedbstansberrysrc/org/jboss/cache/TreeCacheMBean.java[JBCACHE-456] Disable setting FetchStateAtStartup; include cache loader fetchpersistent state in determining whether to do an initial state transfer1.2deletedbstansberrytests/functional/org/jboss/cache/statetransfer/ConcurrentStateTransfer1241Test.javaRemove class that never should have been checked in1.5modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/ForcedStateTransferTest.javaProperly configure whether cache loader is async by using the element rather than the property.1.13modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/StateTransferTestBase.javaProperly configure whether cache loader is async by using the element rather than the property.1.3modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/VersionedTestBase.javaProperly configure whether cache loader is async by using the element rather than the property.1.28modifiedbstansberrysrc/org/jboss/cache/Node.java[JBCACHE-424] Node implements Externalizable1.3modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/StateTransfer123Test.javaInherit from VersionedTestBase1.8modifiedbstansberryetc/META-INF/replAsyncSharedCacheLoader-service.xml[JBCACHE-429] Make state transfer timeout greater than lock acquisition timeout.1.6modifiedbstansberryetc/META-INF/replSync-ChainingCacheLoader-service.xml[JBCACHE-429] Make state transfer timeout greater than lock acquisition timeout.1.5modifiedbstansberryetc/META-INF/replSync-ClusteredCacheLoader-service.xml[JBCACHE-429] Make state transfer timeout greater than lock acquisition timeout.1.4modifiedbstansberryetc/META-INF/replSync-eviction-service.xml[JBCACHE-429] Make state transfer timeout greater than lock acquisition timeout.1.7modifiedbstansberryetc/META-INF/replSync-optimistic-service.xml[JBCACHE-429] Make state transfer timeout greater than lock acquisition timeout.1.7modifiedbstansberryetc/META-INF/replSync-service.xml[JBCACHE-429] Make state transfer timeout greater than lock acquisition timeout.1.124modifiedbstansberrysrc/org/jboss/cache/TreeCache.java[JBCACHE-429] Make state transfer timeout greater than lock acquisition timeout.1.2modifiedbstansberrytests/functional/org/jboss/cache/aop/statetransfer/StateTransfer123AopTest.java[JBCACHE-425] Create state transfer versions for 1.2.31.2modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/StateTransfer123Test.java[JBCACHE-425] Create state transfer versions for 1.2.31.4modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/ForcedStateTransferTest.java[JBCACHE-438] Replace cache attribute StateTransferVersion with ReplicationVersion1.4modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/StateTransfer1241Test.java[JBCACHE-438] Replace cache attribute StateTransferVersion with ReplicationVersion1.4modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/StateTransfer124Test.java[JBCACHE-438] Replace cache attribute StateTransferVersion with ReplicationVersion1.4modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/StateTransfer130Test.java[JBCACHE-438] Replace cache attribute StateTransferVersion with ReplicationVersion1.12modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/StateTransferTestBase.java[JBCACHE-438] Replace cache attribute StateTransferVersion with ReplicationVersion1.2modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/VersionedTestBase.java[JBCACHE-438] Replace cache attribute StateTransferVersion with ReplicationVersion1.3modifiedbstansberrytests/functional/org/jboss/cache/aop/statetransfer/StateTransfer1241AopTest.java[JBCACHE-438] Replace cache attribute StateTransferVersion with ReplicationVersion1.3modifiedbstansberrytests/functional/org/jboss/cache/aop/statetransfer/StateTransfer124AopTest.java[JBCACHE-438] Replace cache attribute StateTransferVersion with ReplicationVersion1.3modifiedbstansberrytests/functional/org/jboss/cache/aop/statetransfer/StateTransfer130AopTest.java[JBCACHE-438] Replace cache attribute StateTransferVersion with ReplicationVersion1.7modifiedbstansberrytests/functional/org/jboss/cache/aop/statetransfer/StateTransferAopTestBase.java[JBCACHE-438] Replace cache attribute
RE: [JBoss-dev] Xalan removal saga
Setting this via a system property cannot be done as this is a global override. We could simply externalize the default factory name to an attribute of the jboss server info mbean and fallback to the jdk default if it cannot be found. I don't know if an extension class can get access to a class from the jdk rt.jar via the ClassLoader.getSystemClassLoader(). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: Wednesday, February 22, 2006 4:02 AM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] Xalan removal saga It all boils down to here: ... return (TransformerFactory) FactoryFinder.find( /* The default property name according to the JAXP spec */ javax.xml.transform.TransformerFactory, /* The fallback implementation class name */ org.apache.xalan.processor.TransformerFactoryImpl); ... I don't see how we can patch the TF to return a proper fallback implementation name, because we just don't know what that is. On Sun jdk1.4 it would be org.apache.xalan.processor.TransformerFactoryImpl On Sun jdk5 it would be com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl But on other vendor jdks, whats the correct value? And if it is just a question of setting a sensible default value, we could do just the same setting the javax.xml.transform.TransformerFactory property. But isn't this exactly the role of the TransformerFactory offered by the jdk vendor? I think the best compromise is to just remove javax.xml.transform.TransformerFactory from xml-apis.jar (replace with xml-apis-notf.jar ?) to let the vendor supplied default apply. I've attached the TransformerFactory code that comes with xml-apis.jar --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060222103217 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:26: Build Successful - Tests completed with errors or failures.Date of build:02/22/2006 10:32:17Time to build:49 minutes 49 secondsLast changed:02/21/2006 11:18:34Last log entry:Adding 3.2.8 on the matrix testsuite list Unit Tests: (1848) Total Errors and Failures: (5)testFederatedorg.jboss.test.jbossnet.external.ExternalUnitTestCasetestClientLoginorg.jboss.test.security.test.LoginModulesUnitTestCasetestJCACallerIdentityorg.jboss.test.security.test.LoginModulesUnitTestCasetestClientLoginorg.jboss.test.security.test.XMLLoginModulesUnitTestCasetestJCACallerIdentityorg.jboss.test.security.test.XMLLoginModulesUnitTestCase Modifications since last build:(first 50 of 18)1.165.2.202modifiedcsuconictestsuite/build.xmlAdding 3.2.8 on the matrix testsuite list1.8.2.9modifieddimitrismanagement/src/main/org/jboss/management/j2ee/MBean.javaJBAS-2082, avoid creating a dynamic proxy for a single attribute read, reduce the trace verboseness of the caught exception when cannot find an MBean's "State" attribute1.12.2.14modifieddimitrisnaming/src/main/org/jnp/server/Main.javaJBAS-1806, call custom RMIClientSocketFactory.setBindAddress() if method is provided (+ tidy up the MBean interface, and synch across branches)1.6.2.4modifieddimitrisnaming/src/main/org/jnp/server/MainMBean.javaJBAS-1806, call custom RMIClientSocketFactory.setBindAddress() if method is provided (+ tidy up the MBean interface, and synch across branches)1.2.2.7modifieddimitrisvaria/src/main/org/jboss/varia/scheduler/ScheduleManager.javaJBAS-2797, fix wrong way for retrieving Hashtable mSchedules values1.1.2.19modifiedbstansberrytomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.java[JBAS-2792] Avoid NPE; don't assign the result of loadSession to local variable1.2.2.6modifieddimitrisvaria/src/main/org/jboss/varia/scheduler/ScheduleManager.javatidy up the ScheduleManager, synch across branches1.2.4.3modifieddimitrisvaria/src/main/org/jboss/varia/scheduler/ScheduleManagerMBean.javatidy up the ScheduleManager, synch across branches1.2.2.4modifiedcsuconicserver/src/main/org/jboss/jmx/adaptor/rmi/RMIAdaptor.javaJBAS-2803 - Proposed fix1.3.2.6modifiedcsuconicserver/src/main/org/jboss/jmx/adaptor/rmi/RMIAdaptorImpl.javaJBAS-2803 - Proposed fix1.9.2.3modifiedcsuconicserver/src/main/org/jboss/jmx/connector/rmi/RMIConnectorImpl.javaJBAS-2803 - Proposed fix1.12.4.22modifiedstarksmsecurity/src/main/org/jboss/security/plugins/JaasSecurityManagerService.javaJBAS-2201, set the securityMgrClass default value to JaasSecurityManager.class.1.1.4.2modifieddimitrisserver/src/bin/jboss_init_hpux.shJBAS-2574, System Startup Script for JBoss AS on HP-UX1.1.4.1deleteddimitrisserver/src/bin/jboss_init_hpux.shfile jboss_init_hpux.sh was added on branch Branch_3_2 on 2006-02-20 10:39:56 +1.5.2.8modifiedstarksmconnector/src/main/org/jboss/resource/connectionmanager/CachedConnectionInterceptor.javaJBAS-545, provide access to the underlying EntityPersistenceManager.1.6.2.7modifiedstarksmserver/src/etc/conf/default/login-config.xmlJBAS-2820, restore-login-identity=true to the client-login configuration so any existing security context will be restored on logout1.3.4.7modifiedstarksmsecurity/src/main/org/jboss/security/ClientLoginModule.javaJBAS-2820, If restore-login-identity=true push on commit, pop on logout/abort the SecurityAssociation context rather than using the old setters/clear as these don't interact with the SecurityAssociation stack correctly when in the server.1.1.2.3modifiedstarksmsecurity/src/main/org/jboss/security/SecurityAssociationActions.javaJBAS-2820, If restore-login-identity=true push on commit, pop on logout/abort the SecurityAssociation context rather than using the old setters/clear as these don't interact with the SecurityAssociation stack correctly when in the server.
RE: [JBoss-dev] Xalan removal saga
I don't follow why this is necessary. If we just remove javax.xml.transform.TransformerFactory from xml-apis.jar then the jdk bundled TransformerFactory will be used to choose the correct implementation. A user can always drop his own xalan.jar to lib/endorsed (for jdk1.4/5), or server/xxx/lib for jdk5, or use a scoped xalan.jar to override the jdk version, since xalan.jar contains: META-INF/services/javax.xml.transform.TransformerFactory file containing the class name of its implementation. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: 22 February, 2006 18:16 To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] Xalan removal saga Setting this via a system property cannot be done as this is a global override. We could simply externalize the default factory name to an attribute of the jboss server info mbean and fallback to the jdk default if it cannot be found. I don't know if an extension class can get access to a class from the jdk rt.jar via the ClassLoader.getSystemClassLoader(). --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Big backlog of cmp2 issues
One a related note, we are down to 194 issues for 4.0.4.GA, 49 of which are CMP ones. Alexey, can you go through them to see if there is anything important that needs to be solved for 4.0.4.GA (i.e. within the next 2-3 weeks)? Thanks /D -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: 17 February, 2006 23:50 To: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] Big backlog of cmp2 issues So in going through the outstanding jira issues for jbas, there are a lot of old cmp2 issues. We have never really made a decision on whether we are going to try to move the cmp2 model onto an ejb3/hibernate based implementation. That would seem to be the best migration and support strategy. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Xalan removal saga
Its not clear that removal of the javax.xml.transform.* is safe. There are references to org.w3c.dom.* from the javax.xml.transform.dom for example. We cannot simply remove just the javax.xml.transform.TransformerFactory. It would have to be all javax.xml.transform.* classes. The presence of the javax.xml.transform.TransformerFactory should not affect a user being able to override the transformer by dropping in an xsl jar with a META-INF/services/javax.xml.transform.TransformerFactory entry as this takes precedence over the TransformerFactory defaults. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: Wednesday, February 22, 2006 9:24 AM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] Xalan removal saga I don't follow why this is necessary. If we just remove javax.xml.transform.TransformerFactory from xml-apis.jar then the jdk bundled TransformerFactory will be used to choose the correct implementation. A user can always drop his own xalan.jar to lib/endorsed (for jdk1.4/5), or server/xxx/lib for jdk5, or use a scoped xalan.jar to override the jdk version, since xalan.jar contains: META-INF/services/javax.xml.transform.TransformerFactory file containing the class name of its implementation. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: 22 February, 2006 18:16 To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] Xalan removal saga Setting this via a system property cannot be done as this is a global override. We could simply externalize the default factory name to an attribute of the jboss server info mbean and fallback to the jdk default if it cannot be found. I don't know if an extension class can get access to a class from the jdk rt.jar via the ClassLoader.getSystemClassLoader(). --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=kkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBossCache 1.2.4.SP2 released
JBossCache version 1.2.4.SP2 has been released. This can be downloaded from: http://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339 and is also available in the repository. Both the jboss-head and jboss-4.0.x branches have been updated to use this new version. Ruel Loehr JBoss QA
RE: [JBoss-dev] JBossCache 1.2.4.SP2 released
Ruel, have you created a JIRA task for the upgrade? Just so it goes into the release notes. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ruel LoehrSent: 22 February, 2006 19:57To: jboss-development@lists.sourceforge.netSubject: [JBoss-dev] JBossCache 1.2.4.SP2 released JBossCache version 1.2.4.SP2 has been released. This can be downloaded from: http://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339 and is also available in the repository. Both the jboss-head and jboss-4.0.x branches have been updated to use this new version. Ruel Loehr JBoss QA
RE: [JBoss-dev] JBossCache 1.2.4.SP2 released
http://jira.jboss.com/jira/browse/JBAS-2789 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris AndreadisSent: Wednesday, February 22, 2006 10:02 AMTo: jboss-development@lists.sourceforge.netSubject: RE: [JBoss-dev] JBossCache 1.2.4.SP2 released Ruel, have you created a JIRA task for the upgrade? Just so it goes into the release notes. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ruel LoehrSent: 22 February, 2006 19:57To: jboss-development@lists.sourceforge.netSubject: [JBoss-dev] JBossCache 1.2.4.SP2 released JBossCache version 1.2.4.SP2 has been released. This can be downloaded from: http://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339 and is also available in the repository. Both the jboss-head and jboss-4.0.x branches have been updated to use this new version. Ruel Loehr JBoss QA
[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=log20060222152807 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-portal.xml:71: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:93: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:204: 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:02/22/2006 15:28:07Time to build:3 minutes 25 secondsLast changed:02/22/2006 13:36:12Last log entry:fixed some synchronization issues Unit Tests: (84) Total Errors and Failures: (1)testJarorg.jboss.portal.test.common.URLNavigatorTestCase Modifications since last build:(first 50 of 298)1.1addedclaprunwsrp/src/main/org/jboss/portal/test/wsrp/WSRPBaseTest.javaMoved tests.1.1addedclaprunwsrp/src/main/org/jboss/portal/test/wsrp/v1/ServiceDescriptionTestCase.javaMoved tests.1.2deletedclaprunwsrp/src/main/org/jboss/portal/wsrp/test/WSRPBaseTest.javaMoved tests.1.2deletedclaprunwsrp/src/main/org/jboss/portal/wsrp/test/v1/ServiceDescriptionTestCase.javaMoved tests.1.9modifiedasaldhanawsrp/src/main/org/jboss/portal/wsrp/endpoints/ServiceDescriptionEndpoint.javaUpdate to follow doc/lit bare style1.2modifiedasaldhanawsrp/src/main/org/jboss/portal/wsrp/WSRPProducer.javaUpdate to use the doc/lit bare pattern1.1addedasaldhanawsrp/src/resources/jndi.propertiesJNDI properties file that is useful for looking up dynamic proxy1.1addedasaldhanawsrp/src/resources/log4j.xmlA log4j xml file useful for the wsrp module particularly in testing1.3modifiedasaldhanawsrp/src/resources/jboss-wsrp-war/WEB-INF/wsdl/wsrp_services.wsdlTemporarily add namespaces to the wsdl to fix a JBossWS bug that once fixed can force a rollback of this ns addition.1.3modifiedasaldhanawsrp/src/resources/jboss-wsrp-war/WEB-INF/jaxrpc-mappings.xmlUpdate the mapping file to follow doc/litbare style.Refer to JBWS-7171.6modifiedasaldhanawsrp/src/resources/jboss-wsrp-sar/META-INF/jboss-service.xmlLet the wsrp engine not depend on the webservices deployer1.1addedasaldhanawsrp/src/resources/jboss-wsrp-client/META-INF/application-client.xmlJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/resources/jboss-wsrp-client/META-INF/jaxrpc-mappings.xmlJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/resources/jboss-wsrp-client/META-INF/jboss-client.xmlJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/resources/jboss-wsrp-client/META-INF/wsdl/wsrp_services.wsdlJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/resources/jboss-wsrp-client/META-INF/wsdl/wsrp_v1_bindings.wsdlJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/resources/jboss-wsrp-client/META-INF/wsdl/wsrp_v1_interfaces.wsdlJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/resources/jboss-wsrp-client/META-INF/wsdl/wsrp_v1_types.xsdJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/main/org/jboss/portal/wsrp/test/WSRPBaseTest.javaJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/main/org/jboss/portal/wsrp/test/v1/ServiceDescriptionTestCase.javaJBPORTAL-673: Test Case for WSRP Web Service InvocationWSRP test case for ServiceDescriptionService1.8modifiedclaprunwsrp/src/main/org/jboss/portal/wsrp/endpoints/ServiceDescriptionEndpoint.java- Started producer test implementation.1.1addedclaprunwsrp/src/main/org/jboss/portal/test/wsrp/producer/ServiceDescriptionTest.java- Cleaned-up tests.- Started producer test implementation.1.1addedclaprunwsrp/src/main/org/jboss/portal/wsrp/WSRPProducer.java- Cleaned-up tests.- Started producer test implementation.1.2deletedclaprunwsrp/src/main/test/WSRP_V1_MarkupServer.java- Cleaned-up tests.- Started producer test implementation.1.3deletedclaprunwsrp/src/main/test/WSRP_V1_ServiceDescriptionServer.java- Cleaned-up tests.- Started producer test implementation.1.4modifiedclaprunwsrp/src/main/org/jboss/portal/wsrp/WSRPPortletMode.java- Simplified instance variables names.- Updated web.xml to Web Application 2.4.- Minor refactorings.1.8modifiedclaprunwsrp/src/main/org/jboss/portal/wsrp/WSRPRequest.java- Simplified instance variables names.- Updated web.xml to Web Application 2.4.- Minor refactorings.1.6modifiedclaprunwsrp/src/main/org/jboss/portal/wsrp/WSRPResponse.java- Simplified instance variables names.- Updated web.xml to Web Application 2.4.- Minor refactorings.1.4modifiedclaprunwsrp/src/main/org/jboss/portal/wsrp/WSRPWindowState.java- Simplified instance variables names.- Updated web.xml to
RE: [JBoss-dev] Xalan removal saga
Removing javax.xml.transform.TransformerFactory or patching it to try invoke the underlying TransformerFactory (if this is possible) which is essentially the same thing, is undesirable because you'll end up with a transformer API and an underlying implementation that may not match (correct?) Removing javax.xml.transform.* is not clear that is safe (I guess because you might have incompatible parser api+impl - transformer api+impl interactions?) Ok, we are doomed :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: 22 February, 2006 19:50 To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] Xalan removal saga Its not clear that removal of the javax.xml.transform.* is safe. There are references to org.w3c.dom.* from the javax.xml.transform.dom for example. We cannot simply remove just the javax.xml.transform.TransformerFactory. It would have to be all javax.xml.transform.* classes. The presence of the javax.xml.transform.TransformerFactory should not affect a user being able to override the transformer by dropping in an xsl jar with a META-INF/services/javax.xml.transform.TransformerFactory entry as this takes precedence over the TransformerFactory defaults. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: Wednesday, February 22, 2006 9:24 AM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] Xalan removal saga I don't follow why this is necessary. If we just remove javax.xml.transform.TransformerFactory from xml-apis.jar then the jdk bundled TransformerFactory will be used to choose the correct implementation. A user can always drop his own xalan.jar to lib/endorsed (for jdk1.4/5), or server/xxx/lib for jdk5, or use a scoped xalan.jar to override the jdk version, since xalan.jar contains: META-INF/services/javax.xml.transform.TransformerFactory file containing the class name of its implementation. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: 22 February, 2006 18:16 To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] Xalan removal saga Setting this via a system property cannot be done as this is a global override. We could simply externalize the default factory name to an attribute of the jboss server info mbean and fallback to the jdk default if it cannot be found. I don't know if an extension class can get access to a class from the jdk rt.jar via the ClassLoader.getSystemClassLoader(). --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=kkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=kkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
Rajesh, can we put jboss-head at the end? If there is only one failure on jboss-head, perhaps we could raise the issue for the portal team to fix. Having Portal 2.4 compatible with Jboss 5.0 would be a nice thing to have if it's easy. If it's a big deal to fix, we should remove jboss-head from the matrix so we can have a clean build. -Original Message- From: Julien Viet Sent: Wednesday, February 22, 2006 3:38 PM To: Rajesh Rajasekaran Cc: QA; Anil Saldhana; [EMAIL PROTECTED]; Chris Laprun; jboss-development@lists.sourceforge.net; QA; Julien Viet; [EMAIL PROTECTED]; Thomas Heute Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors jboss-head (JBoss 5) is not today a target for us but we can test it of course. Here is the list that I would like to see : - Branch_4_0 - 4.0.4RC1 (later 4.0.4) - 4.0.3SP1 (already done) --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] FW: Could not run jacorb on 64 bit jdk
We were able to run the tests which uses Jacorb on a 64-bit JVM. We compiled the JBoss build using a 32-bit JVM to avoid the Jacorb compilation problem and used a 64-bit JVM to run the testsuite. We were not getting the VerifyError at runtime. This happens only during IDL compilation. The compilation error occurs with SUN jdk1.4 and jrockit-1.4 64-bit JVM's. It does not occur with jrockit-1.5 64 bit JVM. Thanks Rajesh -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Francisco Reverbel Sent: Tuesday, February 14, 2006 1:08 PM To: Ryan Campbell Cc: jboss-development@lists.sourceforge.net; Francisco Reverbel Subject: RE: [JBoss-dev] FW: Could not run jacorb on 64 bit jdk Yes, I see that the VerifyError is thrown when you run the IDL compiler. It looks like a JVM bug. Even though I know JacORB's implementation of the ORB run-time library fairly well, I have never looked at the IDL compiler. Do you know if a VerifyError also happens at run time, with JacORB's ORB on a 64-bit JVM? Or the problem happens only during IDL compilation? On Mon, 2006-02-13 at 17:11 -0600, Ryan Campbell wrote: Francisco, Just to make it clear, we are trying to build JBoss on 64bit JVM's and we get this fatal exception when trying to run the jacorb parser: Exception in thread main java.lang.VerifyError: (class: org/jacorb/idl/parser, method: clinit signature: ()V) Call to wrong initialization method Can you patch this? We aren't getting a response from the jacorb list. __ From:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rajesh Rajasekaran Sent: Monday, February 13, 2006 5:04 PM To: jboss-development@lists.sourceforge.net Cc: Francisco Reverbel Subject: [JBoss-dev] FW: Could not run jacorb on 64 bit jdk __ From: Rajesh Rajasekaran Sent: Friday, February 10, 2006 12:05 PM To: '[EMAIL PROTECTED]' Subject: Could not run jacorb on 64 bit jdk This is related to the bug #468 http://www.jacorb.org/cgi-bin/bugzilla/long_list.cgi?buglist=468 We are trying to support Jboss on 64 bit jdk's and this bug is a major blocker. A fix for this ASAP would help us proceed with our process. Thanks Rajesh JBoss QA --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=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: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
I will put jboss-head to the end and rearrange the list as Julien had requested. The portlet tests against jboss-head had failed and the report XML's were not well-formed, hence the failures not reported by CC. I have opened a task for this. Here s the link. http://jira.jboss.com/jira/browse/JBPORTAL-679 Thanks Rajesh -Original Message- From: Ryan Campbell Sent: Wednesday, February 22, 2006 3:54 PM To: Julien Viet; Rajesh Rajasekaran Cc: QA; jboss-development@lists.sourceforge.net Subject: RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors Rajesh, can we put jboss-head at the end? If there is only one failure on jboss-head, perhaps we could raise the issue for the portal team to fix. Having Portal 2.4 compatible with Jboss 5.0 would be a nice thing to have if it's easy. If it's a big deal to fix, we should remove jboss-head from the matrix so we can have a clean build. -Original Message- From: Julien Viet Sent: Wednesday, February 22, 2006 3:38 PM To: Rajesh Rajasekaran Cc: QA; Anil Saldhana; [EMAIL PROTECTED]; Chris Laprun; jboss-development@lists.sourceforge.net; QA; Julien Viet; [EMAIL PROTECTED]; Thomas Heute Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors jboss-head (JBoss 5) is not today a target for us but we can test it of course. Here is the list that I would like to see : - Branch_4_0 - 4.0.4RC1 (later 4.0.4) - 4.0.3SP1 (already done) --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
We target JBoss Portal 3.0.x to work on JBoss 5. However as you say it would be a good thing, still I don't know when JBoss 5 will be released (alpha was scheduled for 1 month ago). Ryan Campbell wrote: Rajesh, can we put jboss-head at the end? If there is only one failure on jboss-head, perhaps we could raise the issue for the portal team to fix. Having Portal 2.4 compatible with Jboss 5.0 would be a nice thing to have if it's easy. If it's a big deal to fix, we should remove jboss-head from the matrix so we can have a clean build. -Original Message- From: Julien Viet Sent: Wednesday, February 22, 2006 3:38 PM To: Rajesh Rajasekaran Cc: QA; Anil Saldhana; [EMAIL PROTECTED]; Chris Laprun; jboss-development@lists.sourceforge.net; QA; Julien Viet; [EMAIL PROTECTED]; Thomas Heute Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors jboss-head (JBoss 5) is not today a target for us but we can test it of course. Here is the list that I would like to see : - Branch_4_0 - 4.0.4RC1 (later 4.0.4) - 4.0.3SP1 (already done) -- Julien Viet JBoss Portal Project Lead --- 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] 4.0.4.GA issues broken by area
We are some 190 JIRA tasks away from JBAS 4.0.4.GA, so please, don't be shy, browse through your area (or adopt a new one :) and qualify/tackle/reschedule tasks: WebServices 6 XML 3 WebSvr(tomcat) 8 Testsuite 5 System 1 Security11 Remoting4 Other 1 Naming 1 CMP 49 Deployment 14 Documentation 2 EJBs17 Hibernate 2 IIOP4 Installer 13 JBossCache 2 JCA 4 JMS 10 No component10 Build system5 Clustering 21 Merci /Dimitris --- 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] Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
it looks that the file is truncated, what is the reason of that ? Rajesh Rajasekaran wrote: I will put jboss-head to the end and rearrange the list as Julien had requested. The portlet tests against jboss-head had failed and the report XML's were not well-formed, hence the failures not reported by CC. I have opened a task for this. Here s the link. http://jira.jboss.com/jira/browse/JBPORTAL-679 Thanks Rajesh -Original Message- From: Ryan Campbell Sent: Wednesday, February 22, 2006 3:54 PM To: Julien Viet; Rajesh Rajasekaran Cc: QA; jboss-development@lists.sourceforge.net Subject: RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors Rajesh, can we put jboss-head at the end? If there is only one failure on jboss-head, perhaps we could raise the issue for the portal team to fix. Having Portal 2.4 compatible with Jboss 5.0 would be a nice thing to have if it's easy. If it's a big deal to fix, we should remove jboss-head from the matrix so we can have a clean build. -Original Message- From: Julien Viet Sent: Wednesday, February 22, 2006 3:38 PM To: Rajesh Rajasekaran Cc: QA; Anil Saldhana; [EMAIL PROTECTED]; Chris Laprun; jboss-development@lists.sourceforge.net; QA; Julien Viet; [EMAIL PROTECTED]; Thomas Heute Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors jboss-head (JBoss 5) is not today a target for us but we can test it of course. Here is the list that I would like to see : - Branch_4_0 - 4.0.4RC1 (later 4.0.4) - 4.0.3SP1 (already done) -- Julien Viet JBoss Portal Project Lead --- 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] 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=log20060222192129 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:94: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:205: 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:02/22/2006 19:21:29Time to build:3 minutes 28 secondsLast changed:02/22/2006 17:55:48Last log entry:added strategy meta data Unit Tests: (84) Total Errors and Failures: (0)All Tests Passed Modifications since last build:(first 50 of 304)1.1addedclaprunwsrp/src/main/org/jboss/portal/test/wsrp/WSRPBaseTest.javaMoved tests.1.1addedclaprunwsrp/src/main/org/jboss/portal/test/wsrp/v1/ServiceDescriptionTestCase.javaMoved tests.1.2deletedclaprunwsrp/src/main/org/jboss/portal/wsrp/test/WSRPBaseTest.javaMoved tests.1.2deletedclaprunwsrp/src/main/org/jboss/portal/wsrp/test/v1/ServiceDescriptionTestCase.javaMoved tests.1.9modifiedasaldhanawsrp/src/main/org/jboss/portal/wsrp/endpoints/ServiceDescriptionEndpoint.javaUpdate to follow doc/lit bare style1.2modifiedasaldhanawsrp/src/main/org/jboss/portal/wsrp/WSRPProducer.javaUpdate to use the doc/lit bare pattern1.1addedasaldhanawsrp/src/resources/jndi.propertiesJNDI properties file that is useful for looking up dynamic proxy1.1addedasaldhanawsrp/src/resources/log4j.xmlA log4j xml file useful for the wsrp module particularly in testing1.3modifiedasaldhanawsrp/src/resources/jboss-wsrp-war/WEB-INF/wsdl/wsrp_services.wsdlTemporarily add namespaces to the wsdl to fix a JBossWS bug that once fixed can force a rollback of this ns addition.1.3modifiedasaldhanawsrp/src/resources/jboss-wsrp-war/WEB-INF/jaxrpc-mappings.xmlUpdate the mapping file to follow doc/litbare style.Refer to JBWS-7171.6modifiedasaldhanawsrp/src/resources/jboss-wsrp-sar/META-INF/jboss-service.xmlLet the wsrp engine not depend on the webservices deployer1.1addedasaldhanawsrp/src/resources/jboss-wsrp-client/META-INF/application-client.xmlJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/resources/jboss-wsrp-client/META-INF/jaxrpc-mappings.xmlJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/resources/jboss-wsrp-client/META-INF/jboss-client.xmlJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/resources/jboss-wsrp-client/META-INF/wsdl/wsrp_services.wsdlJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/resources/jboss-wsrp-client/META-INF/wsdl/wsrp_v1_bindings.wsdlJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/resources/jboss-wsrp-client/META-INF/wsdl/wsrp_v1_interfaces.wsdlJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/resources/jboss-wsrp-client/META-INF/wsdl/wsrp_v1_types.xsdJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/main/org/jboss/portal/wsrp/test/WSRPBaseTest.javaJBPORTAL-673: Test Case for WSRP Web Service Invocation1.1addedasaldhanawsrp/src/main/org/jboss/portal/wsrp/test/v1/ServiceDescriptionTestCase.javaJBPORTAL-673: Test Case for WSRP Web Service InvocationWSRP test case for ServiceDescriptionService1.8modifiedclaprunwsrp/src/main/org/jboss/portal/wsrp/endpoints/ServiceDescriptionEndpoint.java- Started producer test implementation.1.1addedclaprunwsrp/src/main/org/jboss/portal/test/wsrp/producer/ServiceDescriptionTest.java- Cleaned-up tests.- Started producer test implementation.1.1addedclaprunwsrp/src/main/org/jboss/portal/wsrp/WSRPProducer.java- Cleaned-up tests.- Started producer test implementation.1.2deletedclaprunwsrp/src/main/test/WSRP_V1_MarkupServer.java- Cleaned-up tests.- Started producer test implementation.1.3deletedclaprunwsrp/src/main/test/WSRP_V1_ServiceDescriptionServer.java- Cleaned-up tests.- Started producer test implementation.1.4modifiedclaprunwsrp/src/main/org/jboss/portal/wsrp/WSRPPortletMode.java- Simplified instance variables names.- Updated web.xml to Web Application 2.4.- Minor refactorings.1.8modifiedclaprunwsrp/src/main/org/jboss/portal/wsrp/WSRPRequest.java- Simplified instance variables names.- Updated web.xml to Web Application 2.4.- Minor refactorings.1.6modifiedclaprunwsrp/src/main/org/jboss/portal/wsrp/WSRPResponse.java- Simplified instance variables names.- Updated web.xml to Web Application 2.4.- Minor refactorings.1.4modifiedclaprunwsrp/src/main/org/jboss/portal/wsrp/WSRPWindowState.java- Simplified instance variables names.- Updated web.xml to
RE: [JBoss-dev] Xalan removal saga
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: Wednesday, February 22, 2006 1:09 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] Xalan removal saga Removing javax.xml.transform.TransformerFactory or patching it to try invoke the underlying TransformerFactory (if this is possible) which is essentially the same thing, is undesirable because you'll end up with a transformer API and an underlying implementation that may not match (correct?) This is always the case though. Any attempt to override the xsl factory will be subject to matching the javax.xml.transform.* in effect. Removing javax.xml.transform.* is not clear that is safe (I guess because you might have incompatible parser api+impl - transformer api+impl interactions?) Ok, we are doomed :) There are some xml parser class dependencies in the javax.xml.transform.dom and javax.xml.transform.sax packages. I just don't know if the javax.xml.transform.* in jaxp 1.3 can use the 1.2 xml parsers. It's a tradeoff between introducing a xsl parser dependency that the user may not want vs modifying the TransformerFactory to be more flexible at the cost of the user potentially have to configure the TransformerFactory default. I think modifying the TransformerFactory is the most flexible, but maybe just bundling the xsl parser is the simplest. --- 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
