[JBoss-dev] [Design of Mail Services] - Re: What dev tools?
Eclipse JBoss IDE (Makes debugging very easy). Mike. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869900#3869900 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869900 --- 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-testsuite build.64 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050313035313Lbuild.64 BUILD COMPLETE-build.64Date of build:03/13/2005 03:53:13Time to build:99 minutes 45 secondsLast changed:03/13/2005 01:31:39Last log entry:Remove the WrapperDataSourceServiceMBean.java interface as its still generated in 4.0 Unit Tests: (2440) Total Errors and Failures: (13)testStatefulPassiviationExpirationorg.jboss.test.testbeancluster.test.BeanUnitTestCase(Default)testEndpointOneorg.jboss.test.webservice.jbws79.JBWS79TestCasetestEndpointTwoorg.jboss.test.webservice.jbws79.JBWS79TestCasetestSessionTimeoutorg.jboss.test.cluster.test.SimpleTestCase(Default)testSessionTimeoutorg.jboss.test.cluster.test.SimpleTestCase(SyncModeNUseJvm)testPoolingorg.jboss.test.cts.test.MDBUnitTestCasetestUserInRoleServletorg.jboss.test.jacc.test.WebIntegrationUnitTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCasetestPoolingorg.jboss.test.securitymgr.test.MDBUnitTestCasetestJBossEditorsorg.jboss.test.util.test.PropertyEditorsUnitTestCasetestEchoMimeTextPlainorg.jboss.test.webservice.attachment.AttachmentProxyTestCasetestEchoMimeApplicationXMLorg.jboss.test.webservice.attachment.AttachmentProxyTestCase Modifications since last build:(10)1.3.6.1deletedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/WrapperDataSourceServiceMBean.javaRemove the WrapperDataSourceServiceMBean.java interface as its still generated in 4.01.21.2.2modifiedstarksmtools/etc/buildmagic/modules.entUpdate the jboss.aop.classpath and jboss.aspects.classpath to use the thirdparty binaries1.4.2.2modifiedstarksmtools/etc/buildmagic/modules.xmlUpdate the jboss.aop.classpath and jboss.aspects.classpath to use the thirdparty binaries1.355.2.25modifiedstarksmbuild/build.xmlRemove the aop and aspects modules and update the jboss-aop.deployer installation from the thirdparty directory1.21.2.1modifiedstarksmtools/etc/buildmagic/modules.entUpdate the jboss.aop.classpath to be based on the thirdparty binary1.2.6.1modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/SerializableInputStream.javaExplicitly set the serialVersionUID values to the 4.0.0 values to ensure they don't float1.1.6.1modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/SerializableParameterMetaData.javaExplicitly set the serialVersionUID values to the 4.0.0 values to ensure they don't float1.1.6.1modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/SerializableReader.javaExplicitly set the serialVersionUID values to the 4.0.0 values to ensure they don't float1.1.6.1modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/StatementInterceptor.javaExplicitly set the serialVersionUID values to the 4.0.0 values to ensure they don't float1.3.4.1modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/SerializableResultSetMetaData.javaResolve (JBAS-1574) SerializableResultSetMetaData.getColumnCount is off by one.
[JBoss-dev] [Design of Mail Services] - MailStore Integration
Hi, I have just committed the first pass of the Mail Store integration. anonymous wrote : Eventually there should be: | | 1. Always use store | 2. Never use store | 3. Use store when the message is N kb We have 1 2 at the moment. By default it is switched off. To turn it on, configure the UseStore attribute of the MailBodyManager and configure the MailStore that you wish to use (Postgres is recommend). The mailstore at the moment is only benifical to the SMTP side of things. When retrieving mail via POP the whole message is still loaded into memory. From the plan I can see that mailbox implementation is changing so for M3 so I didn't much point in making major changes to the Message interface. Mailbox interaction is a bit hairy at the moment. I wasn't sure what the plan is with regards to data migration from M2 - M3, therefore the store changes are designed to be compatiable with M2. To migrate an additional column BODYTYPE NUMBER(2) is required on the ENTITYMESSAGES table. This should be set to 0 for old messages. The MailBodyManager will take care wrapping old mails into SimpleMailBody objects. StoredMailBody objects make available a String handle which is stored in the body column. Going forward we should simply serialise the MailBody object and store it as a byte array. For now I have just implemented the simplest, least breaking change I could manage. Next I am going to modify the Hibernate Store to implement a paging mechanism. As always, questions, comments are welcome. Mike View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869904#3869904 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869904 --- 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: MailStore
anonymous wrote : Postgres's latest drivers seem to support streaming. Sort of, streaming is supported via JDBC2 for inputing into a byte array field, but not for retrieving data. Also the JDBC3 Blob is not supported, our implemenation uses this (I sent a patch a couple of weeks ago but have not seen any response to it, maybe they don't like my code, sniff, sniff). However that is not a problem as we have an implemenation of the store that talks directly to the LargeObjectAPI. Check out: org.jboss.mail.store.postgresql.PostgreSQLStore. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869905#3869905 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869905 --- 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-jdk-matrix build.90 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050313071558Lbuild.90 BUILD COMPLETE-build.90Date of build:03/13/2005 07:15:58Time to build:31 minutes 47 secondsLast changed:03/12/2005 17:02:00Last log entry:Tests of remote access to a jdbc datasource. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(11)1.1addedstarksmtestsuite/src/main/org/jboss/test/jca/test/RemoteDSUnitTestCase.javaTests of remote access to a jdbc datasource.1.1addedstarksmtestsuite/src/resources/jca/remote-jdbc/remote-ds.xmlA remotely accessible datasource configuration1.1addedbelabancache/src/main/org/jboss/cache/lock/SimpleReadWriteLock.javanew file1.3modifiedbelabancache/src/main/org/jboss/cache/tests/ReentrantWriterPreferenceReadWriteLockTest.javano message1.3modifiedbelabancache/src/main/org/jboss/cache/tests/RpcDelegatingCacheLoaderTests.javano message1.54modifiedbelabancache/build.xmlmodified to create separate bundle for Sleepycat JAR1.3modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/SerializableInputStream.javaExplicitly set the serialVersionUID values to the 4.0.0 values to ensure they don't float1.2modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/SerializableParameterMetaData.javaExplicitly set the serialVersionUID values to the 4.0.0 values to ensure they don't float1.2modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/SerializableReader.javaExplicitly set the serialVersionUID values to the 4.0.0 values to ensure they don't float1.2modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/StatementInterceptor.javaExplicitly set the serialVersionUID values to the 4.0.0 values to ensure they don't float1.4modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/SerializableResultSetMetaData.javaResolve (JBAS-1574) SerializableResultSetMetaData.getColumnCount is off by one.
[JBoss-dev] [Design of JBoss Eclipse IDE (dev)] - Re: Unable to open ejb-jar.xml or any xml! VerifyError
Hi, I assume you are using the Milestone 5 Release of Eclipse. I got the same exception with that one. Anyone on this list: When will the JBoss IDE be tested/compiled against the new release? The Eclipse API must have been changed between M4 and M5. Greetings, Stefan Liebner View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869907#3869907 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869907 --- 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 Management Features on JBoss] - Clearing the class loader repository through the jmx console
Hello, Is it possible to clear the class loader repository through the jmx console. I tried to invoke the flush operation and it does not clear the class loader repository. Any help welcome, Julien. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869909#3869909 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869909 --- 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-1575) Replace Old JAXR implementation (ebxmlrr) with Apache Scout/jUDDI
Replace Old JAXR implementation (ebxmlrr) with Apache Scout/jUDDI - Key: JBAS-1575 URL: http://jira.jboss.com/jira/browse/JBAS-1575 Project: JBoss Application Server Type: Task Components: JAXR service Versions: JBossAS-4.0.2RC1, JBossAS-4.0.2 Final Reporter: Anil Saldhana Assigned to: Anil Saldhana Fix For: JBossAS-4.0.2RC1 The 4.0.x released versions have been carrying a JAXR implementation based on the open source ebxmlrr. Need to replace it with the new JAXR stack based on Apache Scout and Apache jUDDI. The CTS tests for JAXR should pass. -- 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-1575) Replace Old JAXR implementation (ebxmlrr) with Apache Scout/jUDDI
[ http://jira.jboss.com/jira/browse/JBAS-1575?page=history ] Anil Saldhana closed JBAS-1575: --- Resolution: Done The CTS tests for JAXR are passing. The old JAXR implementation has been replaced with the new JAXR stack, based on Apache Scout and Apache jUDDI. Replace Old JAXR implementation (ebxmlrr) with Apache Scout/jUDDI - Key: JBAS-1575 URL: http://jira.jboss.com/jira/browse/JBAS-1575 Project: JBoss Application Server Type: Task Components: JAXR service Versions: JBossAS-4.0.2RC1, JBossAS-4.0.2 Final Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossAS-4.0.2RC1 The 4.0.x released versions have been carrying a JAXR implementation based on the open source ebxmlrr. Need to replace it with the new JAXR stack based on Apache Scout and Apache jUDDI. The CTS tests for JAXR should pass. -- 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-1295) Pass the CTS Tests
[ http://jira.jboss.com/jira/browse/JBAS-1295?page=history ] Anil Saldhana closed JBAS-1295: --- Resolution: Done Passes the CTS tests!!! Pass the CTS Tests -- Key: JBAS-1295 URL: http://jira.jboss.com/jira/browse/JBAS-1295 Project: JBoss Application Server Type: Sub-task Components: JAXR service Versions: JBossAS-5.0 Final Reporter: Anil Saldhana Assignee: Anil Saldhana The Jaxr Integration in JBAS using Apache jUDDI and Apache Scout should pass the CTS Tests. -- 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: (JBAOP-93) JBoss AOP jars in 4.0
[ http://jira.jboss.com/jira/browse/JBAOP-93?page=history ] Scott M Stark closed JBAOP-93: -- Resolution: Done The Branch_EJB_3_0_PREVIEW_3_0 code was used to build the jboss-aop.deployer and the thirdparty/jboss-aop include this deployer and jars. [EMAIL PROTECTED] thirdparty]$ ls -R jboss-aop jboss-aop: CVS/ jboss-aop.deployer* lib/ jboss-aop/lib: CVS/ jboss-aop.jar jboss-aspect-library.jar JBoss AOP jars in 4.0 - Key: JBAOP-93 URL: http://jira.jboss.com/jira/browse/JBAOP-93 Project: JBoss AOP Type: Task Reporter: Adrian Brock Assignee: Scott M Stark Priority: Minor The jboss-aop and aspect library jars in Branch_4_0 should be in thirdparty and the source projects removed altogether from the JBossAS build. Although, we do want to use this approach in future, we don't have the infrastructure in place for this change yet... e.g. How to control versions of dependent projects and thirdparty jars. -- 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-1515) Update the AOP binaries and remove the aop modules
[ http://jira.jboss.com/jira/browse/JBAS-1515?page=history ] Scott M Stark updated JBAS-1515: Comment: was deleted Update the AOP binaries and remove the aop modules -- Key: JBAS-1515 URL: http://jira.jboss.com/jira/browse/JBAS-1515 Project: JBoss Application Server Type: Task Components: Build System Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-4.0.2RC1 The aop deployer seems to no longer be built from the aspects module source. The current 4.0 branch binaries do not include the recent security changes and needs to be updated. If binaries are being used as the integration mechanism, there is no reason to be including obsolete source modules. -- 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-1344) ebxml messaging
[ http://jira.jboss.com/jira/browse/JBAS-1344?page=history ] Anil Saldhana closed JBAS-1344: --- Resolution: Won't Fix We are basing our JAXR implementation on UDDI. Integration of ebxml is complicated. There are other forms of messaging that can be looked at : Java Message Service, WS-Notification etc. ebxml messaging --- Key: JBAS-1344 URL: http://jira.jboss.com/jira/browse/JBAS-1344 Project: JBoss Application Server Type: Feature Request Components: JAXR service Versions: JBossAS-4.0.1 Final Reporter: SourceForge User SourceForge Submitter: pucky . The new standard for Business to Business is around the corner! ebXML backed by OASIS and the United Nations, is the next best thing to sliced bread. I believe that if jboss could become the first app server to deploy ebXML messaging and ebXML repositories(out of the box) JBOSS would become not only the defacto standard in apps servers but the deployment of JBOSS is the B2B World would sky rocket. I hope someone could look into this from the JBOSS front! -- 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] [JBossCache] - Hibernate, JBoss Cache Evaluation
Hi Jboss experts, I am evaluating the JBoss cache for a Hibernate (refactoring) project. I would need a database cache for 6+ java apps running on a distributed archtecture of IBM-Websphere 4.0.6 (jdk 1.3.1). The database tables that need to be cache contain at least few millions of records per table. The cache for now should be read-only (for the java apps) but updated each morning (near 1AM) after a non-java batch process have updated the database. Reloading the entire cache each morning for the java apps can be quite heavy for the network, it could take too much time to load all tables. So I am looking for a way to insert in the cache the modified record only (based on a timestamp..) plus the new records. The cache must be fail safe in some way (for not reloading everything if a web app go down) and should be memory and IO optimised to run on many web apps, on distributed WAS server. At least, on the same web app, it should share the cache memory. The cache is a read-only one. But for the vision, in some months (12++), we might requiered a transactional cache (real-time read-write by the java apps). But for now, there's no transactional requierement. Is Jboss Cache a good option for this use case? Anyone have implemented this architecture with success? Or should I check for some commercial package (like Coherence)? Thanks all. Etienne. Montreal View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869912#3869912 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869912 --- 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-1522) HttpNamingContextFactory fails due to system property read when under a security manager
[ http://jira.jboss.com/jira/browse/JBAS-1522?page=history ] Scott M Stark closed JBAS-1522: --- Resolution: Done The org.jboss.security.httpInvoker.sslSocketFactoryBuilder system property is read in a PrivilegedAction, and failure simply results in the default https SSLSocketFactory being used. HttpNamingContextFactory fails due to system property read when under a security manager Key: JBAS-1522 URL: http://jira.jboss.com/jira/browse/JBAS-1522 Project: JBoss Application Server Type: Bug Components: Naming Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-4.0.2RC1, JBossAS-5.0 Alpha, JBossAS-3.2.8 Final Running under a security manager with the org.jboss.naming.HttpNamingContextFactory can result in the following failure due to the property access not being in a privileged block. The failure should also be ignored since its an optional override setting. java.lang.ExceptionInInitializerError at org.jboss.naming.HttpNamingContextFactory.getNamingServer(HttpNamingContextFactory.java:106) at org.jboss.naming.HttpNamingContextFactory.getInitialContext(HttpNamingContextFactory.java:65) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243) at javax.naming.InitialContext.init(InitialContext.java:219) at javax.naming.InitialContext.(InitialContext.java:195) at com.nineci.applet.HelloBeanApplet.start(HelloBeanApplet.java:31) at sun.applet.AppletPanel.run(AppletPanel.java:377) at java.lang.Thread.run(Thread.java:534) Caused by: java.security.AccessControlException: access denied (java.util.PropertyPermission org.jboss.security.httpInvoker.sslSocketFactoryBuilder read) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:269) at java.security.AccessController.checkPermission(AccessController.java:401) at java.lang.SecurityManager.checkPermission(SecurityManager.java:524) at java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1276) at java.lang.System.getProperty(System.java:573) at org.jboss.invocation.http.interfaces.Util.(Util.java:76) ... 9 more -- 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] Commented: (JBAS-1503) J2EE 1.4 Compliance
[ http://jira.jboss.com/jira/browse/JBAS-1503?page=comments#action_12316099 ] Anil Saldhana commented on JBAS-1503: - are u scoping ur war to use its own libraries? If yes, can you insure that you do not package commons-logging.jar in your war? J2EE 1.4 Compliance --- Key: JBAS-1503 URL: http://jira.jboss.com/jira/browse/JBAS-1503 Project: JBoss Application Server Type: Bug Components: Web (Tomcat) service Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final Environment: Windows XP. Jboss 4.0.1 / 4.0.1 SP1 Reporter: Gilli Atkinson Attachments: server.log Unable to properly deploy .war file when configured to be J2EE 1.4 compliant (configuration based on section 2.1 in http://docs.jboss.org/jbossas/whatsnew40/html/). When running as default config, it deploys fine but because of unified classloader, multiple .wars with conflicting class names are a problem. Hence the attempt using compilance config. I've looked everywhere for a solution, or to see if someone else has come up against this, and I'm at a dead end. If I've missed the answer somewhere I apologise for wasting your time. I get 2 main errors (I've attached the log file) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=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 JMX on JBoss (JBoss/JMX)] - Have you coded a cool MBean service you want to share?
Check this out: http://www.jboss.org/wiki/Wiki.jsp?page=JBossWorldOfMBeans View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869913#3869913 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869913 --- 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: error when I loggin in jboss portal
Has the database user account being used for the connection to the database been given adequate permissions? Try granting the database user account full access to the database that was created for the portal. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869914#3869914 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869914 --- 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.27 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite?log=log20050313090342Lbuild.27 BUILD COMPLETE-build.27Date of build:03/13/2005 09:03:42Time to build:113 minutes 41 secondsLast changed:03/12/2005 17:02:00Last log entry:Tests of remote access to a jdbc datasource. Unit Tests: (2439) Total Errors and Failures: (69)
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1558) HAJNDI should use a thread pool
[ http://jira.jboss.com/jira/browse/JBAS-1558?page=history ] Scott M Stark reassigned JBAS-1558: --- Assign To: Scott M Stark HAJNDI should use a thread pool --- Key: JBAS-1558 URL: http://jira.jboss.com/jira/browse/JBAS-1558 Project: JBoss Application Server Type: Feature Request Components: Clustering Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final Reporter: Adrian Brock Assignee: Scott M Stark Fix For: JBossAS-4.0.2RC1 The DetachedHANamingService should use a ThreadPool like plain JNDI when it is serving the bootstrap stub to clients. -- 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.431 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050313114422Lbuild.431 BUILD COMPLETE-build.431Date of build:03/13/2005 11:44:22Time to build:34 minutes 28 secondsLast changed:03/13/2005 10:18:02Last log entry:Update the aop deployer and library from code on the Branch_EJB_3_0_PREVIEW_3_0 as the previous checkout did not match this tag Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(3)1.1.2.1modifiedstarksmthirdparty/jboss-aop/lib/jboss-aop.jarUpdate the aop deployer and library from code on the Branch_EJB_3_0_PREVIEW_3_0 as the previous checkout did not match this tag1.1.2.1modifiedstarksmthirdparty/jboss-aop/lib/jboss-aspect-library.jarUpdate the aop deployer and library from code on the Branch_EJB_3_0_PREVIEW_3_0 as the previous checkout did not match this tag1.1.2.1modifiedstarksmthirdparty/jboss-aop/jboss-aop.deployerUpdate the aop deployer and library from code on the Branch_EJB_3_0_PREVIEW_3_0 as the previous checkout did not match this tag
[JBoss-dev] jboss-4.0-jdk-matrix build.107 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050313123437Lbuild.107 BUILD COMPLETE-build.107Date of build:03/13/2005 12:34:37Time to build:42 minutes 7 secondsLast changed:03/13/2005 10:18:02Last log entry:Update the aop deployer and library from code on the Branch_EJB_3_0_PREVIEW_3_0 as the previous checkout did not match this tag Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(13)1.1.2.1modifiedstarksmthirdparty/jboss-aop/lib/jboss-aop.jarUpdate the aop deployer and library from code on the Branch_EJB_3_0_PREVIEW_3_0 as the previous checkout did not match this tag1.1.2.1modifiedstarksmthirdparty/jboss-aop/lib/jboss-aspect-library.jarUpdate the aop deployer and library from code on the Branch_EJB_3_0_PREVIEW_3_0 as the previous checkout did not match this tag1.1.2.1modifiedstarksmthirdparty/jboss-aop/jboss-aop.deployerUpdate the aop deployer and library from code on the Branch_EJB_3_0_PREVIEW_3_0 as the previous checkout did not match this tag1.3.6.1deletedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/WrapperDataSourceServiceMBean.javaRemove the WrapperDataSourceServiceMBean.java interface as its still generated in 4.01.21.2.2modifiedstarksmtools/etc/buildmagic/modules.entUpdate the jboss.aop.classpath and jboss.aspects.classpath to use the thirdparty binaries1.4.2.2modifiedstarksmtools/etc/buildmagic/modules.xmlUpdate the jboss.aop.classpath and jboss.aspects.classpath to use the thirdparty binaries1.355.2.25modifiedstarksmbuild/build.xmlRemove the aop and aspects modules and update the jboss-aop.deployer installation from the thirdparty directory1.21.2.1modifiedstarksmtools/etc/buildmagic/modules.entUpdate the jboss.aop.classpath to be based on the thirdparty binary1.2.6.1modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/SerializableInputStream.javaExplicitly set the serialVersionUID values to the 4.0.0 values to ensure they don't float1.1.6.1modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/SerializableParameterMetaData.javaExplicitly set the serialVersionUID values to the 4.0.0 values to ensure they don't float1.1.6.1modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/SerializableReader.javaExplicitly set the serialVersionUID values to the 4.0.0 values to ensure they don't float1.1.6.1modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/StatementInterceptor.javaExplicitly set the serialVersionUID values to the 4.0.0 values to ensure they don't float1.3.4.1modifiedstarksmconnector/src/main/org/jboss/resource/adapter/jdbc/remote/SerializableResultSetMetaData.javaResolve (JBAS-1574) SerializableResultSetMetaData.getColumnCount is off by one.
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1558) HAJNDI should use a thread pool
[ http://jira.jboss.com/jira/browse/JBAS-1558?page=history ] Scott M Stark closed JBAS-1558: --- Resolution: Done Fix Version: JBossAS-5.0 Alpha The DetachedHANamingService now uses a thread pool set via the LookupPool attribute the same as the NamingService. By default this is mapped to the jboss.system:service=ThreadPool in the cluster-service.xml. If this attribute is not set an independent BasicThreadPool(HANamingBootstrap Pool) instance is created. HAJNDI should use a thread pool --- Key: JBAS-1558 URL: http://jira.jboss.com/jira/browse/JBAS-1558 Project: JBoss Application Server Type: Feature Request Components: Clustering Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final Reporter: Adrian Brock Assignee: Scott M Stark Fix For: JBossAS-4.0.2RC1, JBossAS-5.0 Alpha The DetachedHANamingService should use a ThreadPool like plain JNDI when it is serving the bootstrap stub to clients. -- 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-1544) Wrong MBean attribute name in jboss:service=Mail (POP3SererHost )
[ http://jira.jboss.com/jira/browse/JBAS-1544?page=history ] Scott M Stark closed JBAS-1544: --- Resolution: Done MailServiceMBean.java is generated from MailService.java in 4.0 and has been corrected in head. Wrong MBean attribute name in jboss:service=Mail (POP3SererHost ) - Key: JBAS-1544 URL: http://jira.jboss.com/jira/browse/JBAS-1544 Project: JBoss Application Server Type: Bug Components: JMX Versions: JBossAS-4.0.1 SP1 Reporter: Goran Ehrsson Priority: Minor Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-4.0.2RC1 While browsing the Management Console on my newly installed jboss-4.0.1sp1 I found a misspelled MBean attribute in the Mail service. POP3SererHost should be POP3ServerHost I assume. -- 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: (JBAS-1258) Remove jbossha-httpsession.sar
[ http://jira.jboss.com/jira/browse/JBAS-1258?page=history ] Scott M Stark reassigned JBAS-1258: --- Assign To: Scott M Stark (was: Ben Wang) Remove jbossha-httpsession.sar -- Key: JBAS-1258 URL: http://jira.jboss.com/jira/browse/JBAS-1258 Project: JBoss Application Server Type: Task Components: Clustering Versions: JBossAS-4.0.1 Final Reporter: Ben Wang Assignee: Scott M Stark Priority: Optional Fix For: JBossAS-4.0.2RC1 Original Estimate: 1 hour Remaining: 1 hour jbossha-httpsession.sar under server/all/deploy is redundant since we have used JBossCache now. canbe safely removed. -- 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-1258) Remove jbossha-httpsession.sar
[ http://jira.jboss.com/jira/browse/JBAS-1258?page=history ] Scott M Stark closed JBAS-1258: --- Resolution: Done Fix Version: JBossAS-5.0 Alpha Remove jbossha-httpsession.sar -- Key: JBAS-1258 URL: http://jira.jboss.com/jira/browse/JBAS-1258 Project: JBoss Application Server Type: Task Components: Clustering Versions: JBossAS-4.0.1 Final Reporter: Ben Wang Assignee: Scott M Stark Priority: Optional Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2RC1 Original Estimate: 1 hour Remaining: 1 hour jbossha-httpsession.sar under server/all/deploy is redundant since we have used JBossCache now. canbe safely removed. -- 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-1526) Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the permissions of the replaced delegate
[ http://jira.jboss.com/jira/browse/JBAS-1526?page=history ]
Scott M Stark closed JBAS-1526:
---
Resolution: Done
Fix Version: (was: JBossPOJOServer-1.0 Alpha)
Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the
permissions of the replaced delegate
Key: JBAS-1526
URL: http://jira.jboss.com/jira/browse/JBAS-1526
Project: JBoss Application Server
Type: Bug
Components: Security
Versions: JBossAS-4.0.1 SP1
Environment: -
Reporter: Roland R?z
Assignee: Scott M Stark
Fix For: JBossAS-4.0.2RC1, JBossAS-5.0 Alpha
Original Estimate: 1 hour
Remaining: 1 hour
Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the
permissions of the replaced delegate
According to the JACC specification all Permissions of a CodeSource or
ProtectionDomain should be returned. Currently these methods return only the
JACC Permissions, without the Permissions of the delegate class.
The JACC Specification states (http://java.sun.com/j2ee/javaacc/):
2.5 What a Provider Must Do
paragraph 3
A replacement Policy object must assume responsibility for performing all
policy decisions within the JRE in which it is installed that are requested
by way of the Policy interface that it implements.
Example Implementation of DelegatingPolicy.getPermissions(x):
public PermissionCollection getPermissions(ProtectionDomain domain) {
PermissionCollection pc = super.getPermissions(domain);
PermissionCollection delegated =
delegate.getPermissions(domain);
for (Enumeration e = delegated.elements();
e.hasMoreElements();) {
Permission p = (Permission) e.nextElement();
pc.add(p);
}
return pc;
}
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_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-1571) Logging of cluster rpc method exceptions at warn level is incorrect
[ http://jira.jboss.com/jira/browse/JBAS-1571?page=history ] Scott M Stark updated JBAS-1571: JBoss Forum Reference: http://www.jboss.org/index.html?module=bbop=viewtopict=61348 Logging of cluster rpc method exceptions at warn level is incorrect --- Key: JBAS-1571 URL: http://jira.jboss.com/jira/browse/JBAS-1571 Project: JBoss Application Server Type: Bug Components: Clustering Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-4.0.2RC1, JBossAS-5.0 Beta, JBossAS-3.2.8 Final Original Estimate: 1 hour Remaining: 1 hour The HAPartitionImpl handler for cluster rpc method invocations logs Exceptions and Errors thrown from the reflected method invocation at warn level. This results in spurious warnings when the underlying invocation throws an exception as part of its normal operation. An example of where this occurs is when an ha-sigleton binds a jndi entry into its node, and a client does a lookup of the binding through ha-jndi. In a 3 node cluster A, B, C with the ha-singleton on A, a ha-jndi request going to B will produce the following NameNotFoundException on C: 06:52:07,359 WARN [DefaultPartition] javax.naming.NameNotFoundException: TheSingleton not bound These exceptions should be logged at trace level. -- 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-head build.876 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050313133537Lbuild.876 BUILD COMPLETE-build.876Date of build:03/13/2005 13:35:37Time to build:36 minutes 6 secondsLast changed:03/13/2005 12:10:12Last log entry:added tests for new sunday metadata/handling api Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(3)1.12modifiedloubyanskytestsuite/src/main/org/jboss/test/xml/MiscUnitTestCase.javaadded tests for new sunday metadata/handling api1.26modifiedloubyanskycommon/src/main/org/jboss/xml/binding/Unmarshaller.javaanother unmarshalling metadata/handling model. the most comprehensive, hence, the most verbose.1.8modifiedloubyanskycommon/src/main/org/jboss/xml/binding/UnmarshallerImpl.javaanother unmarshalling metadata/handling model. the most comprehensive, hence, the most verbose.
[JBoss-dev] [Design of JBoss Portal] - Re: error when I loggin in jboss portal
the user is named jboss and it is the owner of the DB.. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869931#3869931 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869931 --- 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-jdk-matrix build.76 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050313143624Lbuild.76 BUILD COMPLETE-build.76Date of build:03/13/2005 14:36:24Time to build:44 minutes 18 seconds Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(0)
[JBoss-dev] [JBossCache] - Re: Hibernate, JBoss Cache Evaluation
Hi all, I have read some doc and it seems that JBoss Cache is doing this! great! Etienne. Montreal View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869938#3869938 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869938 --- 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.432 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050313160620Lbuild.432
BUILD COMPLETE-build.432Date of build:03/13/2005 16:06:20Time to build:43 minutes 9 secondsLast changed:03/13/2005 14:29:29Last log entry:Include the delegate policy ProtectionDomain permissions when building the PermissionCollection in getPermissions(ProtectionDomain). Resolves (JBAS-1526) Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the permissions of the replaced delegate.
Unit Tests: (0) Total Errors and Failures: (0)
Modifications since last build:(5)1.5.4.4modifiedstarksmsecurity/src/main/org/jboss/security/jacc/DelegatingPolicy.javaInclude the delegate policy ProtectionDomain permissions when building the PermissionCollection in getPermissions(ProtectionDomain). Resolves (JBAS-1526) Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the permissions of the replaced delegate.1.355.2.26modifiedstarksmbuild/build.xmlRemove the unused jbossha-httpsession.sar1.28.6.4modifiedstarksmcluster/src/etc/cluster-service.xmlExpose all HANamingService attributes by default.1.2.4.7modifiedstarksmcluster/src/main/org/jboss/ha/jndi/DetachedHANamingService.javaRemove all local thread creation and instead use the thread pool passed in via the LookupPool. If no LookupPool is specified a BasicThreadPool("HANamingBootstrap Pool") is created. Resolves (JBAS-1558) HAJNDI should use a thread pool.1.2.4.3modifiedstarksmcluster/src/main/org/jboss/ha/jndi/DetachedHANamingServiceMBean.javaRemove all local thread creation and instead use the thread pool passed in via the LookupPool. If no LookupPool is specified a BasicThreadPool("HANamingBootstrap Pool") is created. Resolves (JBAS-1558) HAJNDI should use a thread pool.
[JBoss-dev] [JBossCache] - Multiple DB in Hibernate in one schema using JBoss-Cache?
Hi, this question concerns the JBoss Cache and Hibernate. Hibernate have a limitation that I would like to overcome. Hibernate cannot use the Same Schma for 2 different databases. Using C-JDBC is not the answer either. See: http://forum.hibernate.org/viewtopic.php?t=937847 http://forum.hibernate.org/viewtopic.php?t=938654highlight=schema+multiple+database I read in the JBoss faq http://docs.jboss.org/jbcache/FAQ.html and in the documentation that the JBoss cache can use a Cache Loader (since 1.1) to persist its cache objects (FileCacheLoader, BdcjeCacheLoader and JDBCCacheLoader). anonymous wrote : | JBossCache 1.2 released: | - JDBC CacheLoader: allows to load/store data from DB | - Common dta transfer format: this allows for replication between different | CacheLoaders, e.g. FileCacheLoader and JDBCCacheLoader. Also | enables replication e.g. between MySQL and Oracle | (still needs more testing though) Would it be possible that 2 SessionFactory (each connect to a different physical DB, with a different schma: Schema 1 on DB1:Oracle, Schema 2 on DB2:Sybase) use the SAME cache loader? I means that if a Parent table is on Sybase, the Children data (on Oracle) could be retreived in memory because it could have been load in the same cache before? But from this mail: http://forum.hibernate.org/viewtopic.php?t=938654highlight=schema+multiple+database it seems that it isn't the case. anonymous wrote : First, no, Hibernate will not be implementing in-memory joins But if the CacheLoader do the job, could it be possible? I think about 2 BdcjeCacheLoader for each SessionFactory loading in the same SleepyCat BD? anonymous wrote : BdbjeCacheLoader: this implementation is based on the Sleepycat Java Edition database, a fast and efficient transactional database. It uses a single file for the entire store. http://www.sleepycat.com/jeforjbosscache for details. Another options could be, using the JDBCCacheLoader, and cache the DB1:Oracle data inside the DB2:Sybase in a extended schema? So, the connection factory on DB2:Sybase might have all the data? I know this sound tricky to say the less, but could it be feasible by writing a CustomClassLoader? The goal of all this is to simulate a transparent SQL INNER JOIN between two physical databases and avoid tousand of SQL SELECT on a real DB. Note that the DB1:Oracle maintain only read-only data (easily cachable) and only updated by a batch process each day at 12AM. The DB2:Sybase would be the transactinoal (r/w) database. Thanks for replying Etienne. Montreal View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869944#3869944 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869944 --- 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] [JBossCache] - Re: Multiple DB in Hibernate in one schema using JBoss-Cache
I am not sure if CacheLoader is what you want. It is used for *state* persistence so it does not have the entity notion of schema and such. -Ben View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869951#3869951 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869951 --- 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: Mail API
Is there a reason why JBoss Mail shouldn't adopt the Apache James Mailet / Matcher API? It seems well documented and is a stable, well thought out API for e-mail workflow processing. Honestly, I've looked at (am still looking at) James as an e-mail server solution for an upcoming project. I suppose the main reason I haven't simply embraced James is its reliance on the now-defunct Avalon project. I cringe at the thought of introducing yet-another server framework into my development and production environments! J2EE, for all its flaws, is well known, mature, stable, and very well documented/supported. I've been monitoring the JBoss effort, but am not at all clear that it's not going to ask me to don a different style straight jacket than James wants me to wear. The talks about relying on BeanShell or JavaScript to process e-mails handled by my Java-based e-mail server is an example of such a straight jacket. To more fully discuss these issues, I'm posting a new topic on What I'm Looking For, And Not looking For, In A Java-Based Enterprise E-mail Server Jack View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869952#3869952 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869952 --- 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-1571) Logging of cluster rpc method exceptions at warn level is incorrect
[ http://jira.jboss.com/jira/browse/JBAS-1571?page=history ] Scott M Stark closed JBAS-1571: --- Resolution: Done The handler now simply returns any exception thrown during the rpc method call dispatch as this is the only way to propagate this back to the caller. Note that this can result in exceptions showing up as return values if the rpc method throws an exception. See the referenced forum postings for more details. Logging of cluster rpc method exceptions at warn level is incorrect --- Key: JBAS-1571 URL: http://jira.jboss.com/jira/browse/JBAS-1571 Project: JBoss Application Server Type: Bug Components: Clustering Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-4.0.2RC1, JBossAS-5.0 Beta, JBossAS-3.2.8 Final Original Estimate: 1 hour Remaining: 1 hour The HAPartitionImpl handler for cluster rpc method invocations logs Exceptions and Errors thrown from the reflected method invocation at warn level. This results in spurious warnings when the underlying invocation throws an exception as part of its normal operation. An example of where this occurs is when an ha-sigleton binds a jndi entry into its node, and a client does a lookup of the binding through ha-jndi. In a 3 node cluster A, B, C with the ha-singleton on A, a ha-jndi request going to B will produce the following NameNotFoundException on C: 06:52:07,359 WARN [DefaultPartition] javax.naming.NameNotFoundException: TheSingleton not bound These exceptions should be logged at trace level. -- 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: Mail API
Look, there is very next to no chance we'll use anything from JAMES. The pieces we DID use from JAMES are being ripped out because they didn't profile well (namely the layered streams). The mailet API may be well documented but its frankly not that good. Furthermore the goal is very different. Our mail API will be geared to allow non-developers to script mail stuff. If you want something different, use the MailListeners which you'll find more similar to JAMES. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869953#3869953 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869953 --- 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: MailStore Integration
No data migration. Use POP, download your emails then install M3 :-). The type 3 should be a configurable size. For instance I might only want mails above 4k in the store and the rest cached. that'd give me a good compromise. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869954#3869954 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869954 --- 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: Mail API
I would however encourage an affirmative and positive What I'm looking for. No one will make you use mail scripting. Just because YOU don't see value in it doesn't mean others (me for instance) won't. I intend to SYNDICATE my spam catch scripts and AGGREGATE those of others in my trust circle. Furthermore, some clients already have contacted me asking when they'll be able to integrate with workflow and this and that for their mail. A scripting approach will make this available even to administrators. Not that we won't have a heavy java based one, but it most decidedly won't be JAMES's. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869955#3869955 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869955 --- 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.94 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050313172129Lbuild.94 BUILD COMPLETE-build.94Date of build:03/13/2005 17:21:29Time to build:137 minutes 49 seconds Unit Tests: (1967) Total Errors and Failures: (9)testAllTx_RWLockorg.jboss.test.cache.stress.EvictionLocalStressTestCasetestNoClassDefFoundErrororg.jboss.test.classloader.test.BasicLoaderUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestMDBDeepRunAsorg.jboss.test.security.test.EJBSpecUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestSessionTimeoutorg.jboss.test.cluster.test.SimpleTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCase Modifications since last build:(0)
[JBoss-dev] [JBossCache] - Re: Multiple DB in Hibernate in one schema using JBoss-Cache
Thank Ben for your answer, I understand. It is probably more on the Hibernate side that the issue of schema must be resolved. But in the JBoss Cache side, would it be possible to do this next scenario. In a way it doesn't matter that the data to cache comes from a database, I just want to know if it is possible to control the PersistenceStore at the data level : to add new relationship between object after putting it in the data store. In the other side, the use of a dataBase (BdcjeCacheLoader) as the persistence store points out that it could be possible in a near future to add relationship between cached object. Here's an example to illustrate the problem: 1- My application wants some data: ObjectTypeA and a Collection of ObjectTypeB linked each other to a Parent-Child relationship. ObjectTypeA and ObjectTypeB come from Data_BaseA. The application check the JBossCache (via the CacheLoader) to see if the data is there, if not it loaded the data from Data_BaseA before and put the Structure (One ObjectTypeA and many ObjectTypeB) in the persistence store. 2- The application needs now to get the ObjectTypeB plus a collection of ObjectTypeC that is linked to ObjectTypeB in a Parent-Child relationship. But this data is in another database: Data_BaseB. I check if the ObjectTypeB is in the cache, lets say I found it (because it load it from Data_BaseA). It then check if the collection of ObjectTypeC is in the cache. It doesn't find it. So it load it from Data_BaseB. Then it update the ObjectTypeB in the cache to linked it to a Collection of added ObjectTypeC. 3- It means that future access of ObjectTypeA-ObjectTypeB-ObjectTypeC will be done in the persistence store without accessing any database, and without any probleme of multiple database inner join. Using Hibernate, I cannot use the same cache for 2 database access. But if by some way we can add an object in the persitence store, and add new relationship between them, Hibernate could maybe use the same cache and the same schema to access 2 databases. I know it sound strange... Thanks, Etienne Montreal View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3869958#3869958 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3869958 --- 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] - What I am (not) Looking For In A Java-Based Enterprise E-mai
I was thrilled when I came across the Apache James e-mail server a couple years ago, but after a bit of investigation, I decided not to embrace it. I really liked the Matcher / Mailet APIs, but honestly, I didn't like the idea that to use James, I had to embrace the Avalon server framework. Then, when JBoss announced its Mail Services project, I was even more excited at the prospect of using a mail server that was integrated into my favorite J2EE container. However, as time has gone on, it seems like I will again be asked to embrace some unrelated APIs in order to handle my e-mail processing; i.e. People are talking about using scripting languages like JavaScript and BeanShell for e-mail workflow processing. I think it would be a mistake to require non-Java languages and APIs as an exclusive means for processing e-mails. So I wanted to get on the record what *I'd* like to see in any Java-based Enterprise E-mail server: - It should be J2EE-based Honestly, I don't want to have to revisit pooling, resource and thread management, security, datasource access and transactions, and all the other services provided by the well-documented J2EE API and JBoss implementation. - It should provide a clear separation of e-mail server behaviors that change rarely and those we might change often The standard e-mail server behaviors (as documented in various RFCs) are well known and essentially static since the backward compatibility is essential to successful Internet e-mail processing. However, new processing behaviors seem to crop up weekly, like anti-Spam processing and dealing with new Internet security threats. When once we were only worried about viruses carried in exe payloads, then we needed to worry about worms and trojans deployed in e-mail attachments, now including image files, etc. New threats like spyware and phishing attacks are not viral in nature, but a robust e-mail server should be extensible enough to allow me to plug-in processing code for the detection and removal of these threats. The separation of concerns issue is very important to me. Consider the highly successful Servlet API. It was written so that the servlet container could handle all the handshaking of the incoming web request, but what was done with that request was up to developers. Given that the servlet container handles all the nasty socket-level details of thread spawning, HTTP handshaking, connection timeouts, etc., we can focus on the business end of the processing. This has resulted in several excellent frameworks, like Struts, Tapestry, and WebWork to deal with the HttpServletRequest and Response artifacts created by the servlet container. As it stands, neither the James project nor the JBoss project seem to cleanly separate the core e-mail server functionality from the post processing activity. (There's some concern in the James community about the idea of accepting all e-mails rather than bouncing rejected ones, but I'll leave that discussion for another time.) For the JBoss e-mail server, it seems like this separation could be achieved by publishing the e-mail from the SMTP server as a JMS message and calling a stateless SessionBean from the POP server. (To prevent being falsely identified as an open relay and getting bombarded with spam, there could be some 0th order check for invalid server domains before delivering the message to JMS.) Developers (including JBoss.org) could then develop the mail processing APIs separately from the server-centric code to handle socket connections, threads, etc. Perhaps some Struts-like framework would emerge to process the SMTP e-mail. Or, maybe the James Matcher/Mailet APIs would be adapted for post-process workflow. Or, maybe someone will implement a Rules Engine approach (JESS, Drools) for complex processing of rules. Thus, JBoss 4.x/5.x could be shipped with default mail services (SMPT server, POP server) and instructions on how an application can subscribe to receive SMTP e-mail messages or extend a stateless SessionBean to override a default, simple e-mail fetching strategy. Then we can focus on implementing the business processing of the SMTP e-mails and returning e-mails to authorized users. - User and mail repositories must support virtual hosting; i.e. the same server instance must be able to distinguish john.smith @ acme.com from john.smith @ jboss.org. - Server must allow runtime changes to user repository without server restart. Ideally, e-mail processing rules should be able to be changed and picked up by the e-mail processor without a server restart - Any post-processing must allow use of different mailstores any kind, file system, datastore, EIS/Connector. By maintaining a separation of concerns of e-mail server vs e-mail processing, e-mail received by the SMTP server should be able to be processed in any way the user desires In summary, in the beginning JBoss needn't develop and deliver every
[JBoss-dev] jboss-head build.877 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050313201021Lbuild.877
BUILD COMPLETE-build.877Date of build:03/13/2005 20:10:21Time to build:25 minutes 46 secondsLast changed:03/13/2005 19:26:50Last log entry:Set the serialVersionUID for the NoHandlerForRPC class.
Unit Tests: (0) Total Errors and Failures: (0)
Modifications since last build:(15)1.46modifiedstarksmcluster/src/main/org/jboss/ha/framework/server/HAPartitionImpl.javaSet the serialVersionUID for the NoHandlerForRPC class.1.45modifiedstarksmcluster/src/main/org/jboss/ha/framework/server/HAPartitionImpl.javaSimply return any throwable seen during the rpc handler method call dispatch as this is the only way to propagate an exception to the caller. Resolves (JBAS-1571) Logging of cluster rpc method exceptions at warn level is incorrect.1.2modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/xsdjava/XSDToJavaTestCase.javaFix issues related to fault codes.Fix SOAPEnvelope.getNamespaceURI(String)1.8modifiedtdieslerwebservice/test/java/org/jboss/test/ws/soap/SOAPEnvelopeTestCase.javaFix issues related to fault codes.Fix SOAPEnvelope.getNamespaceURI(String)1.4modifiedtdieslerwebservice/test/java/org/jboss/test/ws/soap/SOAPHeaderTestCase.javaFix issues related to fault codes.Fix SOAPEnvelope.getNamespaceURI(String)1.4modifiedtdieslerwebservice/test/java/org/jboss/test/ws/binding/SOAPBindingTestCase.javaFix issues related to fault codes.Fix SOAPEnvelope.getNamespaceURI(String)1.11modifiedtdieslerwebservice/src/main/org/jboss/ws/soap/MessageFactoryImpl.javaFix issues related to fault codes.Fix SOAPEnvelope.getNamespaceURI(String)1.13modifiedtdieslerwebservice/src/main/org/jboss/ws/soap/SOAPElementImpl.javaFix issues related to fault codes.Fix SOAPEnvelope.getNamespaceURI(String)1.3modifiedtdieslerwebservice/src/main/org/jboss/ws/jaxrpc/FaultException.javaFix issues related to fault codes.Fix SOAPEnvelope.getNamespaceURI(String)1.3modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/fixture/JBossSourceComparator.javaFix missing NOT operator1.9modifiedstarksmsecurity/src/main/org/jboss/security/jacc/DelegatingPolicy.javaInclude the delegate policy ProtectionDomain permissions when building the PermissionCollection in getPermissions(ProtectionDomain). Resolves (JBAS-1526) Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the permissions of the replaced delegate.1.390modifiedstarksmbuild/build.xmlRemove the unused jbossha-httpsession.sar1.32modifiedstarksmcluster/src/etc/cluster-service.xmlExpose all HANamingService attributes by default.1.8modifiedstarksmcluster/src/main/org/jboss/ha/jndi/DetachedHANamingService.javaRemove all local thread creation and instead use the thread pool passed in via the LookupPool. If no LookupPool is specified a BasicThreadPool("HANamingBootstrap Pool") is created. Resolves (JBAS-1558) HAJNDI should use a thread pool.1.5modifiedstarksmcluster/src/main/org/jboss/ha/jndi/DetachedHANamingServiceMBean.javaRemove all local thread creation and instead use the thread pool passed in via the LookupPool. If no LookupPool is specified a BasicThreadPool("HANamingBootstrap Pool") is created. Resolves (JBAS-1558) HAJNDI should use a thread pool.
[JBoss-dev] jboss-3.2 build.309 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050313210337Lbuild.309 BUILD COMPLETE-build.309Date of build:03/13/2005 21:03:37Time to build:23 minutes 16 secondsLast changed:03/13/2005 19:29:33Last log entry:Simply return any throwable seen during the rpc handler method call dispatch as this is the only way to propagate an exception to the caller. Resolves (JBAS-1571) Logging of cluster rpc method exceptions at warn level is incorrect. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(1)1.20.2.25modifiedstarksmcluster/src/main/org/jboss/ha/framework/server/HAPartitionImpl.javaSimply return any throwable seen during the rpc handler method call dispatch as this is the only way to propagate an exception to the caller. Resolves (JBAS-1571) Logging of cluster rpc method exceptions at warn level is incorrect.
[JBoss-dev] jboss-4.0 build.433 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050313215307Lbuild.433 BUILD COMPLETE-build.433Date of build:03/13/2005 21:53:07Time to build:32 minutes 49 secondsLast changed:03/13/2005 20:11:59Last log entry:Remove the obsolete org/jboss/ejb/timer/* classes from the xdoclet build Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(11)1.173.2.8modifiedstarksmserver/build.xmlRemove the obsolete org/jboss/ejb/timer/* classes from the xdoclet build1.7.4.1modifiedstarksmj2ee/src/main/javax/security/jacc/EJBMethodPermission.javaFix the serialVersionUID variable name1.3.6.1modifiedstarksmj2ee/src/main/javax/security/jacc/EJBRoleRefPermission.javaFix the serialVersionUID variable name1.3.2.10modifiedstarksmtools/etc/buildmagic/version-info.xmlUpdate for the 4.0.2RC1 release1.18.2.15modifiedstarksmtools/etc/buildmagic/buildmagic.entUpdate for the 4.0.2RC1 release1.1.2.6modifiedstarksmbuild/docs/readme.htmlUpdate for the 4.0.2RC1 release1.43.2.2modifiedstarksmcluster/src/main/org/jboss/ha/framework/server/HAPartitionImpl.javaUpdate the rpc handler comment1.43.2.1modifiedstarksmcluster/src/main/org/jboss/ha/framework/server/HAPartitionImpl.javaSimply return any throwable seen during the rpc handler method call dispatch as this is the only way to propagate an exception to the caller. Resolves (JBAS-1571) Logging of cluster rpc method exceptions at warn level is incorrect.1.406.2.44modifiedstarksmtestsuite/build.xmlUse the XMLJUnitMultipleResultFormatter to seperate the JACC tests rerun with a security manager.1.3.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/cts/test/MDBInvoker.javaAdd some additional logging of the invoker.1.15.4.2modifiedstarksmtestsuite/src/resources/cts/META-INF/jboss.xmlUpdate the SubclassMDB destination to queue/C as the B queue is used by the cts test client.
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1494) Need to expose the filter list for the default Filter implementation on URLDeploymentScanner
[ http://jira.jboss.com/jira/browse/JBAS-1494?page=history ]
Scott M Stark closed JBAS-1494:
---
Assign To: Scott M Stark
Resolution: Done
Fix Version: JBossAS-4.0.2RC1
JBossAS-5.0 Alpha
A new FilterInstance attribute allows the prefixes, suffixes and matching
strings for the ignored files:
!-- The FilterInstance specifies a URLLister.URLFilter for scanned
directories. This DeploymentFilter is initialized with the given
prefixes, suffixes and matches that define which URLs should be
ignored.
--
attribute name=FilterInstance
attributeClass=org.jboss.deployment.scanner.DeploymentFilter
serialDataType=javaBean
!-- Files starting with theses strings are ignored --
property name=prefixes#,%,\,,.,_$/property
!-- Files ending with theses strings are ignored --
property
name=suffixes#,$,%,.BAK,.old,.orig,.rej,.bak,.sh,\,v,~/property
!-- Files matching with theses strings are ignored --
property
name=matches.make.state,.nse_depinfo,CVS,CVS.admin,RCS,RCSLOG,SCCS,TAGS,core,tags/property
/attribute
Need to expose the filter list for the default Filter implementation on
URLDeploymentScanner
Key: JBAS-1494
URL: http://jira.jboss.com/jira/browse/JBAS-1494
Project: JBoss Application Server
Type: Feature Request
Components: MicroContainer bus
Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
Reporter: Scott M Stark
Assignee: Scott M Stark
Fix For: JBossAS-4.0.2RC1, JBossAS-5.0 Alpha
Adding new patterns of files that the URLDeploymentScanner should ignore
currently requires a custom class implementation. The default Filter
attribute:
!-- The Filter specifies a java.io.FileFilter for scanned
directories. Any file not accepted by this filter will not be
deployed. The org.jboss.deployment.scanner.DeploymentFilter
rejects the following patterns:
#*, %*, ,*, .*, _$*, *#, *$, *%, *.BAK,
*.old, *.orig, *.rej, *.bak, *,v, *~, .make.state,
.nse_depinfo, CVS, CVS.admin, RCS, RCSLOG, SCCS,
TAGS, core, tags
--
attribute
name=Filterorg.jboss.deployment.scanner.DeploymentFilter/attribute
cannot have prefixes and suffixes added without creating a custom filter
implementation. There should be basic support for configuring the
DeploymentFilter using either the javaBean support:
mbean code=org.jboss.test.jmx.complexattrs.ComplexAttrTests
name=test:name=ComplexAttrTests,case=#1
attribute name=Bean2
attributeClass=org.jboss.test.jmx.complexattrs.JavaBean2
serialDataType=javaBean
property name=i12345678/property
property name=f1.23456/property
property name=d3.14159265358979323846/property
property name=l1234567890/property
/attribute
/mbean
or, the under development jbossxb mechanism:
!-- Tell JBossXB about the namespace to factory mappings in this doc --
?jbossxb ns=urn:schema:ns1:jbossxb
factory=org.jboss.test.jmx.complexattrs.JavaBeanObjectModelFactory?
...
!-- Test the jbossxb attribute data type syntax --
mbean code=org.jboss.test.jmx.complexattrs.ComplexAttrTests
name=test:name=ComplexAttrTests,case=#2
attribute name=Bean1
attributeClass=org.jboss.test.jmx.complexattrs.JavaBean1
serialDataType=jbossxb
xmlns:ns1=urn:schema:ns1:jbossxb
ns1:javabean1
property name=bindAddress127.0.0.1/property
property name=someDateSun Jan 2 23:26:49 PST 2005/property
property name=props
prop1=value1
prop2=value2
prop3=${prop3.systemProperty}
/property
property name=namesname1,name2,name3/property
property name=someURLhttp://www.jboss.org/property
/ns1:javabean1
/attribute
/mbean
--
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-1508) JBoss AS needs JSF
[ http://jira.jboss.com/jira/browse/JBAS-1508?page=history ] Scott M Stark updated JBAS-1508: Fix Version: (was: JBossAS-5.0 Beta) (was: JBossAS-4.0.2RC1) (was: JBossPOJOServer-1.0 Alpha) (was: JBossPOJOServer-1.0 Final) JBoss AS needs JSF -- Key: JBAS-1508 URL: http://jira.jboss.com/jira/browse/JBAS-1508 Project: JBoss Application Server Type: Feature Request Components: Web (Tomcat) service Versions: JBossAS-4.0.2RC1, JBossAS-4.0.2 Final, JBossPOJOServer-1.0 Alpha, JBossAS-5.0 Alpha, JBossPOJOServer-1.0 Final, JBossAS-5.0 Beta, JBossAS-5.0 Final, JBossAS-3.2.8 Final Reporter: Stan Silvert Assignee: Stan Silvert Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha, JBossAS-5.0 Final, JBossAS-3.2.8 Final Original Estimate: 1 week Remaining: 1 week JSF support needs to be added to the JBoss AS distribution. Initially, MyFaces will be the implementation chosen. This will probably also include the JSF Car Demo as an example. -- 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: (JBAS-1559) Check all serverSocket accept threads
[ http://jira.jboss.com/jira/browse/JBAS-1559?page=history ] Scott M Stark reassigned JBAS-1559: --- Assign To: Scott M Stark Check all serverSocket accept threads - Key: JBAS-1559 URL: http://jira.jboss.com/jira/browse/JBAS-1559 Project: JBoss Application Server Type: Task Reporter: Adrian Brock Assignee: Scott M Stark Fix For: JBossAS-4.0.2RC1 Check all serverSocket accept threads to ensure there are not paths through the code that could cause the thread to die and the service stop listening. e.g. is java.lang.Throwable being caught, to trap java.lang.Errors? -- 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-1559) Check all serverSocket accept threads
[ http://jira.jboss.com/jira/browse/JBAS-1559?page=history ] Scott M Stark updated JBAS-1559: Fix Version: JBossAS-4.0.2 Final (was: JBossAS-4.0.2RC1) Check all serverSocket accept threads - Key: JBAS-1559 URL: http://jira.jboss.com/jira/browse/JBAS-1559 Project: JBoss Application Server Type: Task Reporter: Adrian Brock Assignee: Scott M Stark Fix For: JBossAS-4.0.2 Final Check all serverSocket accept threads to ensure there are not paths through the code that could cause the thread to die and the service stop listening. e.g. is java.lang.Throwable being caught, to trap java.lang.Errors? -- 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.434 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050313232945Lbuild.434 BUILD COMPLETE-build.434Date of build:03/13/2005 23:29:45Time to build:25 minutes 19 secondsLast changed:03/13/2005 23:19:46Last log entry:Add a FilterInstance attribute that allows one to set the URLFilter instance Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(4)1.32.2.1modifiedstarksmsystem/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.javaAdd a FilterInstance attribute that allows one to set the URLFilter instance1.6.6.1modifiedstarksmsystem/src/main/org/jboss/deployment/scanner/DeploymentFilter.javaAdd getters/setters for suffixes, prefixes and matches.1.6.4.2modifiedstarksmtestsuite/src/main/org/jboss/test/util/test/PropertyEditorsUnitTestCase.javaUpdate the string array tests to test escaped commas.1.6.6.1modifiedstarksmcommon/src/main/org/jboss/util/propertyeditor/StringArrayEditor.javaUpdate to support escaped commas specified using a backslash: \, to incorporate commas in a string element.
[JBoss-dev] jboss-head build.878 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050314001516Lbuild.878 BUILD COMPLETE-build.878Date of build:03/14/2005 00:15:16Time to build:23 minutes 38 secondsLast changed:03/13/2005 23:34:54Last log entry:Replace the Filter attribute with a FilterInstance attribute that allows the ignored prefixes, suffixes and matches. Resolves (JBAS-1494) Need to expose the filter list for the default Filter implementation on URLDeploymentScanner. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(5)1.130modifiedstarksmserver/src/etc/conf/default/jboss-service.xmlReplace the Filter attribute with a FilterInstance attribute that allows the ignored prefixes, suffixes and matches. Resolves (JBAS-1494) Need to expose the filter list for the default Filter implementation on URLDeploymentScanner.1.33modifiedstarksmsystem/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.javaAdd a FilterInstance attribute that allows one to set the URLFilter instance1.7modifiedstarksmsystem/src/main/org/jboss/deployment/scanner/DeploymentFilter.javaAdd getters/setters for suffixes, prefixes and matches.1.8modifiedstarksmtestsuite/src/main/org/jboss/test/util/test/PropertyEditorsUnitTestCase.javaUpdate the string array tests to test escaped commas.1.7modifiedstarksmcommon/src/main/org/jboss/util/propertyeditor/StringArrayEditor.javaUpdate to support escaped commas specified using a backslash: \, to incorporate commas in a string element.
[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-57) Interfaces for accessing JBossCache
[ http://jira.jboss.com/jira/browse/JBCACHE-57?page=history ] Bela Ban updated JBCACHE-57: Fix Version: 1.3 (was: 1.4) Interfaces for accessing JBossCache --- Key: JBCACHE-57 URL: http://jira.jboss.com/jira/browse/JBCACHE-57 Project: JBoss Cache Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 1.3 Original Estimate: 1 week, 3 days Remaining: 1 week, 3 days - Access JBossCache through interfaces, not impl - Factory-based approach, use either TreeCache or TreeCacheAop: factory.createCache(XML file) - How to provide JMX access ? -- 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.435 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050314011322Lbuild.435 BUILD COMPLETE-build.435Date of build:03/14/2005 01:13:22Time to build:24 minutes 52 secondsLast changed:03/13/2005 23:33:18Last log entry:Replace the Filter attribute with a FilterInstance attribute that allows the ignored prefixes, suffixes and matches. Resolves (JBAS-1494) Need to expose the filter list for the default Filter implementation on URLDeploymentScanner. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(1)1.117.2.5modifiedstarksmserver/src/etc/conf/default/jboss-service.xmlReplace the Filter attribute with a FilterInstance attribute that allows the ignored prefixes, suffixes and matches. Resolves (JBAS-1494) Need to expose the filter list for the default Filter implementation on URLDeploymentScanner.
