[JBoss-dev] jboss-head build.951 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050412015913Lbuild.951 BUILD COMPLETE - build.951Date of build: 04/12/2005 01:59:13Time to build: 22 minutes 42 secondsLast changed: 04/12/2005 01:31:32Last log entry: Updated to fix serialization versioning. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.9modifiedtelrodremoting/src/main/org/jboss/remoting/ConnectionFailedException.javaUpdated to fix serialization versioning.
[JBoss-dev] jboss-head build.950 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050412012543Lbuild.950 BUILD COMPLETE - build.950Date of build: 04/12/2005 01:25:43Time to build: 15 minutes 16 secondsLast changed: 04/12/2005 01:16:45Last log entry: File that has been moved into the wsdl fixture Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (31)1.3deletedosdchicagowebservice/test/resources/tools/W3CExample_DOC_11.wsdlFile that has been moved into the wsdl fixture1.3deletedosdchicagowebservice/test/resources/tools/IncludedSchema20.wsdlRemove unnecessary wsdl/xsd files1.2deletedosdchicagowebservice/test/resources/tools/PrimitiveTypes20.wsdlRemove unnecessary wsdl/xsd files1.2deletedosdchicagowebservice/test/resources/tools/PrimitiveTypes20.xsdRemove unnecessary wsdl/xsd files1.4modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/serverside/ServerSideArtifactsTestCase.javaChanges made to keep wsdlwritedir and wsdlfixture dirs seperate1.3modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/xmlschema/WSDLTypesTestCase.javaChanges made to keep wsdlwritedir and wsdlfixture dirs seperate1.4modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/xmlschema/XMLSchemaTestCase.javaChanges made to keep wsdlwritedir and wsdlfixture dirs seperate1.9modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/JavaToWSDL11TestCase.javaChanges made to keep wsdlwritedir and wsdlfixture dirs seperate1.11modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/JavaToWSDL20TestCase.javaChanges made to keep wsdlwritedir and wsdlfixture dirs seperate1.19modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/WSDL11ToJavaTestCase.javaChanges made to keep wsdlwritedir and wsdlfixture dirs seperate1.4modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/WSDL11ToWSDL20TestCase.javaChanges made to keep wsdlwritedir and wsdlfixture dirs seperate1.5modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/WSDL20ToJavaTestCase.javaChanges made to keep wsdlwritedir and wsdlfixture dirs seperate1.3modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/mapping/MappingFileTestCase.javaChanges made to keep wsdlwritedir and wsdlfixture dirs seperate1.38modifiedosdchicagowebservice/test/build.xmlKeep the wsdl fixture and the wsdl files written by the testcases seperate as far as possible to have a clean workspace1.23modifiedosdchicagowebservice/src/main/org/jboss/ws/wsdl/WSDLDefinitions.javaAllow writing wsdl 1.11.23modifiedosdchicagowebservice/src/main/org/jboss/ws/wsdl/WSDL20Reader.javaformatting change1.8modifiedosdchicagowebservice/src/main/org/jboss/ws/wsdl/WSDL11Writer.javaClean up WSDL 1.1 writing implementation1.17modifiedosdchicagowebservice/src/main/org/jboss/ws/wsdl/WSDL20Writer.javaappend types moved to base class1.14modifiedosdchicagowebservice/src/main/org/jboss/ws/wsdl/WSDLWriter.javaTake care of Types, logging1.10modifiedosdchicagowebservice/src/main/org/jboss/ws/utils/WSDLUtils.javasmall change1.27modifiedosdchicagowebservice/src/main/org/jboss/ws/tools/JavaToWSDL.javatake care of wsdl writing for wsdl 1.1 and 2.01.13modifiedosdchicagowebservice/src/main/org/jboss/ws/tools/Configuration.javaAdd a config for whether wsdl types should be included in the wsdl or imported.1.1addedosdchicagowebservice/test/resources/wsdlfixture/PrimitiveTypes20.wsdlWSDL/XSD files that act as fixture for the testsuite for JBossWS tools1.1addedosdchicagowebservice/test/resources/wsdlfixture/PrimitiveTypes20.xsdWSDL/XSD files that act as fixture for the testsuite for JBossWS tools1.1addedosdchicagowebservice/test/resources/wsdlfixture/PrimitiveTypesService_RPC_11.wsdlWSDL/XSD files that act as fixture for the testsuite for JBossWS tools1.1addedosdchicagowebservice/test/resources/wsdlfixture/StandardJavaTypes20.wsdlWSDL/XSD files that act as fixture for the testsuite for JBossWS tools1.1addedosdchicagowebservice/test/resources/wsdlfixture/StandardJavaTypes20.xsdWSDL/XSD files that act as fixture for the testsuite for JBossWS tools1.1addedosdchicagowebservice/test/resources/wsdlfixture/StandardJavaTypesService_DOC_11.wsdlWSDL/XSD files that act as fixture for the testsuite for JBossWS tools1.1addedosdchicagowebservice/test/resources/wsdlfixture/StandardJavaTypesService_RPC_11.wsdlWSDL/XSD files that act as fixture for the testsuite for JBossWS tools1.1addedosdchicagowebservice/test/resources/wsdlfixture/W3CExample_DOC_11.wsdlWSDL/XSD files that act as fixture for the testsuite for JBossWS tools1.43modifiedreverbeltransaction/src/main/org/jboss/tm/TransactionImpl.javaStore the recovery coordinator.
[JBoss-dev] jboss-4.0 build.497 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050412005134Lbuild.497 BUILD COMPLETE - build.497Date of build: 04/12/2005 00:51:34Time to build: 17 minutes 44 secondsLast changed: 04/11/2005 23:52:38Last log entry: Catch invalid jar exceptions Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (12)1.1.2.2modifiedstarksmvaria/src/main/org/jboss/tools/ClassVersionInfo.javaCatch invalid jar exceptions1.1.2.2modifiedstarksmvaria/src/main/org/jboss/tools/SerialVersionUID.javaCatch invalid jar exceptions1.4.14.4modifiedstarksmremoting/src/main/org/jboss/remoting/ConnectionFailedException.javaCorrect the serialVersionUID values to the 4.0.1 settings.1.7.4.2modifiedstarksmjmx/src/main/javax/management/MBeanServerPermission.javaCorrect the serialVersionUID values to the 4.0.1 settings.1.1.30.4modifiedstarksmjmx/src/main/javax/management/relation/RelationNotFoundException.javaCorrect the serialVersionUID values to the 4.0.1 settings.1.24.2.5modifiedstarksmjmx/src/main/javax/management/modelmbean/DescriptorSupport.javaCorrect the serialVersionUID values to the 4.0.1 settings.1.7.4.4modifiedstarksmj2ee/src/main/javax/security/jacc/EJBMethodPermission.javaCorrect the serialVersionUID values to the 4.0.1 settings.1.3.6.4modifiedstarksmj2ee/src/main/javax/security/jacc/EJBRoleRefPermission.javaCorrect the serialVersionUID values to the 4.0.1 settings.1.2.4.3modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxClientInterceptor.javaCorrect the serialVersionUID values to the 4.0.1 settings.1.3.4.4modifiedstarksmiiop/src/main/org/jboss/iiop/csiv2/SASCurrentImpl.javaCorrect the serialVersionUID values to the 4.0.1 settings.1.2.4.4modifiedstarksmiiop/src/main/org/jboss/iiop/csiv2/SASTargetInterceptor.javaCorrect the serialVersionUID values to the 4.0.1 settings.1.2.6.8modifiedstarksmcommon/src/main/javax/xml/namespace/QName.javaThe correct 4.0.1 legacy serialVersionUID is 8217399441836960859
[JBoss-dev] [Design of JBoss Internal Benchmarking] - Re: jboss-benchmark project - standalone?
Actually just reminded that the new build will eliminate this problem, so guess can just wait till then. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873511#3873511 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873511 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1319) redeploy causes OutOfMemoryError
[ http://jira.jboss.com/jira/browse/JBAS-1319?page=comments#action_12316856 ] Scott M Stark commented on JBAS-1319: - The profiler sar should just be a seperate download that can be used with any jboss version. This issue can be closed as fixed for 4.0.2. > redeploy causes OutOfMemoryError > > > Key: JBAS-1319 > URL: http://jira.jboss.com/jira/browse/JBAS-1319 > Project: JBoss Application Server > Type: Bug > Components: Web (Tomcat) service > Versions: JBossAS-4.0.1 Final > Environment: JBoss 4.0.1 running on fedora core 3, using jdk 1.5.0 > Reporter: Matthew Todd > Assignee: Adrian Brock > Attachments: ServletExample.zip, analysis.zip > > Time Spent: 1 week > > Constant redployment, even of a simple web application eventually causes an > OutOfMemoryError in JBoss. > To duplicate, keep on copying a .war package into a servers hot deploy > directory. Eventually an OutOfMemoryError occurs. > This is especially dangerous when running as a cluster, as when the node is > restarted, it is unable to join the cluster again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.949 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050412000358Lbuild.949 BUILD COMPLETE - build.949Date of build: 04/12/2005 00:03:58Time to build: 17 minutes 26 secondsLast changed: 04/11/2005 23:41:16Last log entry: More DTM stuff. Set/unset the TxManager's ResourceFactories in thestart/stop methods of the DTM and OTS MBeans. Factor out utilitymethods to the new class TMUtil. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (6)1.5modifiedreverbeliiop/src/main/org/jboss/tm/iiop/CorbaTransactionService.javaMore DTM stuff. Set/unset the TxManager's ResourceFactories in thestart/stop methods of the DTM and OTS MBeans. Factor out utilitymethods to the new class TMUtil.1.2modifiedreverbeliiop/src/main/org/jboss/tm/iiop/OTSServant.javaMore DTM stuff. Set/unset the TxManager's ResourceFactories in thestart/stop methods of the DTM and OTS MBeans. Factor out utilitymethods to the new class TMUtil.1.4modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/server/DTMServant.javaMore DTM stuff. Set/unset the TxManager's ResourceFactories in thestart/stop methods of the DTM and OTS MBeans. Factor out utilitymethods to the new class TMUtil.1.3modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/server/DistributedTransactionManager.javaMore DTM stuff. Set/unset the TxManager's ResourceFactories in thestart/stop methods of the DTM and OTS MBeans. Factor out utilitymethods to the new class TMUtil.1.1addedreverbeltransaction/src/main/org/jboss/tm/TMUtil.javaMore DTM stuff. Set/unset the TxManager's ResourceFactories in thestart/stop methods of the DTM and OTS MBeans. Factor out utilitymethods to the new class TMUtil.1.5modifiedtelrodserver/src/main/org/jboss/invocation/unified/interfaces/UnifiedInvokerProxy.javaUpdated to fix serialization versioning.
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1319) redeploy causes OutOfMemoryError
[ http://jira.jboss.com/jira/browse/JBAS-1319?page=comments#action_12316855 ] Clebert Suconic commented on JBAS-1319: --- This should be done in what version? Should we mark the fix to? (At least a trying?) -clebert > redeploy causes OutOfMemoryError > > > Key: JBAS-1319 > URL: http://jira.jboss.com/jira/browse/JBAS-1319 > Project: JBoss Application Server > Type: Bug > Components: Web (Tomcat) service > Versions: JBossAS-4.0.1 Final > Environment: JBoss 4.0.1 running on fedora core 3, using jdk 1.5.0 > Reporter: Matthew Todd > Assignee: Adrian Brock > Attachments: ServletExample.zip, analysis.zip > > Time Spent: 1 week > > Constant redployment, even of a simple web application eventually causes an > OutOfMemoryError in JBoss. > To duplicate, keep on copying a .war package into a servers hot deploy > directory. Eventually an OutOfMemoryError occurs. > This is especially dangerous when running as a cluster, as when the node is > restarted, it is unable to join the cluster again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.496 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050411233522Lbuild.496 BUILD COMPLETE - build.496Date of build: 04/11/2005 23:35:22Time to build: 20 minutes 57 secondsLast changed: 04/11/2005 23:13:15Last log entry: Use the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (2)1.1.6.2modifiedstarksmj2ee/src/main/javax/xml/registry/JAXRException.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.2.6.7modifiedstarksmcommon/src/main/javax/xml/namespace/QName.javaThe serialVersionUID must be static final in order for it to be picked up by the ObjectStreamClass logic.
[JBoss-dev] jboss-4.0-jdk-matrix build.127 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050411222310Lbuild.127 BUILD COMPLETE - build.127Date of build: 04/11/2005 22:23:10Time to build: 44 minutes 27 secondsLast changed: 04/11/2005 16:53:52Last log entry: The 4.0.1 value of the serialVersionUID was compatible with the 1.4.1 ri versions so revert to that as the value. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (61)1.2.30.4modifiedstarksmjmx/src/main/javax/management/InvalidApplicationException.javaThe 4.0.1 value of the serialVersionUID was compatible with the 1.4.1 ri versions so revert to that as the value.1.2.30.4modifiedstarksmjmx/src/main/javax/management/InvalidAttributeValueException.javaThe 4.0.1 value of the serialVersionUID was compatible with the 1.4.1 ri versions so revert to that as the value.1.26.2.3modifiedstarksmjmx/src/main/javax/management/loading/MLet.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.1.2.3modifiednihilitytestsuite/src/main/org/jboss/test/webservice/addressrewrite/AddressRewriteTestCase.javafix javadoc comment1.13.4.5modifiednihilitywebservice/src/resources/META-INF/jboss-service.xmlSwitch default of AlwaysModifySOAPAddress to 4.0.1 behavior1.1.2.2modifiednihilitytestsuite/src/main/org/jboss/test/webservice/addressrewrite/AddressRewriteTestCase.javaModify addressrewrite test to test both behaviors of theAlwaysModifySOAPAddress attribute by toggeling the JMX value in betweentests.1.406.2.55modifiedstarksmtestsuite/build.xmlRun the tests-compatibility target with MaxPermSize of 96m due to the number of loaded classes.1.1.2.2modifiedstarksmtestsuite/src/main/org/jboss/test/compatibility/test/SerialVersionUIDUnitTestCase.javaorg.apache, org.jacorb, org.jboss.webservice package classes as they are not compatible with 4.0.11.25.6.5modifiedstarksmconnector/src/main/org/jboss/resource/connectionmanager/RARDeployment.javaSet the serialVersionUID value to that from 4.0.11.16.2.4modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnectionFactory.javaSet the serialVersionUID value to that from 4.0.11.1.10.2modifiedstarksmremoting/src/main/org/jboss/remoting/invocation/NameBasedInvocation.javaSet the serialVersionUID value to that from 4.0.11.4.14.3modifiedstarksmremoting/src/main/org/jboss/remoting/ConnectionFailedException.javaSet the serialVersionUID value to that from 4.0.11.2.6.2modifiedstarksmjmx/src/main/org/jboss/mx/util/InstanceOfQueryExp.javaSet the serialVersionUID value to that from 4.0.11.12.4.3modifiedstarksmserver/src/main/org/jboss/jms/asf/StdServerSessionPoolFactory.javaSet the serialVersionUID value to that from 4.0.11.4.6.2modifiedstarksmjmx/src/main/org/jboss/mx/server/ServerObjectInstance.javaSet the serialVersionUID value to that from 4.0.11.12.6.2modifiedstarksmjmx/src/main/org/jboss/mx/capability/OptimizedMBeanDispatcher.javaSet the serialVersionUID value to that from 4.0.11.2.4.1modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxServerClientInterceptor.javaSet the serialVersionUID value to that from 4.0.11.1.4.1modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxServerClientInterceptorInitializer.javaSet the serialVersionUID value to that from 4.0.11.4.4.1modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxServerInterceptor.javaSet the serialVersionUID value to that from 4.0.11.2.6.1modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxServerInterceptorInitializer.javaSet the serialVersionUID value to that from 4.0.11.2.4.2modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxClientInterceptor.javaSet the serialVersionUID value to that from 4.0.11.1.6.1modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxClientInterceptorInitializer.javaSet the serialVersionUID value to that from 4.0.11.2.4.1modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxIORInterceptor.javaSet the serialVersionUID value to that from 4.0.11.1.4.1modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxIORInterceptorInitializer.javaSet the serialVersionUID value to that from 4.0.11.1.16.1modifiedstarksmiiop/src/main/org/jboss/iiop/codebase/CodebaseInterceptor.javaSet the serialVersionUID value to that from 4.0.11.3.6.1modifiedstarksmiiop/src/main/org/jboss/iiop/codebase/CodebaseInterceptorInitializer.javaSet the serialVersionUID value to that from 4.0.11.1.16.1modifiedstarksmiiop/src/main/org/jboss/iiop/codebase/CodebasePolicy.javaSet the serialVersionUID value to that from 4.0.11.1.16.1modifiedstarksmiiop/src/main/org/jboss/iiop/codebase/CodebasePolicyFactory.javaSet the serialVersionUID value to that from 4.0.11.8.4.2modifiedstarksmiiop/src/main/org/jboss/iiop/csiv2/CSIv2IORInterceptor.javaSet the serialVersionUID value to that from 4.0.11.4.4.1modifiedstarksmiiop/src/main/org/jboss/iiop/csiv2/CSIv2Initializer.ja
[JBoss-dev] [Design of JBoss Internal Benchmarking] - Re: jboss-benchmark project - standalone?
The forum took out my spacing, but assume you understand the diretory structure. For JBossRemoting I was just going to put a jboss directory under the lib directory with all the jboss libraries and a README.txt file with the versions for all the libraries (and mabye license, but may be repetative). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873510#3873510 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873510 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: shared state between HttpSession and PortletSession
I have come up with a approach for communication between portlet applications and I would like to get some feedback. My requirements are: * a session that is visible across portlet applications * an approach that will work well in a clustered environment (Julian, I couldn't easily see how to extend a static map so I started down an alternate path) What I plan to do is create a Stateful Session Bean for each active user during login. When the Session Bean is first created, I will put the remote reference in the JBoss naming directory using the user's ID as the key. Portlets that need to read or update attributes that cross portlet applications will lookup the remote reference using JNDI and interact with the user's instance of the Session Bean. I believe this approach will behave well in a cluster since JNDI and Stateful Session Beans are well supported in a JBoss AS cluster, right? Any feedback is appreciated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873509#3873509 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873509 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.948 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050411212434Lbuild.948 BUILD COMPLETE - build.948Date of build: 04/11/2005 21:24:34Time to build: 16 minutes 35 secondsLast changed: 04/11/2005 18:47:28Last log entry: remove test target Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (2)1.24modifiedrecampbelltools/etc/jbossbuild/tasks.xmlremove test target1.18modifiedccrouchadmin-console/build.xmlupdated to use new version of cglib
[JBoss-dev] [JBoss JIRA] Created: (JBPORTAL-237) Anonymous Forum postings
Anonymous Forum postings Key: JBPORTAL-237 URL: http://jira.jboss.com/jira/browse/JBPORTAL-237 Project: JBoss Portal Type: Bug Versions: 2.0 RC Reporter: Roy Russo Assigned to: Roy Russo Priority: Minor Fix For: 2.0 RC Anonymous users are not able to post to forums when assigned the proper permissions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: CMS portlet : 404 error
I'm assuming you have all the proper jars under je-config/lib, or you would've encountered problems from the beginning. 1. Are you getting a stack trace? Post it here. 2. Please post the "exact" 404 message text you are getting. I ask this, because there are two. So just copy and paste it here. 3. Are you able to obtain access to the AdminCMS? Try adding/editting files and such. This helps me diagnose the problem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873506#3873506 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873506 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: JSR170?
as soon as there is a decent implementation that fit our needs we start to replace Slide by JCR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873505#3873505 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873505 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - JSR170?
Forgive me if I've overlooked something, but I've searched this forum and the site and can't find any reference to JSR170. Are there plans to support this standard (once it becomes a standard)? Thanks! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873504#3873504 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873504 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1609) Backport latest JBossCache (1.2.2)
[ http://jira.jboss.com/jira/browse/JBAS-1609?page=history ] Ben Wang resolved JBAS-1609: Resolution: Done > Backport latest JBossCache (1.2.2) > -- > > Key: JBAS-1609 > URL: http://jira.jboss.com/jira/browse/JBAS-1609 > Project: JBoss Application Server > Type: Task > Components: JBoss Cache service > Versions: JBossAS-3.2.7 Final, JBossAS-4.0.2RC1 > Reporter: Ben Wang > Assignee: Ben Wang > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 6 hours > Remaining: 6 hours > > We need to backport JBossCache1.2.1 to 4.0.2 release. However, there is one > or two bugs that Bela had to fix after the release in head though. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: CMS portlet : 404 error
I think I may be running into this same problem. We are sharing an instance of JBoss for research purposes, and although I've unzipped the cms files into MY configuration, I'm getting 404 errors all throughout the CMS portlets. (Using Portal 2.0beta1) Note the 'je-config': /usr/local/jboss-4.0.1sp1/server/je-default/data/portal/webdav/store/content I'm starting JBoss with 'run.sh --config=je-config'. Is it required to run the Portal from the default configuration? Is there something I can edit to help it find the files in my configuration? Thanks! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873501#3873501 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873501 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.947 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050411182851Lbuild.947 BUILD COMPLETE - build.947Date of build: 04/11/2005 18:28:51Time to build: 24 minutes 47 secondsLast changed: 04/11/2005 18:00:08Last log entry: Rename TransactionServiceImpl to OTSServant, just to emphasize thesimilarity with the DTMServant. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (20)1.4modifiedreverbeliiop/src/main/org/jboss/tm/iiop/CorbaTransactionService.javaRename TransactionServiceImpl to OTSServant, just to emphasize thesimilarity with the DTMServant.1.1addedreverbeliiop/src/main/org/jboss/tm/iiop/OTSServant.javaRename TransactionServiceImpl to OTSServant, just to emphasize thesimilarity with the DTMServant.1.6deletedreverbeliiop/src/main/org/jboss/tm/iiop/TransactionServiceImpl.javaRename TransactionServiceImpl to OTSServant, just to emphasize thesimilarity with the DTMServant.1.2deletedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicCommitException.javaRemove superfluous exception classes.Use javax.transaction.Heuristic*Exception classes instead.1.3deletedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicMixedException.javaRemove superfluous exception classes.Use javax.transaction.Heuristic*Exception classes instead.1.3deletedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicRollbackException.javaRemove superfluous exception classes.Use javax.transaction.Heuristic*Exception classes instead.1.5modifiedreverbeliiop/src/main/org/jboss/tm/iiop/TransactionServiceImpl.javaMore DTM code. This is still work in progress, but should not affect thenon-distributed usage of the TM.1.2modifiedreverbeliiop/src/main/org/jboss/tm/iiop/wrapper/OTSResourceWrapper.javaMore DTM code. This is still work in progress, but should not affect thenon-distributed usage of the TM.1.3modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/server/DTMServant.javaMore DTM code. This is still work in progress, but should not affect thenon-distributed usage of the TM.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/server/DistributedTransactionManager.javaMore DTM code. This is still work in progress, but should not affect thenon-distributed usage of the TM.1.3modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/Resource.javaMore DTM code. This is still work in progress, but should not affect thenon-distributed usage of the TM.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/Terminator.javaMore DTM code. This is still work in progress, but should not affect thenon-distributed usage of the TM.1.3modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/Invocation.javaMore DTM code. This is still work in progress, but should not affect thenon-distributed usage of the TM.1.24modifiedreverbeltransaction/src/main/org/jboss/tm/TxManager.javaMore DTM code. This is still work in progress, but should not affect thenon-distributed usage of the TM.1.15modifiedreverbeltransaction/src/main/org/jboss/tm/XidFactory.javaMore DTM code. This is still work in progress, but should not affect thenon-distributed usage of the TM.1.1addedreverbeltransaction/src/main/org/jboss/tm/ResourceFactory.javaMore DTM code. This is still work in progress, but should not affect thenon-distributed usage of the TM.1.42modifiedreverbeltransaction/src/main/org/jboss/tm/TransactionImpl.javaMore DTM code. This is still work in progress, but should not affect thenon-distributed usage of the TM.1.4modifiedtelrodserver/src/main/org/jboss/invocation/unified/interfaces/UnifiedInvokerProxy.javaUpdated to fix serialization versioning.1.8modifiedtelrodremoting/src/main/org/jboss/remoting/ConnectionFailedException.javaUpdated to fix serialization versioning.1.4modifiedtelrodremoting/src/main/org/jboss/remoting/invocation/NameBasedInvocation.javaUpdated to fix serialization versioning.
[JBoss-dev] [Design of JBoss Portal] - Re: Will the Portal support deployment to other AS?
Today JBoss Portal uses JBoss microkernel as integration bus for our services and in the future it will use JBoss microcontainer the next generation of the microkernel. Technically, JBoss upcoming micro container will run in any VM and will provide us portability for that layer. So the other technical aspect is about the servlet container layer on which the portal depends and that has already been adressed in a post earlier. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873498#3873498 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873498 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.495 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050411174442Lbuild.495 BUILD COMPLETE - build.495Date of build: 04/11/2005 17:44:42Time to build: 35 minutes 8 secondsLast changed: 04/11/2005 16:53:52Last log entry: The 4.0.1 value of the serialVersionUID was compatible with the 1.4.1 ri versions so revert to that as the value. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (3)1.2.30.4modifiedstarksmjmx/src/main/javax/management/InvalidApplicationException.javaThe 4.0.1 value of the serialVersionUID was compatible with the 1.4.1 ri versions so revert to that as the value.1.2.30.4modifiedstarksmjmx/src/main/javax/management/InvalidAttributeValueException.javaThe 4.0.1 value of the serialVersionUID was compatible with the 1.4.1 ri versions so revert to that as the value.1.26.2.3modifiedstarksmjmx/src/main/javax/management/loading/MLet.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1562) Expose getEntityLockMonitor in the MBean EntityLockMonitorMBean
[ http://jira.jboss.com/jira/browse/JBAS-1562?page=history ] Ivelin Ivanov reassigned JBAS-1562: --- Assign To: Dimitris Andreadis > Expose getEntityLockMonitor in the MBean EntityLockMonitorMBean > --- > > Key: JBAS-1562 > URL: http://jira.jboss.com/jira/browse/JBAS-1562 > Project: JBoss Application Server > Type: Feature Request > Components: EJBs, JMX > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, > JBossAS-4.0.1 SP1 > Reporter: Yaron Zakai Or > Assignee: Dimitris Andreadis > > > In order to perform proper monitoring of EJB locks, the current functionality > is not enough for the following reasons: > 1. The LockMonitor is saved per EJB name, where multiple EJBs can have the > same name. The solution should be to store it based on the jndi name. > 2. The only way to get per-EJB information is to use the printLockMonitor > method. This will create a non reasonable overhead for a real-life monitoring > solution. The solution here is to expose the method getEntityLockMonitor in > the MBean interface. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Looking for more information for an evaluation
"anakhah" wrote : - For example, when I log in, I see a set of portlets, but I don't see a mechanism to create pages or add portlets to a page. I did find the sections in the Reference Guide regarding create pages via the xml. Does that mean that is the only mechanism available? | For now, yes. "anakhah" wrote : | - Can users not create or customize pages? | Not unless they have access to the xml descriptors. ;-) "anakhah" wrote : | - I saw posts regarding the implementation of a thames API in the next release. So does the current release not support any branding/customization of the GUI? What customizations do the users or admins have in JBoss Portal? | Accessible by the user? No. This will be in the upcoming release. "anakhah" wrote : | - I also do not see any way to associate portlets with users via the admin console. Is such security not available? Or can security against portlets only be applied via the xml descriptors? | The UI you speak of, is not available. So, yes, only via xml-descriptors for now. "anakhah" wrote : | Is there a comparison document anywhere that details the features supported (or to be supported soon) by JBoss Portal? | Our jira tasks are here: http://jira.jboss.com/jira/browse/JBPORTAL?report=com.atlassian.jira.plugin.system.project:roadmap-panel;jsessionid=FA7CE05468AA8AEEABFBA1026DACFB0D A basic listing is here: http://www.jboss.org/wiki/Wiki.jsp?page=JBossPortalFeatures View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873496#3873496 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873496 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.946 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050411160617Lbuild.946 BUILD COMPLETE - build.946Date of build: 04/11/2005 16:06:17Time to build: 38 minutes 39 secondsLast changed: 04/11/2005 14:45:29Last log entry: set ignore white space to true in xmlunit Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (7)1.2modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/sourcecomp/XMLCompareTestCase.javaset ignore white space to true in xmlunit1.3modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/serverside/ServerSideArtifactsTestCase.javaValidate wsdl/mapping files using xmlunit and add logging capability.1.2modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/mapping/MappingFileTestCase.javaAdd property to ignore whitespace in XMLUnit1.2modifiedosdchicagowebservice/src/main/org/jboss/ws/tools/mapping/MappingFileGenerator.javaFixes made in comparison with wscompile tool1.12modifiedosdchicagowebservice/src/main/org/jboss/ws/tools/jbossws.javaGenerate the JAXRPC mapping files.1.26modifiedosdchicagowebservice/src/main/org/jboss/ws/tools/JavaToWSDL.javaFix the interface name based on wsdl type (1.1 or 2.0)1.12modifiedosdchicagowebservice/src/main/org/jboss/ws/tools/Configuration.javaAdd servicename as a config property
[JBoss-dev] [Design of JBoss Portal] - Re: Will the Portal support deployment to other AS?
"jjustice" wrote : Thank you for the responses. However, I see two kinds of answers here. One saying that eventually it would be nice for JBoss Portal to be deployable to other AS, and the other saying that there are technical reasons why this won't happen. The short technical answer is that it depends on the jboss5 pojo framework. "jjustice" wrote : | I understand that the Portal-PortletContainer contract is not standardized, but this doesn't prevent Portals like Liferay and eXo from being deployed to different AS. I'm new to JBoss, so I don't really know what JEMS is or what the implications of that link are, but it does seem that the JBoss team may have made choices to couple the Portal to JBoss in ways that are not an immediate consequence of the standards or lack of standards. The decision was made early on in the project to focus on JBoss AS, for reasons of resource-usage. It was much easier for us to focus on one container and do it well than focus on 5 containers and do it poorly with the fixed amount of resources we originally had. Aside from developing the portal, we have to hand the portal code over to our QA labs for testing. It also becomes a resource-usage issue then. "jjustice" wrote : | That being said, if worse comes to worse, we'd still be much better off from a cost of licensing standpoint if we have to deploy JBoss to deliver our Portal to a client who already has WebSphere than we would be if we had to deploy WebSphere to deliver our Portal to a client who already has JBoss. :) This sentence confused me. ;-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873495#3873495 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873495 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Internal Benchmarking] - Re: jboss-benchmark project - standalone?
I agree... it makes sense. But what about jboss libs like jgroups? Should we include it as third party jars? -clebert View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873493#3873493 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873493 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Messaging on JBoss (Messaging/JBoss)] - URGENT Setting System Properties
Hi, I am facing a problem with defining different system properties for 2 different instances of the same web application. In my deploy directory I have two extracted war files and the application expects a system property to be set that holds a directory path and this must be different for the 2 applications. With tomcat I'm doing it like this: | | | | | How can this be achieved with JBOSS? I tried with the properties-service.xml but I have not clue how to use different values for different applications. any help is greatly appreciated thanks, Guido View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873492#3873492 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873492 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Internal Benchmarking] - Re: jboss-benchmark project - standalone?
If you are going to make it standalone, would certainly include the thirdparty jars in the CVS project and in the distribution. My personal suggestion would to maintain a similar structure for the lib directory as in jboss-head. For example: jboss-benchmark - lib - apache-commons - commons-logging.jar - README.txt - LICENSE.txt - junit - junit.jar - README.txt so that versions and licenses can be easily tracked between versions (is much more difficult if just have a lib directory with all the jars in it). I can add this if you like? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873491#3873491 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873491 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Will the Portal support deployment to other AS?
Thank you for the responses. However, I see two kinds of answers here. One saying that eventually it would be nice for JBoss Portal to be deployable to other AS, and the other saying that there are technical reasons why this won't happen. I understand that the Portal-PortletContainer contract is not standardized, but this doesn't prevent Portals like Liferay and eXo from being deployed to different AS. I'm new to JBoss, so I don't really know what JEMS is or what the implications of that link are, but it does seem that the JBoss team may have made choices to couple the Portal to JBoss in ways that are not an immediate consequence of the standards or lack of standards. That being said, if worse comes to worse, we'd still be much better off from a cost of licensing standpoint if we have to deploy JBoss to deliver our Portal to a client who already has WebSphere than we would be if we had to deploy WebSphere to deliver our Portal to a client who already has JBoss. :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873490#3873490 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873490 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1598) Create a compatibility matrix which tracks JBoss client vs. server class versions
[ http://jira.jboss.com/jira/browse/JBAS-1598?page=comments#action_12316851 ] Ivelin Ivanov commented on JBAS-1598: - From: Scott M Stark Sent: Monday, April 11, 2005 1:00 PM To: Clebert Suconic; '[EMAIL PROTECTED]' Subject: RE: Create a compatibility matrix which tracks JBoss client vs. server class versions Serialization should be mostly covered by the SerialVersionUIDUnitTestCase in the bundled testsuite. There needs to be basic testing of all j2ee interfaces by running a subset of the existing testuite modules against the current jboss server. This is not hard. 1. For each release of jboss there is a build of the release source. 2. The current jboss server branch is obtained and built. 3. The current jboss server branch binary is run as with the all configuration. 4. For each release of jboss: a. Run a subset of the testsuite unit tests from within the release build so that the release build binaries are used. 5. Merge the testsuite runs into a cross version compatibility matrix. The toplevel view is a simple pass/fail matrix which indicates whether all of the tests run using the x.y.z binaries passed. From: Clebert Suconic Sent: Monday, April 11, 2005 10:52 AM To: Scott M Stark; '[EMAIL PROTECTED]' Subject: RE: Create a compatibility matrix which tracks JBoss client vs. server class versions We will need to test Serialization across versions or functionalities across version as well? I'm afraid about the answer you would have, as if we have to test functionality, the amount of work will be huge. What if the Serialization works, but it the interceptor on 4.0.1 puts something different on the Marshalling that the stubs are not prepared to receive. (Just wondering some breaking in the functionality) But If it's serialization only, we can do it fast. Clebert From: Scott M Stark Sent: Monday, April 11, 2005 12:42 PM To: Clebert Suconic; '[EMAIL PROTECTED]' Subject: RE: Create a compatibility matrix which tracks JBoss client vs. server class versions No, that is not enough. We need an independent test matrix that is run as part of the nightly qa process that runs the testsuite using the x.y.z release jars against the current 4.0 branch to validate actual functional behavior. Serialization version ids are only one small part of version interop. Addition/removal of classes, and changes in implementation are the other big factors that break interop. The serialization version uid test is the only one that should be part of the normal development testsuite. The cross version matrix needs to be external and not part of the testuite cvs module so as not to bloat the download. From: Clebert Suconic Sent: Monday, April 11, 2005 9:49 AM To: Scott M Stark; '[EMAIL PROTECTED]' Subject: RE: Create a compatibility matrix which tracks JBoss client vs. server class versions I can extend what you did into http://jira.jboss.com/jira/browse/JBAS-1584 Do you think that if I compare SerialUID from previous versions against actual version would be enough to keep this compatibility matrix, or should we be doing something beyond that? Also... I created a simple testcase that verifies if classes are defining UIDs. As cruisecontrol is broken for 4.0 now, I think people haven't look at the results. I think we still have classes not defining SerialUUID. My understanding is that this matrix is dependent of clearing SerialUUIDs first. Is that right? Clebert From: Scott M Stark Sent: Monday, April 11, 2005 12:08 AM To: [EMAIL PROTECTED] Subject: Create a compatibility matrix which tracks JBoss client vs. server class versions What is the status of this issue? http://jira.jboss.com/jira/browse/JBAS-1598 > Create a compatibility matrix which tracks JBoss client vs. server class > versions > -- > > Key: JBAS-1598 > URL: http://jira.jboss.com/jira/browse/JBAS-1598 > Project: JBoss Application Server > Type: Sub-task > Reporter: Ivelin Ivanov > Assignee: Clebert Suconic > > > The matrix should list JBoss client jars, the version of their JBoss distro > and the respective JBoss versions that the clients are compatible with. For > example (not verified) > | JBoss AS Client Jars | Compatible with JBoss AS versions | > | -|---| > | 4.0.2| 4.0.2, 4.0.1 | > | 3.2.7| 3.2.6, 3.2.5 | > > Ideally the matrix should be maintained and updated as part of the build > process using the automated tests from JBAS-1584. -- This message is auto
[JBoss-dev] [Design of JBoss Portal] - Looking for more information for an evaluation
I'm currently evaluating various JSR 168 implementations and I've got JBoss Portal installed and running here. I also have other implementations installed and evaluated (JetSpeed, Liferay) but I'm having trouble determing the feature set that JBoss Portal offers. In looking at just the initial pages you see between the three implementation, it just seems like JBoss Portal is lacking in a number of areas. I'm wondering if perhaps I am missing some areas in my installation. - For example, when I log in, I see a set of portlets, but I don't see a mechanism to create pages or add portlets to a page. I did find the sections in the Reference Guide regarding create pages via the xml. Does that mean that is the only mechanism available? - Can users not create or customize pages? - I saw posts regarding the implementation of a thames API in the next release. So does the current release not support any branding/customization of the GUI? What customizations do the users or admins have in JBoss Portal? - I also do not see any way to associate portlets with users via the admin console. Is such security not available? Or can security against portlets only be applied via the xml descriptors? Rather than go through the full list of features that I'm concerned about and ask them individually, I'll leave it as a more set of general question. Does JBoss Portal support similar features to the other implementations mentioned above (Liferay, JetSpeed)? Will the next JBoss Portal release support similar features? Is there a comparison document anywhere that details the features supported (or to be supported soon) by JBoss Portal? Thanks! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873489#3873489 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873489 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Internal Benchmarking] - Re: jboss-benchmark project - standalone?
My initial though was to be a standalone project. My idea was to redistribute JARS. Like in the jboss-4.0/testsuite we would add it in the classpath. And about the buildsuite, we can use it of course, unless we find any issues. -Clebert View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873488#3873488 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873488 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Internal Benchmarking] - jboss-benchmark project - standalone?
Wanted to know if the jboss-benchmark project in CVS is going to be treated as a standalone project? If so, is it alright to add the needed libraries for this project? Also, will this project be using the new jboss build in the future? Thanks. -Tom View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873487#3873487 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873487 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of XDoclet Tags on JBoss (XDoclet/JBoss)] - Is String in EJB and inet in database possible with Xdoclets
Is it possible to specify a String as EJB CMP field while the database type is inert (PostgreSQL) with XDoclets in JBoss IDE? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873486#3873486 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873486 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1319) redeploy causes OutOfMemoryError
[ http://jira.jboss.com/jira/browse/JBAS-1319?page=comments#action_12316849 ] Clebert Suconic commented on JBAS-1319: --- Adrian wrote: What we really need is to identify the classloader classloader.toString() and then provide backtraces to what is holding references: There is a new method on the JVMTI MBean I created that can expose all objects of a given class. I have a small JSP that is writting details about these class in a simple table, but it's still under work. If you think this might help, let me know! > redeploy causes OutOfMemoryError > > > Key: JBAS-1319 > URL: http://jira.jboss.com/jira/browse/JBAS-1319 > Project: JBoss Application Server > Type: Bug > Components: Web (Tomcat) service > Versions: JBossAS-4.0.1 Final > Environment: JBoss 4.0.1 running on fedora core 3, using jdk 1.5.0 > Reporter: Matthew Todd > Assignee: Adrian Brock > Attachments: ServletExample.zip, analysis.zip > > Time Spent: 1 week > > Constant redployment, even of a simple web application eventually causes an > OutOfMemoryError in JBoss. > To duplicate, keep on copying a .war package into a servers hot deploy > directory. Eventually an OutOfMemoryError occurs. > This is especially dangerous when running as a cluster, as when the node is > restarted, it is unable to join the cluster again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2-jdk-matrix build.95 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050411145948Lbuild.95 BUILD COMPLETE - build.95Date of build: 04/11/2005 14:59:48Time to build: 26 minutes 18 seconds Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (0)
[JBoss-dev] [JBoss JIRA] Commented: (JBIDE-172) Eclipse crashes when adding a method in FiboBean (tutorial)
[ http://jira.jboss.com/jira/browse/JBIDE-172?page=comments#action_12316848 ] vidar haakestad commented on JBIDE-172: --- I consistently manage to recreate it. > Eclipse crashes when adding a method in FiboBean (tutorial) > --- > > Key: JBIDE-172 > URL: http://jira.jboss.com/jira/browse/JBIDE-172 > Project: JBoss IDE > Type: Bug > Environment: Java version: 1.4.2_07,Sun Microsystems Inc. > Java VM: Java HotSpot(TM) Server VM 1.4.2_07-b05,Sun Microsystems Inc. > OS-System: Linux 2.6.8.1-12mdksmp,i386 (Mandrake 10) > HW: Dual channel 2.8Ghz Intel Pentium 4 > 2GB memory > JBoss Eclipse plugin 1.4.1.e31-jre15 > Reporter: vidar haakestad > Assignee: Marshall Culpepper > Priority: Critical > > > Are trying the example from JBossIDE Tutorial 'An introduction and > walkthrough of JBossIDE 1.4', chapter 4, creating business logic. I get the > wizard 'EJB Business Method' launched ok, and starts to fill the wizard with > data. > I MISS COMPREHENDING PUSHING THE ADD BUTTON to add a parameter, and just > activates the 'Parameters' (text?) box by clicking it with the mouse cursor. > Then I start writing exactly what the tutorial specifies in the picture > (including the square brackets) and hits the 'Return' key. Then Eclipse > crashes whith a dialog specifying the parameters used when it was started (no > core file). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBIDE-172) Eclipse crashes when adding a method in FiboBean (tutorial)
Eclipse crashes when adding a method in FiboBean (tutorial) --- Key: JBIDE-172 URL: http://jira.jboss.com/jira/browse/JBIDE-172 Project: JBoss IDE Type: Bug Environment: Java version: 1.4.2_07,Sun Microsystems Inc. Java VM: Java HotSpot(TM) Server VM 1.4.2_07-b05,Sun Microsystems Inc. OS-System: Linux 2.6.8.1-12mdksmp,i386 (Mandrake 10) HW: Dual channel 2.8Ghz Intel Pentium 4 2GB memory JBoss Eclipse plugin 1.4.1.e31-jre15 Reporter: vidar hïkestad Assigned to: Marshall Culpepper Priority: Critical Are trying the example from JBossIDE Tutorial 'An introduction and walkthrough of JBossIDE 1.4', chapter 4, creating business logic. I get the wizard 'EJB Business Method' launched ok, and starts to fill the wizard with data. I MISS COMPREHENDING PUSHING THE ADD BUTTON to add a parameter, and just activates the 'Parameters' (text?) box by clicking it with the mouse cursor. Then I start writing exactly what the tutorial specifies in the picture (including the square brackets) and hits the 'Return' key. Then Eclipse crashes whith a dialog specifying the parameters used when it was started (no core file). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.494 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050411133629Lbuild.494 BUILD COMPLETE - build.494Date of build: 04/11/2005 13:36:29Time to build: 43 minutes 49 secondsLast changed: 04/11/2005 13:12:52Last log entry: fix javadoc comment Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (3)1.1.2.3modifiednihilitytestsuite/src/main/org/jboss/test/webservice/addressrewrite/AddressRewriteTestCase.javafix javadoc comment1.13.4.5modifiednihilitywebservice/src/resources/META-INF/jboss-service.xmlSwitch default of AlwaysModifySOAPAddress to 4.0.1 behavior1.1.2.2modifiednihilitytestsuite/src/main/org/jboss/test/webservice/addressrewrite/AddressRewriteTestCase.javaModify addressrewrite test to test both behaviors of theAlwaysModifySOAPAddress attribute by toggeling the JMX value in betweentests.
[JBoss-dev] [Design of Messaging on JBoss (Messaging/JBoss)] - Unit testing strategy
I was curious as to the unit testing strategy for the project. I imagine the TCK tests would provide good coverage (for the JMS facade at least.) However I also imagine there are licencing issues with these tests? Is the normal strategy to always provide "home grown" unit tests irrespective of any TCK test suite that might exist? -Tim View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873470#3873470 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873470 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Profiler] - Re: New Feature - Memory Profiler
Just did it. org.jboss.profiler.jvmti.JVMTIInterface.getAllObjects(Class class) will return all instance from the give class. And: org.jboss.profiler.jvmti.JVMTIInterface.getLoadedClasses() Will return all the classes loaded in the JVM. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873469#3873469 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873469 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPM-119) Have Node.leave() call executionContext.setTransition() before fireEvent().
Have Node.leave() call executionContext.setTransition() before fireEvent(). --- Key: JBPM-119 URL: http://jira.jboss.com/jira/browse/JBPM-119 Project: JBoss jBPM Type: Feature Request Components: Core Engine Versions: jBPM 3.0 alpha 3 Reporter: chadbo Assigned to: Tom Baeyens Action handlers for node-leave events should be able to figure out what transition is being taken. (I could be wrong but) I believe Node.leave() should do executionContext.setTransition(transition) before line 320 where it does fireEvent(Event.EVENTTYPE_NODE_LEAVE, executionContext). That way, a node-leave action handler could call executionContext.getTransition(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Struts on Portal Server made possible
I sent the implementation to both Julien and Roy. Hope you guys got it View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873467#3873467 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873467 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Struts on Portal Server made possible
I am interested in seeing this as well. Please forward when you have a chance. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873466#3873466 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873466 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Struts on Portal Server made possible
thanks, send it to us (julien and roy) so we can look at it.
I looked at the bridge release in M2 version of JS2 and it seemed we only had
to implement an interface that gives the http request in function of the
portlet request.
| package org.apache.portals.bridges.common;
|
| public interface ServletContextProvider
| {
| ServletContext getServletContext(GenericPortlet portlet);
| HttpServletRequest getHttpServletRequest(GenericPortlet portlet,
PortletRequest request);
| HttpServletResponse getHttpServletResponse(GenericPortlet portlet,
PortletResponse response);
| }
|
Is it what you worked with ?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873464#3873464
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873464
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2-testsuite build.108 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050411092552Lbuild.108 BUILD COMPLETE - build.108Date of build: 04/11/2005 09:25:52Time to build: 148 minutes 48 seconds Unit Tests: (1967) Total Errors and Failures: (9)testAllTx_RWLockorg.jboss.test.cache.stress.EvictionLocalStressTestCasetestNoClassDefFoundErrororg.jboss.test.classloader.test.BasicLoaderUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestMDBDeepRunAsorg.jboss.test.security.test.EJBSpecUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestSessionTimeoutorg.jboss.test.cluster.test.SimpleTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCase Modifications since last build: (0)
[JBoss-dev] [Design of JBoss Portal] - Re: Struts on Portal Server made possible
We have the struts-bridge working with jboss-portal-2.0-beta1. Our implementation required adding jboss-portal specific extension to the bridge. The bridge seems to assume an implementation that is specific to the way Jetspeed-2 implements it. Since jboss-portal implements some of the things differently, making the struts-bridge work with jboss-portal requires non-trivial implementation. We will send our implementation to jboss-portal folks for their review. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873462#3873462 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873462 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Will the Portal support deployment to other AS?
today a given JBoss Portal version is targeted to run on a defined set of JBoss AS versions because JBoss Portal is part of JEMS. When we will support more servlet containers, we will ensure that the portlet container implementation is certified on JBoss AS. So far we cannot guarantee anything for other containers. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873455#3873455 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873455 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1625) JBossQL ORDER BY does not work on string valued mapped types
[ http://jira.jboss.com/jira/browse/JBAS-1625?page=comments#action_12316843 ] cgs commented on JBAS-1625: --- I should note that currentContactInfo.emailAddress is mapped with: com.x.RFC2821Address java.lang.String com.x.RFC2821AddressMapper > JBossQL ORDER BY does not work on string valued mapped types > > > Key: JBAS-1625 > URL: http://jira.jboss.com/jira/browse/JBAS-1625 > Project: JBoss Application Server > Type: Bug > Components: CMP service > Versions: JBossAS-4.0.1 Final > Environment: Windows XP Pro SP2, JBoss 4.0.1, Sun JDK 1.5.0_02 > Reporter: cgs > Assignee: Alexey Loubyansky > > > 09:59:09,147 WARN [ServiceController] Problem starting service > jboss.j2ee:jndiName=ejb/Contact,service=EJB > org.jboss.deployment.DeploymentException: Error compiling JBossQL statement > 'SELECT DISTINCT OBJECT(c) FROM organization o, IN (o.contactList) AS c WHERE > o = ?1 ORDER BY c.currentContactInfo.lastName ASC, > c.currentContactInfo.firstName ASC, c.currentContactInfo.emailAddress ASC > OFFSET ?2 LIMIT ?3'; - nested throwable: > (org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered > "c.currentContactInfo.emailAddress" at line 1, column 186. > Was expecting one of: > ... > ... > ... > ) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCJBossQLQuery.(JDBCJBossQLQuery.java:52) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createJBossQLQuery(JDBCCommandFactory.java:72) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCQueryManager.start(JDBCQueryManager.java:260) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.startStoreManager(JDBCStoreManager.java:490) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:381) > at > org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:157) > at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:340) > at > org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) > at > org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at > org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) > at > org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891) > at $Proxy0.start(Unknown Source) > at org.jboss.system.ServiceController.start(ServiceController.java:416) > at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at > org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > at $Proxy304.start(Unknown Source) > at org.jboss.ejb.EjbModule.startService(EjbModule.java:394) > at > org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) > at > org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at > org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) > at > org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891) > at $Proxy0.start(Unknown Source) > at org.jboss.system.ServiceController.start(ServiceCo
[JBoss-dev] [Design of JBoss Portal] - Re: Will the Portal support deployment to other AS?
Portal heavily depends on the Servlet container implementation. Different vendor?s implementations known to be non compatible in some areas (thread allocation per request, redirect, include, forward, etc), that creates a lot of problems for portlet container implementation. In the future portlet container may be included in the standard j2ee server (j2ee 1.6). There is no standard contract defined between portal and portlet container, so it will be custom implementation for each supported AS. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873453#3873453 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873453 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBIDE-171) Create a help plugin providing online help
Create a help plugin providing online help -- Key: JBIDE-171 URL: http://jira.jboss.com/jira/browse/JBIDE-171 Project: JBoss IDE Type: Task Components: jBPM Designer plugin Versions: 1.5 Milestone 2 Reporter: Koen Aers Assigned to: Koen Aers -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-42) HTTP Protocol Proxy
[
http://jira.jboss.com/jira/browse/JBMAIL-42?page=comments#action_12316842 ]
Andrew Oliver commented on JBMAIL-42:
-
This rfc: http://www.faqs.org/rfcs/rfc2817.html
describes proxying via HTTP connect a bit better. The simplicity of having a
mail client just specify HTTP proxy and wrap all SMTP into that is
appealing
> HTTP Protocol Proxy
> ---
>
> Key: JBMAIL-42
> URL: http://jira.jboss.com/jira/browse/JBMAIL-42
> Project: JBoss Mail
> Type: Feature Request
> Components: SMTP, POP
> Reporter: Andrew Oliver
> Assignee: Andrew Oliver
> Priority: Critical
>
> Original Estimate: 2 days
> Remaining: 2 days
>
> Develop an HTTP Proxy which allows one to tunnel HTTP to SMTP or POP.
> Example:
> C: GET /SMTP/Connect HTTP/1.1
> C:
> S: HTTP/1.1 200 OK
> S: Set-Cookie: JSESSIONID=440CF11A9AB5B28872380A333659F4C1; Path=/
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1
> S:
> S: 220 set.superlinksoftware.com SMTP Server (JBMAIL SMTP Server version 0.1)
> ready March 17, 2005 10:00:36 AM EST
> Connection closed (not necessary for 1.1 but demonstrative)
> C: GET /SMTP/EHLO HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C:
> S: HTTP/1.1 200 OK
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1\
> S:
> S: 334 VXNlcm5hbWU6
> C: GET /SMTP/AUTH_LOGIN HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C:
> S: HTTP/1.1 200 OK
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1\
> S:
> S: 334 VXNlcm5hbWU6
> S:
> C: POST /SMTP/AUTH_LOGIN HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C: Content-Type: application/x-www-form-urlencoded
> C:
> C: {encoded user}
> S:
> S: HTTP/1.1 200 OK
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1\
> S:
> S: 334 UGFzc3dvcmQ6
> S:
> C: POST /SMTP/AUTH_LOGIN HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C: Content-Type: application/x-www-form-urlencoded
> C:
> C: {encoded pwd}
> S:
> S: HTTP/1.1 200 OK
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1\
> S:
> S: 200 Authorized
> S:
> C: POST /SMTP/MAIL_FROM HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C: Content-Type: application/x-www-form-urlencoded
> C:
> C: <[EMAIL PROTECTED]>
> the intent is the "proxy" will be implemneted as a servlet and connect to
> port 25 on the "real" mail server. All submitted data can be based on HTTP
> POSTS. All requests should be valid HTTP. (so urlencode and do
> parm1=<[EMAIL PROTECTED]> if its not valid to pass just a key with no value)
> The Session ID is the key to the open connection from the proxy. In the
> event the connection from the proxy to real mail server closes then an
> invalid session error should be returned to the client.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1673) ClassCastException in JmsActivation in setupQueueConnection
ClassCastException in JmsActivation in setupQueueConnection --- Key: JBAS-1673 URL: http://jira.jboss.com/jira/browse/JBAS-1673 Project: JBoss Application Server Type: Bug Components: JMS service Versions: JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 Reporter: Scott M Stark Fix For: JBossAS-4.0.2 Final There is a copy/paste error in the setupQueueConnection for the QueueConnectionFactory which passes in a TopicConnectionFactory.class: QueueConnectionFactory qcf = (QueueConnectionFactory) Util.lookup(ctx, queueFactoryRef, TopicConnectionFactory.class); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-42) HTTP Protocol Proxy
[
http://jira.jboss.com/jira/browse/JBMAIL-42?page=comments#action_12316841 ]
Andrew Oliver commented on JBMAIL-42:
-
Thanks for that. It looks very er..."interesting". While we'd still need a
go-between to make the REST communicate to the rest of the world (oh bad bad
pun), that looks like it not only solves the issue but goes one up on the
issue.
> HTTP Protocol Proxy
> ---
>
> Key: JBMAIL-42
> URL: http://jira.jboss.com/jira/browse/JBMAIL-42
> Project: JBoss Mail
> Type: Feature Request
> Components: SMTP, POP
> Reporter: Andrew Oliver
> Assignee: Andrew Oliver
> Priority: Critical
>
> Original Estimate: 2 days
> Remaining: 2 days
>
> Develop an HTTP Proxy which allows one to tunnel HTTP to SMTP or POP.
> Example:
> C: GET /SMTP/Connect HTTP/1.1
> C:
> S: HTTP/1.1 200 OK
> S: Set-Cookie: JSESSIONID=440CF11A9AB5B28872380A333659F4C1; Path=/
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1
> S:
> S: 220 set.superlinksoftware.com SMTP Server (JBMAIL SMTP Server version 0.1)
> ready March 17, 2005 10:00:36 AM EST
> Connection closed (not necessary for 1.1 but demonstrative)
> C: GET /SMTP/EHLO HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C:
> S: HTTP/1.1 200 OK
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1\
> S:
> S: 334 VXNlcm5hbWU6
> C: GET /SMTP/AUTH_LOGIN HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C:
> S: HTTP/1.1 200 OK
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1\
> S:
> S: 334 VXNlcm5hbWU6
> S:
> C: POST /SMTP/AUTH_LOGIN HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C: Content-Type: application/x-www-form-urlencoded
> C:
> C: {encoded user}
> S:
> S: HTTP/1.1 200 OK
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1\
> S:
> S: 334 UGFzc3dvcmQ6
> S:
> C: POST /SMTP/AUTH_LOGIN HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C: Content-Type: application/x-www-form-urlencoded
> C:
> C: {encoded pwd}
> S:
> S: HTTP/1.1 200 OK
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1\
> S:
> S: 200 Authorized
> S:
> C: POST /SMTP/MAIL_FROM HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C: Content-Type: application/x-www-form-urlencoded
> C:
> C: <[EMAIL PROTECTED]>
> the intent is the "proxy" will be implemneted as a servlet and connect to
> port 25 on the "real" mail server. All submitted data can be based on HTTP
> POSTS. All requests should be valid HTTP. (so urlencode and do
> parm1=<[EMAIL PROTECTED]> if its not valid to pass just a key with no value)
> The Session ID is the key to the open connection from the proxy. In the
> event the connection from the proxy to real mail server closes then an
> invalid session error should be returned to the client.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBREM-8) Ability to stream files via remoting
[ http://jira.jboss.com/jira/browse/JBREM-8?page=comments#action_12316840 ] Yaron Zakai Or commented on JBREM-8: This ability will be needed by us (Identify software), in order to enable remote installation of our BlackBox into JBoss AS. > Ability to stream files via remoting > > > Key: JBREM-8 > URL: http://jira.jboss.com/jira/browse/JBREM-8 > Project: JBoss Remoting > Type: Feature Request > Components: general > Versions: 1.0.1 alpha > Reporter: Tom Elrod > Assignee: Tom Elrod > Fix For: 1.1.0 beta > > > Would like to add ability for user to stream files using remoting. Initially > requested by Dimitris for deploying files from management console using > remoting. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head-jdk-matrix build.106 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050411075911Lbuild.106 BUILD COMPLETE - build.106Date of build: 04/11/2005 07:59:11Time to build: 47 minutes 10 secondsLast changed: 04/11/2005 00:51:15Last log entry: Set the serialVersionUID value to that from 4.0.1 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (36)1.13modifiedstarksmjmx/src/main/org/jboss/mx/capability/OptimizedMBeanDispatcher.javaSet the serialVersionUID value to that from 4.0.11.14modifiedstarksmserver/src/main/org/jboss/jms/asf/StdServerSessionPoolFactory.javaSet the serialVersionUID value to that from 4.0.11.24modifiedstarksmaop/src/main/org/jboss/aop/ClassInstanceAdvisor.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.4modifiedstarksmaop/src/main/org/jboss/aop/standalone/Package.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.13modifiedstarksmaop/src/main/org/jboss/aop/joinpoint/ConstructorCalledByMethodInvocation.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.7modifiedstarksmaop/src/main/org/jboss/aop/joinpoint/ConstructorCalledByMethodInvocationWrapper.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.5modifiedstarksmaop/src/main/org/jboss/aop/joinpoint/InvocationBase.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.11modifiedstarksmaop/src/main/org/jboss/aop/joinpoint/MethodCalledByMethodInvocation.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.8modifiedstarksmaop/src/main/org/jboss/aop/joinpoint/MethodCalledByMethodInvocationWrapper.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.8modifiedstarksmaop/src/main/org/jboss/aop/advice/Scope.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.15modifiedstarksmaop/src/main/org/jboss/aop/proxy/ClassProxyTemplate.javaAdd the missing serialVersionUID1.8modifiedstarksmaop/src/main/org/jboss/aop/metadata/SimpleMetaData.javaAdd the missing serialVersionUID1.24modifiedstarksmaop/src/main/org/jboss/aop/joinpoint/MethodInvocation.javaAdd the missing serialVersionUID1.2modifiedstarksmcache/src/main/org/jboss/cache/transaction/DummyBaseTransactionManager.javaSet the serialVersionUID value to that from 4.0.11.18modifiedstarksmcache/src/main/org/jboss/cache/transaction/DummyTransactionManager.javaSet the serialVersionUID value to that from 4.0.11.2modifiedstarksmcache/src/main/org/jboss/cache/loader/NodeData.javaSet the serialVersionUID value to that from 4.0.11.72modifiedstarksmcache/src/main/org/jboss/cache/Node.javaSet the serialVersionUID value to that from 4.0.11.4modifiedstarksmj2ee/src/main/javax/xml/rpc/soap/SOAPFaultException.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.10modifiedstarksmcache/src/main/org/jboss/cache/GlobalTransaction.javaSet the serialVersionUID value to that from 4.0.11.16modifiedstarksmcache/src/main/org/jboss/cache/Fqn.javaSet the serialVersionUID value to that from 4.0.11.4modifiedstarksmcommon/src/main/javax/xml/namespace/QName.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.9modifiedstarksmj2ee/src/main/javax/security/jacc/EJBMethodPermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.5modifiedstarksmj2ee/src/main/javax/security/jacc/EJBRoleRefPermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.8modifiedstarksmj2ee/src/main/javax/security/jacc/WebResourcePermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.6modifiedstarksmj2ee/src/main/javax/security/jacc/WebRoleRefPermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.8modifiedstarksmj2ee/src/main/javax/security/jacc/WebUserDataPermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.6modifiedstarksmj2ee/src/main/javax/resource/spi/work/WorkEvent.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.5modifiedstarksmj2ee/src/main/javax/resource/spi/InvalidPropertyException.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.8modifiedstarksmj2ee/src/main/javax/resource/spi/ConnectionEvent.javaUse the SerialVersion
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-135) Beans with @Remote and @Local don't hotdeploy well
Beans with @Remote and @Local don't hotdeploy well -- Key: EJBTHREE-135 URL: http://jira.jboss.com/jira/browse/EJBTHREE-135 Project: EJB 3.0 Type: Bug Versions: Preview 5 Reporter: Bill Burke Fix For: Preview 6 2) When I use session beans that have only @Remote interfaces defined, they seem to deploy and hot deploy fine. But if I change the beans to have both a @Remote and a @Local interface then hot deployment doesn't bind them into JNDI anymore. So now that I have beans with both, I have to keep bouncing the server. This is only a pain cause I was really enjoying the fast code-deploy cycle. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: error by admin login
Please show a dump of your database for tables: jbp_users jbp_roles and jbp_role_membership View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873436#3873436 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873436 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - error by admin login
I want to login with the admin user and the password admin. After this login, I get this Error-Message: 14:58:35,169 INFO [STDOUT] WURFL has been initialized 14:59:44,799 ERROR [CoyoteAdapter] An exception or error occurred in the container during the reques t processing java.lang.NullPointerException at java.util.Arrays.mergeSort(Arrays.java:1156) at java.util.Arrays.sort(Arrays.java:1080) at org.apache.catalina.realm.GenericPrincipal.(GenericPrincipal.java:77) at org.jboss.web.tomcat.security.JBossGenericPrincipal.(JBossGenericPrincipal.java:40) at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.getCachingPrincpal(JBossSecurityMgrRe alm.java:343) at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.ja va:257) at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:2 35) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:54) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11P rotocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:595) Can anybody help me further? regards lars View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873434#3873434 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873434 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: error by admin login
My Configuration: JBoss AS 4.0.1 MySQL 4.0.24 Portal 2.0 Beta 1 JDBC 3.1.6 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873435#3873435 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873435 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Admin Console] - Release plans
Hi, When does this module is planned to be released, and is it going to be part of a JBoss release, or released as a separate application. Thanks, Yaron. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873431#3873431 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873431 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Mail Services] - Re: Minor fixes to HEAD and integration of Nokia branch
Stored mail bodies now work with after removing the nested InputStreams. I have added a IOUtil.dotStuffingCopy method that will copy a dotStuffed stream to a normal output stream. Currently this is only used for stored mail bodies. Simple mail bodies are still using the code from the Nokia branch. Eventually I will refactor it so both use the new copying method, but I want to do some benchmarking first to check that the new util method performs just as well. In theory the new copy method should be slightly faster as it does 1 less copying step than the nokia code. There may be a negitive impact on the performance of the store, as the new copying method runs differently (not likely to be a terrible hit, but not optimal). The buffering within the blob output stream makes some assumptions about the way the copying is done. I will fix this soon. Mike. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873379#3873379 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873379 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Mail Services] - Re: Minor fixes to HEAD and integration of Nokia branch
duh I should have known about the not null int thingy. Excellent Mike. I need to check what the previous numbers were with Thomas Diesler were and I'll give you them I just remember being pleasently shocked. After this I'm thinking our main bottleneck will be the stupid JavaMail+JAF thingy. I'm going to open a dialog up with the JAMES guys to see if there is room for a collaboration on a complete replacement for JavaMail. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873387#3873387 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873387 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-54) Remove ALL hardcoded MBEAN NAMES!!!
[
http://jira.jboss.com/jira/browse/JBMAIL-54?page=comments#action_12316831 ]
Michael Barker commented on JBMAIL-54:
--
Fixed MailBody.java (using MBean properties and comp/env variables for mbean
and ejbs respectively). There is still one case of a hardcoded mbean name in
Mailbox.java
> Remove ALL hardcoded MBEAN NAMES!!!
> ---
>
> Key: JBMAIL-54
> URL: http://jira.jboss.com/jira/browse/JBMAIL-54
> Project: JBoss Mail
> Type: Task
> Components: Mail Server APIs, POP, Security, SMTP
> Versions: 1.0-M3
> Reporter: Andrew Oliver
> Assignee: Michael Barker
> Priority: Critical
> Fix For: 1.0-M3
>
> Original Estimate: 3 hours
> Remaining: 3 hours
>
> There are hardcoded MBean names...
> ...
> public abstract class MailBody
> {
> ...
>public final static String MAILBODY_MANAGER_NAME =
> "jboss.mail:type=MailServices,name=MailBodyManager";
> These should nver be in code but should always be externalized. For one
> there might be multiple instances of JBMS hosted in the same appserver which
> would require different domains. Moreover its just naughty :-)
> I assigned this to Mike because I only see this in the store code so far.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1598) Create a compatibility matrix which tracks JBoss client vs. server class versions
[ http://jira.jboss.com/jira/browse/JBAS-1598?page=history ] Ivelin Ivanov reassigned JBAS-1598: --- Assign To: Clebert Suconic > Create a compatibility matrix which tracks JBoss client vs. server class > versions > -- > > Key: JBAS-1598 > URL: http://jira.jboss.com/jira/browse/JBAS-1598 > Project: JBoss Application Server > Type: Sub-task > Reporter: Ivelin Ivanov > Assignee: Clebert Suconic > > > The matrix should list JBoss client jars, the version of their JBoss distro > and the respective JBoss versions that the clients are compatible with. For > example (not verified) > | JBoss AS Client Jars | Compatible with JBoss AS versions | > | -|---| > | 4.0.2| 4.0.2, 4.0.1 | > | 3.2.7| 3.2.6, 3.2.5 | > > Ideally the matrix should be maintained and updated as part of the build > process using the automated tests from JBAS-1584. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1486) Allow for deployments without an explicit suffix
[ http://jira.jboss.com/jira/browse/JBAS-1486?page=comments#action_12316832 ] Simon Gunzenreiner commented on JBAS-1486: -- This would be very convenient indeed. It would allow directory deployment of the binary directory produced by eclipse wtp, without manually adjusting the default output directory named "bin" to someting like "myejb.jar", or the "WebContent" directory to "WebContent.war". This then allows a very quick development cycle, where nothing has to be copied/exported to the jboss deploy directory; instead, one can use fast url deployment. > Allow for deployments without an explicit suffix > > > Key: JBAS-1486 > URL: http://jira.jboss.com/jira/browse/JBAS-1486 > Project: JBoss Application Server > Type: Feature Request > Components: JMX > Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Priority: Minor > Fix For: JBossAS-4.0.3 Final > > > A not uncommon request is to allow for deployments that do not have a > qualifying suffix, for example, myejb/ instead of myejb.jar/, mywebapp > instead of mywebapp.war > Most deployers require both a sepcific suffix and the correct deployment > descriptor to exist in order to accept the deployment. We should look into > supporting such deployments. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.490 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log2005041017Lbuild.490 BUILD COMPLETE - build.490Date of build: 04/10/2005 22:22:17Time to build: 16 minutes 9 secondsLast changed: 04/10/2005 21:26:47Last log entry: Use the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (5)1.2.8.2modifiedstarksmj2ee/src/main/javax/xml/rpc/JAXRPCException.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.2.8.2modifiedstarksmj2ee/src/main/javax/xml/rpc/ServiceException.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.1.8.2modifiedstarksmj2ee/src/main/javax/xml/soap/SOAPException.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.1.6.2modifiedstarksmj2ee/src/main/javax/xml/registry/RegistryException.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.3.8.2modifiedstarksmj2ee/src/main/javax/xml/rpc/soap/SOAPFaultException.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.
[JBoss-dev] jboss-4.0 build.489 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050410211829Lbuild.489 BUILD COMPLETE - build.489Date of build: 04/10/2005 21:18:29Time to build: 21 minutes 24 secondsLast changed: 04/10/2005 21:12:05Last log entry: Use the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (6)1.2.6.6modifiedstarksmcommon/src/main/javax/xml/namespace/QName.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.7.4.3modifiedstarksmj2ee/src/main/javax/security/jacc/EJBMethodPermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.3.6.3modifiedstarksmj2ee/src/main/javax/security/jacc/EJBRoleRefPermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.5.4.4modifiedstarksmj2ee/src/main/javax/security/jacc/WebResourcePermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.3.4.3modifiedstarksmj2ee/src/main/javax/security/jacc/WebRoleRefPermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.5.4.3modifiedstarksmj2ee/src/main/javax/security/jacc/WebUserDataPermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.
[JBoss-dev] [Design the new POJO MicroContainer] - KernelControllerState
Is there a more detailed explanation on KernelControllerState states? (somekind of transition diagram or explanation). I'm mostly interested in mapping those to the existing 4.x states. Most of them are self describing but I can't figure out the LIFECYCLE state. Is this an extension point? Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873417#3873417 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873417 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1672) ERROR PAGE tag in Tomcat50 embebbed in jboss 4 does not work.
ERROR PAGE tag in Tomcat50 embebbed in jboss 4 does not work. - Key: JBAS-1672 URL: http://jira.jboss.com/jira/browse/JBAS-1672 Project: JBoss Application Server Type: Bug Components: Web (Tomcat) service Versions: JBossAS-4.0.1 SP1 Reporter: Carlos Rodrigo Santos Priority: Minor When configuring tag in tomcat 5 in Jboss 4.0.1sp1 it does not redirects to the error page configured when the error occurs. It dows not work with http error codes nor java exceptions. When the error occurs it generates a blank page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss/Tomcat Integration] - How to use jsf in the JBoss4.0.1's Tomcat?
When I test a jsf example in Tomcat5 alone ,it success. But when I copy the files used in Tomcat5 into jbossweb-tomcat50.sar\*.war , the common *.jsp file can run, but the jsp file including jsf component can not run. I have had *.jar about jsf in the lib. The problem is like "javax.faces.webapp.FacesServlet.init(FacesServlet.java:144) ". View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873395#3873395 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873395 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.493 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050411012508Lbuild.493 BUILD COMPLETE - build.493Date of build: 04/11/2005 01:25:08Time to build: 22 minutes 18 secondsLast changed: 04/11/2005 00:58:04Last log entry: Run the tests-compatibility target with MaxPermSize of 96m due to the number of loaded classes. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (2)1.406.2.55modifiedstarksmtestsuite/build.xmlRun the tests-compatibility target with MaxPermSize of 96m due to the number of loaded classes.1.1.2.2modifiedstarksmtestsuite/src/main/org/jboss/test/compatibility/test/SerialVersionUIDUnitTestCase.javaorg.apache, org.jacorb, org.jboss.webservice package classes as they are not compatible with 4.0.1
[JBoss-dev] jboss-head build.942 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050410181101Lbuild.942 BUILD COMPLETE - build.942Date of build: 04/10/2005 18:11:01Time to build: 23 minutes 23 secondsLast changed: 04/10/2005 17:49:35Last log entry: Use the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (10)1.6modifiedstarksmj2ee/src/main/javax/resource/spi/work/WorkEvent.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.5modifiedstarksmj2ee/src/main/javax/resource/spi/InvalidPropertyException.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.8modifiedstarksmj2ee/src/main/javax/resource/spi/ConnectionEvent.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.4modifiedstarksmj2se/src/main/javax/management/relation/RelationNotFoundException.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.4modifiedstarksmj2se/src/main/javax/management/InvalidAttributeValueException.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.3modifiedstarksmj2se/src/main/javax/management/InvalidApplicationException.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.5modifiedstarksmj2ee/src/main/javax/enterprise/deploy/spi/status/ProgressEvent.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.6modifiedstarksmj2ee/src/main/javax/resource/ResourceException.java- Override the getMessage method to include the error code- Use the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.2deletedstarksmj2ee/src/main/org/jboss/j2ee/util/SerialVersion.javaMove the SerialVersion compatibility constants to the common module for use with serialVersionUID values across all of the modules, not just the j2ee module.1.1addedstarksmcommon/src/main/org/jboss/util/id/SerialVersion.javaMove the SerialVersion compatibility constants to the common module for use with serialVersionUID values across all of the modules, not just the j2ee module.
[JBoss-dev] jboss-4.0 build.491 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050410232842Lbuild.491 BUILD COMPLETE - build.491Date of build: 04/10/2005 23:28:42Time to build: 16 minutes 28 secondsLast changed: 04/10/2005 23:22:52Last log entry: Set the serialVersionUID value to that from 4.0.1 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (40)1.1.10.2modifiedstarksmremoting/src/main/org/jboss/remoting/invocation/NameBasedInvocation.javaSet the serialVersionUID value to that from 4.0.11.4.14.3modifiedstarksmremoting/src/main/org/jboss/remoting/ConnectionFailedException.javaSet the serialVersionUID value to that from 4.0.11.2.6.2modifiedstarksmjmx/src/main/org/jboss/mx/util/InstanceOfQueryExp.javaSet the serialVersionUID value to that from 4.0.11.12.4.3modifiedstarksmserver/src/main/org/jboss/jms/asf/StdServerSessionPoolFactory.javaSet the serialVersionUID value to that from 4.0.11.4.6.2modifiedstarksmjmx/src/main/org/jboss/mx/server/ServerObjectInstance.javaSet the serialVersionUID value to that from 4.0.11.12.6.2modifiedstarksmjmx/src/main/org/jboss/mx/capability/OptimizedMBeanDispatcher.javaSet the serialVersionUID value to that from 4.0.11.2.4.1modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxServerClientInterceptor.javaSet the serialVersionUID value to that from 4.0.11.1.4.1modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxServerClientInterceptorInitializer.javaSet the serialVersionUID value to that from 4.0.11.4.4.1modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxServerInterceptor.javaSet the serialVersionUID value to that from 4.0.11.2.6.1modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxServerInterceptorInitializer.javaSet the serialVersionUID value to that from 4.0.11.2.4.2modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxClientInterceptor.javaSet the serialVersionUID value to that from 4.0.11.1.6.1modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxClientInterceptorInitializer.javaSet the serialVersionUID value to that from 4.0.11.2.4.1modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxIORInterceptor.javaSet the serialVersionUID value to that from 4.0.11.1.4.1modifiedstarksmiiop/src/main/org/jboss/tm/iiop/TxIORInterceptorInitializer.javaSet the serialVersionUID value to that from 4.0.11.1.16.1modifiedstarksmiiop/src/main/org/jboss/iiop/codebase/CodebaseInterceptor.javaSet the serialVersionUID value to that from 4.0.11.3.6.1modifiedstarksmiiop/src/main/org/jboss/iiop/codebase/CodebaseInterceptorInitializer.javaSet the serialVersionUID value to that from 4.0.11.1.16.1modifiedstarksmiiop/src/main/org/jboss/iiop/codebase/CodebasePolicy.javaSet the serialVersionUID value to that from 4.0.11.1.16.1modifiedstarksmiiop/src/main/org/jboss/iiop/codebase/CodebasePolicyFactory.javaSet the serialVersionUID value to that from 4.0.11.8.4.2modifiedstarksmiiop/src/main/org/jboss/iiop/csiv2/CSIv2IORInterceptor.javaSet the serialVersionUID value to that from 4.0.11.4.4.1modifiedstarksmiiop/src/main/org/jboss/iiop/csiv2/CSIv2Initializer.javaSet the serialVersionUID value to that from 4.0.11.6.4.2modifiedstarksmiiop/src/main/org/jboss/iiop/csiv2/CSIv2Policy.javaSet the serialVersionUID value to that from 4.0.11.2.4.1modifiedstarksmiiop/src/main/org/jboss/iiop/csiv2/CSIv2PolicyFactory.javaSet the serialVersionUID value to that from 4.0.11.4.4.3modifiedstarksmiiop/src/main/org/jboss/iiop/csiv2/SASClientIdentityInterceptor.javaSet the serialVersionUID value to that from 4.0.11.3.4.2modifiedstarksmiiop/src/main/org/jboss/iiop/csiv2/SASClientInitializer.javaSet the serialVersionUID value to that from 4.0.11.3.4.3modifiedstarksmiiop/src/main/org/jboss/iiop/csiv2/SASInitializer.javaSet the serialVersionUID value to that from 4.0.11.3.4.3modifiedstarksmiiop/src/main/org/jboss/iiop/csiv2/SASClientInterceptor.javaSet the serialVersionUID value to that from 4.0.11.3.4.3modifiedstarksmiiop/src/main/org/jboss/iiop/csiv2/SASCurrentImpl.javaSet the serialVersionUID value to that from 4.0.11.2.4.3modifiedstarksmiiop/src/main/org/jboss/iiop/csiv2/SASTargetInterceptor.javaSet the serialVersionUID value to that from 4.0.11.2.6.3modifiedstarksmconsole/src/main/org/jboss/console/plugins/monitor/CreateSnapshotServlet.javaSet the serialVersionUID value to that from 4.0.11.2.6.3modifiedstarksmconsole/src/main/org/jboss/console/plugins/monitor/CreateStringThresholdMonitorServlet.javaSet the serialVersionUID value to that from 4.0.11.2.6.3modifiedstarksmconsole/src/main/org/jboss/console/plugins/monitor/CreateThresholdMonitorServlet.javaSet the serialVersionUID value to that from 4.0.11.2.6.4modifiedstarksmconsole/src/main/org/jboss/console/plugins/monitor/ManageSnapshotServlet.javaSet the serialVersionUID value to that from 4.0.11.2.6.3modifiedstarksmconsole/src/main/org/jboss/console/plugins/monitor/ManageStringThresholdMonitorServlet.javaSet the serialVersionUID value to
[JBoss-dev] [Design of JBoss Profiler] - Re: New Feature - Memory Profiler
Just discovered how to create a getObjectsofClass in the MBean: It's easy: http://java.sun.com/j2se/1.5.0/docs/guide/jvmti/jvmti.html#GetObjectsWithTags I think this will be very helpfull. Clebert Suconic View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873390#3873390 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873390 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.941 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log2005041058Lbuild.941 BUILD COMPLETE - build.941Date of build: 04/10/2005 11:11:58Time to build: 22 minutes 32 secondsLast changed: 04/10/2005 11:00:15Last log entry: JBAS1633 another fix Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.13modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaJBAS1633 another fix
[JBoss-dev] [JBoss JIRA] Closed: (JBMICROCONT-4) Virtual File System service
[ http://jira.jboss.com/jira/browse/JBMICROCONT-4?page=history ] Dimitris Andreadis closed JBMICROCONT-4: Resolution: Done This is part of VDF Virtual Deployment Framework > Virtual File System service > --- > > Key: JBMICROCONT-4 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-4 > Project: JBoss MicroContainer > Type: Feature Request > Reporter: Ivelin Ivanov > Assignee: Dimitris Andreadis > Priority: Critical > Fix For: JBossMC_1_0_0M2 > > > [Adrian] > Ok, here is the design I have in mind for the new deployer aspects. > This will be part of JBoss Kernel M2 release due by end of January. > Deploying Deployers: > First you have to be able to deploy a deployer. Not an easy task as I imagine > the deployer will have dependencies on other services. The aim will be to > minimize > these dependencies to ease the problem. > Basic Architecture: > The basic architecture of the aspectized deployer is that the deployments > work with a tree of DeploymentInfo objects just like the deployers do now. > There are two major differences: > 1) The deployers do not deal with urls, they deal with VFS contexts > 2) The deployers do not create objects directly, instead they create kernel > MetaData objects and submit them to the kernel for instantiation/configuration > to obtain correct ordering of startup/shutdown > Deployment Mode: > The deployers work in two different modes > 1) The first step is to ask who recognises the VFS context. This is so > the responsible deployer can correctly decide which part of the context > takes part in the classloading and where the metadata is located. > Additionally, this may introduce subdeployments (VFS contexts) if the > deployment allows/contains them. > 2) The second step (the main chain) allows each deployer to augment the > kernel metadata with its own config. > Deployer Ordering: > Since the deployers are working on a metadata model rather than > constructing objects directly, there should be less problem with ordering. > Most ordering will be in the classloader/instantiation/config stage, > the deployer should insert that ordering in the form of dependencies in the > metadata. > The only ordering required of the deployer chain is where one deployer > needs to work on the kernel metadata output of another deployer. > Killing two birds with one stone: > The problems mentioned with the deployer requiring other services > and the first tasks performed by package specific deployers, > i.e. identifying the deployment and its structure > can be easily solved by splitting the deployers into two classes > 1) A structural component that says "I recognise this deployment and this is > how it is structured" > 2) An interpretive component that creates the kernel metadata from the > package. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Reopened: (JBAS-1639) Integrate Critical JBWS bug fixes
[ http://jira.jboss.com/jira/browse/JBAS-1639?page=history ] Thomas Diesler reopened JBAS-1639: -- Final CTS testrun is missing > Integrate Critical JBWS bug fixes > - > > Key: JBAS-1639 > URL: http://jira.jboss.com/jira/browse/JBAS-1639 > Project: JBoss Application Server > Type: Bug > Components: Web Services service > Reporter: Scott M Stark > Assignee: Thomas Diesler > Priority: Critical > Fix For: JBossAS-4.0.2 Final > > > This issue links to the outstanding JBWS project issues that need to be > included into JBAS 4.0.2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1552) JBoss use wrong version of javax.resource.ResourceException class file
[
http://jira.jboss.com/jira/browse/JBAS-1552?page=comments#action_12316835 ]
Scott M Stark commented on JBAS-1552:
-
The change in setting the serialVersionUID is sufficient if there are no serial
fields involved, however if there are, then the serialPersistentFields must be
conditionally set and readObject/writeObject methods added to control the names
of the fields to read/write. For example, the
javax.enterprise.deploy.spi.status.ProgressEvent changes include:
/** @since 4.0.2 */
static final long serialVersionUID;
// Constants -
/**
* These field names match the j2ee 1.4.1 ri version names
*/
private static final ObjectStreamField[] serialPersistentFields;
private static final int STATUS_IDX = 0;
private static final int MODULE_ID_IDX = 1;
static
{
if (SerialVersion.version == SerialVersion.LEGACY)
{
serialVersionUID = 3097551795061550569L;
serialPersistentFields = new ObjectStreamField[] {
/** @serialField statuscode DeploymentStatus current deployment status
*/
new ObjectStreamField("status", DeploymentStatus.class),
/** @serialField targetModuleID TargetModuleID id of the event target
*/
new ObjectStreamField("moduleID", TargetModuleID.class)
};
}
else
{
// j2ee 1.4.1 RI values
serialVersionUID = 7815118532096485937L;
serialPersistentFields = new ObjectStreamField[] {
/** @serialField statuscode DeploymentStatus current deployment status
*/
new ObjectStreamField("statuscode", DeploymentStatus.class),
/** @serialField targetModuleID TargetModuleID id of the event target
*/
new ObjectStreamField("targetModuleID", TargetModuleID.class)
};
}
}
...
private void readObject(ObjectInputStream ois)
throws ClassNotFoundException, IOException
{
ObjectInputStream.GetField fields = ois.readFields();
String name = serialPersistentFields[STATUS_IDX].getName();
this.status = (DeploymentStatus) fields.get(name, null);
name = serialPersistentFields[MODULE_ID_IDX].getName();
this.moduleID = (TargetModuleID) fields.get(name, null);
}
private void writeObject(ObjectOutputStream oos)
throws IOException
{
// Write j2ee 1.4.1 RI field names
ObjectOutputStream.PutField fields = oos.putFields();
String name = serialPersistentFields[STATUS_IDX].getName();
fields.put(name, status);
name = serialPersistentFields[MODULE_ID_IDX].getName();
fields.put(name, moduleID);
oos.writeFields();
}
> JBoss use wrong version of javax.resource.ResourceException class file
> --
>
> Key: JBAS-1552
> URL: http://jira.jboss.com/jira/browse/JBAS-1552
> Project: JBoss Application Server
> Type: Bug
> Components: JCA service
> Versions: JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1
> Environment: All platforms
> Reporter: Manfred Rosenboom
> Fix For: JBossAS-4.0.2 Final
> Attachments: build.properties, build.xml
>
>
> When passing a javax.resource.ResourceException via RMI into the JBoss
> application server we get the following error message:
> ...
> javax.resource.ResourceException; local class incompatible: stream classdesc
> serialVersionUID = 547071213627824490, local class serialVersionUID =
> 4770679801401540475
> at net.fsc.jca.tutorial.SimpleOltpConnectBean.callService(Unknown
> Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
> ...
> When comparing class files, you can see, that JBoss 4.0.x doesn't use the
> same class file as is used in Sun's j2ee.jar (J2EE 1.4 reference
> implementation).
> Both Sun Java System Application Server Platform Edition 8.1 2005Q1 and
> Oracle OC4J 10.1.3 use the same class file, which differes from the JBoss
> version. So I assume, that this is a JBoss related problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
ht
[JBoss-dev] jboss-head build.945 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050411005731Lbuild.945 BUILD COMPLETE - build.945Date of build: 04/11/2005 00:57:31Time to build: 17 minutes 19 secondsLast changed: 04/11/2005 00:51:15Last log entry: Set the serialVersionUID value to that from 4.0.1 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (13)1.13modifiedstarksmjmx/src/main/org/jboss/mx/capability/OptimizedMBeanDispatcher.javaSet the serialVersionUID value to that from 4.0.11.14modifiedstarksmserver/src/main/org/jboss/jms/asf/StdServerSessionPoolFactory.javaSet the serialVersionUID value to that from 4.0.11.24modifiedstarksmaop/src/main/org/jboss/aop/ClassInstanceAdvisor.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.4modifiedstarksmaop/src/main/org/jboss/aop/standalone/Package.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.13modifiedstarksmaop/src/main/org/jboss/aop/joinpoint/ConstructorCalledByMethodInvocation.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.7modifiedstarksmaop/src/main/org/jboss/aop/joinpoint/ConstructorCalledByMethodInvocationWrapper.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.5modifiedstarksmaop/src/main/org/jboss/aop/joinpoint/InvocationBase.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.11modifiedstarksmaop/src/main/org/jboss/aop/joinpoint/MethodCalledByMethodInvocation.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.8modifiedstarksmaop/src/main/org/jboss/aop/joinpoint/MethodCalledByMethodInvocationWrapper.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.8modifiedstarksmaop/src/main/org/jboss/aop/advice/Scope.javaSet the missing serialVersionUIDs to the 4.0.1 version.1.15modifiedstarksmaop/src/main/org/jboss/aop/proxy/ClassProxyTemplate.javaAdd the missing serialVersionUID1.8modifiedstarksmaop/src/main/org/jboss/aop/metadata/SimpleMetaData.javaAdd the missing serialVersionUID1.24modifiedstarksmaop/src/main/org/jboss/aop/joinpoint/MethodInvocation.javaAdd the missing serialVersionUID
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1552) JBoss use wrong version of javax.resource.ResourceException class file
[ http://jira.jboss.com/jira/browse/JBAS-1552?page=history ] Scott M Stark closed JBAS-1552: --- Resolution: Done The SerialVersion class has been moved to the common package under the org.jboss.util.id so that it can be used as the basis for 4.0.1 compatibility by classes outside of the j2ee package. All of the j2ee classes with serialVersionUIDs that are inconsistent with the 1.4.1 ri now have default values that match. To use the version compatible with 4.0.1 set the org.jboss.j2ee.LegacySerialization to any value. > JBoss use wrong version of javax.resource.ResourceException class file > -- > > Key: JBAS-1552 > URL: http://jira.jboss.com/jira/browse/JBAS-1552 > Project: JBoss Application Server > Type: Bug > Components: JCA service > Versions: JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1 > Environment: All platforms > Reporter: Manfred Rosenboom > Fix For: JBossAS-4.0.2 Final > Attachments: build.properties, build.xml > > > When passing a javax.resource.ResourceException via RMI into the JBoss > application server we get the following error message: > ... > javax.resource.ResourceException; local class incompatible: stream classdesc > serialVersionUID = 547071213627824490, local class serialVersionUID = > 4770679801401540475 > at net.fsc.jca.tutorial.SimpleOltpConnectBean.callService(Unknown > Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.jboss.invocation.Invocation.performCall(Invocation.java:345) > ... > When comparing class files, you can see, that JBoss 4.0.x doesn't use the > same class file as is used in Sun's j2ee.jar (J2EE 1.4 reference > implementation). > Both Sun Java System Application Server Platform Edition 8.1 2005Q1 and > Oracle OC4J 10.1.3 use the same class file, which differes from the JBoss > version. So I assume, that this is a JBoss related problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: ws-addressing
Hi Steffen, ws-addressing will be addressed as part of the new JBossWS implementation. There is also a JSR assigned to this topic http://www.jcp.org/en/jsr/detail?id=261 If you like, I could keep you in the feedback loop for this JSR and we can drive together an early implementation of it in jboss-head. To get started, if you have not already, you could familarize yourself with our new implementation in jboss-head. And we can setup a few JIRA tasks arround addressing for you to work on. I don't plan to expend resources in this area on the J2EE-1.4 compatible Axis based stack that is available in jboss-4.0.x Thanks for your interest View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873420#3873420 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873420 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.943 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050410214716Lbuild.943 BUILD COMPLETE - build.943Date of build: 04/10/2005 21:47:16Time to build: 16 minutes 49 secondsLast changed: 04/10/2005 21:12:23Last log entry: Use the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (6)1.4modifiedstarksmcommon/src/main/javax/xml/namespace/QName.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.9modifiedstarksmj2ee/src/main/javax/security/jacc/EJBMethodPermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.5modifiedstarksmj2ee/src/main/javax/security/jacc/EJBRoleRefPermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.8modifiedstarksmj2ee/src/main/javax/security/jacc/WebResourcePermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.6modifiedstarksmj2ee/src/main/javax/security/jacc/WebRoleRefPermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.8modifiedstarksmj2ee/src/main/javax/security/jacc/WebUserDataPermission.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.
[JBoss-dev] [Design of Mail Services] - Re: Minor fixes to HEAD and integration of Nokia branch
I have fixed the Nokia branch integration for simple mail bodies. The problem was Jamesesque nested InputStreams where still being used. Unfortunately stored mail bodies are broken until I merge the parseBody functionality into store. Will do some refactoring to make sure this code is shared. Stored mail bodies are now disabled in the jboss-service.xml file until this is fixed. Will have this fixed for M3. The bodyType not null constraint is probably some type of CMP weirdness as you can not have a int value that is null. However this is also fixed, as the changes I have made to the mailbox/store integration are such that the bodyType field should always be populated. Mike. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873373#3873373 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873373 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - HTTP Status 403 - Access to the requested resource has been
Hello I'm using jboss4.0.1sp1, portal2.0b1,forums2.0b1a on windows, jdk1.4.2 with mysql. once I'm logged in, I can't access to any url starting with http://localhost:8080/portal/auth/ http://localhost:8080/portal/admin/ is working... http://localhost:8080/portal/ too... but not the auth directory... so I can not do anything interesting.. any ideas ?? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873385#3873385 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873385 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (EJBTHREE-134) ManyToOne annotation - fetch attribute ignored
[ http://jira.jboss.com/jira/browse/EJBTHREE-134?page=history ]
Dan Pupaza updated EJBTHREE-134:
Summary: ManyToOne annotation - fetch attribute ignored (was: ManyToOne
annotation ? fetch attribute ignored)
> ManyToOne annotation - fetch attribute ignored
> --
>
> Key: EJBTHREE-134
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-134
> Project: EJB 3.0
> Type: Bug
> Components: EJB3 Extensions
> Versions: Preview 5, Preview 4
> Environment: JBoss sp1, linux, JDK 5.0 Sun
> Reporter: Dan Pupaza
>
>
> I have the following entity bean:
> @javax.persistence.Entity
> @javax.persistence.Table(name = "USER")
> public class User implements Serializable {
>...
>private Customer customer;
>@javax.persistence.ManyToOne(fetch = javax.persistence.FetchType.LAZY)
>@javax.persistence.JoinColumn(name = "customerId")
>public Customer getCustomer() {
> return customer;
>}
> ...
> }
> The fetch attribute is ignored and when the User object is returned the
> customer field is automatically populated (the default option is
> FetchType.EAGER).
> Running the entity2xml target I get the following section corresponding to
> the method defined above:
> access="property"
> entity-name="com.business.persistence.Customer"
> cascade="none">
>
>
> Conform to the definition (Persistence-edr2.pdf, at page 98):
> @Target({METHOD, FIELD}) @Retention(RUNTIME)
> public @interface ManyToOne {
> String targetEntity() default "";
> CascadeType[] cascade() default {};
> FetchType fetch() default EAGER;
> boolean optional() default true;
> }
> ManyToOne accepts the fetch attribute and it could have the FetchType.EAGER
> (default) or FetchType.LAZY value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head-testsuite build.38 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite?log=log20050411035901Lbuild.38 BUILD COMPLETE - build.38Date of build: 04/11/2005 03:59:01Time to build: 134 minutes 34 secondsLast changed: 04/11/2005 00:51:15Last log entry: Set the serialVersionUID value to that from 4.0.1 Unit Tests: (2517) Total Errors and Failures: (175)unknownorg.jboss.test.bank.test.BankEJB20StressTestCasetestAllTx_RWLockorg.jboss.test.cache.stress.EvictionLocalStressTestCasetestConcurrentUpgradeorg.jboss.test.cache.test.local.TxDeadlockUnitTestCasetestMoreThanOneUpgraderorg.jboss.test.cache.test.local.TxDeadlockUnitTestCasetestScopedTransactionorg.jboss.test.classloader.test.ScopedTransactionUnitTestCasetestServerFoundorg.jboss.test.classloader.test.ScopedTransactionUnitTestCasetestEjbCreateorg.jboss.test.cts.test.BmpUnitTestCase(JRMP-Invoker)testEjbFinderorg.jboss.test.cts.test.BmpUnitTestCase(JRMP-Invoker)testEjbRemoveorg.jboss.test.cts.test.BmpUnitTestCase(JRMP-Invoker)testEjbLifeCycleorg.jboss.test.cts.test.BmpUnitTestCase(JRMP-Invoker)testPrimaryKeyObjectIdentityorg.jboss.test.cts.test.BmpUnitTestCase(JRMP-Invoker)testEjbRemoteIForg.jboss.test.cts.test.BmpUnitTestCase(JRMP-Invoker)testEntityHandleorg.jboss.test.cts.test.BmpUnitTestCase(JRMP-Invoker)testSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.BmpUnitTestCase(JRMP-Invoker)testProbeContainerCallbacksorg.jboss.test.cts.test.BmpUnitTestCase(JRMP-Invoker)testContainerObjectsorg.jboss.test.cts.test.BmpUnitTestCase(JRMP-Invoker)testUserTransactionorg.jboss.test.cts.test.BmpUnitTestCase(JRMP-Invoker)testServerFoundorg.jboss.test.cts.test.BmpUnitTestCase(JRMP-Invoker)unknownorg.jboss.test.cts.test.BmpUnitTestCase(JRMP-Invoker)testServerFoundorg.jboss.test.cts.test.BmpUnitTestCasetestServerFoundorg.jboss.test.cts.test.CmpUnitTestCasetestV1org.jboss.test.cts.test.CtsCmp2UnitTestCase(JRMP-Invoker)testV2org.jboss.test.cts.test.CtsCmp2UnitTestCase(JRMP-Invoker)testV1Sarorg.jboss.test.cts.test.CtsCmp2UnitTestCase(JRMP-Invoker)testV2Sarorg.jboss.test.cts.test.CtsCmp2UnitTestCase(JRMP-Invoker)testInterJarCallorg.jboss.test.cts.test.IndependentJarsUnitTestCasetestCallByValueInSameJarorg.jboss.test.cts.test.IndependentJarsUnitTestCasetestServerFoundorg.jboss.test.cts.test.IndependentJarsUnitTestCasetestServerFoundorg.jboss.test.cts.test.LongWaitStatefulSessionUnitTestCasetestServerFoundorg.jboss.test.cts.test.MDBUnitTestCasetestPassivationByTimeLocalorg.jboss.test.cts.test.StatefulSessionLocalUnitTestCasetestServerFoundorg.jboss.test.cts.test.StatefulSessionLocalUnitTestCasetestServerFoundorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestServerFoundorg.jboss.test.cts.test.StatelessSessionStressTestCasetestServerFoundorg.jboss.test.cts.test.StatelessSessionUnitTestCasetestEjbInterceptionorg.jboss.test.hibernate.test.HibernateIntgUnitTestCasetestServerFoundorg.jboss.test.hibernate.test.HibernateIntgUnitTestCasetestSpeedServletorg.jboss.test.jacc.test.WebIntegrationUnitTestCasetestOIL2MutliSessionOneConnectionorg.jboss.test.jbossmq.perf.OIL2InvocationLayerStressTestCasetestOnePoolTxorg.jboss.test.jca.test.PoolingUnitTestCasetestOnePoolTxTrackorg.jboss.test.jca.test.PoolingUnitTestCasetestTrackConnectionByTxorg.jboss.test.jca.test.PoolingUnitTestCasetestTrackConnectionByTxAndCRIorg.jboss.test.jca.test.PoolingUnitTestCasetestCallerIdentityPropagationorg.jboss.test.jca.test.SecurityContextUnitTestCasetestConfiguredIdentityPropagationorg.jboss.test.jca.test.SecurityContextUnitTestCasetestRunAsIdentityPropagationFSorg.jboss.test.jca.test.SecurityContextUnitTestCasetestRunAsIdentityPropagationDSorg.jboss.test.jca.test.SecurityContextUnitTestCasetestXAExceptionToTransactionRolledbackExceptionorg.jboss.test.jca.test.XAExceptionUnitTestCasetestRMERRInOnePCToTransactionRolledbackExceptionorg.jboss.test.jca.test.XAExceptionUnitTestCasetestEnlistInExistingTxorg.jboss.test.jca.test.XATxConnectionManagerUnitTestCasetestEnlistCheckedOutConnectionInNewTxorg.jboss.test.jca.test.XATxConnectionManagerUnitTestCasetestReconnectConnectionHandlesOnNotificationorg.jboss.test.jca.test.XATxConnectionManagerUnitTestCasetestEnlistAfterMarkRollbackorg.jboss.test.jca.test.XATxConnectionManagerUnitTestCasetestCreateSubcontextorg.jboss.test.naming.test.PooledInvokerUnitTestCasetestLookupFailuresorg.jboss.test.naming.test.PooledInvokerUnitTestCasetestHaParitionNameorg.jboss.test.naming.test.SimpleUnitTestCasetestDiscoveryPortorg.jboss.test.naming.test.SimpleUnitTestCasetestOldProxyorg.jboss.test.pooled.test.BeanStressTestCasetestServerFoundorg.jboss.test.securitymgr.test.BMPUnitTestCasetestServerFoundorg.jboss.test.securitymgr.test.CMPUnitTestCasetestServerFoundorg.jboss.test.securitymgr.test.MDBUnitTestCasetestServerFoundorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestServerFoundorg.jboss.test.securitymgr.test.StatelessSessionUnitTestCasetestSpeedServletorg.jboss.test.securitymgr.test
[JBoss-dev] jboss-head build.944 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050410225648Lbuild.944 BUILD COMPLETE - build.944Date of build: 04/10/2005 22:56:48Time to build: 17 minutes 33 secondsLast changed: 04/10/2005 22:51:48Last log entry: Set the serialVersionUID value to that from 4.0.1 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (7)1.2modifiedstarksmcache/src/main/org/jboss/cache/transaction/DummyBaseTransactionManager.javaSet the serialVersionUID value to that from 4.0.11.18modifiedstarksmcache/src/main/org/jboss/cache/transaction/DummyTransactionManager.javaSet the serialVersionUID value to that from 4.0.11.2modifiedstarksmcache/src/main/org/jboss/cache/loader/NodeData.javaSet the serialVersionUID value to that from 4.0.11.72modifiedstarksmcache/src/main/org/jboss/cache/Node.javaSet the serialVersionUID value to that from 4.0.11.4modifiedstarksmj2ee/src/main/javax/xml/rpc/soap/SOAPFaultException.javaUse the SerialVersion constants to choose between the 4.0.2 serialVersionUID value compatible with the 1.4.1 RI or the legacy value of 4.0.1.1.10modifiedstarksmcache/src/main/org/jboss/cache/GlobalTransaction.javaSet the serialVersionUID value to that from 4.0.11.16modifiedstarksmcache/src/main/org/jboss/cache/Fqn.javaSet the serialVersionUID value to that from 4.0.1
[JBoss-dev] [Design of JBoss Portal] - admin cms
My configuration: JBoss AS 4.0.1 Portal 2.0 Beta 1 bin MYsql 4.0.24 I am announced as admin and when I click in the left menu on "create a new file" i get this message in the admin cms box: javax.portlet.PortletException at org.jboss.portal.portlet.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:127) at org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet.doView(AdminCMSPortlet.java:485) at org.jboss.portlet.JBossPortlet.doDispatch(JBossPortlet.java:169) at org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet.render(AdminCMSPortlet.java:1051) at org.jboss.portlet.JBossPortlet.render(JBossPortlet.java:233) at org.jboss.portal.portlet.invocation.DispatcherInterceptor.invokeRequest(DispatcherInterceptor.java:143) at org.jboss.portal.portlet.invocation.DispatcherInterceptor.invoke(DispatcherInterceptor.java:171) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.portlet.invocation.PreferencesInterceptor.invoke(PreferencesInterceptor.java:93) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.server.invocation.component.ContextDispatcherInterceptor$InvokeNextCommand.execute(ContextDispatcherInterceptor.java:94) at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.portal.server.servlet.CommandServlet.doGet(CommandServlet.java:49) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:552) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510) at org.jboss.portal.server.invocation.component.ContextDispatcherInterceptor.invoke(ContextDispatcherInterceptor.java:58) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.core.invocation.AccessControlInterceptor.invoke(AccessControlInterceptor.java:125) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.server.invocation.component.ModeInterceptor.invoke(ModeInterceptor.java:37) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.core.invocation.ConstrainedWindowStateInterceptor.invoke(ConstrainedWindowStateInterceptor.java:51) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.server.invocation.component.ParametersInterceptor.invoke(ParametersInterceptor.java:70) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.server.invocation.component.CacheInterceptor.invoke(CacheInterceptor.java:74) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:242) at org.jboss.portal.server.Component.invoke(Component.java:127) at org.jboss.portal.server.invocation.portal.MainDispatcherInterceptor.invoke(MainDispatcherInterceptor.java:164) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.core.invocation.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:117) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.core.invocation.ViewInterceptor.invoke(ViewInterceptor.java:58) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.core.invocation.UserContextInterceptor.invoke(UserContextInterceptor.java:121) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:242) at org.jboss.portal.server.PortalServer.invoke(PortalServer.java:195) at org.jboss.portal.server.servlet.AbstractMainServlet.invoke(AbstractMainServlet.java:62) at org.jboss
[JBoss-dev] [TODO -- DEVELOPMENT] - Re: CVS repository problems
Well, definitely someone must have done something :) 5 minutes to checkout the Branch_4_0 against the almost 12 hours that took to checkout the head. Whoever you are, thank you my unknown friend :) Gabriele. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873418#3873418 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873418 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-42) HTTP Protocol Proxy
[
http://jira.jboss.com/jira/browse/JBMAIL-42?page=comments#action_12316838 ]
First Last commented on JBMAIL-42:
--
Hmmm... this looks, er, "interesting"...
Have you looked at "Reinventing Email using REST"?
http://www.prescod.net/rest/restmail/
Alternatively, one could simply route regular email protocols through HTTP's
CONNECT, no?
http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.9
> HTTP Protocol Proxy
> ---
>
> Key: JBMAIL-42
> URL: http://jira.jboss.com/jira/browse/JBMAIL-42
> Project: JBoss Mail
> Type: Feature Request
> Components: SMTP, POP
> Reporter: Andrew Oliver
> Assignee: Andrew Oliver
> Priority: Critical
>
> Original Estimate: 2 days
> Remaining: 2 days
>
> Develop an HTTP Proxy which allows one to tunnel HTTP to SMTP or POP.
> Example:
> C: GET /SMTP/Connect HTTP/1.1
> C:
> S: HTTP/1.1 200 OK
> S: Set-Cookie: JSESSIONID=440CF11A9AB5B28872380A333659F4C1; Path=/
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1
> S:
> S: 220 set.superlinksoftware.com SMTP Server (JBMAIL SMTP Server version 0.1)
> ready March 17, 2005 10:00:36 AM EST
> Connection closed (not necessary for 1.1 but demonstrative)
> C: GET /SMTP/EHLO HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C:
> S: HTTP/1.1 200 OK
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1\
> S:
> S: 334 VXNlcm5hbWU6
> C: GET /SMTP/AUTH_LOGIN HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C:
> S: HTTP/1.1 200 OK
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1\
> S:
> S: 334 VXNlcm5hbWU6
> S:
> C: POST /SMTP/AUTH_LOGIN HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C: Content-Type: application/x-www-form-urlencoded
> C:
> C: {encoded user}
> S:
> S: HTTP/1.1 200 OK
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1\
> S:
> S: 334 UGFzc3dvcmQ6
> S:
> C: POST /SMTP/AUTH_LOGIN HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C: Content-Type: application/x-www-form-urlencoded
> C:
> C: {encoded pwd}
> S:
> S: HTTP/1.1 200 OK
> S: Content-Type: text/html;charset=UTF-8
> S: Content-Length: xxx
> S: Date: Thu, 17 Mar 2005 15:22:33 GMT
> S: Server: Apache-Coyote/1.1\
> S:
> S: 200 Authorized
> S:
> C: POST /SMTP/MAIL_FROM HTTP/1.1
> C: Keep-Alive: 300^M
> C: Connection: keep-alive^M
> C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M
> C: Content-Type: application/x-www-form-urlencoded
> C:
> C: <[EMAIL PROTECTED]>
> the intent is the "proxy" will be implemneted as a servlet and connect to
> port 25 on the "real" mail server. All submitted data can be based on HTTP
> POSTS. All requests should be valid HTTP. (so urlencode and do
> parm1=<[EMAIL PROTECTED]> if its not valid to pass just a key with no value)
> The Session ID is the key to the open connection from the proxy. In the
> event the connection from the proxy to real mail server closes then an
> invalid session error should be returned to the client.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: [testing with AOP]
well, i tried many things, but for the moment i can't intercept a constructor
call.
| public class HelloAOP {
| public void callMe () {
| System.out.println("AOP");
| }
| /**
| *
| */
| public static void main (String args[] ) {
| new HelloAOP().callMe();
| }
| }
|
jboss-aop.xml file
|
|
|
|
|
|
|
import org.jboss.aop.advice.Interceptor;
| import org.jboss.aop.joinpoint.Invocation;
|
| public class HelloAOPInterceptor implements Interceptor {
|
| public String getName() {
|
| return "HelloAOPInterceptor";
| }
|
|
| public Object invoke(Invocation invocation) throws Throwable {
| System.out.println("Hello, ");
| return invocation.invokeNext();
| }
| }
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873413#3873413
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873413
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBMICROCONT-6) Virtual Deployment Framework
[ http://jira.jboss.com/jira/browse/JBMICROCONT-6?page=history ] Dimitris Andreadis reassigned JBMICROCONT-6: Assign To: Dimitris Andreadis > Virtual Deployment Framework > > > Key: JBMICROCONT-6 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-6 > Project: JBoss MicroContainer > Type: Task > Components: Deployment > Reporter: Adrian Brock > Assignee: Dimitris Andreadis > Fix For: JBossMC_1_0_0M2 > > > VDF - Virtual Deployment Framework > -- > VDF registry > The VDF registry acts as a helper/registry of the VDF contexts. > Each deployment is made up a top level VDF context > which might contain sub VDF contexts. > It does: > 1) Unpack subdeployments > 2) Download remote deployments > 3) Abstract packed/unpacked > 4) Allow config/registration of url handlers for things like webdav > 5) Supplying "directory" lists, cf (3) and (4) > VDF Context > The VDF context is a replacement for the DeploymentInfo > of current JBoss it holds the following information: > name - a name probably a shorted version of the url > deployer - the identified structural deployer > logicalURL - the url presented to the user > physicalURL - the url where it is really located > parentVDFContext - any parent VDF context (null when top level) > subVDFContexts - any subdeployments > classpath - the urls where classes are located > metainf - the location of any meta data > manifest - any manifest information > classloader - constructed by the classloading deployer > stats/state - e.g. when deployed, the state of the deployment, any errors, etc > There will be a set of utility methods that provide > other access, e.g. get me the metadata url for "ejb-jar.xml" > VDF Context - extensions > Each structural component can extend the VDF context > to add more information > There will also be a "slot" available for each > deployment component to associate some data with the deployment. > Context identification > -- > A top level deployment must have a structure deployer > subdeployments that are not explcitly identifed > (cf Default SubContext processing) that don't have > deployers are ignored. > Explicity identified subdeployments must have a > structure deployer > Default SubContext processing > - > All files in the root of the deployment > are treated as possible subcontexts -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [TODO -- DEVELOPMENT] - CVS repository problems
Hi everybody, pls can someone have a look to Sourceforge repository? It's since friday evening that i'm trying to checkout Jboss source, but i have continously to restart because the checkouts stop with "No space left on device" messages. Besides the checkout, when running, is awfully slow, 40 minutes to download a 2 Meg jar!! Thanks, Gabriele. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873411#3873411 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873411 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss's Web Services Implementation] - ws-addressing
hi folks, I'm working in a project which uses bpel. Therefore I need asynchronous communication between a SessionBean deployed in JBoss and actually the Oracle BPEL Process Manager and the other(server) side. The Oracle Manager use ws-addressing to identify the incoming and outgoing calls to the session bean. But JBoss doesn't support ws-addressing yet. Could someone explain the actual state of the ws-addressing implementation? I've found a entry, that I've voted for, in the JBossWS jira. And could I help on implementing it? As workaround, I've implemented an RPC-Handler, that I put in the HanderRegistry for my webservice client aka SessionBean. Regards Steffen... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873406#3873406 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873406 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
