[JBoss-dev] [Design of JBoss Eclipse IDE (dev)] - JBossIDE 1.4.1 and JBossIDE 1.5 Preview released
The JBossIDE Team is happy to announce the release of both JBossIDE 1.4.1 and JBossIDE 1.5 Preview! JBossIDE 1.4.1 Release Notes: http://sourceforge.net/project/shownotes.php?release_id=300969 Install Doc: HTML: http://docs.jboss.org/jbosside/install/build/en/html/index.html PDF: http://docs.jboss.org/jbosside/install/build/en/pdf/JBossIDE-Installation-1.4.1.pdf Tutorial: HTML: http://docs.jboss.org/jbosside/tutorial/build/en/html/index.html PDF: http://docs.jboss.org/jbosside/tutorial/build/en/pdf/JBossIDE-Tutorial-1.4.1.pdf JBossIDE 1.5 Preview Release Notes: http://sourceforge.net/project/shownotes.php?release_id=300998 See the homepage for links to docs, demos, and what's new with JBossIDE 1.5 Preview. http://www.jboss.com/products/jbosside View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864262#3864262 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864262 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1359) Remove the castor dependency for the snmp adapter, use jbossxb
Remove the castor dependency for the snmp adapter, use jbossxb -- Key: JBAS-1359 URL: http://jira.jboss.com/jira/browse/JBAS-1359 Project: JBoss Application Server Type: Task Environment: varia, snmp adaptor Reporter: Dimitris Andreadis Assigned to: Dimitris Andreadis Priority: Minor Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final The snmp-adaptor uses castor for generating POJO metadata classes, and for parsing its configuration xml files. Replacing this with JBossXB will make it a lot lighter and remove the unecessary castor dependency. -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Admin Console] - Re: New approach for updating Datasource/Drivers via Admin C
If we fall back to the traditional jboss view, then: 1) Invoking on a template for copying static libs into ./lib is not the best way. It'd be more straightforward to have on the DeploymentService something like: | String[] listStaticLibs(); | boolean uploadStaticLib(URL url); | (This doesn't solve the modifications issue, i.e. remove/update a lib) 2) From a design point of view, I believe it's much more clear to the admin to provide him an exact view of the system, it's restrictions and the ability to change it. In this sense you admit that the ./lib directory contains static libs that can only be changed with a reboot. So maybe a better interface is something like: |boolean scheduleLibUpdate(URL url); |boolean scheduleLibRemoval(String libname); | The 2 schedule methods will store the new lib/info for removal somewhere, then the server upon boot will have to make those changes. The thing is, the changes need to take place *before* ./conf/jboss-service.xml is loaded, because this is where the libs are loaded. Maybe we could pass a new arg at command line, e.g. --update-libs to triger this behaviour. In any case we could proceed with (1) and optionally do (2). View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864265#3864265 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864265 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.346 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050130112331Lbuild.346 BUILD COMPLETE-build.346Date of build:01/30/2005 11:23:31Time to build:19 minutes 7 secondsLast changed:01/30/2005 11:13:45Last log entry:- Improve the default configuration so that clustering works in all. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(4)1.355.2.20modifiedremmbuild/build.xml- Improve the default configuration so that clustering works in all.1.1.2.1modifiedremmtomcat/src/resources/jboss-service-all.xml- Improve the default configuration so that clustering works in all.1.3.2.2modifiedremmtomcat/src/resources/jboss-service.xml- Improve the default configuration so that clustering works in all.1.3.2.2modifiedremmtomcat/src/resources/server.xml- Improve the default configuration so that clustering works in all.
[JBoss-dev] jboss-head build.750 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050130114905Lbuild.750 BUILD COMPLETE-build.750Date of build:01/30/2005 11:49:05Time to build:26 minutes 34 secondsLast changed:01/30/2005 11:21:32Last log entry:tests for metadata driven object model factory and xsd binder Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(16)1.4modifiedloubyanskytestsuite/src/main/org/jboss/test/xml/MiscUnitTestCase.javatests for metadata driven object model factory and xsd binder1.4modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/AbstractBasicElementBinding.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/AttributeBinding.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.3modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/BasicElementBinding.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/BindingCursor.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.3modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/DocumentBindingFactory.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.3modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/RuntimeDocumentBinding.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/XsdBinder.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/MetadataDrivenObjectModelFactory.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.5modifiedloubyanskycommon/src/main/org/jboss/xml/binding/SimpleTypeBindings.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.24modifiedloubyanskycommon/src/main/org/jboss/xml/binding/Unmarshaller.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.4modifiedloubyanskycommon/src/main/org/jboss/xml/binding/UnmarshallerImpl.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.384modifiedremmbuild/build.xml- Improve the default configuration so that clustering works in all.1.2modifiedremmtomcat/src/resources/jboss-service-all.xml- Improve the default configuration so that clustering works in all.1.4modifiedremmtomcat/src/resources/jboss-service.xml- Improve the default configuration so that clustering works in all.1.4modifiedremmtomcat/src/resources/server.xml- Improve the default configuration so that clustering works in all.
[JBoss-dev] [ jboss-Bugs-1112731 ] MEMBER OF Bug in SQL92 Compiler
Bugs item #1112731, was opened at 2005-01-30 20:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1112731group_id=22866 Category: JBossCMP Group: v4.0 Status: Open Resolution: None Priority: 5 Submitted By: Jens Bräuer (jensbr) Assigned to: Nobody/Anonymous (nobody) Summary: MEMBER OF Bug in SQL92 Compiler Initial Comment: Hi there ! I was experimenting with dynamic created JBossQL-Queries, when i found what i expect to be a bug. Ok, here some facts about the app i am writing: 2 (for this post relevant) Entity-Beans: - Publication with a 1:M CMR to Author - Author with fields firstName and lastName Writing a method that creates queries on the fly, i found that using the EJBToSQL92Compiler delivers incorrect results. I am searching a Publication written by 2 Authors i know the firstName of. So i expected the query SELECT p.id FROM Publication AS p, Author AS a1, Author AS a2 WHERE (a1.firstName = 'Timo') AND (a1 MEMBER OF p.author) AND ( a2.firstName = 'Jens' ) AND ( a2 MEMBER OF p.author ) to deliver the id of this Publication. This is true for the default compiler, but using the SQL92 one also delivers another Publication in the result. As i do only tests, there are only two entries in the db. I double-checked the database and returning only one Publication would definately be correct. Ok: here is a test-run with the default EJBQL-Compiler: --- [PublicationLocalHome] queryString: SELECT p.id FROM Publication AS p, Author AS a1, Author AS a2 WHERE (a1.firstName = 'Timo') AND (a1 MEMBER OF p.author) AND ( a2.firstName = 'Jens' ) AND ( a2 MEMBER OF p.author ) org.jboss.ejb.plugins.cmp.jdbc.JDBCDynamicQLQuery.Publication#ejbSelectGeneric null - Executing SQL: SELECT t0_p.id FROM PUBLICATION t0_p, AUTHOR t1_a1, AUTHOR t4_a2 WHERE ((t1_a1.firstName = 'Timo') AND (EXISTS (SELECT t3_p_author_RELATION_TABLE.authorId FROM PUBLICATIONAUTHORS t3_p_author_RELATION_TABLE WHERE t0_p.id=t3_p_author_RELATION_TABLE.publicationId AND t1_a1.id=t3_p_author_RELATION_TABLE.authorId)) AND (t4_a2.firstName = 'Jens') AND (EXISTS (SELECT t3_p_author_RELATION_TABLE.authorId FROM PUBLICATIONAUTHORS t3_p_author_RELATION_TABLE WHERE t0_p.id=t3_p_author_RELATION_TABLE.publicationId AND t4_a2.id=t3_p_author_RELATION_TABLE.authorId))) 20:29:44,215 WARN [PublicationLocalHome] result was : [1] 20:29:44,216 WARN [PublicationLocalHome] result class: java.util.ArrayList And here a run using the EJBQLToSQL92Compiler: -- [PublicationLocalHome] queryString: SELECT p.id FROM Publication AS p, Author AS a1, Author AS a2 WHERE (a1.firstName = 'Timo') AND (a1 MEMBER OF p.author) AND ( a2.firstName = 'Jens' ) AND ( a2 MEMBER OF p.author ) org.jboss.ejb.plugins.cmp.jdbc.JDBCDynamicQLQuery.Publication#ejbSelectGeneric null - Executing SQL: SELECT t0_p.id FROM AUTHOR t5_a2, AUTHOR t1_a1, PUBLICATION t0_p WHERE (t1_a1.firstName = 'Timo') AND (EXISTS (SELECT t2_p_local.id FROM PUBLICATION t2_p_local INNER JOIN PUBLICATIONAUTHORS t4_p_author_local_RELATION_TABLE ON t2_p_local.id=t4_p_author_local_RELATION_TABLE.publicationId INNER JOIN AUTHOR t3_p_author_local ON t3_p_author_local.id=t4_p_author_local_RELATION_TABLE.authorId WHERE t1_a1.id=t3_p_author_local.id)) AND (t5_a2.firstName = 'Jens') AND (EXISTS (SELECT t2_p_local.id FROM PUBLICATION t2_p_local INNER JOIN PUBLICATIONAUTHORS t4_p_author_local_RELATION_TABLE ON t2_p_local.id=t4_p_author_local_RELATION_TABLE.publicationId INNER JOIN AUTHOR t3_p_author_local ON t3_p_author_local.id=t4_p_author_local_RELATION_TABLE.authorId WHERE t5_a2.id=t3_p_author_local.id)) 20:35:44,763 WARN [PublicationLocalHome] result was : [1, 2] 20:35:44,766 WARN [PublicationLocalHome] result class: java.util.ArrayList The query is exactly the same in both test-runs, but the result is different. I will supply any descriptors/source/etc needed. Environment is: - JBoss 4.0.1 - included Hypersonic - Java 1.4.2 regards, Jens Braeuer -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1112731group_id=22866 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Refactor the SARDeployer xml parsing
We are limited in our ability to extend the service creation capabilities by the hard coded xml processing of the SARDeployer/ServiceCreator. With the jbossxb framework this can be externalized such that multiple formats of the jboss-service.xml descriptor can be supported and more sophisticated configuration can be applied at every level: attributes, interceptors, ctors, etc. One context to which this applies is the prototype for adding interceptors to subdeployers discussed here: http://www.jboss.org/index.html?module=bbop=viewtopict=57296 The solution promoted there requires every deployer to declare an xmbean deployment with custom interceptors for the deployment interceptors. There should be some deployer specific format which allows for references to a shared interceptor stack along with a jbossxb schema that allows for more extensive configuration of the interceptors and deployers. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864275#3864275 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864275 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ 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: Dynamically Attaching Interceptors to any (X)MBean
There are two problems with this. 1. The LoginConfigInterceptor is not considering operation in an aggregate deployment like an ear that can have multiple login-config.xml descriptors. It would just work if very login-config.xml was distinct, but it will fail if there are overlapping application-policy definitions. One possible mode of operation in the aggregate case would be to merge all login-config.xml descriptors with any conflicts being resolved by taking the application-policy first defined in a breadth-first traversal of the deployment heirarchy. 2. There is no support for a global specification of inteceptor(s) which should be applied to all deployers. This is an aspect of the more general configuration issue raised here: http://www.jboss.org/index.html?module=bbop=viewtopicp=3864275#3864275 View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864276#3864276 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864276 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Admin Console] - Re: New approach for updating Datasource/Drivers via Admin C
A view of the static libs is not an admin view. An admin may not even know that a datasource has a jdbc driver jar. You have to make a distinction between a package and the installation of that package. A package is a self contained collection of descriptors, jars, os libs, etc. that needs to be installed into the server with version and duplication concerns resolved. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864277#3864277 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864277 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-604) housekeeping in ServerImpl and ServerConfigLocator
[ http://jira.jboss.com/jira/browse/JBAS-604?page=history ] Juha Lindfors closed JBAS-604: -- Resolution: Out of Date housekeeping in ServerImpl and ServerConfigLocator -- Key: JBAS-604 URL: http://jira.jboss.com/jira/browse/JBAS-604 Project: JBoss Application Server Type: Bug Versions: JBossAS-3.2.6 Final Reporter: SourceForge User Assignee: Juha Lindfors SourceForge Submitter: rodburgett . This patch addresses housekeeping deficiencies in the org.jboss.system.server.ServerImpl and ServerConfigLocator classes. The ServerConfigLocator class has no shutdown method but it does hold a static reference to an MBeanProxyExt. This reference becomes invalid when the MBeanServer is shutdown. This patch adds a static shutdown method to null out the reference. Code to invoke this new method is added to the shutdown processing in ServerImpl. Several updates are made to the ServerImpl class, some making use of updates to other classes from this and another patch. The dependency on another patch is noted in the change descriptions below. There are two changes to the ServerImpl.shutdown() method: the shutdown hook that was registered with the system runtime during startup is removed, and a null check is added before invoking accessors on the ServerConfig. It makes sense to unregister the shutdown hook when JBoss is shutdown manually. In the situation where JBoss startup/shutdown is controlled by an outside class, this shutdown hook will attempt to repeat the process when the VM exits. Since the init() method will throw an IllegalStateException if it finds a non-null config field, the shutdown process needs to null out this field. That makes it prudent to check for a null value prior to attempting to access methods. Default values for local 'exitOnShutdown' and 'blockingShutdown' flags are taken from ServerConfig when config == null. A few lines of cleanup are added to the ShutdownHook.run() method to null out some ServerImpl fields and to encourage the GC to run. This shutdown() method needs a (config == null) before attempting to find and delete the tmp/deploy directory. A few comments and error literals from the ShutdownHook.shutdownDeployments() and shutdownServices() methods suffered from cut-n-paste lapse, they are corrected in this patch. The ShutdownHook.removeMBeans() method is updated to include a check for non-null mbean server reference. Also, the previous request that the MBeanServerFactory release the current mbean server is replaced with a request to shutdown the mbean registry. The registry shutdown() method is added by JBoss patch #763378, which includes addition of a shutdown method to the MBeanServerImpl. The mbean server shutdown process includes a call to the MBeanSercverFactory.releaseMBeanServer() method. Note that the current patch will cause a run time error - probably UnsupportedMethod - if patch #763378 is not applied before the current patch. Prior to shutting down the registry, a new ShutdownHook method is called to remove any leftover service mbeans. This new method, removeLeftoverMBeans(), queries the mbean server for all registered mbeans and attempts to remove most. This server impl lacks permission to remove mbeans from the 'implementation' domain, so these are skipped, they must be removed by the mbean server. -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design the new POJO MicroContainer] - Re: Convenience or use case configurations
Clarify what you mean by the advanced config option here please: | But this could be worked around by allowing an advanced config option | List beans = EJBDeployment.getBeans(); | //process beans to add config; | EJBDeployment.setBeans(beans); | This convenience config topic is too wide open to grok effectively because its mixing several different layers. Its a variation of the *-ds.xml vs the underlying jboss-service.xml mbeans for the datasource layer, and as such its really intersecting with the admin ui layer. Turing around and discussing how this impacts the type interfaces showing up at the object based kernel metamodel is making a huge leap without any usecases to justify it. Due to the historical tight coupling of xml configuration views with xml parsing showing up in the codebase, I want to be clear that when we discuss configuration using xml fragments that this implies the existence of a jbossxb layer which is handling the actual xml to object transformation. As such, a convience configuration further impiles another layer on top of the jbossxb layer. The layer could just be an xml transformation to the full schema, or it could be another namespace that maps to jbossxb factories that extend the full schema factories. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864279#3864279 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864279 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2-testsuite build.59 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050130145402Lbuild.59 BUILD COMPLETE-build.59Date of build:01/30/2005 14:54:02Time to build:74 minutes 10 secondsLast changed:01/28/2005 20:44:16Last log entry:Create a ServiceContext in the RUNNING state in the preRegister callback so that the ServiceController can be used as a depends target. Resolves [JBAS-1354] Dependency on the ServiceController is broken. Unit Tests: (1936) Total Errors and Failures: (23)testNoClassDefFoundErrororg.jboss.test.classloader.test.BasicLoaderUnitTestCaseunknownorg.jboss.test.jbossmq.test.LargeMessageUnitTestCaseunknownorg.jboss.test.jbossmq.test.OILConnectionUnitTestCasetestQueueMessageOrderorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestRequestReplyQueueorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTemporaryQueueDeleteorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTemporaryTopicDeleteorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestInvalidDestinationQueueSendorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestInvalidDestinationQueueBrowseorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestInvalidDestinationTopicPublishorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestErrorsTopicSubscribeorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestCreateQueueorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestMessageListenerorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestApplicationServerStufforg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicsorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicNoLocalorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicNoLocalBounceorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicSelectorChangeorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicSelectorNullOrEmptyorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSendReceiveOutdatedorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSendReceiveExpiredorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSendListenOutdatedorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCase Modifications since last build:(2)1.18.2.20modifiedstarksmsystem/src/main/org/jboss/system/ServiceController.javaCreate a ServiceContext in the RUNNING state in the preRegister callback so that the ServiceController can be used as a depends target. Resolves [JBAS-1354] Dependency on the ServiceController is broken.1.1.2.6modifiedstarksmserver/src/main/org/jboss/proxy/GenericProxyFactory.javaCreate a ClientContainerEx if the proxy interceptor list includes the org.jboss.proxy.IClientContainer so that the proxy handler has an implementation for the IClientContainer methods. Resolves [JBAS-1352] Generalized detached invoker proxy factory handling of IClientContainer.
[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-37) Stack Overflow when using Collection classes in TreeCacheAop
[ http://jira.jboss.com/jira/browse/JBCACHE-37?page=comments#action_12315062 ] Ben Wang commented on JBCACHE-37: - Andrew, I have checked in a CacheObjectMBeanUnitTestCase under jboss-head/testsuite/src/main/org/jboss/test/cache/test/aop directory. I have a bind method and do a look up of MBeanServer like you did (in cache/bean directory). However, I can't reproduce the error! Did you ever try your test case under jboss-head build? You can wait for 24 hours to check out the source and see for yourself. Let me know what you find. Meanwhile, I will ask Aop team to see if they see anything wrong on the aop lib. -Ben Stack Overflow when using Collection classes in TreeCacheAop Key: JBCACHE-37 URL: http://jira.jboss.com/jira/browse/JBCACHE-37 Project: JBoss Cache Type: Bug Versions: 1.2 Environment: JBoss 4.0.1, JDK 1.5 (and also 1.4.2), Linux (Mandrake 10.0) Reporter: Andrew May Assignee: Ben Wang Fix For: 1.2.1 Attachments: cachetest.jar, cachetest.zip, jboss-aop.xml, project.zip, treeCacheAop-service.xml Stack overflow when calling TreeCacheAop.putObject(Fqn, Object) for an aspectized object that contains a Collection class (tested with HashSet, ArrayList and HashMap): Thread [http-0.0.0.0-7001-Processor25] (Suspended (exception java.lang.StackOverflowError)) org.jboss.aop.deployment.JBossClassPool(javassist.ClassPool).toClass(javassist.CtClass) line: 713 ... org.jboss.aop.deployment.JBossClassPool.toClass(javassist.CtClass, java.lang.ClassLoader) line: 50 org.jboss.aop.deployment.JBossClassPool(javassist.ClassPool).toClass(javassist.CtClass) line: 713 org.jboss.aop.deployment.JBossClassPool.toClass(javassist.CtClass, java.lang.ClassLoader) line: 50 org.jboss.aop.deployment.JBossClassPool(javassist.ClassPool).toClass(javassist.CtClass) line: 713 org.jboss.aop.deployment.JBossClassPool.toClass(javassist.CtClass, java.lang.ClassLoader) line: 50 javassist.CtNewClass(javassist.CtClass).toClass() line: 1000 org.jboss.aop.proxy.ClassProxyFactory.generateProxy(java.lang.Class) line: 138 org.jboss.aop.proxy.ClassProxyFactory.newInstance(java.lang.Class) line: 52 org.jboss.cache.aop.CollectionInterceptorUtil.getMethodMap(java.lang.Class) line: 50 org.jboss.cache.aop.CachedSetInterceptor.init(org.jboss.cache.aop.TreeCacheAop, org.jboss.cache.Fqn, java.lang.Class) line: 41 org.jboss.cache.aop.TreeCacheAop._putObject(org.jboss.cache.Fqn, java.lang.Object) line: 372 org.jboss.cache.aop.TreeCacheAop._putObject(org.jboss.cache.Fqn, java.lang.Object) line: 265 org.jboss.cache.aop.TreeCacheAop.putObject(org.jboss.cache.Fqn, java.lang.Object) line: 130 Originally this was happening within our application, but I've managed to write a simple test bean that demonstrates the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design the new POJO MicroContainer] - Re: Deployers overview
This is the common behavior mode when there is aggregation: anonymous wrote : | The use case I can think of where coupling of metadata is required is when the classloader metadata is constructed. Each subdeployment can add metadata (urls) to the top level metadata that creates the classloader. | | This is probably the more common pattern. i.e. Each subdeployment builds up metadata (e.g. urls) at the top level which is processed last and adds global policy (e.g. classloader isolation, java2 delegation, etc.) | A given deployment is likely to have configuration of an aspect that needs to be merged into the aggregate view when the deployment is joined to other deployments. In addition to class loading, logging and security are two more examples of aspects that should have an aggregate metadata and behavior. Its also non-deterministic as to what the aggregate behavior should be. In the case of logging it may be that the independent logging configurations should be left as is. An equally valid view is that the logging configuration seen at the root most level takes precedence. Likewise how the merged security aspect should behave is arbitrary. It can be anything from independent untrusted domains to a global override from the root, to federated domains that have to arrange migration of security contexts based on trust relationships that are described by metadata that has no meaning in absence of aggregation. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864280#3864280 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864280 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design the new POJO MicroContainer] - Re: VDFComponent
Another attribute missing in the VDFComponent is the notion of attributes. The current LastModified is a read-only attribute and Context is a read-write attribute. A generic DirContext like notion of attributes should be available. The DeploymentContext is missing an arbitrary context map that existed in the DeploymentInfo. This is something that is used by the current deployers for shared state. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864282#3864282 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864282 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design the new POJO MicroContainer] - Re: JARDeployer
I don't see that the JARDeployer has any reason for existence. If there is referenced content that has no associated deployer it should not just be added to some classpath. The configuration of the class and resource paths is an aspect of some deployment. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864283#3864283 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864283 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBIDE-115) Differentiate icons for fork/join
Differentiate icons for fork/join - Key: JBIDE-115 URL: http://jira.jboss.com/jira/browse/JBIDE-115 Project: JBoss IDE Type: Feature Request Components: jBPM Designer plugin Versions: 1.5 alpha Environment: JBossIDE 1.5 Preview JRE 1.5 Reporter: Juha Lindfors Assigned to: Koen Aers Priority: Minor The fork and join nodes should have visually slightly different icons. I was shifting some nodes around in the designer and ended up placing a join node where I wanted a fork node. Designer correctly did not allow me to add more than one outgoing transition from a join which was very confusing since I thought I was handling a fork node (since there was no visual cue as to which is which as the icons are identical -- very perplexing). A simple +/- signs or similar to match fork/join node pairs would be sufficient to avoid such mix-ups with the designer icons. -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design the new POJO MicroContainer] - Re: Keep STARTUP notification
The more generic issue here is that there is often the desire to have a dependency on a collection of services with some quality. Examples include: Services with network endpoints Services which interact with the filesystem access Services which write to the filesystem Its not always that there should be a true start/stop type of dependency on the services. If there was a snapshot service which periodically backedup the contents of serveral directories when the filesystem had no active writers, its not that the services which wrote to the filesystem need to be stopped. They simply need to be in a state that has no writers. Its more of a lock the snapshot service wishes to acquire and will wait until its notified that its the sole holder of the lock. The problem with trying to introduce this notion is that services are not generally written with sufficient granularity to allow facets of their behavior to be micromanged. The existing JNDI service and a desire to control when network interfaces are established is an example. The JNDI service can operation fine without an external interface, but the way its coded today, if it were to depend on a network interface barrier service to delay the creation of its remote JNDI access endpoint, the local operation mode would also be unavailable and the server startup would fail horribly as numerous services failed to access JNDI via the default InitialContext. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864284#3864284 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864284 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.751 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050130165452Lbuild.751 BUILD COMPLETE-build.751Date of build:01/30/2005 16:54:52Time to build:18 minutes 14 secondsLast changed:01/30/2005 16:28:21Last log entry:Used different JGroups ports Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(9)1.3modifiedbwang00testsuite/src/resources/cache/META-INF/tree-aop-service.xmlUsed different JGroups ports1.7modifiedbwang00testsuite/src/resources/cache/META-INF/tree-service.xmlUsed different JGroups ports1.1addedbwang00testsuite/src/main/org/jboss/test/cache/test/aop/CacheObjectMBeanUnitTestCase.javaRenamed CacheObjectUnitAopTest to CacheObjectMBeanUnitTestCase1.2deletedbwang00testsuite/src/main/org/jboss/test/cache/test/aop/CacheObjectUnitAopTest.javaRenamed CacheObjectUnitAopTest to CacheObjectMBeanUnitTestCase1.1addedbwang00testsuite/src/main/org/jboss/test/cache/test/standAloneAop/CacheObject.javaAdded a new test case1.1addedbwang00testsuite/src/main/org/jboss/test/cache/test/aop/CacheObjectUnitAopTest.javaAdded a new test case1.1addedbwang00testsuite/src/main/org/jboss/test/cache/bean/CacheObjectMeanTesterBean.javaAdded a new test case1.9modifiedbwang00testsuite/src/resources/cache/standalone/META-INF/jboss-aop.xmlUpdated1.8modifiedbwang00testsuite/src/resources/cache/standalone/META-INF/jboss-aop.xmlAdded ObjectCach
[JBoss-dev] [JBoss JIRA] Updated: (EJBTHREE-60) Write plugin interface for persistence manager
[ http://jira.jboss.com/jira/browse/EJBTHREE-60?page=history ] Bill Burke updated EJBTHREE-60: --- Description: Abstract out persistence so that a thirdparty persistence manager can be plugged into JBoss' EJB3 implementation (was: ) Write plugin interface for persistence manager -- Key: EJBTHREE-60 URL: http://jira.jboss.com/jira/browse/EJBTHREE-60 Project: EJB 3.0 Type: Feature Request Versions: Preview 5 Reporter: Bill Burke Assignee: Bill Burke Fix For: Preview 5 Abstract out persistence so that a thirdparty persistence manager can be plugged into JBoss' EJB3 implementation -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-60) Write plugin interface for persistence manager
Write plugin interface for persistence manager -- Key: EJBTHREE-60 URL: http://jira.jboss.com/jira/browse/EJBTHREE-60 Project: EJB 3.0 Type: Feature Request Versions: Preview 5 Reporter: Bill Burke Assigned to: 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: timed expiry
Our design of eviction policy is not based on per-node basis. Rather it is per-region. Nonetheless to create *roughly* what you want to achieve, it still can be done through the current eviction policy framework. Couple things need to happen though: 1. Region parameters will need to be configure dynamically. So you work with a Region still. Now it is still through configured thorugh xml. But we do have plan to add it later. See http://jira.jboss.com/jira/browse/JBCACHE?report=com.atlassian.jira.plugin.system.project:roadmap-panel for the roadmap. 2. Write an eviction policy that ignores any node modification event and evict based on time. If you want to contribute this piece of code, let me know. -Ben View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864285#3864285 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864285 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: Session Replication using JBossCache
Yes, you can. But keep in mind that Tomcat seems to have its own persistency framework. I haven't looked into it fully yet. -Ben View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864286#3864286 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864286 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: NullPointerException: TreeCache.put
You will need to supply the JBossCache version. There is little information in your posting to see what's going on. -Ben View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864287#3864287 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864287 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: Cache deadlock problem when using TreeCache as 2LC for h
Can you enable this in Hibernate to see if that solves the problem: hibernate.cache.use_minimal_puts Gavin and I have had a discussion on the potential problem. That, when using query cache, Hibernate will do a put on the JBossCache while retrieving from db. This can cause a long lock that resulting in TimeoutException. If this were the case, we will need to provide a way to get around this. -Ben View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864288#3864288 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864288 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ 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.43 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050130174537Lbuild.43 BUILD COMPLETE-build.43Date of build:01/30/2005 17:45:37Time to build:48 minutes 43 seconds Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(0)
[JBoss-dev] [Design of JBoss Admin Console] - Re: New approach for updating Datasource/Drivers via Admin C
[EMAIL PROTECTED] wrote : If we fall back to the traditional jboss view, then: | | 1) Invoking on a template for copying static libs into ./lib is not the best way. It'd be more straightforward to have on the DeploymentService something like: | | | String[] listStaticLibs(); | | boolean uploadStaticLib(URL url); | | | | (This doesn't solve the modifications issue, i.e. remove/update a lib) | I am fine with which either implementing this as a template or new API on DeploymentSerivce, as long as the functionality requirements are met [EMAIL PROTECTED] wrote : 2) From a design point of view, I believe it's much more clear to the admin to provide him an exact view of the system, it's restrictions and the ability to change it. In this sense you admit that the ./lib directory contains static libs that can only be changed with a reboot. So maybe a better interface is something like: | | |boolean scheduleLibUpdate(URL url); | |boolean scheduleLibRemoval(String libname); | | | The 2 schedule methods will store the new lib/info for removal somewhere, then the server upon boot will have to make those changes. | | The thing is, the changes need to take place *before* ./conf/jboss-service.xml is loaded, because this is where the libs are loaded. | | Maybe we could pass a new arg at command line, e.g. --update-libs to triger this behaviour. | | In any case we could proceed with (1) and optionally do (2). | Agreed lets do (1). For the first phase we will not be requiring any removal or update of jars from /lib, so let's not do (2). Overall the datasource component of the admin console will attempt to abstract away some of the details of the implementation. An administrator will optionally specify a driver jar to upload and some datasource properties, without having to know precisely what we are going to do with that jar. In future versions I hope that we will be able to move away from copying the driver jars into /lib, without affecting how administrators use the console. Thanks View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864289#3864289 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864289 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050130190046 BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jboss-head.xml:66: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See tests.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build:01/30/2005 19:00:46Time to build:92 minutes 25 secondsLast changed:01/30/2005 11:13:45Last log entry:- Improve the default configuration so that clustering works in all. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(86)1.355.2.20modifiedremmbuild/build.xml- Improve the default configuration so that clustering works in all.1.1.2.1modifiedremmtomcat/src/resources/jboss-service-all.xml- Improve the default configuration so that clustering works in all.1.3.2.2modifiedremmtomcat/src/resources/jboss-service.xml- Improve the default configuration so that clustering works in all.1.3.2.2modifiedremmtomcat/src/resources/server.xml- Improve the default configuration so that clustering works in all.1.3.2.6modifiedvietjtomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javabug fix : JBAS-1358 - Tomcat session replication breaks if there is already an active transaction1.8.6.1modifiedstarksmconsole/src/main/org/jboss/console/plugins/helpers/AbstractPluginWrapper.javaGuard against NPE during shutdown when the plugin manager was not initialized1.45.2.3modifiedstarksmsystem/src/main/org/jboss/system/ServiceController.javaCreate a ServiceContext in the RUNNING state in the preRegister callback so that the ServiceController can be used as a depends target. Resolves [JBAS-1354] Dependency on the ServiceController is broken.1.25.2.2modifiedejortconnector/src/main/org/jboss/resource/connectionmanager/TxConnectionManager.javaPort delist fix from 3.2.x1.64.2.4modifiedejortserver/src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java[JBAS-1356] Fix typo in activation config parsing subscriptionDurablity - subscriptionDurability1.35.2.1modifiedejortjboss.net/.classpathFix the eclipse build1.8.4.1modifiedejorttomcat/.classpathFix the eclipse build1.10.6.2modifiedejortsecurity/src/main/org/jboss/security/srp/SRPRemoteServer.javaThis exception can no longer be thrown.1.1.2.1modifiedremmtomcat/src/resources/context.xml- Update JBoss 4.0 branch to Tomcat 5.5.7.1.1.1.1.16.1deletedremmtomcat/src/resources/jboss-mbeans.xml- Update JBoss 4.0 branch to Tomcat 5.5.7.1.14.2.3deletedremmtomcat/src/resources/jboss-service-50.xml- Update JBoss 4.0 branch to Tomcat 5.5.7.1.3.2.1modifiedremmtomcat/src/resources/jboss-service.xml- Update JBoss 4.0 branch to Tomcat 5.5.7.1.16.2.3deletedremmtomcat/src/resources/server-50.xml- Update JBoss 4.0 branch to Tomcat 5.5.7.1.3.2.1modifiedremmtomcat/src/resources/server.xml- Update JBoss 4.0 branch to Tomcat 5.5.7.1.1.1.1.16.1deletedremmtomcat/src/main/org/jboss/web/tomcat/Log4jLogger.java- Update JBoss 4.0 branch to Tomcat 5.5.7.1.1.6.1deletedremmtomcat/src/main/org/jboss/web/tomcat/mbean-descriptors.xml- Update JBoss 4.0 branch to Tomcat 5.5.7.1.2.2.3modifiedremmtomcat/src/resources/tc5-cluster-service.xml- Update JBoss 4.0 branch to Tomcat 5.5.7.1.4.2.1modifiedremmtomcat/src/resources/web.xml- Update JBoss 4.0 branch to Tomcat 5.5.7.1.4.2.1modifiedremmtomcat/src/main/org/jboss/web/tomcat/tc5/sso/ClusteredSingleSignOn.java- Update JBoss 4.0 branch to Tomcat 5.5.7.1.3.2.3modifiedremmtomcat/src/main/org/jboss/web/tomcat/tc5/session/AttributeBasedClusteredSession.java- Update JBoss 4.0 branch to Tomcat 5.5.7.1.5.2.3modifiedremmtomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.java- Update JBoss 4.0 branch to Tomcat 5.5.7.1.1.2.2modifiedremmtomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSessionCMP.java- Update JBoss 4.0 branch to Tomcat 5.5.7.1.4.2.1modifiedremmtomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSessionValve.java- Update JBoss 4.0 branch to Tomcat 5.5.7.1.4.2.2modifiedremmtomcat/src/main/org/jboss/web/tomcat/tc5/session/InstantSnapshotManager.java- Update JBoss 4.0 branch to Tomcat 5.5.7.1.4.2.2modifiedremmtomcat/src/main/org/jboss/web/tomcat/tc5/session/IntervalSnapshotManager.java- Update JBoss 4.0 branch to Tomcat 5.5.7.1.3.2.5modifiedremmtomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.java- Update JBoss 4.0 branch to Tomcat 5.5.7.1.3.2.3modifiedremmtomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.java- Update JBoss 4.0 branch to Tomcat 5.5.7.1.5.2.4modifiedremmtomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossManager.java- Update JBoss 4.0 branch to Tomcat 5.5.7.1.1.2.2modifiedremmtomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossManagerCMP.java- Update JBoss 4.0 branch to Tomcat
[JBoss-dev] jboss-4.0-jdk-matrix build.76 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050130212643Lbuild.76 BUILD COMPLETE-build.76Date of build:01/30/2005 21:26:43Time to build:23 minutes 45 secondsLast changed:01/30/2005 11:13:45Last log entry:- Improve the default configuration so that clustering works in all. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(5)1.355.2.20modifiedremmbuild/build.xml- Improve the default configuration so that clustering works in all.1.1.2.1modifiedremmtomcat/src/resources/jboss-service-all.xml- Improve the default configuration so that clustering works in all.1.3.2.2modifiedremmtomcat/src/resources/jboss-service.xml- Improve the default configuration so that clustering works in all.1.3.2.2modifiedremmtomcat/src/resources/server.xml- Improve the default configuration so that clustering works in all.1.3.2.6modifiedvietjtomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javabug fix : JBAS-1358 - Tomcat session replication breaks if there is already an active transaction
[JBoss-dev] jboss-head-testsuite build.11 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite?log=log20050130222507Lbuild.11 BUILD COMPLETE-build.11Date of build:01/30/2005 22:25:07Time to build:93 minutes 6 secondsLast changed:01/30/2005 16:28:21Last log entry:Used different JGroups ports Unit Tests: (2394) Total Errors and Failures: (60)unknownorg.jboss.test.bank.test.BankEJB20StressTestCasetestAllTx_RWLockorg.jboss.test.cache.stress.EvictionLocalStressTestCasetestBindingorg.jboss.test.cache.test.aop.CacheObjectMBeanUnitTestCasetestEntityIdentityorg.jboss.test.cts.test.LocalEjbTestCase(UnifiedInvoker)testAllCompleteOrFailCMRorg.jboss.test.deadlock.test.BeanStressTestCasetestEjbInterceptionorg.jboss.test.hibernate.test.HibernateIntgUnitTestCasetestClientContainerorg.jboss.test.invokers.test.MultiInvokersUnitTestCasetestStatefulCreateCallerorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestGetCallerPrincipalorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestPrincipalPropagationorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestMethodAccessorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestDomainMethodAccessorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestMethodAccess2org.jboss.test.jacc.test.EJBSpecUnitTestCasetestLocalMethodAccessorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestUncheckedRemoteorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestRemoteUncheckedorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestUncheckedorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestUncheckedWithLoginorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestExcludedorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestRunAsorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestDeepRunAsorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestHandleorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestStatefulHandleorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestClientLoginServletorg.jboss.test.jacc.test.WebIntegrationUnitTestCasetestSecureEJBAccessorg.jboss.test.jacc.test.WebIntegrationUnitTestCasetestUnsecureAnonEJBAccessorg.jboss.test.jacc.test.WebIntegrationUnitTestCasetestUnsecureRunAsServletorg.jboss.test.jacc.test.WebIntegrationUnitTestCasetestUnsecureRunAsServletWithPrincipalNameorg.jboss.test.jacc.test.WebIntegrationUnitTestCasetestUnsecureRunAsServletWithPrincipalNameAndRolesorg.jboss.test.jacc.test.WebIntegrationUnitTestCasetestOIL2MutliSessionOneConnectionorg.jboss.test.jbossmq.perf.OIL2InvocationLayerStressTestCaseunknownorg.jboss.test.jbossmq.test.LargeMessageUnitTestCaseunknownorg.jboss.test.jbossmq.test.OILConnectionUnitTestCasetestUnsharedConnectionorg.jboss.test.jca.test.UnsharedConnectionUnitTestCasetestCreateSubcontextorg.jboss.test.naming.test.PooledInvokerUnitTestCasetestLookupFailuresorg.jboss.test.naming.test.PooledInvokerUnitTestCasetestClientSessionorg.jboss.test.perf.test.PerfStressTestCasetestClientSessionorg.jboss.test.perf.test.SecurePerfStressTestCasetestOldProxyorg.jboss.test.pooled.test.BeanStressTestCasetestUnsecureRunAsServletorg.jboss.test.securitymgr.test.WebIntegrationUnitTestCasetestUnsecureRunAsServletorg.jboss.test.web.test.WebIntegrationUnitTestCasetestHttpRedirectorg.jboss.test.web.test.ssl.SSLUnitTestCasetestHttpsorg.jboss.test.web.test.ssl.SSLUnitTestCasewarningorg.jboss.test.cts.test.ClientCallbackImpl(UnifiedInvoker)warningorg.jboss.test.cts.test.MDBInvoker(UnifiedInvoker)testPoolingorg.jboss.test.cts.test.MDBUnitTestCase(UnifiedInvoker)testPoolingorg.jboss.test.cts.test.MDBUnitTestCasewarningorg.jboss.test.cts.test.SessionInvoker(UnifiedInvoker)testMDBRunAsorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestRunAsWithRolesorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestStressorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestStressNoJaasCacheorg.jboss.test.jacc.test.EJBSpecUnitTestCasetestUserInRoleServletorg.jboss.test.jacc.test.WebIntegrationUnitTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCasetestPoolingorg.jboss.test.securitymgr.test.MDBUnitTestCasetestUserInRoleServletorg.jboss.test.securitymgr.test.WebIntegrationUnitTestCasetestMDBTimerorg.jboss.test.timer.test.BasicTimerUnitTestCasetestJBossEditorsorg.jboss.test.util.test.PropertyEditorsUnitTestCasetestFormAuthSingleSignOnorg.jboss.test.web.test.ClusteredSingleSignOnUnitTestCase(tomcat-sso-cluster)testFormAuthSingleSignOnorg.jboss.test.web.test.SingleSignOnUnitTestCasetestUserInRoleServletorg.jboss.test.web.test.WebIntegrationUnitTestCase Modifications since last build:(25)1.3modifiedbwang00testsuite/src/resources/cache/META-INF/tree-aop-service.xmlUsed different JGroups ports1.7modifiedbwang00testsuite/src/resources/cache/META-INF/tree-service.xmlUsed different JGroups ports1.1addedbwang00testsuite/src/main/org/jboss/test/cache/test/aop/CacheObjectMBeanUnitTestCase.javaRenamed CacheObjectUnitAopTest to
[JBoss-dev] jboss-head-jdk-matrix build.70 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050131002031Lbuild.70 BUILD COMPLETE-build.70Date of build:01/31/2005 00:20:31Time to build:21 minutes 29 secondsLast changed:01/30/2005 16:28:21Last log entry:Used different JGroups ports Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(25)1.3modifiedbwang00testsuite/src/resources/cache/META-INF/tree-aop-service.xmlUsed different JGroups ports1.7modifiedbwang00testsuite/src/resources/cache/META-INF/tree-service.xmlUsed different JGroups ports1.1addedbwang00testsuite/src/main/org/jboss/test/cache/test/aop/CacheObjectMBeanUnitTestCase.javaRenamed CacheObjectUnitAopTest to CacheObjectMBeanUnitTestCase1.2deletedbwang00testsuite/src/main/org/jboss/test/cache/test/aop/CacheObjectUnitAopTest.javaRenamed CacheObjectUnitAopTest to CacheObjectMBeanUnitTestCase1.1addedbwang00testsuite/src/main/org/jboss/test/cache/test/standAloneAop/CacheObject.javaAdded a new test case1.1addedbwang00testsuite/src/main/org/jboss/test/cache/test/aop/CacheObjectUnitAopTest.javaAdded a new test case1.1addedbwang00testsuite/src/main/org/jboss/test/cache/bean/CacheObjectMeanTesterBean.javaAdded a new test case1.9modifiedbwang00testsuite/src/resources/cache/standalone/META-INF/jboss-aop.xmlUpdated1.8modifiedbwang00testsuite/src/resources/cache/standalone/META-INF/jboss-aop.xmlAdded ObjectCach1.4modifiedloubyanskytestsuite/src/main/org/jboss/test/xml/MiscUnitTestCase.javatests for metadata driven object model factory and xsd binder1.4modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/AbstractBasicElementBinding.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/AttributeBinding.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.3modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/BasicElementBinding.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/BindingCursor.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.3modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/DocumentBindingFactory.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.3modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/RuntimeDocumentBinding.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/XsdBinder.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/MetadataDrivenObjectModelFactory.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.5modifiedloubyanskycommon/src/main/org/jboss/xml/binding/SimpleTypeBindings.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.24modifiedloubyanskycommon/src/main/org/jboss/xml/binding/Unmarshaller.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.4modifiedloubyanskycommon/src/main/org/jboss/xml/binding/UnmarshallerImpl.javaadded AttributeBinding metadata, metadata driven ObjectModelFactory impl, xsd binder that reads xsd and creates binding metadata1.384modifiedremmbuild/build.xml- Improve the default configuration so that clustering works in all.1.2modifiedremmtomcat/src/resources/jboss-service-all.xml- Improve the default configuration so that clustering works in all.1.4modifiedremmtomcat/src/resources/jboss-service.xml- Improve the default configuration so that clustering works in all.1.4modifiedremmtomcat/src/resources/server.xml- Improve the default configuration so that clustering works in all.
[JBoss-dev] [Design of JBoss Portal] - Re: Postgresql setup
I have the same problem as you have. And I want to know the reason too. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864290#3864290 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864290 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1358) Tomcat session replication breaks if there is already an active transaction
[ http://jira.jboss.com/jira/browse/JBAS-1358?page=comments#action_12315067 ] Ben Wang commented on JBAS-1358: Julien, Thanks for fixing this clustering related bug. Just curious though. How did you discover this bug? I thought when httprequest is called by the container, it will have no associated active tx since this is web that we are talking about? BTW, have you applied change to head as well? -Ben Tomcat session replication breaks if there is already an active transaction --- Key: JBAS-1358 URL: http://jira.jboss.com/jira/browse/JBAS-1358 Project: JBoss Application Server Type: Bug Components: Clustering Versions: JBossAS-4.0.2RC1, JBossAS-4.0.2 Final Environment: the all configuration Reporter: Julien Viet Assignee: Julien Viet Fix For: JBossAS-4.0.2RC1, JBossAS-4.0.2 Final Original Estimate: 4 hours Remaining: 4 hours When an active transaction is running the session replication breaks. It uses javax.transaction.UserTransaction to begin/commit to wrap the jboss cache replication. This breaks when a transaction is already active. The solution is to use the transaction manager instead of user transaction and suspend/resume any incoming transaction before/after the session replication occurs. -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1360) session unbound event not fired
session unbound event not fired --- Key: JBAS-1360 URL: http://jira.jboss.com/jira/browse/JBAS-1360 Project: JBoss Application Server Type: Bug Components: Clustering Versions: JBossAS-3.2.6 Final Reporter: Ben Wang Assigned to: Ben Wang Fix For: JBossAS-3.2.8 Final When using http session replication, session attribute unbound event is not fired. -- 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 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - new release already old?
Hi, I just wanna start to evaluate the Portal, but unfortunately there is no way, to get it compiled and thus to test :(. Digging around, I saw, that the build system enforces target 1.2 and source 1.3 ! Why? I thought, this is a new major release ? Are there any reasons, why you force people and yourself to outdated (antique) Java versions? IMHO since it is (at least according to announcements) a complete rewrite of Nukes, why are you not using all the nice features comming with tiger aka JDK 1.5 and really get rid of the old limitations ? Even JBoss AS compiles with 1.5 without any problems (ok, sometimes target 1.4 is used - I guess because of unfixed thirdparty software - however, that's still better than the other ancient stuff) BTW2: Is there any reason to force people to use the outdated version of ant ? Or is this just introduced due to the scary/limited build system used ? Regards, jens. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864295#3864295 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864295 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - exceptions when tried to List of all the users
there was an exception when i login as admin and tried to do List of all the users Caused by: java.sql.SQLException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '? '%' limit ?' at line 1 How can i solve this prob? thanks! btw, i'm using JBoss 4.0.1 with portal 2.0 alpha, thanx! View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3864297#3864297 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3864297 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
