[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1579) Need to cleanup the serialVersionUIDs for Serializable/Externalizable classes
[ http://jira.jboss.com/jira/browse/JBAS-1579?page=comments#action_12316641 ] Scott M Stark commented on JBAS-1579: - The serialVersionUIDs have been set and I tried running several sets of unit tests from the 4.0.1sp1 build against the current 4.0 branch. The cts, jbossmq, jmx, security tests run fine. The webservice tests have two failures. The first is due to a change in the javax.xml.namespace.QName from 8217399441836960859 to the 4418622981026545151 value found in jdk5: [junit] Tests run: 5, Failures: 0, Errors: 1, Time elapsed: 6.359 sec Cannot unmarshall service ref meta data, cause: java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = 4418622981026545151, local class serialVersionUID = 8217399441836960859 type=javax.naming.NamingExceptionjavax.naming.NamingException: Cannot unmarshall service ref meta data, cause: java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = 4418622981026545151, local class serialVersionUID = 8217399441836960859 at org.jboss.webservice.client.ServiceObjectFactory.getObjectInstance(ServiceObjectFactory.java:114) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:636) at org.jboss.naming.client.java.javaURLContextFactory$EncContextProxy.invoke(javaURLContextFactory.java:120) at $Proxy1.lookup(Unknown Source) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.test.webservice.header.HeaderEndpointTestCase.testImplicitHeaderEndpoint(HeaderEndpointTestCase.java:70) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) The SerialVersion.LEGACY approach could be added support interop with the older id. The second is failure is a lookup failure. [junit] Test org.jboss.test.webservice.header.HeaderEndpointTestCase FAILED [junit] Running org.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCase [junit] Tests run: 32, Failures: 0, Errors: 32, Time elapsed: 8.844 sec javax.naming.NamingException: Could not dereference object [Root exception is java.lang.RuntimeException: Cannot access wsdl from [http://localhost:8080/ws4ee-marshall-doclit?wsdl], http://localhost:8080/ws4ee-marshall-doclit?wsdl] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:647) at org.jboss.naming.client.java.javaURLContextFactory$EncContextProxy.invoke(javaURLContextFactory.java:120) at $Proxy1.lookup(Unknown Source) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCase.setUp(MarshallDocLiteralTestCase.java:72) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: java.lang.RuntimeException: Cannot access wsdl from [http://localhost:8080/ws4ee-marshall-doclit?wsdl], http://localhost:8080/ws4ee-marshall-doclit?wsdl at org.jboss.webservice.WSDLDefinitionFactory$WSDLLocatorImpl.getBaseInputSource(WSDLDefinitionFactory.java:103) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at org.jboss.webservice.WSDLDefinitionFactory.parse(WSDLDefinitionFactory.java:71) at org.jboss.webservice.metadata.ServiceRefMetaData.getWsdlDefinition(ServiceRefMetaData.java:180) at org.jboss.webservice.client.ServiceObjectFactory.getObjectInstance(ServiceObjectFactory.java:145) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:636) ... 20 more Need to cleanup the serialVersionUIDs for Serializable/Externalizable classes - Key: JBAS-1579 URL: http://jira.jboss.com/jira/browse/JBAS-1579 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 Reporter: Scott M Stark Assignee: Scott M Stark Priority: Blocker Fix For: JBossAS-4.0.2 Final Attachments: SerializableHasSerialVersionUIDField.zip, TestResultSample.zip, compatibilityCheckProposedSourceCde.zip I'm seeing incomptibilities between versions that are simply due to
[JBoss-dev] [Design of JBoss Eclipse IDE (dev)] - Run Packaging shortcut reserves much needed } key for Da
In JBoss 1.4.1 the sequence CTRL+ALT+0 (or ALT GR + 0) is reserved as shortcut for the command Run Packaging. This is not very convinient, since the sequence is the only way to get a } character with a Danish (and possibly other) keyboard layout. Quickfix is to remove the shortcut in Window- Preferences-Workbench-Keys. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872501#3872501 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872501 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050404015802 BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build:04/04/2005 01:58:02Time to build:53 minutes 26 secondsLast changed:04/04/2005 01:44:25Last log entry:Backporting 1.2.2 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(73)1.1.8.1modifiedbwang00cache/src/main/org/jboss/cache/transaction/BatchModeTransactionManager.javaBackporting 1.2.21.1.8.1modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyBaseTransactionManager.javaBackporting 1.2.21.19.4.2modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransaction.javaBackporting 1.2.21.12.6.2modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransactionManager.javaBackporting 1.2.21.5.6.2modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyUserTransaction.javaBackporting 1.2.21.4.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/CallbackTest.javaBackporting 1.2.21.1.8.1modifiedbwang00cache/src/main/org/jboss/cache/tests/Client.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/CopyOnWriteArrayTest.javaBackporting 1.2.21.16.2.3modifiedbwang00cache/src/main/org/jboss/cache/tests/FileCacheLoaderTest.javaBackporting 1.2.21.4.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/InterceptorConfigurationTest.javaBackporting 1.2.21.4.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/JDBCCacheLoaderTest.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/LocalDelegatingCacheLoaderTest.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/ReadWriteLockTest.javaBackporting 1.2.21.3.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/ReentrantWriterPreferenceReadWriteLockTest.javaBackporting 1.2.21.2.8.1modifiedbwang00cache/src/main/org/jboss/cache/tests/RestartTest.javaBackporting 1.2.21.3.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/RpcDelegatingCacheLoaderTests.javaBackporting 1.2.21.1.2.2modifiedbwang00cache/src/main/org/jboss/cache/tests/SamplePojo.javaBackporting 1.2.21.2.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/TreeCacheFunctionalTest.javaBackporting 1.2.21.3.2.2modifiedbwang00cache/src/main/org/jboss/cache/tests/BdbjeCacheLoaderTest.javaBackporting 1.2.21.3.2.3modifiedbwang00cache/src/main/org/jboss/cache/tests/BdbjeUnitTestCase.javaBackporting 1.2.21.2.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/CacheLoaderTestsBase.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/lock/BelasLockStrategy.javaBackporting 1.2.21.13.2.2modifiedbwang00cache/src/main/org/jboss/cache/lock/IdentityLock.javaBackporting 1.2.21.2.6.1modifiedbwang00cache/src/main/org/jboss/cache/lock/IsolationLevel.javaBackporting 1.2.21.4.6.2modifiedbwang00cache/src/main/org/jboss/cache/lock/LockMap.javaBackporting 1.2.21.7.2.2modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyFactory.javaBackporting 1.2.21.6.2.2modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyReadUncommitted.javaBackporting 1.2.21.5.2.1modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyRepeatableRead.javaBackporting 1.2.21.3.2.2modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategySerializable.javaBackporting 1.2.21.3.2.3modifiedbwang00cache/src/main/org/jboss/cache/lock/OwnerNotExistedException.javaBackporting 1.2.21.8.2.1modifiedbwang00cache/src/main/org/jboss/cache/lock/ReadWriteLockWithUpgrade.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/lock/SimpleReadWriteLock.javaBackporting 1.2.21.13.2.2modifiedbwang00cache/src/main/org/jboss/cache/loader/bdbje/BdbjeCacheLoader.javaBackporting 1.2.21.23.2.2modifiedbwang00cache/src/main/org/jboss/cache/loader/CacheLoader.javaBackporting 1.2.21.2.2.1modifiedbwang00cache/src/main/org/jboss/cache/loader/DelegatingCacheLoader.javaBackporting 1.2.21.11.4.2modifiedbwang00cache/src/main/org/jboss/cache/loader/FileCacheLoader.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/loader/LocalDelegatingCacheLoader.javaBackporting 1.2.21.1.4.2modifiedbwang00cache/src/main/org/jboss/cache/loader/NodeData.javaBackporting 1.2.21.2.2.1modifiedbwang00cache/src/main/org/jboss/cache/loader/RmiDelegatingCacheLoader.javaBackporting 1.2.21.4.2.1modifiedbwang00cache/src/main/org/jboss/cache/loader/RpcDelegatingCacheLoader.javaBackporting 1.2.21.4.4.2modifiedbwang00cache/src/main/org/jboss/cache/loader/SharedStoreCacheLoader.javaBackporting
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1638) Urgent - JBoss Servlet Container
Urgent - JBoss Servlet Container Key: JBAS-1638 URL: http://jira.jboss.com/jira/browse/JBAS-1638 Project: JBoss Application Server Type: Patch Components: Deployment Service Versions: JBossAS-3.2.7 Final Environment: Platform: Microsoft Windows XP, Application development tool: Oracle JDeveloper 10.1.2 Reporter: wayne hauchee Hi, I am seeking help from Jboss community. Here is my problem: I have an application developed by using Jdeveloper 10g. Most of the pages are ADF UIX and almost all these pages are including a specific JSP file. In this case, servletinclude tag is using to include that JSP file. However, when i deploy my application to Jboss and run it, whenever i open a page which including a JSP file, it encounter the following exception: 2005-03-08 11:14:00,140 ERROR [org.jboss.web.localhost.Engine] ApplicationDispatcher[/TestDeploy-ViewController-context-root] Servlet.service() for servlet jsp threw exception java.lang.IllegalStateException: getOutputStream() has already been called for this response at org.apache.coyote.tomcat5.CoyoteResponse.getWriter(CoyoteResponse.java:599) at org.apache.coyote.tomcat5.CoyoteResponseFacade.getWriter(CoyoteResponseFacade.java:163) at javax.servlet.ServletResponseWrapper.getWriter(ServletResponseWrapper.java:111) at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:122) at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:115) at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:182) at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:115) at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:75) at org.apache.jsp.JTest_jsp._jspService(JTest_jsp.java:63) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) etc From my researches, this may because of the confusing of OutputStream and Writter where UIX using OutputStream and Jboss is using Writter to perform output. Besides, i heard that since Jboss 3.2.4 and onward, Jboss is able to choose/switch using OutputStream or Writter. Am i right? If yes, can you please tell me how to configure the jboss so it use OutputStream rather than Writter? I really need your help. Please help me. Your help is highly appreciated. Thanks in advance. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1609) Backport latest JBossCache (1.2.2)
[ http://jira.jboss.com/jira/browse/JBAS-1609?page=history ] Ben Wang updated JBAS-1609: --- Summary: Backport latest JBossCache (1.2.2) (was: Backport latest JBossCache (1.2.1)) 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-4.0.2RC1, JBossAS-3.2.7 Final Reporter: Ben Wang Assignee: Bela Ban 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1632) clustering unit test failure
[ http://jira.jboss.com/jira/browse/JBAS-1632?page=history ] Ben Wang resolved JBAS-1632: Resolution: Done Fix Version: JBossAS-3.2.8 Final (was: JBossAS-5.0 Alpha) (was: JBossAS-3.2.7 Final) clustering unit test failure Key: JBAS-1632 URL: http://jira.jboss.com/jira/browse/JBAS-1632 Project: JBoss Application Server Type: Bug Components: Clustering Versions: JBossAS-3.2.7 Final, JBossAS-5.0 Alpha, JBossAS-4.0.2RC1 Reporter: Ben Wang Assignee: Ben Wang Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final Attachments: 2005-03-30.17-34.tgz, jboss-cache.jar, jboss-cache.jar Original Estimate: 4 hours Remaining: 4 hours Currently, tests-clustering target has numerous failure. It was because that the jboss-cache.jar is not the latest. In order for the test to success, we will need it. Clebert, you can verify this by copying /tmp/jboss-cache.jar in Atl machine to all/lib directory. This issue is therefore depends on backporting JBossCache release 1.2.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=6595alloc_id=14396op=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-4.0.2RC1, JBossAS-3.2.7 Final Reporter: Ben Wang Assignee: Bela Ban 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-98) Backporting JBossCache 1.2.2 in JBossAS 4.0.x and 3.2.x releases
[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=history ] Ben Wang resolved JBCACHE-98: - Assign To: Luc Texier (was: Ben Wang) Resolution: Done Backporting JBossCache 1.2.2 in JBossAS 4.0.x and 3.2.x releases Key: JBCACHE-98 URL: http://jira.jboss.com/jira/browse/JBCACHE-98 Project: JBoss Cache Type: Support Patch Components: Clustering Versions: 1.2 Environment: should work in any environment Reporter: Luc Texier Assignee: Luc Texier Fix For: 1.2.2 Attachments: jboss-cache.jar Some customers have expressed the wish to take avantages of the optimizations/bug fixes/enhancements being implemented in the latest releases of JBossCache (i.e. 1.2.1 and the upcoming 1.2.2). Therefore, it has been decided to backport JBossCache 1.2.2 to JBossAS 4.0.0 and JBossAS 4.0.1. In addition, there is 3.2.x release. -- 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=6595alloc_id=14396op=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: fetchmail
I won't have any spare time this week, but will have a look asap. Heiko View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872513#3872513 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872513 --- 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=6595alloc_id=14396op=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_12316643 ] Simon Gunzenreiner commented on JBAS-1598: -- A server-server compatibility matrix would also be interesting - for the case where we have a JBoss server beeing client of another JBoss AS. 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 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.327 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050404043856Lbuild.327 BUILD COMPLETE-build.327Date of build:04/04/2005 04:38:56Time to build:42 minutes 6 secondsLast changed:04/04/2005 03:49:07Last log entry:Backporting from 1.2.2 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(78)1.1.2.4modifiedbwang00testsuite/src/main/org/jboss/test/cache/test/local/ConcurrentTransactionalUnitTestCase.javaBackporting from 1.2.21.3.2.5modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyUserTransaction.javaBackporting from 1.2.21.1.10.1modifiedbwang00cache/src/main/org/jboss/cache/transaction/BatchModeTransactionManager.javaBackporting from 1.2.21.1.10.1modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyBaseTransactionManager.javaBackporting from 1.2.21.12.2.7modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransaction.javaBackporting from 1.2.21.10.2.5modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransactionManager.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/NonBlockingWriterLock.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/OwnerNotExistedException.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/ReadWriteLockWithUpgrade.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/SimpleLock.javaBackporting from 1.2.21.1.4.1modifiedbwang00cache/src/main/org/jboss/cache/lock/SimpleReadWriteLock.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/TimeoutException.javaBackporting from 1.2.21.1.2.5modifiedbwang00cache/src/main/org/jboss/cache/lock/UpgradeException.javaBackporting from 1.2.21.3.2.8modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyFactory.javaBackporting from 1.2.21.2.2.4modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyNone.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyReadCommitted.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyReadUncommitted.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyRepeatableRead.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategySerializable.javaBackporting from 1.2.21.1.2.7modifiedbwang00cache/src/main/org/jboss/cache/lock/LockingException.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockMap.javaBackporting from 1.2.21.1.2.4modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategy.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/DeadlockException.javaBackporting from 1.2.21.2.2.7modifiedbwang00cache/src/main/org/jboss/cache/lock/IdentityLock.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/IsolationLevel.javaBackporting from 1.2.21.1.4.1modifiedbwang00cache/src/main/org/jboss/cache/lock/BelasLockStrategy.javaBackporting from 1.2.21.13.4.3modifiedbwang00cache/src/main/org/jboss/cache/loader/bdbje/BdbjeCacheLoader.javaBackporting from 1.2.21.4.2.4modifiedbwang00cache/src/main/org/jboss/cache/loader/SharedStoreCacheLoader.javaBackporting from 1.2.21.1.2.5modifiedbwang00cache/src/main/org/jboss/cache/loader/CacheLoaderAop.javaBackporting from 1.2.21.1.2.3modifiedbwang00cache/src/main/org/jboss/cache/loader/DelegatingCacheLoader.javaBackporting from 1.2.21.11.2.4modifiedbwang00cache/src/main/org/jboss/cache/loader/FileCacheLoader.javaBackporting from 1.2.21.13.4.2modifiedbwang00cache/src/main/org/jboss/cache/loader/JDBCCacheLoader.javaBackporting from 1.2.21.1.4.1modifiedbwang00cache/src/main/org/jboss/cache/loader/LocalDelegatingCacheLoader.javaBackporting from 1.2.21.1.2.3modifiedbwang00cache/src/main/org/jboss/cache/loader/NodeData.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/loader/CacheLoader.javaBackporting from 1.2.21.1.4.4modifiedbwang00cache/src/main/org/jboss/cache/interceptors/Interceptor.javaBackporting from 1.2.21.13.2.2modifiedbwang00cache/src/main/org/jboss/cache/interceptors/LockInterceptor.javaBackporting from 1.2.21.2.2.4modifiedbwang00cache/src/main/org/jboss/cache/interceptors/OrderedSynchronizationHandler.javaBackporting from 1.2.21.6.2.4modifiedbwang00cache/src/main/org/jboss/cache/interceptors/ReplicationInterceptor.javaBackporting from 1.2.21.4.10.1modifiedbwang00cache/src/main/org/jboss/cache/interceptors/UnlockInterceptor.javaBackporting from 1.2.21.5.4.2modifiedbwang00cache/src/main/org/jboss/cache/interceptors/CacheStoreInterceptor.javaBackporting from 1.2.21.1.4.4modifiedbwang00cache/src/main/org/jboss/cache/interceptors/CallInterceptor.javaBackporting from
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP on JBoss 3.2
Hi all, Has this problem been fixed yet ? Does the only problem there is some classes missing or is it deeper than that ? IMHO, AOP should work standalone and be jboss version independent. I know that the project staff should be pretty busy with various things but is it planned and if so, when? Thx and keep up the good work, you are doing a great job ! Jean View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872529#3872529 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872529 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Pls Help!!! HTTPInvoker Does not Work
Hi, i have a problem access my JBOSS thru firewall, i have followed the instruction below but unfortunately no luck! http://www.nemesisit.ro/opendocs/simplearch/simplejboss.html I think i have missed out something as the xml file below. BTW, do i need to specified the firewall ip or the server ip that running JBOSS? If the firewall ip, which port should use? jboss-service.xml ?xml version=1.0 encoding=UTF-8? !DOCTYPE server !-- The HTTP invoker service configration-- http://192.168.0.71:8080/invoker/EJBInvokerServlet http://192.168.0.71:8080/invoker/EJBInvokerHAServlet !-- Expose the Naming service interface via HTTP -- !-- The Naming service we are proxying -- jboss:service=Naming http://192.168.0.71:8080/invoker/JMXInvokerServlet org.jnp.interfaces.Naming !-- Expose the Naming service interface via clustered HTTP. This maps to the ReadOnlyJNDIFactory servlet URL-- jboss:service=Naming http://192.168.0.71:8080/invoker/JMXInvokerServlet org.jnp.interfaces.Naming View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872537#3872537 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872537 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Pls Help!!! HTTPInvoker Does not Work
... View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872538#3872538 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872538 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite?log=log20050404055928 BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build:04/04/2005 05:59:28Time to build:42 minutes 0 secondsLast changed:04/03/2005 16:38:18Last log entry:JBBUILD-17 fixed execant for windows Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(11)1.23modifiedrecampbelltools/etc/jbossbuild/tasks.xmlJBBUILD-17 fixed execant for windows1.394modifiedloubyanskybuild/build.xmlinclude ha connection factory rars into jca examples1.8modifiedloubyanskyconnector/src/resources/dtd/jboss-ds_1_5.dtdadded ha-xa-datasource as a possible child of datasources1.8modifiedstarksmj2ee/src/main/javax/security/jacc/EJBMethodPermission.javaSet the serialVersionUID to the j2ee 1.4.1RI value1.4modifiedstarksmj2ee/src/main/javax/security/jacc/EJBRoleRefPermission.javaSet the serialVersionUID to the j2ee 1.4.1RI value1.7modifiedstarksmj2ee/src/main/javax/security/jacc/WebResourcePermission.javaSet the serialVersionUID to the j2ee 1.4.1RI value1.5modifiedstarksmj2ee/src/main/javax/security/jacc/WebRoleRefPermission.javaSet the serialVersionUID to the j2ee 1.4.1RI value1.7modifiedstarksmj2ee/src/main/javax/security/jacc/WebUserDataPermission.javaSet the serialVersionUID to the j2ee 1.4.1RI value1.5modifiedstarksmj2ee/src/main/javax/resource/spi/work/WorkEvent.javaSet the serialVersionUID to the j2ee 1.4.1RI value1.4modifiedstarksmj2ee/src/main/javax/resource/spi/InvalidPropertyException.javaSet the serialVersionUID to the j2ee 1.4.1RI value1.7modifiedstarksmj2ee/src/main/javax/resource/spi/ConnectionEvent.javaSet the serialVersionUID to the j2ee 1.4.1RI value
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1391) Add support for datasource failover
[ http://jira.jboss.com/jira/browse/JBAS-1391?page=history ] Luc Texier reassigned JBAS-1391: Assign To: Alexey Loubyansky (was: Luc Texier) Add support for datasource failover --- Key: JBAS-1391 URL: http://jira.jboss.com/jira/browse/JBAS-1391 Project: JBoss Application Server Type: Feature Request Components: JCA service Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final Reporter: Scott M Stark Assignee: Alexey Loubyansky Fix For: JBossAS-4.0.2 Final The change to org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory is easier than org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory In LocalManagedConnectionFactory add a property delimiter which when present will parse the connectionURL into multiple urls. In XAManagedConnectionFactory you will also need a property to identify which of the xaProps needs to be parsed for mulitple urls. i.e. you need to identify which property contains the server to contact. In both cases, if createManagedConnection fails for the first url, replace it with the second url, and try again until all urls are exhausted. Of course, you can get clever and remember which urls are currently failing and try the non failing urls first, And also if the db is replicating, you might want it to load balance connections across the urls? Also, this design does not allow for using different properties with different db servers, e.g. user and password might change across the servers. It also doesn't enforce that only connections from one connectionURL (db server) are in the pool at the same time in the event the db is not replicating. If you are going to do this, I would suggest you subclass/replicate the managed connection factories and create separate rars so we can mark them as experimental. Adrian Brock Director of Support Back Office JBoss Inc. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Eclipse IDE (dev)] - download error:reqires plug-in org.eclipse.core.runtime.
while downloading of jbosside plugin through update feature of eclipse i get list of jboss ides but when i click any of them error message comes that JBoss-IDE (1.4.1.e30) requires plug-in org.eclipse.core.runtime. thanxs in advance View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872554#3872554 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872554 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-105) Administrator should be able to edit a user profile
[ http://jira.jboss.com/jira/browse/JBPORTAL-105?page=history ] Julien Viet updated JBPORTAL-105: - Assign To: Julien Viet Environment: Administrator should be able to edit a user profile --- Key: JBPORTAL-105 URL: http://jira.jboss.com/jira/browse/JBPORTAL-105 Project: JBoss Portal Type: Feature Request Components: Portal Core Versions: 2.0 RC, 2.0 Final Reporter: Thomas Heute Assignee: Julien Viet Priority: Minor Fix For: 2.0 RC An administrator should be allowed to change a user profile. The admin could then change the password of someone if needed. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-120) If @LongLived is also @Transient, don't serialize on passivation
[ http://jira.jboss.com/jira/browse/EJBTHREE-120?page=history ] Bill Burke closed EJBTHREE-120: --- Resolution: Done If @LongLived is also @Transient, don't serialize on passivation Key: EJBTHREE-120 URL: http://jira.jboss.com/jira/browse/EJBTHREE-120 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke Fix For: Preview 5 -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-121) Support @EJB injection with no parameters
Support @EJB injection with no parameters - Key: EJBTHREE-121 URL: http://jira.jboss.com/jira/browse/EJBTHREE-121 Project: EJB 3.0 Type: Feature Request Versions: Preview 4 Reporter: Bill Burke Fix For: Preview 5 @EJB requires you to specify the jndiName of the EJB you want to inject. Since JBoss, by default, uses the FQN of the remote/local itnerface (if there is only one interface), then allow it so that @EJB doesn't need any other parameters and infer the JNDI name from either the @Remote or @Local 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-121) Support @EJB injection with no parameters
[ http://jira.jboss.com/jira/browse/EJBTHREE-121?page=history ] Bill Burke closed EJBTHREE-121: --- Resolution: Done Support @EJB injection with no parameters - Key: EJBTHREE-121 URL: http://jira.jboss.com/jira/browse/EJBTHREE-121 Project: EJB 3.0 Type: Feature Request Versions: Preview 4 Reporter: Bill Burke Fix For: Preview 5 @EJB requires you to specify the jndiName of the EJB you want to inject. Since JBoss, by default, uses the FQN of the remote/local itnerface (if there is only one interface), then allow it so that @EJB doesn't need any other parameters and infer the JNDI name from either the @Remote or @Local 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JCA on JBoss] - Re: DataSource failover
Go ahead. Raise some new tasks in JIRA for any improvements you think should be made in future versions (including integrating the HA behaviour with the main RARs). View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872568#3872568 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872568 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-102) make Jboss AOP standalone and jboss version independent
make Jboss AOP standalone and jboss version independent --- Key: JBAOP-102 URL: http://jira.jboss.com/jira/browse/JBAOP-102 Project: JBoss AOP Type: Feature Request Versions: 1.1.1, 1.1, 1.1.2, 2.0, 2.1 Environment: All environements Reporter: jean deruelle make Jboss AOP standalone and jboss version independent -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-103) make Jboss AOP standalone and jboss version independent
make Jboss AOP standalone and jboss version independent --- Key: JBAOP-103 URL: http://jira.jboss.com/jira/browse/JBAOP-103 Project: JBoss AOP Type: Feature Request Versions: 1.1, 2.0, 2.1, 1.1.1, 1.1.2 Environment: All environements Reporter: jean deruelle make Jboss AOP standalone and jboss version independent -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - Re: Cleanup of the common module
Some of this is there so we can write code in JBoss4 and backport to JBoss-3.2 without having to worry about functionality not in java1.3, e.g. NestedRuntimeException View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872569#3872569 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872569 --- 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=6595alloc_id=14396op=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: AspectDeployer is calling method that doesn't exist
Here is the stack trace if start with PER_CLASS or PER_VM (sounds like packaging issue): Unexpected Error in method: public abstract com.crossbeamsys.nms.task.TaskManagerLocal com.crossbeamsys.nms.task.TaskManagerLocalHome.create() throws javax.ejb.CreateException java.lang.NoClassDefFoundError: org/jboss/mx/loading/RepositoryClassLoader at org.jboss.aop.deployment.JBossClassPool.isUnloadedClassLoader(JBossClassPool.java:47) at org.jboss.aop.AspectManager.clearUnregisteredClassLoaders(AspectManager.java:350) at org.jboss.aop.AspectManager.getRegisteredCLs(AspectManager.java:334) at org.jboss.aop.AOPClassPool.getCached(AOPClassPool.java:72) at javassist.ClassPool.checkNotFrozen(ClassPool.java:385) at javassist.ClassPool.makeClass(ClassPool.java:501) at javassist.ClassPool.makeClass(ClassPool.java:486) at org.jboss.aop.advice.PerVmAdvice.generateInterceptor(PerVmAdvice.java:64) at org.jboss.aop.advice.PerClassAdvice.generate(PerClassAdvice.java:26) at org.jboss.aop.advice.AdviceFactory.create(AdviceFactory.java:61) at org.jboss.aop.Advisor.createInterceptorChain(Advisor.java:494) at org.jboss.aop.Advisor.resolveMethodPointcut(Advisor.java:535) at org.jboss.aop.ClassAdvisor.createInterceptorChains(ClassAdvisor.java:454) at org.jboss.aop.ClassAdvisor$1.run(ClassAdvisor.java:237) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.aop.ClassAdvisor.attachClass(ClassAdvisor.java:209) at org.jboss.aop.AspectManager.getAdvisor(AspectManager.java:321) at com.crossbeamsys.nms.security.auth.spi.NMSLoginModule.(NMSLoginModule.java) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:219) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:637) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:610) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:607) at javax.security.auth.login.LoginContext.login(LoginContext.java:534) at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:480) at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:431) at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:246) at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:221) at org.jboss.ejb.plugins.SecurityInterceptor.checkSecurityAssociation(SecurityInterceptor.java:151) at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:74) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:120) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93) at org.jboss.ejb.StatelessSessionContainer.internalInvokeHome(StatelessSessionContainer.java:319) at org.jboss.ejb.Container.invoke(Container.java:729) at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invokeHome(BaseLocalProxyFactory.java:347) at org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:110) at $Proxy72.create(Unknown Source) at com.crossbeamsys.nms.support.ServiceLocator.getTaskManager(ServiceLocator.java:212) at com.crossbeamsys.nms.task.TaskMigrationSchedulable.perform(TaskMigrationSchedulable.java:62) at org.jboss.varia.scheduler.Scheduler$Listener.handleNotification(Scheduler.java:1222) at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138) at $Proxy9.handleNotification(Unknown Source) at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:104) at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:87) at javax.management.timer.Timer.sendNotifications(Timer.java:442) at javax.management.timer.Timer.access$000(Timer.java:31) at javax.management.timer.Timer$RegisteredNotification.doRun(Timer.java:613) at org.jboss.mx.util.SchedulableRunnable.run(SchedulableRunnable.java:164) at org.jboss.mx.util.ThreadPool$Worker.run(ThreadPool.java:240) 10:34:29,773 ERROR [Scheduler$Listener] Handling a Scheduler call failed javax.ejb.EJBException: Unexpected Error: java.lang.NoClassDefFoundError:
[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-98) Backporting JBossCache 1.2.2 in JBossAS 4.0.x and 3.2.x releases
[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=comments#action_12316646 ] Luc Texier commented on JBCACHE-98: --- Ben, You mentioned that this patch would work with 3.2.x releases. Could you confirm? Backporting JBossCache 1.2.2 in JBossAS 4.0.x and 3.2.x releases Key: JBCACHE-98 URL: http://jira.jboss.com/jira/browse/JBCACHE-98 Project: JBoss Cache Type: Support Patch Components: Clustering Versions: 1.2 Environment: should work in any environment Reporter: Luc Texier Assignee: Luc Texier Fix For: 1.2.2 Attachments: jboss-cache.jar Some customers have expressed the wish to take avantages of the optimizations/bug fixes/enhancements being implemented in the latest releases of JBossCache (i.e. 1.2.1 and the upcoming 1.2.2). Therefore, it has been decided to backport JBossCache 1.2.2 to JBossAS 4.0.0 and JBossAS 4.0.1. In addition, there is 3.2.x release. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.471 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050404083257Lbuild.471 BUILD COMPLETE-build.471Date of build:04/04/2005 08:32:57Time to build:92 minutes 7 secondsLast changed:04/04/2005 06:27:20Last log entry:Sync up with HEAD Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(78)1.9.2.64modifiedtdieslertestsuite/imports/test-jars.xmlSync up with HEAD1.2.2.9modifiedtdieslerjaxrpc/build.xmlSync up with HEAD1.1.2.1deletedbwang00cache/src/main/org/jboss/cache/tests/DelegatingCacheLoaderTest.javaBackorting from 1.2.21.1.8.1modifiedbwang00cache/src/main/org/jboss/cache/transaction/BatchModeTransactionManager.javaBackporting 1.2.21.1.8.1modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyBaseTransactionManager.javaBackporting 1.2.21.19.4.2modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransaction.javaBackporting 1.2.21.12.6.2modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransactionManager.javaBackporting 1.2.21.5.6.2modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyUserTransaction.javaBackporting 1.2.21.4.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/CallbackTest.javaBackporting 1.2.21.1.8.1modifiedbwang00cache/src/main/org/jboss/cache/tests/Client.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/CopyOnWriteArrayTest.javaBackporting 1.2.21.16.2.3modifiedbwang00cache/src/main/org/jboss/cache/tests/FileCacheLoaderTest.javaBackporting 1.2.21.4.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/InterceptorConfigurationTest.javaBackporting 1.2.21.4.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/JDBCCacheLoaderTest.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/LocalDelegatingCacheLoaderTest.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/ReadWriteLockTest.javaBackporting 1.2.21.3.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/ReentrantWriterPreferenceReadWriteLockTest.javaBackporting 1.2.21.2.8.1modifiedbwang00cache/src/main/org/jboss/cache/tests/RestartTest.javaBackporting 1.2.21.3.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/RpcDelegatingCacheLoaderTests.javaBackporting 1.2.21.1.2.2modifiedbwang00cache/src/main/org/jboss/cache/tests/SamplePojo.javaBackporting 1.2.21.2.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/TreeCacheFunctionalTest.javaBackporting 1.2.21.3.2.2modifiedbwang00cache/src/main/org/jboss/cache/tests/BdbjeCacheLoaderTest.javaBackporting 1.2.21.3.2.3modifiedbwang00cache/src/main/org/jboss/cache/tests/BdbjeUnitTestCase.javaBackporting 1.2.21.2.2.1modifiedbwang00cache/src/main/org/jboss/cache/tests/CacheLoaderTestsBase.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/lock/BelasLockStrategy.javaBackporting 1.2.21.13.2.2modifiedbwang00cache/src/main/org/jboss/cache/lock/IdentityLock.javaBackporting 1.2.21.2.6.1modifiedbwang00cache/src/main/org/jboss/cache/lock/IsolationLevel.javaBackporting 1.2.21.4.6.2modifiedbwang00cache/src/main/org/jboss/cache/lock/LockMap.javaBackporting 1.2.21.7.2.2modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyFactory.javaBackporting 1.2.21.6.2.2modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyReadUncommitted.javaBackporting 1.2.21.5.2.1modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyRepeatableRead.javaBackporting 1.2.21.3.2.2modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategySerializable.javaBackporting 1.2.21.3.2.3modifiedbwang00cache/src/main/org/jboss/cache/lock/OwnerNotExistedException.javaBackporting 1.2.21.8.2.1modifiedbwang00cache/src/main/org/jboss/cache/lock/ReadWriteLockWithUpgrade.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/lock/SimpleReadWriteLock.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/loader/rmi/RemoteTreeCache.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/loader/rmi/RemoteTreeCacheImpl.javaBackporting 1.2.21.13.2.2modifiedbwang00cache/src/main/org/jboss/cache/loader/bdbje/BdbjeCacheLoader.javaBackporting 1.2.21.23.2.2modifiedbwang00cache/src/main/org/jboss/cache/loader/CacheLoader.javaBackporting 1.2.21.2.2.1modifiedbwang00cache/src/main/org/jboss/cache/loader/DelegatingCacheLoader.javaBackporting 1.2.21.11.4.2modifiedbwang00cache/src/main/org/jboss/cache/loader/FileCacheLoader.javaBackporting 1.2.21.1.2.1modifiedbwang00cache/src/main/org/jboss/cache/loader/LocalDelegatingCacheLoader.javaBackporting 1.2.21.1.4.2modifiedbwang00cache/src/main/org/jboss/cache/loader/NodeData.javaBackporting 1.2.21.2.2.1modifiedbwang00cache/src/main/org/jboss/cache/loader/RmiDelegatingCacheLoader.javaBackporting 1.2.21.4.2.1modifiedbwang00cache/src/main/org/jboss/cache/loader/RpcDelegatingCacheLoader.javaBackporting
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1639) Integrate Critical JBWS bug fixes
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 Assigned to: Thomas Diesler 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1639) Integrate Critical JBWS bug fixes
[ http://jira.jboss.com/jira/browse/JBAS-1639?page=history ] Scott M Stark updated JBAS-1639: Priority: Critical (was: Major) 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: configuration of RMI dynamic classloading
This behavior is handled by JBoss Remoting, which EJB3 implementation uses for the remote calls. In earlier releases of JBoss Remoting, dynamic classloading was enabled, but did not have any security checks. As of JBoss Remoting 1.0.1 final release, dynamic classloading has been turned off, with the exception of internal loading of marshallers/unmarshallers, until security can be added to authenticate the client in some way. This feature should be added to the next JBoss Remoting release (1.2.0), which will be what the following EJB3 release will be using. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872573#3872573 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872573 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-69) Clustered SFSB: load balancing works, failover does not
[ http://jira.jboss.com/jira/browse/EJBTHREE-69?page=history ]
Kabir Khan closed EJBTHREE-69:
--
Resolution: Done
Clustered SFSB: load balancing works, failover does not
---
Key: EJBTHREE-69
URL: http://jira.jboss.com/jira/browse/EJBTHREE-69
Project: EJB 3.0
Type: Bug
Environment: XP
JBoss 5.0.0 alpha
Reporter: Keyur Shah
Assignee: Kabir Khan
Fix For: Preview 5
Ref: http://jboss.com/index.html?module=bbop=viewtopict=60214
Consider this simple example:
[code]
@Stateful
@org.jboss.ejb3.remoting.Clustered
public class SFSBClusterBean implements SFSBCluster, Serializable {
transient String state = null;
String dto = null;
transient boolean modified = false;
public String getState() {
System.out.println(getState);
return state;
}
public void updateState(String newState) {
System.out.println(updateState);
state = newState;
modified = true;
}
@PrePassivate public void passivate() {
System.out.println(passivate);
dto = state;
state = null;
modified = false;
}
@PostActivate public void activate() {
System.out.println(activate);
state = dto;
dto = null;
modified = false;
}
public boolean isModified() {
System.out.println(isModified);
return modified;
}
}
[/code]
I have setup a cluster with 2 nodes... When I run multiple clients, it load
balances well... However, when I shutdown one of the nodes, the clients
accessing that node also die...
I built a similar example in EJB 2.1 and it load balances as well as fails
over correctly.
One difference I noted was that while the EJB 2.1 bean's isModified() was
called (and subsequently, ejbPassivate() if the bean was modified) after
every client method call, the isModified() method is never called for EJB3
(and so by extension neither is the passivate() method called).
--
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=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Pls Help!!! HTTPInvoker Does not Work
Check Chapter 8.8 in the Admin/Developer guide, which instructs on how to use JBoss from behind a firewall (http://www.jboss.org/docs/index#as). Also can reference wiki entry at http://www.jboss.org/wiki/Wiki.jsp?page=UsingJBossBehindAFirewall. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872574#3872574 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872574 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - proposed mods to SARDeployer
The HARDeployer has a lot of duplicated code in common with the SARDeployer. The only real differences between the two being: 1) The service descriptor used to describe the service 2) preparation of the defined mbeans during create, which is something extra the HARDeployer does to inject some values into its MBean. So locally, I've modified the HARDeployer to simply extend a slightly modified version of the SARDeployer. The only differences in the new SARDeployer: 1) a new getRelativeServiceDescriptorName(), overrideable by subclasses, which defines the deployment-relative descriptor to locate; used throughout instead of hard-coded META-INF/jboss-service.xml; 2) a slightly more modularized init() method to allow subclasses to override certain pieces of init-processing; 3) a slightly more modularized create() method to allow subclasses to override stuff here also; 4) changes to log statements that hard-coded SAR Any objections to committing these changes? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872575#3872575 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872575 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: proposed mods to SARDeployer
Common code should be in SubDeployerSupport. I even created a SimpleSubDeployerSupport, that models more how deployment should be done, rather than exposing all the details of SubDeployerSupport. 1) Define your extension - getExtension() 2) Define where your metadata xml exists relative the main deployment - getMetaDataURL() 3) Define your deployment's ObjectName - getObjectName() 4) Define your deployment's class - getDeploymentClass() 5) Define your xml parsing - getObjectModelFactory() The idea is that the deployer creates an MBean for each deployment. Then the SimpleSubDeployer will create the MBeans of type getDeploymentClass() with the name getObjectName() for each deployment and handle the lifecycle for you, including injecting the parsed xml document's javabean equivalent into the deployment The RAR deployer is currently the only one that uses it. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872579#3872579 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872579 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1640) JACC web application validation fails when Tomcat Connector is secure
JACC web application validation fails when Tomcat Connector is secure
-
Key: JBAS-1640
URL: http://jira.jboss.com/jira/browse/JBAS-1640
Project: JBoss Application Server
Type: Bug
Components: Web (Tomcat) service, Security
Versions: JBossAS-4.0.2RC1
Environment: -
Reporter: Roland R?z
The JACC validation for web applications fails when JBoss runs with a secured
Tomcat Connector (Attribute secure=true).
The problem appears because the user-data-constraint of a web.xml is not used
during the JACC Permission creation.
1. JACC Permission Creation (during deployment):
In class TomcatDeployer.createPermissions(), line 933
The creation of a WebResourcePermission uses a httpMethods[] (eg. GET,POST
,)which stores only the methods without the required security constraint.
Therefore the PermissionMaps (excluded-, unchecked-, rolePermissions) in
ContextPolicy will look something like this:
(javax.security.jacc.WebResourcePermission /html/allowed_to_a/* GET)
2. Request Creation (during runtime):
The method WebResourcePermission.requestActions() adds the security state of
tomcat connector attribute secure to the requested http method:
In method WebResourcePermission.requestActions()
String actions = request.getMethod() + (request.isSecure() ? :CONFIDENTIAL :
);
So the HttpMethodsString looks like:
HttpMethodsString=GET:CONFIDENTIAL
3. Request Validation:
In ContextPolicy.implies() fails the validation because the entries are
different:
Eg:
(javax.security.jacc.WebResourcePermission /html/allowed_to_a/* GET)
(javax.security.jacc.WebResourcePermission /html/allowed_to_a/*
GET:CONFIDENTIAL)
How to reproduce this situation:
- Enable JACC in the server.xml of tomcat:
(http://www.jboss.org/wiki/Wiki.jsp?page=JACC)
- Add the attribute secure=true to the Connector in the server.xml:
eg:Connector port=8080 address=${jboss.bind.address} secure=true
- secure a resource in a web.xml
= the secured resource can never be accessed.
Regards,
Andrea
--
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_ide95alloc_id396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: proposed mods to SARDeployer
So you and I did a bunch of the same stuff ;) So really I was extending SARDeployer for 1) its XML parsing; since it is the same logic needed for the HAR; 2) its deployment lifecycle logic; since, aside from the two deviations mentioned previously, it is exactly the same needed for the HAR One significant difference is that HAR and SAR can create multiple MBeans per deployment. The HAR descriptor, for example, might define both a Hibernate-MBean and a TreeCache-MBean. Certainly this distinction goes away after the ability is added to allow multiple deployers to be able to interact with a single deployment; but it is currently a limitation here. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872581#3872581 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872581 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Deleted: (JBPM-105) one task per task-node
[ http://jira.jboss.com/jira/browse/JBPM-105?page=history ] Tom Baeyens deleted JBPM-105: - one task per task-node -- Key: JBPM-105 URL: http://jira.jboss.com/jira/browse/JBPM-105 Project: JBoss jBPM Type: Task Reporter: Tom Baeyens Assignee: Tom Baeyens Only allow one task per task node. now, more then one task per task-node is supported which results in 2 different concurrency mechanisms. by allowing only one task per task-node, 2 problems are solved : * users only have to know one concurrency mechansim (forks and joins) * specify a transitionName when completing a task makes sense 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBPM-93) add the identity component
[ http://jira.jboss.com/jira/browse/JBPM-93?page=history ] Tom Baeyens closed JBPM-93: --- Resolution: Done add the identity component -- Key: JBPM-93 URL: http://jira.jboss.com/jira/browse/JBPM-93 Project: JBoss jBPM Type: Task Components: Core Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Priority: Minor Fix For: jBPM 3.0 alpha 3 as an extension, a simple organisation component should be created. the initial ideas are in module jbpm.organisation in the jbpm cvs. the idea is that a single interface is specified for accessing the user-roles relation. then we can create different implementations for different storage technologies e.g. a relational database, an LDAP system, the tomcat-users.xml, the jboss users-roles property files, ... then assignment handlers and authorization extensions could be written against this simple 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-81) document jpdl schema of exception handlers
[ http://jira.jboss.com/jira/browse/JBPM-81?page=history ] Tom Baeyens updated JBPM-81: Summary: document jpdl schema of exception handlers (was: document jpdl schema for exception handlers) document jpdl schema of exception handlers -- Key: JBPM-81 URL: http://jira.jboss.com/jira/browse/JBPM-81 Project: JBoss jBPM Type: Task Components: Core Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 3.0 alpha 3 summary says it all. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBPM-81) document jpdl schema of exception handlers
[ http://jira.jboss.com/jira/browse/JBPM-81?page=history ] Tom Baeyens closed JBPM-81: --- Resolution: Done document jpdl schema of exception handlers -- Key: JBPM-81 URL: http://jira.jboss.com/jira/browse/JBPM-81 Project: JBoss jBPM Type: Task Components: Core Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 3.0 alpha 3 summary says it all. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: proposed mods to SARDeployer
Just to complete my thought ;) Given the limitation I mentioned regarding the potential of multiple heterogeneous-typed mbeans, would your suggestion be to extract the pertinent lifecycle logic out of SARDeployer into a new deployer support class (say, HeterogeneousSubDeployerSupport) which provides that same kind of lifecycle simplification to this deployment scenario and having both SARDeployer and HARDeployer extend that new deployer support? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872584#3872584 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872584 --- 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=6595alloc_id=14396op=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: reaonsably confused about setup...
Try changing the jndi-name in the DS to PortalDS. ?xml version=1.0 encoding=UTF-8? | datasources | local-tx-datasource | jndi-namePortalDS/jndi-name | connection-urljdbc:mysql://localhost:3306/jbossportal/connection-url | driver-classorg.gjt.mm.mysql.Driver/driver-class | user-nameroot/user-name | password/password | /local-tx-datasource | /datasources View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872585#3872585 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872585 --- 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=6595alloc_id=14396op=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: 2 Problems: 1. can't get into the AdminCMSPortlet 2. c
I believe you are the first to try installing portal on MSSQL. Where di you run the setup.ddl and setup.sql from? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872586#3872586 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872586 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JCA on JBoss] - Re: DataSource failover
I see ha-xa-datasource on the wiki but not in the jboss_ds DTD. Is it valid? If it is, the DTD should be updated so I can generate the schema diagrams for the book. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872587#3872587 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872587 --- 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=6595alloc_id=14396op=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: Can I use JBoss AS 3.25 with JBoss Portal 2.0?
I have not tested this. Try deploying on /default, but we depend on jgroup, jboss cache, and remoting jars. I believe not all of them are present in the standard 3.2.5 install. *I could be wrong here. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872589#3872589 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872589 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPTL-17) Theme API
[ http://jira.jboss.com/jira/browse/JBPTL-17?page=history ] Julien Viet updated JBPTL-17: - Assign To: Martin Holzner (was: Julien Viet) Description: Define a theme API The Portal Container will procude during an invocation a result which is a set of page fragment. These page fragment will all inherit the same class but will have various custom properties (for instance a Portlet window has a PortletMode). We need to find the right architecture for theming here. A fragment should be rendered on screen by a general mechanism and let room for customized renderers. Also we need a way to package and deploy new theme (ThemeDeployer ?) was: Define a theme API The Portal Container will procude during an invocation a result which is a set of page fragment. These page fragment will all inherit the same class but will have various custom properties (for instance a Portlet window has a PortletMode). We need to find the right architecture for theming here. A fragment should be rendered on screen by a general mechanism and let room for customized renderers. Also we need a way to package and deploy new theme (ThemeDeployer ?) Environment: Theme API - Key: JBPTL-17 URL: http://jira.jboss.com/jira/browse/JBPTL-17 Project: JBoss Portal Type: Feature Request Reporter: Julien Viet Assignee: Martin Holzner Fix For: 2.0 RC Define a theme API The Portal Container will procude during an invocation a result which is a set of page fragment. These page fragment will all inherit the same class but will have various custom properties (for instance a Portlet window has a PortletMode). We need to find the right architecture for theming here. A fragment should be rendered on screen by a general mechanism and let room for customized renderers. Also we need a way to package and deploy new theme (ThemeDeployer ?) -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-225) Window state strategy pluggable
[ http://jira.jboss.com/jira/browse/JBPORTAL-225?page=history ] Julien Viet updated JBPORTAL-225: - Assign To: Martin Holzner (was: Julien Viet) Window state strategy pluggable --- Key: JBPORTAL-225 URL: http://jira.jboss.com/jira/browse/JBPORTAL-225 Project: JBoss Portal Type: Task Components: Portal Core Versions: 2.0 RC, 2.0 Final Reporter: Julien Viet Assignee: Martin Holzner Fix For: 2.0 RC -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JCA on JBoss] - Re: DataSource failover
??? I think you are looking at the wrong dtd? http://cvs.sourceforge.net/viewcvs.py/jboss/jbosscx/src/resources/dtd/jboss-ds_1_5.dtd?r1=1.1.2.4r2=1.1.2.5 View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872592#3872592 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872592 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBPORTAL-105) Administrator should be able to edit a user profile
[ http://jira.jboss.com/jira/browse/JBPORTAL-105?page=history ] Julien Viet closed JBPORTAL-105: Resolution: Duplicate Issue Administrator should be able to edit a user profile --- Key: JBPORTAL-105 URL: http://jira.jboss.com/jira/browse/JBPORTAL-105 Project: JBoss Portal Type: Feature Request Components: Portal Core Versions: 2.0 RC, 2.0 Final Reporter: Thomas Heute Assignee: Julien Viet Priority: Minor Fix For: 2.0 RC An administrator should be allowed to change a user profile. The admin could then change the password of someone if needed. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-69) Update profile of someone else
[ http://jira.jboss.com/jira/browse/JBPORTAL-69?page=history ] Julien Viet updated JBPORTAL-69: Assign To: Julien Viet (was: Roy Russo) Version: 2.0 RC (was: 2.0 Alpha) Update profile of someone else -- Key: JBPORTAL-69 URL: http://jira.jboss.com/jira/browse/JBPORTAL-69 Project: JBoss Portal Type: Sub-task Components: Portal Core Versions: 2.0 RC Reporter: Thomas Heute Assignee: Julien Viet Fix For: 2.0 RC For administrators only -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-187) JBoss Portal setup the database and files on deploy
[ http://jira.jboss.com/jira/browse/JBPORTAL-187?page=history ] Julien Viet updated JBPORTAL-187: - Assign To: Polina Alber JBoss Portal setup the database and files on deploy --- Key: JBPORTAL-187 URL: http://jira.jboss.com/jira/browse/JBPORTAL-187 Project: JBoss Portal Type: Task Versions: 2.0 RC Reporter: Julien Viet Assignee: Polina Alber Fix For: 2.0 RC Original Estimate: 4 days Remaining: 4 days - it is an optional service (setup.sar) that is nested within portal-core.sar, the goal is to put it in the default configuration. But as this config is exploded, it can be easily removed from it. For instance once it is setup, it can be removed. Another example are people that prefer to do a manual installation and thus does not need it. - the setup.sar contains all the basic portal state, which means : tables SQL statements, insert SQL statements and also the files for Slide. - that setup.sar must be configurable and must not be tied in particular to the module core as it will be used also for other modules (like forums). Therefore it must be done as a separate module in the build (like jboss-portal-2.0/core). - the setup of the state must be done on the service startService() phase. - the insertion of data must be done only if no data already exists. For instance if the portal data directory already exists, no file must be copied. Or if the tables already exist, the sql insertions must be bypassed - the setup.sar must define an XML file format that will describe the data to setup : SQL statements and files to copy. Perhaps it could be possible to execute ANT build files from with the start, since ANT already has a lot of tasks. This is an option to explore imho - the test cases must be written -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: proposed mods to SARDeployer
Can't you just extend SimpleSubDeployerSupport to have multiple mbeans deployed? i.e. create a MultipleSubDeployerSupport or whatever you want to call it. Alternatively (and probably better), you could do it the other way around and make a SingleSubDeployerSupport that specialises the multiple deployment version with just one MBean deployed. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872593#3872593 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872593 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-6) Develop Fetchmail MBean
[ http://jira.jboss.com/jira/browse/JBMAIL-6?page=comments#action_12316651 ] Andrew Oliver commented on JBMAIL-6: I remember that dots are escaped like so .. == 1 dot However they only have to be escaped IIRC if they are preceeded and anticeeded by a CR. That being said headers are seperated from the body by a blank line (nothing more) Hope that helps. Develop Fetchmail MBean --- Key: JBMAIL-6 URL: http://jira.jboss.com/jira/browse/JBMAIL-6 Project: JBoss Mail Type: Feature Request Components: POP Versions: 1.0-M3 Reporter: Andrew Oliver Assignee: Heiko W. Rupp Priority: Critical Fix For: 1.0-M3 Original Estimate: 2 days Remaining: 2 days Develop an MBean which: 1. retrieves messages from an external POP server and stores them in the database. 2. Writes a schedule to a database using Hibernate containing: a. how often to check the external POP server (seconds, hours, days, day of week, dates) b. What user/password to use 3. has checkAvailable operation which checks to see if there are mails available for the user on the external server 4. has retrieveMails operation which retrieves the mails and stores them in the datbase. 5. has addFetch(user, password, ScheduleSpecification spec) which adds a fetch schedule to the database and creates a timer for runtime 6. onStart sets up timers and polls the external POP servers as expected 7. supports unencrypted POP, encrypted POP, TLS POP 8. has provision for IMAP later (operation/attribute names are demonstrative only) -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: proposed mods to SARDeployer
I don't understand what you mean by anonymous wrote : | specialises the multiple deployment version with just one MBean deployed | By one MBean deployed are you refering to the deployer MBean? Or the MBean deployed by the deployer? ;) I assume you mean that we create a SARDeployment and HARDeployment similiar to the RARDeployment used in the RARDeployer to plug into the getDeploymentClass()? But the getDeploymentClass() piece is a bit limiting here I think, when you look at it from the perspective of SAR/HAR (unless I am missing something, which is always a possibility ;) The reason is that the JCA deployment is failry close-ended, whereas the SAR/HAR is open-ended. What I mean by this is that a JCA adapter is always going to have the same fixed number of subordinate collaboration MBeans (i.e., MCF-MBean, CM, etc). Fixed both in terms of the number as well as the type of each. That's not the case for the SAR/HAR stuff though. So from what I saw in the RARDeployment class, it takes on the configuration face for the JCA deployment for the end-user; they interact with it, and then it interacts with the various back-end pieces. That would be pretty difficult to acheive with SAR/HAR deployments. Essentially, all the code I want is already defined in SARDeployer. The reason is that a HAR is really just a simple service archive except that the HibernateMBean additionally needs to know about the deployment url (so that it can locate the hibernate mappings). If y'all want that I take that SARDeployer code and move it into another base class intended for the SAR/HAR use-cases, then I'm fine with that. The other option is that SARDeployer could just take on that role. Either way... View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872598#3872598 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872598 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBREM-95) Need to clean up lib directory
Need to clean up lib directory -- Key: JBREM-95 URL: http://jira.jboss.com/jira/browse/JBREM-95 Project: JBoss Remoting Type: Sub-task Components: general Versions: 1.2.0 beta Reporter: Tom Elrod Assigned to: Tom Elrod Fix For: 1.2.0 beta Need to clean up lib directory so only using exactly what is needed by remoting. Also need to make sure using the exact versions for jboss binaries for release so no conflict when used within jboss as. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: proposed mods to SARDeployer
I'm speaking in the abstract because I don't fully understand what you are trying to achieve. I am saying don't extend SARDeployer. Just basic OO principles tells me that the HAR deployer is NOT a SAR deployer. public class X extends Y means X isA Y in OO speak. I don't see why you need to touch SARDeployer. It is something that works now. In fact, the whole problem is a bit moot since we are changing the way deployers works anyway for JBoss5. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872600#3872600 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872600 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMAIL-52) Let (outgoing) mail be delivered through a smarthost
[ http://jira.jboss.com/jira/browse/JBMAIL-52?page=comments#action_12316659 ] Andrew Oliver commented on JBMAIL-52: - We should target this for M4. I think this should be part of the SMTPSenderMBean and the DNS stuff should be decoupled. I think the DNS stuff should handle it however and you should be able to add MX records to it (for the purpose of relaying) including patterns. Thus I could say relay.foo.com handles [EMAIL PROTECTED] and relaynet.foo.com handles [EMAIL PROTECTED] Eventually I actually want to add DNS as a protocol ;-) (Part of my world domination strategy) Let (outgoing) mail be delivered through a smarthost Key: JBMAIL-52 URL: http://jira.jboss.com/jira/browse/JBMAIL-52 Project: JBoss Mail Type: Feature Request Components: SMTP Versions: 1.0-M2 Reporter: Heiko W. Rupp Assignee: Andrew Oliver Original Estimate: 1 day Remaining: 1 day In some scenarios, mail should not be deliered directly to the MX, but only be sent to a manually configured smarthost. This smarthost will then take care about mail delivery. This requirement is common in intranets, where branch offices don't deliver (outgoing) mail on their own, but sent mail to the main office, that also provdes content scanning etc. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: proposed mods to SARDeployer
anonymous wrote : | I am saying don't extend SARDeployer. Just basic OO principles tells me | that the HAR deployer is NOT a SAR deployer. | | public class X extends Y | means X isA Y in OO speak. | I don't disagree. But basic software maintence philosphy tells me to not write a class that is 340 lines of code where approximately 300 is duplicated somewhere else ;) I need to also make changes in JB4. Is the deployer redesign going to be backported? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872601#3872601 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872601 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: proposed mods to SARDeployer
On my proposal. I am saying:
1) SubDeployerSupport is too generic (deliberatly) since it allows things like
Tomcat deployments to be processed through it.
2) Ideally, deployments should be:
archive/file - MBeans/JavaBeans
- means many-to-one
3) I wrote SimpleSubDeployerSupport that does
archive/file -- MBean
-- means one-to-one
So my proposal is to have something like:
StandardSubDeployerSupport extends SubDeployerSupport
SimpleSubDeployerSupport extends StandardSubDeployerSupport
StandardSubDeployerSupport would allow multiple mbeans per deployment
something like
String[] getDeploymentClasses()
etc.
and SimpleSubDeployerSupport would just be a specialzation one for deployment
String[] getDeploymentClasses()
{
return new String[] { getDeploymentClass() };
}
and even that depends upon whether you think such a simplication is useful.
e.g. you may want something closer to the wire in the standard deployer?
ServiceMBean[] getMBeans()
But like I say, there isn't much point spending too much time on figuring out
an ideal abstraction when there will be a much better deployer framework in
JBoss5.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3872602#3872602
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872602
---
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=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss internal QA (Test Suite)] - Re: distributed test framework
It seems that JBoss Benchmarking (Clebert's work) is what we need. I would check it out from CVS and look at it. Is there a functional spec document around? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872603#3872603 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872603 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: proposed mods to SARDeployer
anonymous wrote : | I don't disagree. But basic software maintence philosphy tells me to not write a class that is 340 lines of code where approximately 300 is duplicated somewhere else ;) | Agreed, but also 300 lines across 4 or five classes isn't that big an issue when they hardly ever change. It becomes an issue when you want to add cross cutting behaviour on the fly (hence the need for the new framework). anonymous wrote : | I need to also make changes in JB4. Is the deployer redesign going to be backported? Not that I'm aware of, although Dimitris was doing an experiment with the deployment aspects working as XMBean interceptors? http://www.jboss.org/index.html?module=bbop=viewtopict=57296 View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872604#3872604 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872604 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JCA on JBoss] - Re: DataSource failover
Woops. My CVS was a couple days out of date. I should have updated before posting just to be sure. My mistake - sorry for the confusion. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872607#3872607 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872607 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-27) build for cache
[ http://jira.jboss.com/jira/browse/JBBUILD-27?page=history ] Ryan Campbell updated JBBUILD-27: - Description: Environment: Fix Version: milestone-2 (was: milestone-1) delaying until milestone 2 until I know what to do with this module. build for cache --- Key: JBBUILD-27 URL: http://jira.jboss.com/jira/browse/JBBUILD-27 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assignee: Ryan Campbell Fix For: milestone-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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-32) build for deployment
[ http://jira.jboss.com/jira/browse/JBBUILD-32?page=history ] Ryan Campbell updated JBBUILD-32: - Description: Environment: Fix Version: milestone-1 (was: milestone-2) Moving to milestone-1 to compensate for cache build being delayed. build for deployment Key: JBBUILD-32 URL: http://jira.jboss.com/jira/browse/JBBUILD-32 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assignee: Ryan Campbell Fix For: milestone-1 -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: proposed mods to SARDeployer
I think the experiment overall worked (although Scott had some reservations about it so it's in HEAD but not 4.x). It was about providing the EJBDeployer (in fact, it should work with all other deployers) the ability to instantiate and tear-down security domains, in the presence of a META-INF/login-config.xml. In fact, a lot of the the functionlity was already there, you write a JMX interceptor and apply it to an XMBean, so you need (a) to XMBean-ize the target deployer, (not a big deal) and (b) make sure your deployer is always accessed through the MBeanServer and not using a direct reference (some subdeployers do that). So I added the ability to attach/detach this interceptor dynamically to an XMBean. As a convenience I've made org.jboss.deployment.SubDeployerInterceptor that can be subclassed to demonstrate this. If the HARDeployer can be thought-of as an add-on (aspect, interceptor, whatever) to SARDeployer or other subdeployers then this will probably work. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872620#3872620 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872620 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBREM-96) Get stand alone build working
Get stand alone build working - Key: JBREM-96 URL: http://jira.jboss.com/jira/browse/JBREM-96 Project: JBoss Remoting Type: Sub-task Reporter: Tom Elrod Assigned to: Tom Elrod -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Pls Help!!! HTTPInvoker Does not Work
Hi, Tom. Thks for reply. The external_host_name is refer to the firewall ip or the server ip that running jboss? -Djava.rmi.server.hostname=external_host_name -Djava.rmi.server.useLocalHostname=false View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872623#3872623 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872623 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-122) AOP hooks for exception handling for EntityManager methods
AOP hooks for exception handling for EntityManager methods -- Key: EJBTHREE-122 URL: http://jira.jboss.com/jira/browse/EJBTHREE-122 Project: EJB 3.0 Type: Feature Request Versions: Preview 4 Reporter: Bill Burke Priority: Optional Fix For: EJB 3.0 Beta 1 -- 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=6595alloc_id=14396op=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)] - EAR hotdeploy
Hi, I'm getting java.lang.ExceptionInInitializerError's every time I redeploy a J2EE application that is using jboss-aop. If I simply restart Jboss it all works perfectly. I'm using Jboss 4.0.1sp1 with jdk5 and jboss-aop-1.1 Are there any known issues about AOP and EAR hotdeploy? I haven't see it posted anywhere... thank's java.lang.ExceptionInInitializerError at br.com.tsi.aion.rh.web.CadastroEmpregado.salvar(CadastroEmpregado.jav a:103) at br.com.tsi.aion.rh.web.CadastroEmpregado.doPost(CadastroEmpregado.jav a:57) at br.com.tsi.aion.rh.web.CadastroEmpregado.doGet(CadastroEmpregado.java :41) 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(Appl icationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:157) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi lter.java:75) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV alve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv eContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(Standard ContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV alve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv eContext.java:104) at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrinc ipalValve.java:66) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv eContext.java:102) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit yAssociationValve.java:150) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv eContext.java:102) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv e.java:54) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv eContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j ava:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv eContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j ava:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv eContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal ve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv eContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16 0) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java :799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce ssConnection(Http11Protocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java :577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP ool.java:683) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.RuntimeException: java.lang.NullPointerException at org.jboss.aop.advice.AdviceFactory.create(AdviceFactory.java:54) at org.jboss.aop.Advisor.createInterceptorChain(Advisor.java:494) at org.jboss.aop.Advisor.resolveMethodPointcut(Advisor.java:535) at org.jboss.aop.ClassAdvisor.createInterceptorChains(ClassAdvisor.java: 454) at org.jboss.aop.ClassAdvisor$1.run(ClassAdvisor.java:237) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.aop.ClassAdvisor.attachClass(ClassAdvisor.java:209) at org.jboss.aop.AspectManager.getAdvisor(AspectManager.java:321) at br.com.tsi.aion.rh.Empregado.(Empregado.java) ... 38 more Caused by: java.lang.NullPointerException at org.jboss.mx.loading.RepositoryClassLoader.addURL(RepositoryClassLoad er.java:647) at org.jboss.aop.deployment.JBossClassPoolFactory.createTempDir(JBossCla ssPoolFactory.java:66) at org.jboss.aop.deployment.JBossClassPoolFactory.create(JBossClassPoolF
[JBoss-dev] [Design of JBoss Portal] - Re: JBoss portal development status
I've searched through the jira link above and was wondering about tasks related to completing Nukes functionality (News, Sections, etc). Are these tasks hidden in there somewhere. What can be done to help? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872633#3872633 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872633 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-104) EAR redeployment problem
EAR redeployment problem Key: JBAOP-104 URL: http://jira.jboss.com/jira/browse/JBAOP-104 Project: JBoss AOP Type: Bug Versions: 1.1.1 Reporter: Bill Burke -- 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=6595alloc_id=14396op=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: EAR hotdeploy
This seems like a bug. I've created a JIRA task for it here: http://jira.jboss.com/jira/browse/JBAOP-104 It would help tremendously if you could create a small testcase that reproduces this? Kabir and I are currently swamped and anything that would help us move faster on this would greatly enhanve the chances of this bug getting resolved. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872634#3872634 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872634 --- 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=6595alloc_id=14396op=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: JBoss portal development status
you are welcome to participate, which one do you want ? news, download ? I'll create it for you ? (btw I think that news module already exists) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872635#3872635 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872635 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPORTAL-231) Bundled Release
Bundled Release --- Key: JBPORTAL-231 URL: http://jira.jboss.com/jira/browse/JBPORTAL-231 Project: JBoss Portal Type: Feature Request Reporter: Roy Russo Assigned to: Julien Viet Offer a bundled version of JBoss Portal with JBoss AS 4.0.1 running on HSQLDB. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBPORTAL-231) Bundled Release
[ http://jira.jboss.com/jira/browse/JBPORTAL-231?page=history ] Roy Russo reassigned JBPORTAL-231: -- Assign To: Roy Russo (was: Julien Viet) Bundled Release --- Key: JBPORTAL-231 URL: http://jira.jboss.com/jira/browse/JBPORTAL-231 Project: JBoss Portal Type: Feature Request Reporter: Roy Russo Assignee: Roy Russo Offer a bundled version of JBoss Portal with JBoss AS 4.0.1 running on HSQLDB. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBPORTAL-69) Update profile of someone else
[ http://jira.jboss.com/jira/browse/JBPORTAL-69?page=history ] Julien Viet resolved JBPORTAL-69: - Resolution: Done Update profile of someone else -- Key: JBPORTAL-69 URL: http://jira.jboss.com/jira/browse/JBPORTAL-69 Project: JBoss Portal Type: Sub-task Components: Portal Core Versions: 2.0 RC Reporter: Thomas Heute Assignee: Julien Viet Fix For: 2.0 RC For administrators only -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBPTL-11) Parser framework
[ http://jira.jboss.com/jira/browse/JBPTL-11?page=history ] Julien Viet resolved JBPTL-11: -- Resolution: Done Parser framework Key: JBPTL-11 URL: http://jira.jboss.com/jira/browse/JBPTL-11 Project: JBoss Portal Type: Task Reporter: Julien Viet Assignee: Julien Viet Fix For: 2.0 RC Port the parser framework from nukes -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPTL-14) Add new parsers
[ http://jira.jboss.com/jira/browse/JBPTL-14?page=history ] Julien Viet updated JBPTL-14: - Environment: Security Level: (was: Public) Fix Version: (was: 2.0 RC) Add new parsers --- Key: JBPTL-14 URL: http://jira.jboss.com/jira/browse/JBPTL-14 Project: JBoss Portal Type: Sub-task Reporter: Julien Viet Assignee: Julien Viet Priority: Optional Add new parsers to the stack like full HTML or wiki -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-207) Dynamic deployment and configuration of components
[ http://jira.jboss.com/jira/browse/JBPORTAL-207?page=history ] Julien Viet updated JBPORTAL-207: - Version: (was: 2.0 RC) Fix Version: (was: 2.0 RC) Dynamic deployment and configuration of components -- Key: JBPORTAL-207 URL: http://jira.jboss.com/jira/browse/JBPORTAL-207 Project: JBoss Portal Type: Feature Request Reporter: Julien Viet Assignee: Julien Viet Original Estimate: 2 weeks Remaining: 2 weeks -- 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=6595alloc_id=14396op=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)] - ClosedInterceptor design approach
Hi All- I've been looking at implementing the ClosedInterceptor functionality for the JMS Facade, and wanted to run my design approach by you to make sure I'm on the right track. I've had a look at how this was implemented in JBoss 4 messaging, and I believe there is a fair amount in the actually ClosedInterceptor logic that could be re-used :) (In particular the valve logic itself.) However, I believe the code that maintains the tree of containers (JBoss 4 messaging terminology ??), so that close and closing() can be cascaded down the nodes of the tree (i.e. close on a connection causes a session to close that causes a producer to close...), needs to be done somewhat differently. In JBoss 4, the hierarchy is held in the InvocationHandler classes (Container class) and the parent child relation-ship is set-up when the Container class is constructed). This is fine since in JBoss 4 the client side interceptor stack is created on the client side. In the new JBoss messaging, the client side interceptor stack is created on the server side and sent back to the client so the approach of maintaining the hierarchy on the server side won't seem to work (and also is more stuff to shift across the network), since each call to createSessionDelegate would end up with it's own copy of it's parent JMSInvocationHandler being sent back. A solution to this seems to be to maintain the hierarchy on the client side. This can be done by intercepting calls to createSessionDelegate(), createProducer() etc. and adding the child to the parent's invocation handler, so each invocation handler maintains a set of it's child invocation handlers. Assuming this sounds the right thing to do, then the question arises of which interceptor to use to actually maintain the hierarchy. Choices seem to be: 1. Just use the ClosedInterceptor itself. 2. Create a new client side interceptor 3. FactoryInterceptor? So far I've assumed 1. but not sure if that's the right approach. I'd much like to hear what you think here. Another question I have involves the MessageProducer and MessageConsumer close() method. Is there any need to do anything on the server side for this method. I.e. is there any server side clean-up to do? I notice currently the ProducerDelegate does not have a close() method, but not sure if this will be implemented in the future. If there is nothing to do, this could simplify the ClosedInterceptor since you'd just be traversing from Connection to Session. So, basically I have, so far, implemented everything as mentioned above, and have knocked some tests together and everything seems to be working ok, so if the approach seems reasonable I should be able to get this finished by tomorrow hopefully. Sorry for boring you with the long mail ;) -Tim Almost forgot... A couple of misc. questions: Do people at JBoss maintain copyright over their code? If so, I believe I would need to ask permission of the authors if I were to re-use any code from R4.0? I'm not really sure of the procedure here. Eclipse coding template. Is there an eclipse coding template (or something like that) available for the JBoss coding style? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872637#3872637 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872637 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-58) Cleanup of Common Module
Cleanup of Common Module Key: JBBUILD-58 URL: http://jira.jboss.com/jira/browse/JBBUILD-58 Project: JBoss Build System Type: Task Reporter: Ryan Campbell Assigned to: Ryan Campbell From Scott: There is a lot of unused utility classes along with obsolete functionality that is duplicating the jdk 1.4 behavior that I would like to get cleaned up jboss4.0+. Examples of such classes are: org.jboss.util.Coercible and all of org.jboss.util.coerce org.jboss.util.DirectoryBuilder org.jboss.util.MethodHashing org.jboss.util.Mu* org.jboss.util.collection.* much of this is now duplicate functionality org.jboss.net.sockets.RMI* is an unused experiement in multiplexing org.jboss.net.sockets.Timeout* is now obsolete functionality supported by the JDK sockets org.jboss.util.property.* is mostly unused org.jboss.util.stream.* org.jboss.xml.* should be incorported into the org.jboss.xml.* jbossxb framework at some point Before proceeding, modify this description with the precise list of classes to remove and get approval from affected developers. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - Re: Cleanup of the common module
I've created a task to track this: http://jira.jboss.com/jira/browse/JBBUILD-58 We can at least see if these classes are being used and remove them if not. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872651#3872651 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872651 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss internal QA (Test Suite)] - Re: distributed test framework
I don't think we have a functional spec, but the roadmap is in the JIRA Benchmarking project: http://jira.jboss.com/jira/browse/JBBENCH?report=com.atlassian.jira.plugin.system.project:roadmap-panel At the bottom - MicroBenchmark Framework 1.0 View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872652#3872652 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872652 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - Standalone JBossCache module
I am going to convert JBossCache from a source build to a binary depedency in jboss-4.0 using the old build. I'm looking for any missing steps and guidance on when this should be done with regards to the 4.0.2 release. I know how to add to thirdparty, but I want to make sure I understand the impact of moving an artifact from cache/output to thirdparty. Steps required: - import the jboss-cache.jar into /thirdparty/jboss/cache - add the definitions to CVSROOT/modules - and thidparty/licesnses - remove jboss.cache.lib from modules.ent and add it to libraries.ent - modify build/build.xml to reflect new location of jboss-cache.jar - run the testsuite With regards to the timing, is this a prerequisite to the 4.0.2 release? If not, can we do this after 4.0.2 Final is released? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872654#3872654 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872654 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1611) ClientMonitorIntecepor
[ http://jira.jboss.com/jira/browse/JBAS-1611?page=history ]
Adrian Brock closed JBAS-1611:
--
Resolution: Duplicate Issue
Is the search function broken or something?
ClientMonitorIntecepor
--
Key: JBAS-1611
URL: http://jira.jboss.com/jira/browse/JBAS-1611
Project: JBoss Application Server
Type: Bug
Reporter: Alex
If client used HTTPConnection (HTTPConnectionFactory) to subscribe to the
nondurable topic and client don't receive messages during ClientTimeout time
ClientMonitorIntecepor (if it running) close connection for it, because http
connection is stateles and client don't ping server even I set PingPeriod for
http connection to some value difference from 0, and
getClientStats(dc).lastUsed value udate only if client receive any message
from the server.
In the source code of HTTPILService the PingPeriod value set to the 0,
and client never send ping message to the server.
It's HTTPILService.startService source:
public void startService() throws Exception
{
super.startService();
this.pingPeriod = 0;// We don't do pings.
...
--
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=6595alloc_id=14396op=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.102 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050404185443Lbuild.102 BUILD COMPLETE-build.102Date of build:04/04/2005 18:54:43Time to build:74 minutes 38 secondsLast changed:04/04/2005 03:49:07Last log entry:Backporting from 1.2.2 Unit Tests: (1967) Total Errors and Failures: (8)testNoClassDefFoundErrororg.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:(78)1.1.2.4modifiedbwang00testsuite/src/main/org/jboss/test/cache/test/local/ConcurrentTransactionalUnitTestCase.javaBackporting from 1.2.21.3.2.5modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyUserTransaction.javaBackporting from 1.2.21.1.10.1modifiedbwang00cache/src/main/org/jboss/cache/transaction/BatchModeTransactionManager.javaBackporting from 1.2.21.1.10.1modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyBaseTransactionManager.javaBackporting from 1.2.21.12.2.7modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransaction.javaBackporting from 1.2.21.10.2.5modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransactionManager.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/NonBlockingWriterLock.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/OwnerNotExistedException.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/ReadWriteLockWithUpgrade.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/SimpleLock.javaBackporting from 1.2.21.1.4.1modifiedbwang00cache/src/main/org/jboss/cache/lock/SimpleReadWriteLock.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/TimeoutException.javaBackporting from 1.2.21.1.2.5modifiedbwang00cache/src/main/org/jboss/cache/lock/UpgradeException.javaBackporting from 1.2.21.3.2.8modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyFactory.javaBackporting from 1.2.21.2.2.4modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyNone.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyReadCommitted.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyReadUncommitted.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyRepeatableRead.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategySerializable.javaBackporting from 1.2.21.1.2.7modifiedbwang00cache/src/main/org/jboss/cache/lock/LockingException.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockMap.javaBackporting from 1.2.21.1.2.4modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategy.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/DeadlockException.javaBackporting from 1.2.21.2.2.7modifiedbwang00cache/src/main/org/jboss/cache/lock/IdentityLock.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/IsolationLevel.javaBackporting from 1.2.21.1.4.1modifiedbwang00cache/src/main/org/jboss/cache/lock/BelasLockStrategy.javaBackporting from 1.2.21.13.4.3modifiedbwang00cache/src/main/org/jboss/cache/loader/bdbje/BdbjeCacheLoader.javaBackporting from 1.2.21.4.2.4modifiedbwang00cache/src/main/org/jboss/cache/loader/SharedStoreCacheLoader.javaBackporting from 1.2.21.1.2.5modifiedbwang00cache/src/main/org/jboss/cache/loader/CacheLoaderAop.javaBackporting from 1.2.21.1.2.3modifiedbwang00cache/src/main/org/jboss/cache/loader/DelegatingCacheLoader.javaBackporting from 1.2.21.11.2.4modifiedbwang00cache/src/main/org/jboss/cache/loader/FileCacheLoader.javaBackporting from 1.2.21.13.4.2modifiedbwang00cache/src/main/org/jboss/cache/loader/JDBCCacheLoader.javaBackporting from 1.2.21.1.4.1modifiedbwang00cache/src/main/org/jboss/cache/loader/LocalDelegatingCacheLoader.javaBackporting from 1.2.21.1.2.3modifiedbwang00cache/src/main/org/jboss/cache/loader/NodeData.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/loader/CacheLoader.javaBackporting from 1.2.21.1.4.4modifiedbwang00cache/src/main/org/jboss/cache/interceptors/Interceptor.javaBackporting from
[JBoss-dev] [Design of JBoss Portal] - Re: jsp compilation errors
Sit tight. I'm working on a bundled version as we discussed today. I'll post here and email you personally, when its available. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872660#3872660 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872660 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1642) Benchmarking http session replication under different settings
Benchmarking http session replication under different settings -- Key: JBAS-1642 URL: http://jira.jboss.com/jira/browse/JBAS-1642 Project: JBoss Application Server Type: Task Components: Clustering Reporter: Ben Wang Assigned to: Clebert Suconic Fix For: JBossAS-5.0 Alpha Need to benchmark http session replication under different settings: 1. Replication granularity: SESSION, ATTRIBUTE, and FIELD 2. Sync and Async cache mode 3. Snapshot manager: instant and interval -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1641) Load testing http session replication between different settings
Load testing http session replication between different settings Key: JBAS-1641 URL: http://jira.jboss.com/jira/browse/JBAS-1641 Project: JBoss Application Server Type: Task Components: Clustering Reporter: Ben Wang Assigned to: Clebert Suconic Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final We will need load test http session replication using different config settings. For example, 1. Syncrhonous vs. asychronous cache mode 2. Replicationg ranularity: SESSION, ATTRIBUTE, and FIELD 3. Snapshot manager: instant and periodic -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-1176717 ] UsersRolesLoginModule has limited configurations in sar
Bugs item #1176717, was opened at 2005-04-04 19:43 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1176717group_id=22866 Category: JBossServer Group: v4.0 Status: Open Resolution: None Priority: 5 Submitted By: rwag (rollin368) Assigned to: Nobody/Anonymous (nobody) Summary: UsersRolesLoginModule has limited configurations in sar Initial Comment: I have an EJB application, headless without the web, that uses UsersRolesLoginModule for JAAS security. Originally I defined my application-policy in the server's conf/login-config.xml. I defined the usersProperties and rolesProperties that were contained in the EJB. Later on I decided to move that configuration to a sar file. I found that the sar's META-INF/login-config.xml did not appear to accept my usersProperties or rolesProperties configurations. As a result I had to comment out those module-options and use the default roles.properties and users.properties files. It is a relatively minor bug but took time. Also I started to wonder how much can be defined in a sar versus the server-config. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1176717group_id=22866 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1643) UsersRolesLoginModule has limited configurations in sar
UsersRolesLoginModule has limited configurations in sar --- Key: JBAS-1643 URL: http://jira.jboss.com/jira/browse/JBAS-1643 Project: JBoss Application Server Type: Bug Components: EJBs, Security Versions: JBossAS-4.0.1 SP1 Environment: Suse Linux 9.1 Reporter: Rollin Crittendon Priority: Minor I have an EJB application, headless without the web, that uses UsersRolesLoginModule for JAAS security. Originally I defined my application-policy in the server's conf/login-config.xml. I defined the usersProperties and rolesProperties that were contained in the EJB. Later on I decided to move that configuration to a sar file. I found that the sar's META-INF/login-config.xml did not appear to accept my usersProperties or rolesProperties configurations. As a result I had to comment out those module-options and use the default roles.properties and users.properties files. It is a relatively minor bug but took time. Also I started to wonder how much can be defined in a sar versus the server-config. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - JBoss Portal and Google
I will begin this thread with a post from our CTO, regarding the spidering of JBoss Portal portlet content by google: anonymous wrote : It seems that the target parameters should map well to a hierarchical | tree structure described by a uri from the perspective of the client. | Looking at figure 4-2 from the 1.0 portlet spec, there are the following | elements that could the associated uri elements: | | porlet app deployment root context = /app-context | porlet page = /pageN | portletA = /portletA | portletB = /portletB | portletC = /portletC | portletD = /portletD | | gives the following target uris without state information: | | /app-context/pageN/portletA | /app-context/pageN/portletB | /app-context/pageN/portletC | /app-context/pageN/portletD | | Issues: | | - These logical uris should be meaningful if they are to be interpreted | by people using web tools so there would have to be a mapping, for | example: | /app-context/dashboard/todo-list | /app-context/dashboard/rss-news | /app-context/dashboard/calendar | /app-context/dashboard/forum-most-active-list | | - The jboss portal supports some type of multi-page notion. This could | be incorporated into the logical page element of the uri using a syntax | like pageN.M. This could complicate the parsing of the uri and it | mapping to a meaningful name. | | - The PortletURL window states and mode certainly complicate this. Its | not clear that state information should be encoded into the uri. I think | that the default state of a normal, visible portlet should have a | canonical representation that requires no parameters. I'm not familiar | with the restriction web analyzers, google, etc. place on parameters. | There could be a compressed parameter mode that compressed all state | information into a single parameter or single letter aliases for the | parameter names and enumeration values. | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872662#3872662 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872662 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss internal QA (Test Suite)] - Re: distributed test framework
I was looking to dtf when I was creating the framework. Actually the config for JGroups I'm using was literally copied from Tom's work. :-). And I'll be copying/using anything cool he has created. :-) But the only problem is that the framework also needs lots of improvements, and I was not being able to invest time as I'm focusing in Specj and HP right now. (And we have now Intel coming to Specj also). I have validated the idea with some people and everybody thinks the idea for the framework is valid. I've used decorators for submitting load, so you won't need to code loops and Thread synchronizations. All you would have to do is to decorate your testcase with a decorator and you have the loader done. I'm considering a decorator for synchronizing multiple clients as well. I have the Roadmap for the framework at: http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=truepid=12310062fixfor=12310214 What about you guys contribute to the framework? As you guys might need to develop something, maybe adding effort in something generic is better. The code is committed as jboss-benchmark in our public cvs. Clebert View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3872667#3872667 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872667 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1635) DEPLOY TO JBOSS - SERVLETINCLUDE GENERATES AN EXCEPTION
[ http://jira.jboss.com/jira/browse/JBAS-1635?page=history ] Adrian Brock updated JBAS-1635: --- Component: Web (Tomcat) service (was: Deployment Service) DEPLOY TO JBOSS - SERVLETINCLUDE GENERATES AN EXCEPTION --- Key: JBAS-1635 URL: http://jira.jboss.com/jira/browse/JBAS-1635 Project: JBoss Application Server Type: Bug Components: Web (Tomcat) service Versions: JBossAS-3.2.7 Final Environment: Platform: Microsoft Windows XP, Application development tool: Oracle JDeveloper 10.1.2 Reporter: wayne hauchee Original Estimate: 2 weeks Remaining: 2 weeks My project is developed by using the following tools: - JDeveloper 10g version 10.1.2, - ADF UIX framework , - Oracle 9.2.0.1 (Database) I have created a JSP file which need to be included in most of the UIX files in order to perform some desired task. It works properly in oracle JDeveloper. However, at the end i would like to deploy my project to JBoss-3.2.7RC1 which is supported by JDeveloper. Everything go fine but whenever i open a page which including a JSP file (An UIX including a JSP file using ServletInclude tag), it encountered an exception as below: 2005-03-08 11:14:00,140 ERROR [org.jboss.web.localhost.Engine] ApplicationDispatcher[/TestDeploy-ViewController-context-root] Servlet.service() for servlet jsp threw exception java.lang.IllegalStateException: getOutputStream() has already been called for this response at org.apache.coyote.tomcat5.CoyoteResponse.getWriter(CoyoteResponse.java:599) at org.apache.coyote.tomcat5.CoyoteResponseFacade.getWriter(CoyoteResponseFacade.java:163) at javax.servlet.ServletResponseWrapper.getWriter(ServletResponseWrapper.java:111) at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:122) at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:115) at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:182) at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:115) at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:75) at org.apache.jsp.JTest_jsp._jspService(JTest_jsp.java:63) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) 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:590) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510) at oracle.cabo.ui.laf.base.RequestDispatcherIncluder.includeByPath(Unknown Source) at oracle.cabo.ui.laf.base.ServletIncludeRenderer.renderContent(Unknown Source) at oracle.cabo.ui.BaseRenderer.render(Unknown Source) at oracle.cabo.ui.BaseUINode.render(Unknown Source) at oracle.cabo.ui.BaseUINode.render(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderChild(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderIndexedChild(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderIndexedChild(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderContent(Unknown Source) at oracle.cabo.ui.laf.base.xhtml.DocumentRenderer.renderContent(Unknown Source) at oracle.cabo.ui.BaseRenderer.render(Unknown Source) at oracle.cabo.ui.laf.base.xhtml.DocumentRenderer.render(Unknown Source) at oracle.cabo.ui.BaseUINode.render(Unknown Source) at oracle.cabo.ui.BaseUINode.render(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderChild(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderIndexedChild(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderIndexedChild(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderContent(Unknown Source) at oracle.cabo.ui.laf.base.DataScopeRenderer.renderContent(Unknown Source) at oracle.cabo.ui.BaseRenderer.render(Unknown Source) at oracle.cabo.ui.BaseUINode.render(Unknown Source) at oracle.cabo.ui.BaseUINode.render(Unknown Source) at oracle.cabo.servlet.ui.UINodePageRenderer.renderPage(Unknown
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1635) DEPLOY TO JBOSS - SERVLETINCLUDE GENERATES AN EXCEPTION
[ http://jira.jboss.com/jira/browse/JBAS-1635?page=history ] Adrian Brock closed JBAS-1635: -- Resolution: Rejected You aren't going to get any response to a bug report against an old release candidate. Anyway this is an old invalid bug report: http://issues.apache.org/bugzilla/show_bug.cgi?id=1771 that was discussed again on the tomcat dev list only last week: http://www.mail-archive.com/tomcat-dev%40jakarta.apache.org/msg70202.html DEPLOY TO JBOSS - SERVLETINCLUDE GENERATES AN EXCEPTION --- Key: JBAS-1635 URL: http://jira.jboss.com/jira/browse/JBAS-1635 Project: JBoss Application Server Type: Bug Components: Web (Tomcat) service Versions: JBossAS-3.2.7 Final Environment: Platform: Microsoft Windows XP, Application development tool: Oracle JDeveloper 10.1.2 Reporter: wayne hauchee Original Estimate: 2 weeks Remaining: 2 weeks My project is developed by using the following tools: - JDeveloper 10g version 10.1.2, - ADF UIX framework , - Oracle 9.2.0.1 (Database) I have created a JSP file which need to be included in most of the UIX files in order to perform some desired task. It works properly in oracle JDeveloper. However, at the end i would like to deploy my project to JBoss-3.2.7RC1 which is supported by JDeveloper. Everything go fine but whenever i open a page which including a JSP file (An UIX including a JSP file using ServletInclude tag), it encountered an exception as below: 2005-03-08 11:14:00,140 ERROR [org.jboss.web.localhost.Engine] ApplicationDispatcher[/TestDeploy-ViewController-context-root] Servlet.service() for servlet jsp threw exception java.lang.IllegalStateException: getOutputStream() has already been called for this response at org.apache.coyote.tomcat5.CoyoteResponse.getWriter(CoyoteResponse.java:599) at org.apache.coyote.tomcat5.CoyoteResponseFacade.getWriter(CoyoteResponseFacade.java:163) at javax.servlet.ServletResponseWrapper.getWriter(ServletResponseWrapper.java:111) at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:122) at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:115) at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:182) at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:115) at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:75) at org.apache.jsp.JTest_jsp._jspService(JTest_jsp.java:63) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) 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:590) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510) at oracle.cabo.ui.laf.base.RequestDispatcherIncluder.includeByPath(Unknown Source) at oracle.cabo.ui.laf.base.ServletIncludeRenderer.renderContent(Unknown Source) at oracle.cabo.ui.BaseRenderer.render(Unknown Source) at oracle.cabo.ui.BaseUINode.render(Unknown Source) at oracle.cabo.ui.BaseUINode.render(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderChild(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderIndexedChild(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderIndexedChild(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderContent(Unknown Source) at oracle.cabo.ui.laf.base.xhtml.DocumentRenderer.renderContent(Unknown Source) at oracle.cabo.ui.BaseRenderer.render(Unknown Source) at oracle.cabo.ui.laf.base.xhtml.DocumentRenderer.render(Unknown Source) at oracle.cabo.ui.BaseUINode.render(Unknown Source) at oracle.cabo.ui.BaseUINode.render(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderChild(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderIndexedChild(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderIndexedChild(Unknown Source) at oracle.cabo.ui.BaseRenderer.renderContent(Unknown Source) at
[JBoss-dev] jboss-3.2-jdk-matrix Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050404204018 BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jboss-head.xml:76: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile_jdk131.log in Build Artifacts for details. JAVA_HOME=/opt/jdk1.3.1_13/Date of build:04/04/2005 20:40:18Time to build:57 minutes 40 secondsLast changed:04/04/2005 03:49:07Last log entry:Backporting from 1.2.2 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(78)1.1.2.4modifiedbwang00testsuite/src/main/org/jboss/test/cache/test/local/ConcurrentTransactionalUnitTestCase.javaBackporting from 1.2.21.3.2.5modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyUserTransaction.javaBackporting from 1.2.21.1.10.1modifiedbwang00cache/src/main/org/jboss/cache/transaction/BatchModeTransactionManager.javaBackporting from 1.2.21.1.10.1modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyBaseTransactionManager.javaBackporting from 1.2.21.12.2.7modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransaction.javaBackporting from 1.2.21.10.2.5modifiedbwang00cache/src/main/org/jboss/cache/transaction/DummyTransactionManager.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/NonBlockingWriterLock.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/OwnerNotExistedException.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/ReadWriteLockWithUpgrade.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/SimpleLock.javaBackporting from 1.2.21.1.4.1modifiedbwang00cache/src/main/org/jboss/cache/lock/SimpleReadWriteLock.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/TimeoutException.javaBackporting from 1.2.21.1.2.5modifiedbwang00cache/src/main/org/jboss/cache/lock/UpgradeException.javaBackporting from 1.2.21.3.2.8modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyFactory.javaBackporting from 1.2.21.2.2.4modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyNone.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyReadCommitted.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyReadUncommitted.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategyRepeatableRead.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategySerializable.javaBackporting from 1.2.21.1.2.7modifiedbwang00cache/src/main/org/jboss/cache/lock/LockingException.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/LockMap.javaBackporting from 1.2.21.1.2.4modifiedbwang00cache/src/main/org/jboss/cache/lock/LockStrategy.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/DeadlockException.javaBackporting from 1.2.21.2.2.7modifiedbwang00cache/src/main/org/jboss/cache/lock/IdentityLock.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/lock/IsolationLevel.javaBackporting from 1.2.21.1.4.1modifiedbwang00cache/src/main/org/jboss/cache/lock/BelasLockStrategy.javaBackporting from 1.2.21.13.4.3modifiedbwang00cache/src/main/org/jboss/cache/loader/bdbje/BdbjeCacheLoader.javaBackporting from 1.2.21.4.2.4modifiedbwang00cache/src/main/org/jboss/cache/loader/SharedStoreCacheLoader.javaBackporting from 1.2.21.1.2.5modifiedbwang00cache/src/main/org/jboss/cache/loader/CacheLoaderAop.javaBackporting from 1.2.21.1.2.3modifiedbwang00cache/src/main/org/jboss/cache/loader/DelegatingCacheLoader.javaBackporting from 1.2.21.11.2.4modifiedbwang00cache/src/main/org/jboss/cache/loader/FileCacheLoader.javaBackporting from 1.2.21.13.4.2modifiedbwang00cache/src/main/org/jboss/cache/loader/JDBCCacheLoader.javaBackporting from 1.2.21.1.4.1modifiedbwang00cache/src/main/org/jboss/cache/loader/LocalDelegatingCacheLoader.javaBackporting from 1.2.21.1.2.3modifiedbwang00cache/src/main/org/jboss/cache/loader/NodeData.javaBackporting from 1.2.21.1.2.6modifiedbwang00cache/src/main/org/jboss/cache/loader/CacheLoader.javaBackporting from 1.2.21.1.4.4modifiedbwang00cache/src/main/org/jboss/cache/interceptors/Interceptor.javaBackporting from 1.2.21.13.2.2modifiedbwang00cache/src/main/org/jboss/cache/interceptors/LockInterceptor.javaBackporting from 1.2.21.2.2.4modifiedbwang00cache/src/main/org/jboss/cache/interceptors/OrderedSynchronizationHandler.javaBackporting from 1.2.21.6.2.4modifiedbwang00cache/src/main/org/jboss/cache/interceptors/ReplicationInterceptor.javaBackporting from
[JBoss-dev] [JBoss JIRA] Reopened: (JBAS-1609) Backport latest JBossCache (1.2.2)
[ http://jira.jboss.com/jira/browse/JBAS-1609?page=history ] Adrian Brock reopened JBAS-1609: Assign To: Ben Wang (was: Bela Ban) This doesn't compile with jdk1.3 in branch 3.2.x compile-classes: [mkdir] Created dir: /scratch/cruisecontrol/checkout/jboss-3.2/cache/output/classes [javac] Compiling 88 source files to /scratch/cruisecontrol/checkout/jboss-3.2/cache/output/classes /scratch/cruisecontrol/checkout/jboss-3.2/cache/src/main/org/jboss/cache/TreeCache.java:1513: cannot resolve symbol symbol : class LinkedHashSet location: class org.jboss.cache.TreeCache return retval != null? new LinkedHashSet(retval) : null; ^ /scratch/cruisecontrol/checkout/jboss-3.2/cache/src/main/org/jboss/cache/TreeCache.java:1962: cannot resolve symbol symbol : class LinkedHashSet location: class org.jboss.cache.TreeCache return new LinkedHashSet(m.keySet()); ^ /scratch/cruisecontrol/checkout/jboss-3.2/cache/src/main/org/jboss/cache/Node.java:498: cannot resolve symbol symbol : class LinkedHashSet location: class org.jboss.cache.Node Set retval=new LinkedHashSet(); ^ 3 errors BUILD FAILED /scratch/cruisecontrol/checkout/jboss-3.2/cache/build.xml:207: Compile failed; see the compiler error output for details. Total time: 2 minutes 34 seconds 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-4.0.2RC1, JBossAS-3.2.7 Final 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1613) NPE in PersistenceManager.loadFromStorage
[ http://jira.jboss.com/jira/browse/JBAS-1613?page=history ] Adrian Brock closed JBAS-1613: -- Resolution: Duplicate Issue 1) Use search before reporting bugs. 2) Test the latest version before reporting bugs. NPE in PersistenceManager.loadFromStorage - Key: JBAS-1613 URL: http://jira.jboss.com/jira/browse/JBAS-1613 Project: JBoss Application Server Type: Bug Environment: JBoss 4.0.1sp1, JDK 1.4.2, WinXP Reporter: d00d ranch I have been testing JBoss Messaging, and ran into an interesting exception on the server. Our testing of TextMessage worked great. We then went to test BytesMessage, and received the below exception. This exception occurs when a Consumer attempts to get a message from the queue. Placing messages into the queue did not generate an exception. These ByteMessages are 7MB in size. 15:39:03,467 ERROR [SocketManager] Failed to handle: org.jboss.mq.il.uil2.msgs.R eceiveMsg26485067[msgType: m_receive, msgID: 7, error: null] java.lang.NullPointerException at org.jboss.mq.pm.jdbc3.PersistenceManager.loadFromStorage(PersistenceM anager.java:850) at org.jboss.mq.server.MessageCache.loadFromStorage(MessageCache.java:41 1) at org.jboss.mq.server.MessageReference.makeHard(MessageReference.java:3 51) at org.jboss.mq.server.MessageReference.getMessage(MessageReference.java :156) at org.jboss.mq.server.BasicQueue.setupMessageAcknowledgement(BasicQueue .java:881) at org.jboss.mq.server.BasicQueue.receive(BasicQueue.java:488) at org.jboss.mq.server.JMSQueue.receive(JMSQueue.java:136) at org.jboss.mq.server.ClientConsumer.receive(ClientConsumer.java:222) at org.jboss.mq.server.JMSDestinationManager.receive(JMSDestinationManag er.java:673) at org.jboss.mq.server.JMSServerInterceptorSupport.receive(JMSServerInte rceptorSupport.java:226) at org.jboss.mq.security.ServerSecurityInterceptor.receive(ServerSecurit yInterceptor.java:100) at org.jboss.mq.server.TracingInterceptor.receive(TracingInterceptor.jav a:570) at org.jboss.mq.server.JMSServerInvoker.receive(JMSServerInvoker.java:22 6) at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocke tManagerHandler.java:149) at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.j ava:362) at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExec utor.java:748) at java.lang.Thread.run(Thread.java:534) -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-123) Remove 4.0.1sp1 patch for MDB/Consumer
Remove 4.0.1sp1 patch for MDB/Consumer -- Key: EJBTHREE-123 URL: http://jira.jboss.com/jira/browse/EJBTHREE-123 Project: EJB 3.0 Type: Task Versions: Preview 5 Reporter: Bill Burke Fix For: EJB 3.0 Beta 1 Search for TODO in MDB.java and Consumer.java. Remove that reflection calls to getServerSessionPool. -- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
