[JBoss-dev] jboss-4.0 Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050329015143 BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build:03/29/2005 01:51:43Time to build:36 minutes 39 secondsLast changed:03/28/2005 21:44:55Last log entry:Another fix for JBAS-1622 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(57)1.3.2.11modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaAnother fix for JBAS-16221.15.4.3modifiedstarksmtestsuite/src/resources/cts/META-INF/ejb-jar.xmlAdd the personsAge field1.7.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/cts/ejb/CtsCmpBean.javaAdd the personsAge field1.12.6.1modifiedanddsystem/src/main/org/jboss/system/server/ServerInfo.javaJBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really.1.5.2.6modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaFixed sm getString message1.3.2.10modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaJBAS-1622 findSessions api wasn't correct1.3.2.8modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaJBAS-1622 findSessions api wasn't correct1.406.2.48modifiedovidiuftestsuite/build.xmltests-clustering-all-stacks generates different test report sets for each stack configuration1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-coyote.jar- Update to Tomcat 5.5.9.1.5.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-http.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-util.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/naming-resources.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-cgi.renametojar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-default.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-invoker.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-ssi.renametojar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-webdav.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-ajp.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/jasper-runtime.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/jasper-compiler.jar- Update to Tomcat 5.5.9.1.1.2.4modifiedremmthirdparty/apache-tomcat55/jasper-compiler-jdt.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina-manager.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina-optional.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina.jar- Update to Tomcat 5.5.9.1.2.2.5modifiedremmthirdparty/apache-tomcat55/README- Update to Tomcat 5.5.9.1.2.8.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsMessageConsumer.java[JBAS-1604] - Make a start on the JMSRA trace logging1.10.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSession.java[JBAS-1604] - Make a start on the JMSRA trace logging1.11.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.java[JBAS-1604] - Make a start on the JMSRA trace logging1.8.2.1modifiedstarksmserver/src/main/org/jboss/tm/usertx/client/ClientUserTransaction.javaUse the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.1.8.6.1modifiedejortconnector/src/main/org/jboss/resource/deployment/RARDeployment.java[JBAS-1446] - Add trace logging for rar deployment operations1.3.4.2modifiedejortconnector/src/main/org/jboss/resource/deployment/ActivationSpecFactory.java[JBAS-1446] - Add trace logging to activation spec construction1.1.2.3modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObject.java[JBAS-1446] - Add TRACE logging to AdminObject construction.1.1.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObjectFactory.java[JBAS-1446] - Add TRACE logging to
[JBoss-dev] [JBoss JIRA] Closed: (JBPM-100) renamed JbpmSchemaMgr to JbpmSchema
[ http://jira.jboss.com/jira/browse/JBPM-100?page=history ] Tom Baeyens closed JBPM-100: Resolution: Done renamed JbpmSchemaMgr to JbpmSchema --- Key: JBPM-100 URL: http://jira.jboss.com/jira/browse/JBPM-100 Project: JBoss jBPM Type: Task Components: Core Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Priority: Minor Fix For: jBPM 3.0 alpha 3 to be in sync with the identity module that is under development -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPM-100) renamed JbpmSchemaMgr to JbpmSchema
renamed JbpmSchemaMgr to JbpmSchema --- Key: JBPM-100 URL: http://jira.jboss.com/jira/browse/JBPM-100 Project: JBoss jBPM Type: Task Components: Core Engine Reporter: Tom Baeyens Assigned to: Tom Baeyens Priority: Minor Fix For: jBPM 3.0 alpha 3 to be in sync with the identity module that is under development -- 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: (JBPORTAL-224) Forum user's preferences
[ http://jira.jboss.com/jira/browse/JBPORTAL-224?page=comments#action_12316465 ] Julien Viet commented on JBPORTAL-224: -- define a set or preferences that modify the behaviour of the forums that the user can override to personnalize it. like - how many topic per page - how many post per page - what is the reading direction of the posts : old post to young post or the reverse etc... Forum user's preferences Key: JBPORTAL-224 URL: http://jira.jboss.com/jira/browse/JBPORTAL-224 Project: JBoss Portal Type: Task Components: Forums Versions: 2.0 Beta 2, 2.0 Final Reporter: Julien Viet Assignee: Roy Russo -- 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: (JBPORTAL-223) Edit a message
[ http://jira.jboss.com/jira/browse/JBPORTAL-223?page=comments#action_12316466 ] Julien Viet commented on JBPORTAL-223: -- the person with the appropriate right (admin or moderator) can edit an already existing message to change its content. Edit a message -- Key: JBPORTAL-223 URL: http://jira.jboss.com/jira/browse/JBPORTAL-223 Project: JBoss Portal Type: Task Components: Forums Versions: 2.0 Final, 2.0 Beta 2 Reporter: Julien Viet Assignee: Roy Russo -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBJMX-87) Implement getFixedRate() and add fixed-rate notification inTimerMBean, as of JMX1.2
Implement getFixedRate() and add fixed-rate notification inTimerMBean, as of
JMX1.2
---
Key: JBJMX-87
URL: http://jira.jboss.com/jira/browse/JBJMX-87
Project: JBoss JMX
Type: Feature Request
Versions: JBossAS-4.0.0
Environment: (jmx) javax.management.timer.Timer
Reporter: Dimitris Andreadis
Priority: Minor
public Integer addNotification(String type, String message, Object userData,
Date date, long period, long nbOccurences, boolean fixedRate) throws
IllegalArgumentException
{
// [todo] implement addNotification
throw new RuntimeException(NYI);
}
public Boolean getFixedRate(Integer id)
{
//[todo] implement getFixedRate
throw new RuntimeException(NYI);
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPM-101) add in- and out parameters to task
add in- and out parameters to task -- Key: JBPM-101 URL: http://jira.jboss.com/jira/browse/JBPM-101 Project: JBoss jBPM Type: Task Components: Core Engine Reporter: Tom Baeyens Assigned to: Tom Baeyens if this can be used for form generation. conversion between process variables and task parameters in both directions should be looked at. if it can be done generically, it would be a very good basis for the form generation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1627) Evaluate and implement missing JSR-88 functionality
Evaluate and implement missing JSR-88 functionality --- Key: JBAS-1627 URL: http://jira.jboss.com/jira/browse/JBAS-1627 Project: JBoss Application Server Type: Feature Request Components: Deployment Service Versions: JBossAS-4.0.1 Final Environment: deployment module Reporter: Dimitris Andreadis -- 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: (JBPORTAL-219) See new posts
[ http://jira.jboss.com/jira/browse/JBPORTAL-219?page=comments#action_12316467 ] Thomas Heute commented on JBPORTAL-219: --- Last login date is not stored, so new posts cannot be displayed accordingly. See new posts - Key: JBPORTAL-219 URL: http://jira.jboss.com/jira/browse/JBPORTAL-219 Project: JBoss Portal Type: Task Components: Forums Versions: 2.0 Beta 2, 2.0 Final Reporter: Julien Viet Assignee: Roy Russo Fix For: 2.0 Beta 2 Works with last login date, user should differenciate the newest posts from the others. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.320 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050329030124Lbuild.320 BUILD COMPLETE-build.320Date of build:03/29/2005 03:01:24Time to build:57 minutes 55 secondsLast changed:03/29/2005 01:05:09Last log entry:JBAS-1622 findSessions api is not correct Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(3)1.1.2.15modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaJBAS-1622 findSessions api is not correct1.1.2.15modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaJBAS-1622 findSessions api is not correct1.1.2.13modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaFixed sm getString messages
[JBoss-dev] [JBossCache] - Question of session about jboss4
I developed a project with jboss4 as app server,but there a problem: I can visit the project pages after jboss4 started,but when I shutdown the jboss4 server and restart it, the session for the pages which I have visited is still validate, that is I needn't login again and the user information is still available.this feature is useful when developing,but may have security problem when release project. Can anybody tell me how to turn off the feature ? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871865#3871865 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871865 --- 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] - General questions about JBoss Mail
Hi all, I'm searching for an open source mail server that meet some requirements. I've took a look to JBoss Mail docs but I'm not sure if it suits my requirements. My mail server may fulfill the following: - it should be able to filter mail and to discard every message that does not include a specific e-mail address in the target addresses list. - it should be able to process filtered messages in order to take some actions other than to deliver messages (e.g. extract a message content and store it to further processing) - it should be able to discard messages sent from a non authorized e-amil address and/or IP without any mail client action. Therefore, any digital signature method is excluded and also encryption. I know that it means a very low security, but it's a critical requirement to avoid installing any mail client plugin even security plugins like PGP. I guess that JBoss Mail should meet previous requirements but I'm not sure. Furthermore, I don't know if any stable JBoss Mail release is available or if JBoss Mail is a raising project. Thanks in advance. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871867#3871867 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871867 --- 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-1625) JBossQL ORDER BY does not work on string valued mapped types
[ http://jira.jboss.com/jira/browse/JBAS-1625?page=history ] Alexey Loubyansky reassigned JBAS-1625: --- Assign To: Alexey Loubyansky JBossQL ORDER BY does not work on string valued mapped types Key: JBAS-1625 URL: http://jira.jboss.com/jira/browse/JBAS-1625 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.1 Final Environment: Windows XP Pro SP2, JBoss 4.0.1, Sun JDK 1.5.0_02 Reporter: cgs Assignee: Alexey Loubyansky 09:59:09,147 WARN [ServiceController] Problem starting service jboss.j2ee:jndiName=ejb/Contact,service=EJB org.jboss.deployment.DeploymentException: Error compiling JBossQL statement 'SELECT DISTINCT OBJECT(c) FROM organization o, IN (o.contactList) AS c WHERE o = ?1 ORDER BY c.currentContactInfo.lastName ASC, c.currentContactInfo.firstName ASC, c.currentContactInfo.emailAddress ASC OFFSET ?2 LIMIT ?3'; - nested throwable: (org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered c.currentContactInfo.emailAddress at line 1, column 186. Was expecting one of: NUMERIC_VALUED_PATH ... STRING_VALUED_PATH ... DATETIME_VALUED_PATH ... ) at org.jboss.ejb.plugins.cmp.jdbc.JDBCJBossQLQuery.init(JDBCJBossQLQuery.java:52) at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createJBossQLQuery(JDBCCommandFactory.java:72) at org.jboss.ejb.plugins.cmp.jdbc.JDBCQueryManager.start(JDBCQueryManager.java:260) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.startStoreManager(JDBCStoreManager.java:490) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:381) at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:157) at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:340) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:416) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy304.start(Unknown Source) at org.jboss.ejb.EjbModule.startService(EjbModule.java:394) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:416) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at
[JBoss-dev] [Design of XDoclet Tags on JBoss (XDoclet/JBoss)] - Xdoclet2 Jboss, is it to early to upgrade 1.x - 2?
Hi, I've just been browsing on the Xdoclet2 site. I haven't find anything for jboss yet. Looks like the default ejb's etc are implemented but nothing on jboss deployment descriptors. Is anybody using Xdoclet2 with jboss ? or is it better for now to stick with xdoclet 1.x for now and wait untill Xdoclet2 is matured. I'm using xdoclet 1.x with struts, ejb's and web for generating the classes and teh deployment descriptors. Any opinions? Wessel de Roode View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871876#3871876 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871876 --- 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-1270) UserTransaction with non default ProviderURL
[
http://jira.jboss.com/jira/browse/JBAS-1270?page=comments#action_12316468 ]
Scott M Stark commented on JBAS-1270:
-
As indicated in the 3.2.8 fix version the change has been incorporated into the
3.2 branch for that release.
UserTransaction with non default ProviderURL
Key: JBAS-1270
URL: http://jira.jboss.com/jira/browse/JBAS-1270
Project: JBoss Application Server
Type: Bug
Components: Transaction Manager service
Versions: JBossAS-3.2.6 Final
Environment: WinXP Client SP 2, java version 1.4.2_04-b05, jboss-3.2.6
Reporter: Dirk Niemeier
Assignee: Scott M Stark
Priority: Critical
Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-3.2.8 Final
Problem to initiate an UserTransaction from client with non default
providerURL.
java.util.Hashtable env = new java.util.Hashtable();
env.put( Context.PROVIDER_URL, myserver:1199);
InitialContext ctx = new InitialContext(env);
javax.transaction.UserTransaction tx = (UserTransaction)
ctx.lookup(UserTransaction);
The lookup cause an stacktrace like this :
08:36:54,531 DEBUG [AWT-EventQueue-0] (NamingContext.java:1192) - Failed to
connect to 172.30.1.22:1099
javax.naming.CommunicationException: Failed to connect to server
172.30.1.22:1099 [Root exception is javax.naming.ServiceUnavailableException:
Failed to connect to server 172.30.1.22:1099 [Root exception is
java.net.ConnectException: Connection timed out: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:213)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1187)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:516)
The provider 172.30.1.22:1099 is the default provider in my jndi properties
file which is not online at this time.
I think the problem is in
org.jboss.tm.usertx.client.ClientUserTransactionObjectFactory, which will be
called in lookup handling.
The getUserTransaction() tries to create an new InitialContext with default
parameters. It should use the context available by getObjectInstance(..).
An additional problem to this is in class
org.jboss.tm.usertx.client.ClientUserTransaction :
private synchronized void createSession()
{
// Destroy any old session.
if (session != null)
destroySession();
try {
// Get a reference to the UT session factory.
UserTransactionSessionFactory factory;
factory = (UserTransactionSessionFactory)new
InitialContext().lookup(UserTransactionSessionFactory);
// Call factory to get a UT session.
session = factory.newInstance();
} catch (Exception ex) {
throw new RuntimeException(UT factory lookup failed: + ex);
}
}
This occurs when begin() is invoked. Same problem with new InitialContext().
In class ServerVMClientUserTransaction the same problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - JDBCCacheLoader feature
Is there a posibility to map existing tables to JDBCCachLoader ? In the documentation I saw just the posibility to create new tables according to your nodes . View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871880#3871880 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871880 --- 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-1579) Need to cleanup the serialVersionUIDs for Serializable/Externalizable classes
[ http://jira.jboss.com/jira/browse/JBAS-1579?page=history ] Scott M Stark reassigned JBAS-1579: --- Assign To: Scott M Stark (was: Clebert Suconic) Need to cleanup the serialVersionUIDs for Serializable/Externalizable classes - Key: JBAS-1579 URL: http://jira.jboss.com/jira/browse/JBAS-1579 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 Reporter: Scott M Stark Assignee: Scott M Stark Priority: Blocker Fix For: JBossAS-4.0.2 Final Attachments: SerializableHasSerialVersionUIDField.zip, TestResultSample.zip, compatibilityCheckProposedSourceCde.zip I'm seeing incomptibilities between versions that are simply due to the fact that Serializable/Externalizable classes are letting their serialVersionUIDs float instead of explicitly defining them. We need to get this cleaned up. There should not be a single Serializable/Externalizable class that does not fix its serialVersionUID and then take responsibility for maintaining compatibility with the indicated version. The attached SerializableHasSerialVersionUIDField.zip unzips to create a SerializableHasSerialVersionUIDField-index.html and SerializableHasSerialVersionUIDField directory which is a report of all classes in the 4.0 codebase that are not defining a serialVersionUID as they should. The JDK object serialization spec defines all you need to know about the apis and contracts for object serialization: http://java.sun.com/j2se/1.4.2/docs/guide/serialization/spec/serialTOC.html In particular, Versioning of Serializable Objects: http://java.sun.com/j2se/1.4.2/docs/guide/serialization/spec/version.html#wp9419 talks about binary compatibility and what is available to manage this. -- 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-1579) Need to cleanup the serialVersionUIDs for Serializable/Externalizable classes
[ http://jira.jboss.com/jira/browse/JBAS-1579?page=comments#action_12316469 ] Scott M Stark commented on JBAS-1579: - The requirement is to have a serialVersionUID defined in every Serializable/Externalizable class. Its value should be fixed to the 4.0.1 version if possible. The javax.* classes should match the j2ee 1.4 reference implementation class serialVersionUID values. Need to cleanup the serialVersionUIDs for Serializable/Externalizable classes - Key: JBAS-1579 URL: http://jira.jboss.com/jira/browse/JBAS-1579 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 Reporter: Scott M Stark Assignee: Clebert Suconic Priority: Blocker Fix For: JBossAS-4.0.2 Final Attachments: SerializableHasSerialVersionUIDField.zip, TestResultSample.zip, compatibilityCheckProposedSourceCde.zip I'm seeing incomptibilities between versions that are simply due to the fact that Serializable/Externalizable classes are letting their serialVersionUIDs float instead of explicitly defining them. We need to get this cleaned up. There should not be a single Serializable/Externalizable class that does not fix its serialVersionUID and then take responsibility for maintaining compatibility with the indicated version. The attached SerializableHasSerialVersionUIDField.zip unzips to create a SerializableHasSerialVersionUIDField-index.html and SerializableHasSerialVersionUIDField directory which is a report of all classes in the 4.0 codebase that are not defining a serialVersionUID as they should. The JDK object serialization spec defines all you need to know about the apis and contracts for object serialization: http://java.sun.com/j2se/1.4.2/docs/guide/serialization/spec/serialTOC.html In particular, Versioning of Serializable Objects: http://java.sun.com/j2se/1.4.2/docs/guide/serialization/spec/version.html#wp9419 talks about binary compatibility and what is available to manage this. -- 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] - Re: JDBCCacheLoader feature
Yes, look into the documentation (http://docs.jboss.org/jbcache/current/TreeCache/html/) or the javadoc for JDBCCacheLoader View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871881#3871881 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871881 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-93) add the identity component
[ http://jira.jboss.com/jira/browse/JBPM-93?page=history ] Tom Baeyens updated JBPM-93: Summary: add the identity component (was: add the organisation component) add the identity component -- Key: JBPM-93 URL: http://jira.jboss.com/jira/browse/JBPM-93 Project: JBoss jBPM Type: Task Components: Core Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Priority: Minor Fix For: jBPM 3.0 alpha 3 as an extension, a simple organisation component should be created. the initial ideas are in module jbpm.organisation in the jbpm cvs. the idea is that a single interface is specified for accessing the user-roles relation. then we can create different implementations for different storage technologies e.g. a relational database, an LDAP system, the tomcat-users.xml, the jboss users-roles property files, ... then assignment handlers and authorization extensions could be written against this simple interface. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Messaging on JBoss (Messaging/JBoss)] - JBossConnection and JBossConnectionFactory
Hi All- I've been having a look at JIRA tasks 32 and 33: Modify org.jboss.jms.client.JBossConnectionFactory to implement the complete set of ConnectionFactory interfaces... and Modify org.jboss.jms.client.JBossConnection to implement the complete set of Connection interfaces... Implementing the required interfaces for JBossConnectionFactory seems reasonably straightforward - it seems mainly a matter of casting to QueueConnection/TopicConnection etc. For this one I didn't seem to need change any interceptors or the delegate. I'm not sure if I haven't missed something here though. JBossConnection seems somewhat more involved. Again, some of the stuff seems just a matter of casting between TopicConnection/QueueConnection, but for the rest I just wanted to check with you that I'm along the right track. I ended up adding a member: isXAConnection which is set when constructing the object. (In a similar way to how it's done in JBoss 4). This is then checked in methods like getXASession to check whether the connection represents an XA connection. For getMetaData() I think I need to write a simple class that implements ConnectionMetaData. For get/setExceptionListener() - this seems a simple matter of just storing the listener in a member. For start() and stop(), I'm not really sure where this should be handled and would appreciate a steer in the right direction. I guess I need to implement this in some interceptor(s) but not really sure where. For close() I believe the CloseInterceptor() needs to be implemented. I noticed there's one in Jboss4, although I'm not sure if's similar enough to be (partly) re-used? There are also a set of createConnectionConsumer() methods. I notice from the spec. that these are optional, and aren't implemented in JBoss 4. Do we need consider these yet? Or should they be left for later? I can just throw NotYetSupportedException if appropriate for now. I also noticed in the design docs. that there's a ConnectionInterceptor mentioned although I'm not sure of it's exact role and if it's a place where some of this functionality should be implemented. If someone could clarify it's role and whether it's related to these tasks, that would be great. Thanks in advance. -Tim View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871885#3871885 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871885 --- 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: JavaServerFaces Portlet integration working with JBoss P
Any movement on the MyFaces integration? We are currently working on som e generic JSF components for our portal apps, and it would be nice to check that everything works ok against MyFaces+JBossPortal rather than the SunRI+JBossPortal combination we are currently using. Cheers, Kev View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871886#3871886 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871886 --- 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: JavaServerFaces Portlet integration working with JBoss P
I know I need to fix the way parameters are encoded in URL that prevents some stuff to work with JSF, but I don't know if it prevents to work with myfaces yet View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871893#3871893 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871893 --- 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: (JBCACHE-98) Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases
[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=comments#action_12316470 ] Ben Wang commented on JBCACHE-98: - Options here: 1. There is JBossCache_1.1.1 release that solves the eviction start sequence problem. 2. Directly patch JBossCache1.2.1 (jboss-cache.jar) against 4.0.0 and 4.0.1. This should work but we will need QA to do sanity checking. Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases -- Key: JBCACHE-98 URL: http://jira.jboss.com/jira/browse/JBCACHE-98 Project: JBoss Cache Type: Support Patch Versions: 1.2 Environment: should work in any environment Reporter: Luc Texier Assignee: Bela Ban Fix For: 1.2.2 Some customers have expressed the wish to take avantages of the optimizations/bug fixes/enhancements being implemented in the latest releases of JBossCache (i.e. 1.2.1 and the upcoming 1.2.2). Therefore, it has been decided to backport JBossCache 1.2.2 to JBossAS 4.0.0 and JBossAS 4.0.1. -- 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.454 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050329082111Lbuild.454 BUILD COMPLETE-build.454Date of build:03/29/2005 08:21:11Time to build:47 minutes 38 secondsLast changed:03/29/2005 07:14:20Last log entry:Add the personsAge field Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(58)1.1.32.1modifiedstarksmtestsuite/src/main/org/jboss/test/cts/interfaces/CtsCmp.javaAdd the personsAge field1.3.2.11modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaAnother fix for JBAS-16221.15.4.3modifiedstarksmtestsuite/src/resources/cts/META-INF/ejb-jar.xmlAdd the personsAge field1.7.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/cts/ejb/CtsCmpBean.javaAdd the personsAge field1.12.6.1modifiedanddsystem/src/main/org/jboss/system/server/ServerInfo.javaJBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really.1.5.2.6modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaFixed sm getString message1.3.2.10modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaJBAS-1622 findSessions api wasn't correct1.3.2.8modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaJBAS-1622 findSessions api wasn't correct1.406.2.48modifiedovidiuftestsuite/build.xmltests-clustering-all-stacks generates different test report sets for each stack configuration1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-coyote.jar- Update to Tomcat 5.5.9.1.5.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-http.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-util.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/naming-resources.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-cgi.renametojar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-default.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-invoker.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-ssi.renametojar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/servlets-webdav.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/tomcat-ajp.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/jasper-runtime.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/jasper-compiler.jar- Update to Tomcat 5.5.9.1.1.2.4modifiedremmthirdparty/apache-tomcat55/jasper-compiler-jdt.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina-manager.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina-optional.jar- Update to Tomcat 5.5.9.1.1.2.5modifiedremmthirdparty/apache-tomcat55/catalina.jar- Update to Tomcat 5.5.9.1.2.2.5modifiedremmthirdparty/apache-tomcat55/README- Update to Tomcat 5.5.9.1.2.8.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsMessageConsumer.java[JBAS-1604] - Make a start on the JMSRA trace logging1.10.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSession.java[JBAS-1604] - Make a start on the JMSRA trace logging1.11.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.java[JBAS-1604] - Make a start on the JMSRA trace logging1.8.2.1modifiedstarksmserver/src/main/org/jboss/tm/usertx/client/ClientUserTransaction.javaUse the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.1.8.6.1modifiedejortconnector/src/main/org/jboss/resource/deployment/RARDeployment.java[JBAS-1446] - Add trace logging for rar deployment operations1.3.4.2modifiedejortconnector/src/main/org/jboss/resource/deployment/ActivationSpecFactory.java[JBAS-1446] - Add trace logging to activation spec construction1.1.2.3modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObject.java[JBAS-1446] - Add TRACE logging to AdminObject construction.1.1.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObjectFactory.java[JBAS-1446] - Add TRACE logging to AdminObject construction.1.1.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/dlq/GenericDLQHandler.javaSource code
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-117) NPE when undeploying node in a cluster
NPE when undeploying node in a cluster
--
Key: EJBTHREE-117
URL: http://jira.jboss.com/jira/browse/EJBTHREE-117
Project: EJB 3.0
Type: Bug
Components: Clustering
Versions: Preview 4
Reporter: Kabir Khan
Fix For: Preview 5
The stuff below is before clustering steps in. If you run the
clustering example (or I think any for that matter, but haven't
tried), and shut down one of the servers gracefully:
-It starts undeploying
-Entries in AOP Dispatcher are removed
-When the client next tries to connect to the closing down server, the
server is still up, but there is no entry in AOP Dispatcher (target is
null). It tries to use the null target, and it fails with a NPE which is
propagated all the way up to the client
The client code is:
public static void main(String[] args) throws Exception
{
InitialContext ctx = new InitialContext();
Session remote = (Session) ctx.lookup(Session.class.getName());
while (true)
{
remote.test(); //Fail here
Thread.sleep(1000);
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-117) NPE when undeploying node in a cluster
[ http://jira.jboss.com/jira/browse/EJBTHREE-117?page=history ]
Kabir Khan closed EJBTHREE-117:
---
Assign To: Kabir Khan
Resolution: Done
NPE when undeploying node in a cluster
--
Key: EJBTHREE-117
URL: http://jira.jboss.com/jira/browse/EJBTHREE-117
Project: EJB 3.0
Type: Bug
Components: Clustering
Versions: Preview 4
Reporter: Kabir Khan
Assignee: Kabir Khan
Fix For: Preview 5
The stuff below is before clustering steps in. If you run the
clustering example (or I think any for that matter, but haven't
tried), and shut down one of the servers gracefully:
-It starts undeploying
-Entries in AOP Dispatcher are removed
-When the client next tries to connect to the closing down server, the
server is still up, but there is no entry in AOP Dispatcher (target is
null). It tries to use the null target, and it fails with a NPE which is
propagated all the way up to the client
The client code is:
public static void main(String[] args) throws Exception
{
InitialContext ctx = new InitialContext();
Session remote = (Session) ctx.lookup(Session.class.getName());
while (true)
{
remote.test(); //Fail here
Thread.sleep(1000);
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPM-102) optimize performance for delegation instantiation
optimize performance for delegation instantiation
-
Key: JBPM-102
URL: http://jira.jboss.com/jira/browse/JBPM-102
Project: JBoss jBPM
Type: Task
Components: Core Engine
Reporter: Tom Baeyens
Assigned to: Tom Baeyens
delegation instantiation could be optimized by object pooling. this might
require a configuration property on the delegation xml to specify the scope of
a delegation object {new-for-each-usage, synchronized, singleton}
note that ExpressionAssignmentHandler is not threadsafe.
--
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: (JBCACHE-110) Cache aop Overriding toString or hashCode will trigger stack overflow
[ http://jira.jboss.com/jira/browse/JBCACHE-110?page=history ] Bela Ban updated JBCACHE-110: - Fix Version: 1.2.3 (was: 1.2.2) Cache aop Overriding toString or hashCode will trigger stack overflow - Key: JBCACHE-110 URL: http://jira.jboss.com/jira/browse/JBCACHE-110 Project: JBoss Cache Type: Bug Versions: 1.2 Reporter: Ben Wang Assignee: Ben Wang Fix For: 1.2.3 Original Estimate: 2 weeks Remaining: 2 weeks In TreeCacheAOp, certain over-riding will trigger stack overflow. THis is becuase of the recursive field interecption that results. Solution is to detect the field recusion. Kabir has done it in: org.jboss.aspects.dbc.DesignByContractAspect -- 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: (JBCACHE-103) ConfiguratorFactory#getConfigStream should not throw a AccessControlException
[ http://jira.jboss.com/jira/browse/JBCACHE-103?page=history ]
Bela Ban updated JBCACHE-103:
-
Fix Version: 1.2.3
(was: 1.2.2)
ConfiguratorFactory#getConfigStream should not throw a AccessControlException
-
Key: JBCACHE-103
URL: http://jira.jboss.com/jira/browse/JBCACHE-103
Project: JBoss Cache
Type: Bug
Versions: 2.x
Environment: JBoss 4.0.1_sp1 / JCache 2.2.7
Reporter: Roland R?z
Assignee: Bela Ban
Fix For: 1.2.3
Original Estimate: 30 minutes
Remaining: 30 minutes
Hi,
the following will cause an AccessControlException when working with a
Java security file policy that sets limited FilePermissions:
class org.jgroups.conf.ConfiguratorFactory
method
InputStream getConfigStream(String properties) throws IOException
...
// Check to see if the properties string is the name of a file.
if (configStream == null) {
try {
configStream=new FileInputStream(properties);
}
catch(FileNotFoundException fnfe) {
// the properties string is likely not a file
}
}
If the properties are not a file but the real properties a
AccessControlException
will be thrown when checking the FilePermission that looks like this (for
example)
UDP(ip_mcast=true;ip_ttl=32;loopback=false;mcast_addr=228.1.2.3;mcast_port=12020;...)
Possibly you should check if the String properties starts with UDP.
Regards
--
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: (JBCACHE-54) JBossCacheAop nees a customized interceptor option
[ http://jira.jboss.com/jira/browse/JBCACHE-54?page=history ] Bela Ban updated JBCACHE-54: Fix Version: 1.2.3 (was: 1.2.2) JBossCacheAop nees a customized interceptor option -- Key: JBCACHE-54 URL: http://jira.jboss.com/jira/browse/JBCACHE-54 Project: JBoss Cache Type: Feature Request Versions: 1.2.1 Reporter: Ben Wang Assignee: Bela Ban Fix For: 1.2.3 Original Estimate: 1 week, 3 days Remaining: 1 week, 3 days In designing the implementation of http session repl using JBossCacheAop, there is a need to add a customized interceptor (in addition to the CacheInterceptor) to handle specific session request. This feature can be generalized to a generic customized interceptor chain that a user of aop can add to his own. Idea then is the chain (of which starts with the CacheInterceptor) will be added as a dynamic aop interceptors. -- 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: (JBCACHE-104) Mass Removal
[ http://jira.jboss.com/jira/browse/JBCACHE-104?page=history ] Bela Ban updated JBCACHE-104: - Fix Version: 1.2.3 (was: 1.2.2) Mass Removal Key: JBCACHE-104 URL: http://jira.jboss.com/jira/browse/JBCACHE-104 Project: JBoss Cache Type: Feature Request Versions: 1.2 Reporter: fredatwork Assignee: Ben Wang Fix For: 1.2.3 Hello, I would like to propose to enhance JBossCache API with a mass-removal function : Let's say I entered several objects in an AOP cache : cache.putObject(/root/1, object1); cache.putObject(/root/2, object2); .../... cache.putObject(/root/999, object999); I would like to be able to remove masseively all objects under the /root frq, with a single method call. The idea here is to be able to reset whole regions of the cache by removing all objects contained in this region. For instance, a servlet init method could use this new method to reset a cache dedicated to a particular enterprise application. Whiout this method, there is no way to reseta cache region. With current 1.2 version, you have to keep track of individual objects in order to remove them one after the other one. Note: Ben Wang proposed me to create this feature request so he can add it to the roadmpa. See http://www.jboss.org/index.html?module=bbop=viewtopicp=3868494#3868494. -- 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: (JBCACHE-100) RMI-based DelegatingCacheLoader
[ http://jira.jboss.com/jira/browse/JBCACHE-100?page=history ] Bela Ban updated JBCACHE-100: - Fix Version: 1.2.3 (was: 1.2.2) RMI-based DelegatingCacheLoader --- Key: JBCACHE-100 URL: http://jira.jboss.com/jira/browse/JBCACHE-100 Project: JBoss Cache Type: Feature Request Versions: 1.2 Reporter: Bela Ban Assignee: Bela Ban Fix For: 1.2.3 -- 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: (JBCACHE-85) TreeCacheAop object event listener
[ http://jira.jboss.com/jira/browse/JBCACHE-85?page=history ] Bela Ban updated JBCACHE-85: Fix Version: 1.2.3 (was: 1.2.2) TreeCacheAop object event listener -- Key: JBCACHE-85 URL: http://jira.jboss.com/jira/browse/JBCACHE-85 Project: JBoss Cache Type: Feature Request Reporter: Ben Wang Assignee: Ben Wang Fix For: 1.2.3 Original Estimate: 4 days Remaining: 4 days Need to add a TreeCacheAop object event listener. Currently we have TreeCache listener to listen for individual node event. We need to listen the event at the object level for the cache aop. This is also needed for the aop implementation of Tomcat http session replication (fine-grained one) to update the session related data (e.g., time stamp). -- 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: (JBCACHE-7) JBossCacheAop benchmark and performance tuning
[ http://jira.jboss.com/jira/browse/JBCACHE-7?page=history ] Bela Ban updated JBCACHE-7: --- Fix Version: 1.2.3 (was: 1.2.2) JBossCacheAop benchmark and performance tuning -- Key: JBCACHE-7 URL: http://jira.jboss.com/jira/browse/JBCACHE-7 Project: JBoss Cache Type: Task Versions: 1.3 Reporter: Bela Ban Assignee: Ben Wang Priority: Minor Fix For: 1.2.3 Original Estimate: 6 weeks Remaining: 6 weeks Test large amounts of data: should be handled by CacheLoader plus eviction policies -- 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: (JBCACHE-42) White paper on AOP (for session repl)
[ http://jira.jboss.com/jira/browse/JBCACHE-42?page=history ] Bela Ban updated JBCACHE-42: Fix Version: 1.2.3 (was: 1.2.2) White paper on AOP (for session repl) - Key: JBCACHE-42 URL: http://jira.jboss.com/jira/browse/JBCACHE-42 Project: JBoss Cache Type: Task Versions: 1.2.1 Reporter: Bela Ban Assignee: Ben Wang Priority: Minor Fix For: 1.2.3 Original Estimate: 1 week Remaining: 1 week -- 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: (JBCACHE-53) JBossCacheAop can use prepare annotation
[ http://jira.jboss.com/jira/browse/JBCACHE-53?page=history ] Bela Ban updated JBCACHE-53: Fix Version: 1.2.3 (was: 1.2.2) JBossCacheAop can use prepare annotation -- Key: JBCACHE-53 URL: http://jira.jboss.com/jira/browse/JBCACHE-53 Project: JBoss Cache Type: Feature Request Versions: 1.2.1 Reporter: Ben Wang Assignee: Bela Ban Priority: Minor Fix For: 1.2.3 Original Estimate: 2 days Remaining: 2 days Currently, JBossCacheAop uses an external jboss-aop.xml to declare the POJO. The latest JBossAop supports prepare annotation tag. We will need to test it out and document it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-116) CacheLoaderInterceptor calls CacheLoader.exists() spuriously
[ http://jira.jboss.com/jira/browse/JBCACHE-116?page=history ] Bela Ban resolved JBCACHE-116: -- Resolution: Done accepted patch CacheLoaderInterceptor calls CacheLoader.exists() spuriously Key: JBCACHE-116 URL: http://jira.jboss.com/jira/browse/JBCACHE-116 Project: JBoss Cache Type: Bug Versions: 1.2.1 Reporter: Bela Ban Assignee: Bela Ban Fix For: 1.2.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-116) CacheLoaderInterceptor calls CacheLoader.exists() spuriously
CacheLoaderInterceptor calls CacheLoader.exists() spuriously Key: JBCACHE-116 URL: http://jira.jboss.com/jira/browse/JBCACHE-116 Project: JBoss Cache Type: Bug Versions: 1.2.1 Reporter: Bela Ban Assigned to: Bela Ban Fix For: 1.2.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.906 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050329102625Lbuild.906 BUILD COMPLETE-build.906Date of build:03/29/2005 10:26:25Time to build:46 minutes 15 secondsLast changed:03/29/2005 09:00:49Last log entry:Fix for NPE when gracefully shutting down a clustered server Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(3)1.1addedkabkhanaop/src/main/org/jboss/aop/NotFoundInDispatcherException.javaFix for NPE when gracefully shutting down a clustered server1.12modifiedkabkhanaop/src/main/org/jboss/aop/Dispatcher.javaFix for NPE when gracefully shutting down a clustered server1.5modifiedkabkhanaspects/src/main/org/jboss/aspects/remoting/ClusterChooserInterceptor.javaFix for NPE when gracefully shutting down a clustered server
[JBoss-dev] [Design of JBoss Eclipse IDE (dev)] - JBossIDE 1.5 Milestone 1 Released
The JBossIDE Team is happy to announce the release of JBossIDE 1.5 Milestone 1! Release Notes: http://sourceforge.net/project/shownotes.php?release_id=315593 See the homepage for links to docs, demos, and what's new with JBossIDE 1.5 Milestone 1. http://www.jboss.com/products/jbosside Please note that this release is only compatible with Eclipse 3.1M5a. It will not work on previous Milestones of 3.1. Please see https://bugs.eclipse.org/bugs/show_bug.cgi?id=87298 We are working on setting up a new update site that will have increased bandwidth and usability compared to the current sourceforge-based update site. We will post a new announcement as soon as the new site is ready. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871919#3871919 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871919 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: CacheInterceptor not intercepting
I'm deploying the jboss-aop-jdk50.deployer package to my server's deploy
directory and then using loadtime transformation:
| attribute name=EnableTransformertrue/attribute
|
I'm not using AOPC.
I have a .aop package in my .ear file which contains a meta-inf/jboss-aop.xml
file.
In the xml file I have
prepare expr=field(* $instanceof{com.memeticsystems.item.common.IItem}-*)/
where my class implements IItem
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3871926#3871926
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871926
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: CacheInterceptor not intercepting
you have to add a jboss-app.xml to your EAR's META-INF directory (it is the jboss specific application.xml DD). | jboss-app |module | servicefoo.aop/service |/module | /jboss-aop | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871928#3871928 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871928 --- 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-1602) Can't use container level taglibs
[
http://jira.jboss.com/jira/browse/JBAS-1602?page=comments#action_12316474 ]
Stan Silvert commented on JBAS-1602:
The problem is with the way that Jasper is trying to locate TLD's. If you look
at EmbeddedServletOptions.java, you can see that somebody meant for the
TldLocationsCache to be pluggable. If it were we could easily write our own
and pass the class name into the JspServlet as an option.
Can we make this change to Tomcat/Jasper so that we can write our own
TldLocationsCache?
Can't use container level taglibs
-
Key: JBAS-1602
URL: http://jira.jboss.com/jira/browse/JBAS-1602
Project: JBoss Application Server
Type: Bug
Components: Web (Tomcat) service
Reporter: Stan Silvert
Priority: Critical
Attachments: TldLocationsCache.java
JBoss/Tomcat needs a way to install tag libraries globally so they are
available to all web applications. This functionality is mentioned in the
JSP 2.0 spec section 7.3.5. In Tomcat standalone, you can do this, but it
doesn?t work in JBoss/Tomcat.
The way this works is that the Jasper TldLocationsCache ?Scans all JARs
accessible to the webapp's classloader and its parent classloaders for TLDs.?
If I put my jar into Tomcat standalone?s common/lib directory then the tag
library will be shared across all web apps. I?ve tried putting the jar in
several ?well known? locations in JBoss/Tomcat and nothing seems to work.
For Reference, I?ve attached the TldLocationsCache source code from Tomcat
5.5.8.
Concerning TldLocationsCache, Scott Stark says:
This class is useless for non-URLClassLoaders and URLClassLoaders that do
not expose their classpath via getURLs which is what we currently do because
of an old bad behavior with annotated codebases of rmi classes.
Remy Maucherat offered this as a possible solution:
Would it be possible to have the ENCLoader facade return more interesting
things ?
/**
* A trival extension of URLClassLoader that uses an empty URL[] as its
* classpath so that all work is delegated to its parent.
*/
static class ENCLoader extends URLClassLoader
{
private URL[] urllist = new URL[0];
ENCLoader(ClassLoader parent)
{
super(new URL[0], parent);
}
void addURLInternal(URL url)
{
URL[] result = new URL[urllist.length + 1];
for (int i = 0; i urllist.length; i++)
result[i] = urllist[i];
result[urllist.length] = url;
urllist = result;
}
public URL[] getURLs()
{
return urllist;
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - IS AOP with Session stateless working on 4.0 AS ?
Hi all, I am testing a custom aspect on the method of session bean. For that purpose I have setup two files : - one that is the .aop and is holding the Interceptor and its configuration - the other, an .ear that is holding my application (a .jar and a .war) Deploying this, I am able to see that my method has been recognized and the class transformed, right. I can see in the tmp folder the class generated and was able to JAD it. But as soon as I call the method, nothing happen. I am also not able to find the transformed version of my bean in the tmp. I am using the dynamic generation of the AOP as I can not find a way to exacute the aopc in the JBoss IDE on an existing J2EE project :( I am locked since more than a week so I would be glad to hear from anybody that have succesfully done such a simple thing. Rgs, JB View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871929#3871929 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871929 --- 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-1602) Can't use container level taglibs
[ http://jira.jboss.com/jira/browse/JBAS-1602?page=history ]
Stan Silvert updated JBAS-1602:
---
Attachment: EmbeddedServletOptions.java
Can't use container level taglibs
-
Key: JBAS-1602
URL: http://jira.jboss.com/jira/browse/JBAS-1602
Project: JBoss Application Server
Type: Bug
Components: Web (Tomcat) service
Reporter: Stan Silvert
Priority: Critical
Attachments: EmbeddedServletOptions.java, TldLocationsCache.java
JBoss/Tomcat needs a way to install tag libraries globally so they are
available to all web applications. This functionality is mentioned in the
JSP 2.0 spec section 7.3.5. In Tomcat standalone, you can do this, but it
doesn?t work in JBoss/Tomcat.
The way this works is that the Jasper TldLocationsCache ?Scans all JARs
accessible to the webapp's classloader and its parent classloaders for TLDs.?
If I put my jar into Tomcat standalone?s common/lib directory then the tag
library will be shared across all web apps. I?ve tried putting the jar in
several ?well known? locations in JBoss/Tomcat and nothing seems to work.
For Reference, I?ve attached the TldLocationsCache source code from Tomcat
5.5.8.
Concerning TldLocationsCache, Scott Stark says:
This class is useless for non-URLClassLoaders and URLClassLoaders that do
not expose their classpath via getURLs which is what we currently do because
of an old bad behavior with annotated codebases of rmi classes.
Remy Maucherat offered this as a possible solution:
Would it be possible to have the ENCLoader facade return more interesting
things ?
/**
* A trival extension of URLClassLoader that uses an empty URL[] as its
* classpath so that all work is delegated to its parent.
*/
static class ENCLoader extends URLClassLoader
{
private URL[] urllist = new URL[0];
ENCLoader(ClassLoader parent)
{
super(new URL[0], parent);
}
void addURLInternal(URL url)
{
URL[] result = new URL[urllist.length + 1];
for (int i = 0; i urllist.length; i++)
result[i] = urllist[i];
result[urllist.length] = url;
urllist = result;
}
public URL[] getURLs()
{
return urllist;
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: CacheInterceptor not intercepting
I have that. AOP is generally working fine. It's just this one specific instance that is not working. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871930#3871930 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871930 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: IS AOP with Session stateless working on 4.0 AS ?
you have to add a jboss-app.xml to your EAR's META-INF directory (it is the jboss specific application.xml DD). | | jboss-app |module | servicefoo.aop/service |/module | /jboss-aop | | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871934#3871934 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871934 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: IS AOP with Session stateless working on 4.0 AS ?
Also, did you try out the tutorial? examples/injboss? So yes...We have done such a simple thing. What version of JBoss? Did you set up the load-time transformer correctly? Or are you using AOPC? How did you set up the load-time transformer? I can't really help with with JBoss IDE as I don't maintain it. Rob Stryker may be able to help you out: [EMAIL PROTECTED] View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871935#3871935 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871935 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBREM-92) in-VM push callbacks don't work
in-VM push callbacks don't work Key: JBREM-92 URL: http://jira.jboss.com/jira/browse/JBREM-92 Project: JBoss Remoting Type: Bug Components: callbacks Versions: 1.0.2 final Reporter: Ovidiu Feodorov Assigned to: Tom Elrod When registering a push callback handler with the callback server evertything seems to go well, the ServerInvokerCallbackHandler proxy is created and registered on the target server, but when trying to actually call back, the callback does not reach the callback server. The client, the callback server and the target server are colocated. I created a test case that fails: org.jboss.remoting.callback.push.InVMPushCallbackTestCase. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1628) Naming SimpleUnitTestCase failures
Naming SimpleUnitTestCase failures -- Key: JBAS-1628 URL: http://jira.jboss.com/jira/browse/JBAS-1628 Project: JBoss Application Server Type: Bug Components: Naming Versions: JBossAS-4.0.2RC1 Environment: qa lab Reporter: Ryan Campbell testHaPartitionName and testDiscoveryPort are both failing due to a SocketTimeoutException: http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite/20050323024613/results/org/jboss/test/naming/test/SimpleUnitTestCase.html org.jboss.test.naming.test.SimpleUnitTestCase.testHaPartitionName is failing: testHaParitionName: avax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1302) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1382) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579) ... at org.jboss.test.naming.test.SimpleUnitTestCase.testHaParitionName(SimpleUnitTestCase.java:224) testDiscoveryPort is failing at the same point: ... at org.jboss.test.naming.test.SimpleUnitTestCase.testDiscoveryPort(SimpleUnitTestCase.java:265) -- 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: (JBREM-92) in-VM push callbacks don't work
[ http://jira.jboss.com/jira/browse/JBREM-92?page=comments#action_12316477 ] Ovidiu Feodorov commented on JBREM-92: -- Checked in tentative fix: org.jboss.remoting.transport.local.LocalClientInvoker in-VM push callbacks don't work Key: JBREM-92 URL: http://jira.jboss.com/jira/browse/JBREM-92 Project: JBoss Remoting Type: Bug Components: callbacks Versions: 1.0.2 final Reporter: Ovidiu Feodorov Assignee: Tom Elrod When registering a push callback handler with the callback server evertything seems to go well, the ServerInvokerCallbackHandler proxy is created and registered on the target server, but when trying to actually call back, the callback does not reach the callback server. The client, the callback server and the target server are colocated. I created a test case that fails: org.jboss.remoting.callback.push.InVMPushCallbackTestCase. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: shared state between HttpSession and PortletSession
I did some testing with JBoss Portal Beta 1 and JBoss AS 4.0.2RC1 and the HTTP Session and Portlet Session were being handled correctly per the Portlet spec. I did have to add crossContext=true to each of the context.xml files (portal core and portlets). I understand that you won't need to do this after the next release of the JBoss AS 4.0.2. Has anyone looked at an approach for intra portlet communication across portlet applications? I have a requirement for this that will work well in a clustered environment. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871938#3871938 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871938 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBREM-93) Callback handler returning a generic Object
Callback handler returning a generic Object --- Key: JBREM-93 URL: http://jira.jboss.com/jira/browse/JBREM-93 Project: JBoss Remoting Type: Feature Request Components: callbacks Reporter: Ovidiu Feodorov Assigned to: Tom Elrod Priority: Optional InvokerCallbackHandler.handleCallback() returns void. However, is is able to throw a HandleCallbackException that ultimately reaches the calling party. I was wondering if it is a big deal to have handleCallback() returning a generic Object. This would make the handleCallback()'s semantics more flexible. -- 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] - Custom LRU Caching Policy Based on Memory Footprint of Cache
At my company, we are very interested in using an open source caching solution, but there is great concern that variances in the actual size of objects or data cached will result in unmanageable or unpredictable memory usage by a cache. Proper tuning of a cache should in theory be the answer, but our cautious CTO is looking for extra protection. Most implementations seem to have caching expriy algorithms/policies based on max elements in the cache, but none I have seen allow a bounded memory constraint for a cache. I was wondering if anyone has implemented a custom policy that will evict from a cache based on its size in memory? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871942#3871942 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871942 --- 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: (JBREM-93) Callback handler returning a generic Object
[ http://jira.jboss.com/jira/browse/JBREM-93?page=comments#action_12316478 ] Ovidiu Feodorov commented on JBREM-93: -- or at least have ServerInvokerCallbackHandler.handleCallback() pass along unchanged HandleCallbackExceptions it catches from callBackClient.invoke(internalInvocation, callback.getRequestPayload())? Callback handler returning a generic Object --- Key: JBREM-93 URL: http://jira.jboss.com/jira/browse/JBREM-93 Project: JBoss Remoting Type: Feature Request Components: callbacks Reporter: Ovidiu Feodorov Assignee: Tom Elrod Priority: Optional InvokerCallbackHandler.handleCallback() returns void. However, is is able to throw a HandleCallbackException that ultimately reaches the calling party. I was wondering if it is a big deal to have handleCallback() returning a generic Object. This would make the handleCallback()'s semantics more flexible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: shared state between HttpSession and PortletSession
what do you call inter portlet communication ? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871944#3871944 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871944 --- 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 Admin Console] - JMS - Destinations - Use case 1
This is the first in several use cases in support of CRUD for topics and queues. Comments are welcome. USE CASE 1: View a list of Destinations Basic Description An administrator uses the system to view information on existing destinations. Goal Display a list of destinations including queue and topic types. Basic flow of events 1. The user indicates to the system that they wish to view a list of all existing destinations. 2. The system displays a list of destinations of queue and topic types. 3. The use case ends. Extension points E1.1: Refresh the list After step 3) in the Basic Flow: 1. The user indicates to the system that they wish to refresh the list of destinations. 2. The system re-checks the current state and displays a new list of destinations. 3. The use case ends. Alternate flows A1.1: View a List of Queue Only During step 1) of the Basic Flow: 1. The user indicates to the system that they wish to view only a list of queues. 2. The use case rejoins the Basic flow at step 2). A1.2: View a List of Topic Only During step 1) of the Basic Flow: 1. The user indicates to the system that they wish to view only a list of topics. 2. The use case rejoins the Basic flow at step 2). Special Requirements 1. The minimal information of a destination to display should include: a. Queue/Topic name b. JNDI name c. Status, e.g. Started. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871947#3871947 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871947 --- 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 Admin Console] - JMS - Destinations - Use case 2
This is the second in several use cases in support of CRUD for topics and queues. Comments are welcome. USE CASE 2: View the Settings of a Destination Basic Description An administrator uses the system to view the settings of an existing destination within a JBoss server. Preconditions It is assumed that Use Case 1 will already have been executed and the user has a list of destinations from which to choose. Goal Display information relating to a destination of type queue or topic. Basic flow of events 1. The user indicates to the system that they wish to view information on a particular destination from the list. 2. The system displays information on the selected destination. 3. The use case ends. Extension Points E2.1: Show a list of messages After step 2) in the Basic Flow: 1. The user indicates to the system that they wish to show a list of message of the selected destination. 2. The system displays the message count and a list of messages that the selected destination currently holds. 3. The use case ends. E2.1: Remove messages After step 2) in the Basic Flow: 1. The user indicates to the system that they wish to remove all messages from the selected destination. 2. The system removes the messages from the destination and resets the message count. Then the system indicates to the user that the removal of messages succeeded. 3. The use case ends. Alternate Flows A2.1: Removal of messages fails, messages not removed During step 2) of Extension Point Flow E2.1: 1. The system failed to remove the messages from the specified destination. 2. The system indicates to the user that the removal of messages failed and displays the error exception information to the user. 3. The use case ends without removing the messages. Special Requirements 1. Different attributes will be displayed depending upon the type of the destination being viewed, i.e. queue or topic. The precise breakdown of attributes by type is listed in the reference documents - queue_elements.xls and topic_elements.xls) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871948#3871948 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871948 --- 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 Admin Console] - JMS - Destinations - Use case 3
This is the third of several use cases in support of CRUD for topics and queues. Comments are welcome. USE CASE 3: Create a Destination Basic Description An administrator uses the system to add a new destination to a JBoss server. Preconditions It is assumed that Use Case 1 will already have been executed and the user has indicated which type of destination, i.e. queue or topic, is going to create. Goal A destination of a specified type (queue or topic) is successfully created. Basic flow of events 1. The user indicates to the system that they wish to create a new destination of either queue or topic type. 2. The system displays a destination attribute fields for the user to fill in. 3. The user fills in the fields and indicates to the system to create a destination with the given settings. 4. The system takes the information entered by the user, validates it and creates a new destination of the specified type. 5. The system indicates to the user that the destination was successfully created. 6. The use case ends. Alternate Flows A4.1: Information validation fails, destination not created During step 4) of the Basic Flow: 1. The system finds a problem with the information the user submitted. 2. The system displays the information the user submitted and indicates to the user which piece(s) of information caused the problem. 3. The use case ends. A4.2: Information validation fails, user fixes problem After step 2) of Alternative Flow A4.1: 1. The user updates the pieces of information which the system indicated had caused the problem and indicates to the system to create the destination. 2. The system takes the information entered by the user, validates it and creates the destination. 3. The system indicates to the user that the destination was successfully created. 4. The use case ends. A4.3: User cancels creation During step 3) of the Basic Flow: 1. The user indicates to the system that they want to cancel the creation of a destination. 2. The system does not attempt to create a destination. The system displays the page the user was on before attempting to create the destination. 3. The use case ends. Special Requirements 1. Different attributes can be entered depending upon the type of the destination being created, i.e. queue or topic. The precise breakdown of attributes by type is listed in the reference documents - queue_elements.xls and topic_elements.xls). 2. A destination created through the system must persist across restarts of the JBoss server. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871950#3871950 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871950 --- 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 Admin Console] - JMS - Destinations - Use case 4
This is the fourth of several use cases in support of CRUD for topics and queues. Comments are welcome. USE CASE 4: Update a Destination Basic Description An administrator uses the system to update a destination which already exists within a JBoss server. Preconditions It is assumed that the user has already authenticated to the system and has been successfully authorized. It is also assumed that the Use 1 will already have been executed and the user has a list of destinations from which to choose. Goal A destination is successfully updated. Basic flow of events 1. The user indicates to the system that they wish to update a particular destination. 2. The system displays a list of attributes of the destination for update. 3. The user updates some attributes and indicates to the system to update the destination with the given settings. 4. The system takes the information entered by the user, validates it and updates the existing destination. 5. The system indicates to the user that the destination was successfully updated. 6. The use case ends. Alternate flows A4.1: Information validation fails, destination not updated During step 4) of the Basic Flow: 1. The system finds a problem with the information the user submitted. 2. The system displays the information the user submitted and indicates to the user which piece(s) of information caused the problem. 3. The use case ends leaving the destination unchanged. A4.2: Information validation fails, user fixes problem After step 2) of Alternative Flow A4.1: 1. The user updates the pieces of information which the system indicated had caused the problem and indicates to the system to update the destination. 2. The system takes the information entered by the user, validates it and updates the destination. 3. The system indicates to the user that the destination was successfully updated. 4. The use case ends. A4.3: User cancels update During step 3) of the Basic Flow: 1. The user indicates to the system that they want to cancel the update of the destination. 2. The system does not attempt to update the destination. The system displays the page the user was on before attempting to update the destination. 3. The use case ends leaving the destination unchanged. Special Requirements 1. Different attributes are displayed for update depending upon the type of the destination being updated, i.e. queue or topic. The precise breakdown of attributes by type is listed in the reference documents - queue_elements.xls and topic_elements.xls). 2. A destination updated through the system must persist across restarts of the JBoss server. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871951#3871951 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871951 --- 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 Admin Console] - JMS - Destinations - Use case 5
This is the last of several use cases in support of CRUD for topics and queues. Comments are welcome. USE CASE 5: Delete a Destination Basic Description An administrator uses the system to delete a destination from a JBoss server. Preconditions It is assumed that Use Case 1 will already have been executed and the user has a list of destinations from which to choose. Goal Delete the selected destination. Basic flow of events 1. The user indicates to the system that they wish to delete a particular destination. 2. The system prompts the user to confirm their desire to delete the destination. 3. The user confirms the deletion. 4. The system attempts to delete the selected destination. 5. The use case ends. Alternate flows A5.1: User cancels deletion During step 3) of the Basic Flow: 1. The user indicates to the system that they want to cancel the deletion of the destination. 2. The system does not attempt to delete the destination. 3. The use case ends. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871952#3871952 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871952 --- 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-58) Complete testing of JMS Message Inflow
[ http://jira.jboss.com/jira/browse/JBAS-58?page=history ] Adrian Brock closed JBAS-58: Resolution: Done I've updated the tests to include the basic deployment strategies as outlined in the FAQ: http://www.jboss.org/wiki/Wiki.jsp?page=WhatAreTheDifferentStrategiesForDeployingAnMDB There are still a lot of parameters and failure conditions that are not being tested. The full tests are deferred to 4.0.3, the old JMSContainerInvoker already supports standard EJB2.1 style deployments. Complete testing of JMS Message Inflow -- Key: JBAS-58 URL: http://jira.jboss.com/jira/browse/JBAS-58 Project: JBoss Application Server Type: Task Components: JCA service Versions: JBossAS-4.0.0 Final Reporter: Adrian Brock Fix For: JBossAS-4.0.2 Final Complete the testing of JMS Message Inflow -- 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-1434) JMS Message Inflow
[ http://jira.jboss.com/jira/browse/JBAS-1434?page=history ] Adrian Brock updated JBAS-1434: --- Description: Forums Discussion Thread: http://www.jboss.org/index.html?module=bbop=viewtopict=48672 The JMS message inflow in the JMS resource adapter needs properly testing. There are basic tests, but the following are missing: 1) Complete tests of edge cases for each configuration parameter in the activation spec 2) Failure tests to confirm the implementation handles error gracefully 3) Stress tests to make sure there the implementation is stable 4) Performance tests to optimize the implementation Additionally, we need to confirm that it is possible to use this implementation for EJB2.0 style deployments and hence as the default configuration. This should be possible provided the user has not created their own container configuration that uses the old JMSContainerInvoker explicitly. was: Forums Discussion Thread: http://www.jboss.org/index.html?module=bbop=viewtopict=48672 The JMS message inflow in the JMS resource adapter needs properly testing. There are basic tests, but the following are missing: 1) Complete tests of edge cases for each configuration parameter in the activation spec 2) Failure tests to confirm the implementation handles error gracefully 3) Stress tests to make sure there the implementation is stable 4) Performance tests to optimize the implementation Additionally, we need to confirm that it is possible to use this implementation for EJB2.0 style deployments and hence as the default configuration. This should be possible provided the user has not created their own container configuration that uses the old JMSContainerInvoker explicitly. Environment: Version: JBossAS-4.0.2 Final JBAS-58 has been closed, there are still a number of tests that need to be written before the jms inbound rar is not considered experimental. JMS Message Inflow -- Key: JBAS-1434 URL: http://jira.jboss.com/jira/browse/JBAS-1434 Project: JBoss Application Server Type: Task Components: JCA service Versions: JBossAS-4.0.2 Final Reporter: Adrian Brock Assignee: Adrian Brock Forums Discussion Thread: http://www.jboss.org/index.html?module=bbop=viewtopict=48672 The JMS message inflow in the JMS resource adapter needs properly testing. There are basic tests, but the following are missing: 1) Complete tests of edge cases for each configuration parameter in the activation spec 2) Failure tests to confirm the implementation handles error gracefully 3) Stress tests to make sure there the implementation is stable 4) Performance tests to optimize the implementation Additionally, we need to confirm that it is possible to use this implementation for EJB2.0 style deployments and hence as the default configuration. This should be possible provided the user has not created their own container configuration that uses the old JMSContainerInvoker explicitly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1629) message-destination-link does not work for MDB's
message-destination-link does not work for MDB's Key: JBAS-1629 URL: http://jira.jboss.com/jira/browse/JBAS-1629 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 SP1 Reporter: Matthias Germann Setting the message-destination-link child element of the message-driven element does not work on JBoss 4.0.1sp1. JBAS-1130 is related to this but i think that message-destination-link support was only added for the message-destination-ref element but not for the message-driven element. A message-driven bean can sspecify the message-destination it want's to listen to with the message-destination-link element (see http://java.sun.com/developer/EJTechTips/2005/tt0322.html#1). i.e.: message-driven ejb-nameRegEmailSender/ejb-name ejb-classch.tvfrutigen.chandertaler.ejb.service.RegEmailSenderBean/ejb-class messaging-typejavax.jms.MessageListener/messaging-type transaction-typeContainer/transaction-type message-destination-typejavax.jms.Queue/message-destination-type message-destination-linkRegEmailsQueue/message-destination-link ... /message-driven It should be possible that the senders of a message and the processing MDBs can link to the same message-destination in the assembly-descriptor. Therefore, only the message-destination in the assembly-descriptor must be mapped to a jndi-name in jboss.xml. Setting the message-destination-link elment on JBoss 4.0.1sp1 has no effect. It is still necessary to map the MDB's to the jndi-name of the queue/topic using the destination-jndi-name element. IMHO, it should not be necessary to specify the destination-jndi-name element when using message-destinations. -- 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-1434) JMS Message Inflow
[ http://jira.jboss.com/jira/browse/JBAS-1434?page=history ] Adrian Brock updated JBAS-1434: --- Fix Version: JBossAS-4.0.3 Final Rescheduled for 4.0.3 JMS Message Inflow -- Key: JBAS-1434 URL: http://jira.jboss.com/jira/browse/JBAS-1434 Project: JBoss Application Server Type: Task Components: JCA service Versions: JBossAS-4.0.2 Final Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossAS-4.0.3 Final Forums Discussion Thread: http://www.jboss.org/index.html?module=bbop=viewtopict=48672 The JMS message inflow in the JMS resource adapter needs properly testing. There are basic tests, but the following are missing: 1) Complete tests of edge cases for each configuration parameter in the activation spec 2) Failure tests to confirm the implementation handles error gracefully 3) Stress tests to make sure there the implementation is stable 4) Performance tests to optimize the implementation Additionally, we need to confirm that it is possible to use this implementation for EJB2.0 style deployments and hence as the default configuration. This should be possible provided the user has not created their own container configuration that uses the old JMSContainerInvoker explicitly. -- 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-1604) Add detailed logging to the jms resource adapter
[ http://jira.jboss.com/jira/browse/JBAS-1604?page=history ] Adrian Brock closed JBAS-1604: -- Resolution: Done The jms rar now logs connection/session and receiver usage. It does not intercept producer usage so no logging was added here. Add detailed logging to the jms resource adapter Key: JBAS-1604 URL: http://jira.jboss.com/jira/browse/JBAS-1604 Project: JBoss Application Server Type: Feature Request Components: JMS service Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossAS-4.0.2 Final Need to add detailed logging to the jms resource adapter for when we integrate thirdparty jms providers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPM-103) in variables on Script uses same DB table as out variables, causes evaluation errors.
in variables on Script uses same DB table as out variables, causes evaluation errors. - Key: JBPM-103 URL: http://jira.jboss.com/jira/browse/JBPM-103 Project: JBoss jBPM Type: Bug Components: Core Engine Versions: jBPM 3.0 alpha 2 Environment: J2SE 1.4.2_07, Windows XP Reporter: Mark LaFond Assigned to: Tom Baeyens Priority: Blocker The following script was failing for me. script + expression + outParm = response.getTestOutputParm(); + /expression + out variable='outParm' / + /script + The problem was traced back to Script.hbm.xml which was mapping the in variables to the same table as the out variables. This caused Script.createInterpreter() to load all of the out variables as in variables which caused my response variable to NOT be loaded into the Interpreter which then caused the script to fail. I've attached the fix below, I've tested it in the core project as well as in the db project that generates the SQL. ** ?xml version=1.0? !DOCTYPE hibernate-mapping PUBLIC -//Hibernate/Hibernate Mapping DTD 3.0//EN http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd; hibernate-mapping default-access=field subclass name=org.jbpm.jpdl.def.Script discriminator-value=S extends=org.jbpm.graph.def.Action property name=expression column=EXPRESSION_ / property name=resultVariableName column=RESULTVARIABLENAME_ / set name=inVariables table=JBPM_SCRIPTVARIABLES_IN key column=SCRIPT_ foreign-key=FK_VARIABLE_SCRIPT_IN / element type=string / /set set name=outVariables table=JBPM_SCRIPTVARIABLES_OUT key column=SCRIPT_ foreign-key=FK_VARIABLE_SCRIPT_OUT/ element type=string / /set /subclass /hibernate-mapping -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-103) in variables on Script uses same DB table as out variables, causes evaluation errors.
[ http://jira.jboss.com/jira/browse/JBPM-103?page=history ] Mark LaFond updated JBPM-103: - Attachment: Script.hbm.xml attached hibernate config for Script object. in variables on Script uses same DB table as out variables, causes evaluation errors. - Key: JBPM-103 URL: http://jira.jboss.com/jira/browse/JBPM-103 Project: JBoss jBPM Type: Bug Components: Core Engine Versions: jBPM 3.0 alpha 2 Environment: J2SE 1.4.2_07, Windows XP Reporter: Mark LaFond Assignee: Tom Baeyens Priority: Blocker Attachments: Script.hbm.xml The following script was failing for me. script + expression + outParm = response.getTestOutputParm(); + /expression + out variable='outParm' / + /script + The problem was traced back to Script.hbm.xml which was mapping the in variables to the same table as the out variables. This caused Script.createInterpreter() to load all of the out variables as in variables which caused my response variable to NOT be loaded into the Interpreter which then caused the script to fail. I've attached the fix below, I've tested it in the core project as well as in the db project that generates the SQL. ** ?xml version=1.0? !DOCTYPE hibernate-mapping PUBLIC -//Hibernate/Hibernate Mapping DTD 3.0//EN http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd; hibernate-mapping default-access=field subclass name=org.jbpm.jpdl.def.Script discriminator-value=S extends=org.jbpm.graph.def.Action property name=expression column=EXPRESSION_ / property name=resultVariableName column=RESULTVARIABLENAME_ / set name=inVariables table=JBPM_SCRIPTVARIABLES_IN key column=SCRIPT_ foreign-key=FK_VARIABLE_SCRIPT_IN / element type=string / /set set name=outVariables table=JBPM_SCRIPTVARIABLES_OUT key column=SCRIPT_ foreign-key=FK_VARIABLE_SCRIPT_OUT/ element type=string / /set /subclass /hibernate-mapping -- 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: (JBADMCON-110) Document use case
[ http://jira.jboss.com/jira/browse/JBADMCON-110?page=comments#action_12316486 ] Peter Johnson commented on JBADMCON-110: Use cases have been posted on the forum. Document use case - Key: JBADMCON-110 URL: http://jira.jboss.com/jira/browse/JBADMCON-110 Project: JBoss Admin Console Type: Sub-task Components: JBossMQ Versions: 1.1 alpha Reporter: Peter Johnson Assignee: Peter Johnson Fix For: 1.1 alpha -- 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: (JBADMCON-106) Document use case
[ http://jira.jboss.com/jira/browse/JBADMCON-106?page=comments#action_12316485 ] Peter Johnson commented on JBADMCON-106: Use cases have been posted on the forum. Document use case - Key: JBADMCON-106 URL: http://jira.jboss.com/jira/browse/JBADMCON-106 Project: JBoss Admin Console Type: Sub-task Components: JBossMQ Versions: 1.1 alpha Reporter: Peter Johnson Assignee: Peter Johnson Fix For: 1.1 alpha -- 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: (JBADMCON-111) Implement and test View
[ http://jira.jboss.com/jira/browse/JBADMCON-111?page=history ] Peter Johnson reassigned JBADMCON-111: -- Assign To: Peter Johnson Tentative classes have been coded. Implement and test View - Key: JBADMCON-111 URL: http://jira.jboss.com/jira/browse/JBADMCON-111 Project: JBoss Admin Console Type: Sub-task Reporter: Peter Johnson Assignee: Peter Johnson -- 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: (JBADMCON-112) Implement and test Controller
[ http://jira.jboss.com/jira/browse/JBADMCON-112?page=history ] Peter Johnson reassigned JBADMCON-112: -- Assign To: Peter Johnson Implement and test Controller --- Key: JBADMCON-112 URL: http://jira.jboss.com/jira/browse/JBADMCON-112 Project: JBoss Admin Console Type: Sub-task Reporter: Peter Johnson Assignee: Peter Johnson -- 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: (JBADMCON-113) Implement and test Model
[ http://jira.jboss.com/jira/browse/JBADMCON-113?page=history ] Peter Johnson reassigned JBADMCON-113: -- Assign To: Peter Johnson Implement and test Model -- Key: JBADMCON-113 URL: http://jira.jboss.com/jira/browse/JBADMCON-113 Project: JBoss Admin Console Type: Sub-task Reporter: Peter Johnson Assignee: Peter Johnson -- 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: (JBADMCON-112) Implement and test Controller
[ http://jira.jboss.com/jira/browse/JBADMCON-112?page=comments#action_12316488 ] Peter Johnson commented on JBADMCON-112: Tentative classes have been coded. Implement and test Controller --- Key: JBADMCON-112 URL: http://jira.jboss.com/jira/browse/JBADMCON-112 Project: JBoss Admin Console Type: Sub-task Reporter: Peter Johnson Assignee: Peter Johnson -- 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: (JBADMCON-113) Implement and test Model
[ http://jira.jboss.com/jira/browse/JBADMCON-113?page=comments#action_12316489 ] Peter Johnson commented on JBADMCON-113: Tentative classes have been coded. Implement and test Model -- Key: JBADMCON-113 URL: http://jira.jboss.com/jira/browse/JBADMCON-113 Project: JBoss Admin Console Type: Sub-task Reporter: Peter Johnson Assignee: Peter Johnson -- 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: (JBADMCON-108) Implement and test Controller
[ http://jira.jboss.com/jira/browse/JBADMCON-108?page=history ] Peter Johnson reassigned JBADMCON-108: -- Assign To: Peter Johnson Implement and test Controller --- Key: JBADMCON-108 URL: http://jira.jboss.com/jira/browse/JBADMCON-108 Project: JBoss Admin Console Type: Sub-task Reporter: Peter Johnson Assignee: Peter Johnson -- 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: (JBADMCON-107) Implement and test View
[ http://jira.jboss.com/jira/browse/JBADMCON-107?page=history ] Peter Johnson reassigned JBADMCON-107: -- Assign To: Peter Johnson Implement and test View - Key: JBADMCON-107 URL: http://jira.jboss.com/jira/browse/JBADMCON-107 Project: JBoss Admin Console Type: Sub-task Reporter: Peter Johnson Assignee: Peter Johnson -- 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: (JBADMCON-107) Implement and test View
[ http://jira.jboss.com/jira/browse/JBADMCON-107?page=comments#action_12316490 ] Peter Johnson commented on JBADMCON-107: Tentative classes have been coded. Implement and test View - Key: JBADMCON-107 URL: http://jira.jboss.com/jira/browse/JBADMCON-107 Project: JBoss Admin Console Type: Sub-task Reporter: Peter Johnson Assignee: Peter Johnson -- 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: (JBADMCON-109) Implement and test Model
[ http://jira.jboss.com/jira/browse/JBADMCON-109?page=history ] Peter Johnson reassigned JBADMCON-109: -- Assign To: Peter Johnson Implement and test Model -- Key: JBADMCON-109 URL: http://jira.jboss.com/jira/browse/JBADMCON-109 Project: JBoss Admin Console Type: Sub-task Reporter: Peter Johnson Assignee: Peter Johnson -- 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: (JBADMCON-108) Implement and test Controller
[ http://jira.jboss.com/jira/browse/JBADMCON-108?page=comments#action_12316491 ] Peter Johnson commented on JBADMCON-108: Tentative classes have been coded. Implement and test Controller --- Key: JBADMCON-108 URL: http://jira.jboss.com/jira/browse/JBADMCON-108 Project: JBoss Admin Console Type: Sub-task Reporter: Peter Johnson Assignee: Peter Johnson -- 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: (JBADMCON-109) Implement and test Model
[ http://jira.jboss.com/jira/browse/JBADMCON-109?page=comments#action_12316492 ] Peter Johnson commented on JBADMCON-109: Tentative classes have been coded. Implement and test Model -- Key: JBADMCON-109 URL: http://jira.jboss.com/jira/browse/JBADMCON-109 Project: JBoss Admin Console Type: Sub-task Reporter: Peter Johnson Assignee: Peter Johnson -- 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-1629) message-destination-link does not work for MDB's
[ http://jira.jboss.com/jira/browse/JBAS-1629?page=history ] Adrian Brock closed JBAS-1629: -- Resolution: Duplicate Issue Please test the latest version (including release candidates) before reporting bugs. http://cvs.sourceforge.net/viewcvs.py/jboss/jboss/src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java?r1=1.64.2.9r2=1.64.2.10 If it doesn't work for you, feel free to reopen the original bug report. message-destination-link does not work for MDB's Key: JBAS-1629 URL: http://jira.jboss.com/jira/browse/JBAS-1629 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 SP1 Reporter: Matthias Germann Setting the message-destination-link child element of the message-driven element does not work on JBoss 4.0.1sp1. JBAS-1130 is related to this but i think that message-destination-link support was only added for the message-destination-ref element but not for the message-driven element. A message-driven bean can sspecify the message-destination it want's to listen to with the message-destination-link element (see http://java.sun.com/developer/EJTechTips/2005/tt0322.html#1). i.e.: message-driven ejb-nameRegEmailSender/ejb-name ejb-classch.tvfrutigen.chandertaler.ejb.service.RegEmailSenderBean/ejb-class messaging-typejavax.jms.MessageListener/messaging-type transaction-typeContainer/transaction-type message-destination-typejavax.jms.Queue/message-destination-type message-destination-linkRegEmailsQueue/message-destination-link ... /message-driven It should be possible that the senders of a message and the processing MDBs can link to the same message-destination in the assembly-descriptor. Therefore, only the message-destination in the assembly-descriptor must be mapped to a jndi-name in jboss.xml. Setting the message-destination-link elment on JBoss 4.0.1sp1 has no effect. It is still necessary to map the MDB's to the jndi-name of the queue/topic using the destination-jndi-name element. IMHO, it should not be necessary to specify the destination-jndi-name element when using message-destinations. -- 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: (JBADMCON-109) Implement and test Model
[ http://jira.jboss.com/jira/browse/JBADMCON-109?page=history ] Peter Johnson updated JBADMCON-109: --- Attachment: queue_elements.pdf Preliminary property set for queues Implement and test Model -- Key: JBADMCON-109 URL: http://jira.jboss.com/jira/browse/JBADMCON-109 Project: JBoss Admin Console Type: Sub-task Reporter: Peter Johnson Assignee: Peter Johnson Attachments: queue_elements.pdf -- 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: (JBADMCON-113) Implement and test Model
[ http://jira.jboss.com/jira/browse/JBADMCON-113?page=history ] Peter Johnson updated JBADMCON-113: --- Attachment: topic_elements.pdf Preliminary property set for topics. Implement and test Model -- Key: JBADMCON-113 URL: http://jira.jboss.com/jira/browse/JBADMCON-113 Project: JBoss Admin Console Type: Sub-task Reporter: Peter Johnson Assignee: Peter Johnson Attachments: topic_elements.pdf -- 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-1461) Add support for JBossXB to the service deployment layer
[ http://jira.jboss.com/jira/browse/JBAS-1461?page=history ]
Scott M Stark updated JBAS-1461:
Fix Version: JBossAS-4.0.3 Final
(was: JBossAS-4.0.2 Final)
Add support for JBossXB to the service deployment layer
---
Key: JBAS-1461
URL: http://jira.jboss.com/jira/browse/JBAS-1461
Project: JBoss Application Server
Type: Task
Components: MicroContainer bus, JMX
Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
Reporter: Scott M Stark
Priority: Critical
Fix For: JBossAS-4.0.3 Final
Original Estimate: 2 days
Remaining: 2 days
We need to add support for use of the JBossXB framework for the processing of
non-trivial service attribute specifications using pluggable object
factories. One prototype document illustrating different forms of
externalized attribute parsing is:
?xml version=1.0 encoding=UTF-8?
!-- Tell JBossXB about the namespace to factory mappings in this doc --
?jbossxb ns=urn:schema:ns1:jbossxb
factory=org.jboss.test.jmx.complexattrs.JavaBeanObjectModelFactory?
!-- Tests of unmarshalling complex attributes
--
server
!-- Set the prop3.systemProperty system property --
mbean code=org.jboss.varia.property.SystemPropertiesService
name=test:name=ComplexAttrTests,action=SystemProperties
attribute name=Propertiesprop3.systemProperty=value3/attribute
/mbean
!-- Test the javaBean attribute data type syntax --
mbean code=org.jboss.test.jmx.complexattrs.ComplexAttrTests
name=test:name=ComplexAttrTests,case=#1
attribute name=Bean1
attributeClass=org.jboss.test.jmx.complexattrs.JavaBean1
serialDataType=javaBean
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
/attribute
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
!-- 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
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
/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
---
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-1559) Check all serverSocket accept threads
[ http://jira.jboss.com/jira/browse/JBAS-1559?page=history ] Scott M Stark closed JBAS-1559: --- Resolution: Done I have gone through the existing 4.0 codebase and updated all ServerSocket.accept usage found and added Throwable exception handling. There are a few testcases and deprecated jms ils that were not touched. 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 Priority: Critical Fix For: JBossAS-5.0 Alpha, 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 JIRA] Updated: (JBREM-43) custom socket factories
[ http://jira.jboss.com/jira/browse/JBREM-43?page=history ] Tom Elrod updated JBREM-43: Priority: Critical (was: Major) custom socket factories --- Key: JBREM-43 URL: http://jira.jboss.com/jira/browse/JBREM-43 Project: JBoss Remoting Type: Feature Request Components: transport Versions: 1.0.1 beta Reporter: Tom Elrod Assignee: Tom Elrod Priority: Critical Fix For: 1.2.0 beta Add support for custom socket factories for socket invoker (and maybe others) -- 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-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050329154331 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:03/29/2005 15:43:31Time to build:122 minutes 30 secondsLast changed:03/29/2005 15:07:31Last log entry:[JBAS-1434] - Backport tests for jms inbound rar from jboss-head Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(111)1.1.2.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/dlq/AbstractDLQHandler.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.2.2.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/JmsActivationSpec.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.2.2.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/JmsActivation.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/resources/messagedriven/jboss-service.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/resources/messagedriven/queuexa/META-INF/ejb-jar.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/resources/messagedriven/queuexa/META-INF/jboss.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/beans/TestMessageDriven.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/main/org/jboss/test/messagedriven/beans/TestMessageDrivenManagement.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/main/org/jboss/test/messagedriven/beans/TestMessageDrivenManagementMBean.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.2modifiedejorttestsuite/src/resources/messagedriven/jmscontainerinvoker/META-INF/ejb-jar.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/resources/messagedriven/jmscontainerinvoker/META-INF/jboss.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.9.2.62modifiedejorttestsuite/imports/test-jars.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.2modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/test/JMSContainerInvokerMessageDrivenUnitTestCase.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/test/SimpleQueueMessageDrivenUnitTestCase.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/test/SimpleTopicMessageDrivenUnitTestCase.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/resources/messagedriven/topicxa/META-INF/ejb-jar.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/resources/messagedriven/topicxa/META-INF/jboss.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/BasicMessageDrivenUnitTest.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/main/org/jboss/test/messagedriven/support/BasicTest.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/CheckJMSDestinationOperation.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/CheckMessageIDOperation.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/CheckMessagePropertyOperation.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/CheckMessageSizeOperation.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.2deletedejorttestsuite/src/main/org/jboss/test/messagedriven/support/JMSContainerInvokerTest.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/Operation.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/main/org/jboss/test/messagedriven/support/QueueXATest.java[JBAS-1434] - Backport tests for jms inbound rar from
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1629) message-destination-link does not work for MDB's
[ http://jira.jboss.com/jira/browse/JBAS-1629?page=comments#action_12316497 ] Matthias Germann commented on JBAS-1629: Yes, JBoss 4.0.2RC1 works as i expect it to. I'm really sorry for that i did not check it with the latest release candidate before opening a bug report. Next time i will do it... Regards, Matthias message-destination-link does not work for MDB's Key: JBAS-1629 URL: http://jira.jboss.com/jira/browse/JBAS-1629 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.1 SP1 Reporter: Matthias Germann Setting the message-destination-link child element of the message-driven element does not work on JBoss 4.0.1sp1. JBAS-1130 is related to this but i think that message-destination-link support was only added for the message-destination-ref element but not for the message-driven element. A message-driven bean can sspecify the message-destination it want's to listen to with the message-destination-link element (see http://java.sun.com/developer/EJTechTips/2005/tt0322.html#1). i.e.: message-driven ejb-nameRegEmailSender/ejb-name ejb-classch.tvfrutigen.chandertaler.ejb.service.RegEmailSenderBean/ejb-class messaging-typejavax.jms.MessageListener/messaging-type transaction-typeContainer/transaction-type message-destination-typejavax.jms.Queue/message-destination-type message-destination-linkRegEmailsQueue/message-destination-link ... /message-driven It should be possible that the senders of a message and the processing MDBs can link to the same message-destination in the assembly-descriptor. Therefore, only the message-destination in the assembly-descriptor must be mapped to a jndi-name in jboss.xml. Setting the message-destination-link elment on JBoss 4.0.1sp1 has no effect. It is still necessary to map the MDB's to the jndi-name of the queue/topic using the destination-jndi-name element. IMHO, it should not be necessary to specify the destination-jndi-name element when using message-destinations. -- 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)] - Dynamic Class loading, SPI?, advice please
Hello, I have a custom server that I run in JBoss within an MBean. This server needs to dynamically initialise certain objects seperate from the main core of the custom server. I tried to load these classes with using standard Class.forName(..) type stuff but I kept getting class loader errors when running within JBoss (3.2.6). How should I go about dynamically loading classes within an Mbean? The classes are likely to be bundled within different .jar files inside the MBean directory. Could I use the SPI, service provide interface? or if there a better method I should use. Any suggestions would be much appreciated as I'm not really sure what is the most JBoss way of solving this problem. best wishes James View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871958#3871958 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871958 --- 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] - Error with nested transactions, but I'm not nesting transact
I'm getting erratic, non-repeatable exceptions involving nested transactions,
apparently from within code which is not nesting transactions. This code is
accessing the TreeCacheAop service. and it runs flawlessly most of the time.
Even after the exceptions are caught by JBoss I can continue with the
application with no apparent side effects, and the exceptions may or may not
appear again for some time.
The method in which the exception is detected is updateReceivedTime(), which
creates and starts a UserTransaction. It calls another method which creates no
transaction, and this method calls a third method which creates no transaction.
The second and third methods in the chain each access the TreeCacheAop service
via the MBeanServer, invoking the exists() and getObject() methods of the
TreeCacheAop service. Once a dynamic proxy for a HashMap object is retrieved
from the TreeCacheAop and returned to the original method
(updateReceivedTime()) it is then used to construct a new object (UserActivity)
which has two Date fields which are immediately set with values. The
transaction is then committed and the method returns. The UserActivity
object's field values are updated in the corresponding HashMap object stored in
the TreeCacheAop -- I'm not sure how JBossCache accomplishes this, but it works
almost every time, except when the nested transactions are detected. To
illustrate I will list the code of the three methods mentioned above. These
are part of an MBean which is being accessed from my Servlets and EJBs via
MBeanServer.invoke() method calls.
public synchronized void updateReceivedTime (String userId)
| throws MBeanException
| {
| try
| {
| // create and begin a transaction
| UserTransaction userTransaction = (UserTransaction)
m_jndiContext.lookup(UserTransaction);
| userTransaction.begin();
|
| // get the UserActivity for the user
| HashMap userActivityMap = getUserActivityMap(userId);
| UserActivity userActivity = new UserActivity(userActivityMap);
|
| // set the access time, received time, and session
| userActivity.setLastHeartbeatTime(new Date());
| userActivity.setLastReceivedTime(new Date());
|
| // commit the transaction
| userTransaction.commit();
| }
| catch (Exception e)
| {
| // log the error and throw an Exception
| m_logger.error(Unable to update the user activity information
for the user with ID + userId, e);
| throw new MBeanException(e, Unable to update the user activity
information for the user with ID + userId);
| }
| }
|
|
| private HashMap getUserActivityMap (String userId)
| throws MBeanException
| {
| // get the corresponding fqn of the UserActivity HashMap object for
the user, if one already exists
| String fullyQualifiedName = getFullyQualifiedName(userId);
|
| // if we found a fqn then a UserActivity HashMap object for the
user exists
| if (fullyQualifiedName != null)
| {
| try
| {
| // return the dynamic proxy for the HashMap we're using to
represent the user's UserActivity object
| return (HashMap) m_mbeanServer.invoke(m_cacheService,
| getObject,
| new Object[]
{fullyQualifiedName},
| new String[]
{String.class.getName()});
| }
| catch (Exception e)
| {
| // log the error and throw an Exception
| m_logger.error(Unable to get the cached UserActivity
HashMap object for the user with ID + userId, e);
| throw new MBeanException(e, Unable to get the cached
UserActivity HashMap object for the user with ID + userId);
| }
| }
| else
| {
| // a corresponding HashMap object wasn't found in the cache
| m_logger.warn(Unable to find a UserActivity HashMap object for
the user with ID + userId);
| return null;
| }
| }
|
|
| private String getFullyQualifiedName (String userId)
| throws MBeanException
| {
| // build fully qualified names using the node names and the user ID
| String himName = NODE_HIM + / + userId;
| String webName = NODE_WEB + / + userId;
|
| try
| {
| // see if a UserActivity object exists for the user under the
HIM node
| Boolean userExists = (Boolean)
m_mbeanServer.invoke(m_cacheService,
[JBoss-dev] [Design of JMX on JBoss (JBoss/JMX)] - Re: Dynamic Class loading, SPI?, advice please
Appologies, just realised this is not the place for this kind query. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871960#3871960 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871960 --- 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.907 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050329181256Lbuild.907 BUILD COMPLETE-build.907Date of build:03/29/2005 18:12:56Time to build:17 minutes 19 secondsLast changed:03/29/2005 18:04:43Last log entry:Add xsd:annotation Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(47)1.3modifiedosdchicagowebservice/test/resources/tools/xsd/complextypes/ComplexType_ElementsOnly.xsdAdd xsd:annotation1.2modifiedosdchicagowebservice/docs/tools-docs/wscompileIssues.txtSome wscompile issues.1.47modifiedejorttestsuite/imports/test-jars.xmlForward port the jmscontainerinvoker tests that usethe EJB2.1 style deployments.This will make it easier to port the tests.1.8modifiedovidiufremoting/src/main/org/jboss/remoting/transport/local/LocalClientInvoker.javatentative fix for http://jira.jboss.org/jira/browse/JBREM-921.2modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/test/JMSContainerInvokerMessageDrivenUnitTestCase.javaForward port the jmscontainerinvoker tests that usethe EJB2.1 style deployments.This will make it easier to port the tests.1.6modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/BasicMessageDrivenUnitTest.javaForward port the jmscontainerinvoker tests that usethe EJB2.1 style deployments.This will make it easier to port the tests.1.1addedkabkhanaop/src/main/org/jboss/aop/DispatcherConnectException.javaException hierarchy for Dispatcher exceptions1.2modifiedkabkhanaop/src/main/org/jboss/aop/NotFoundInDispatcherException.javaException hierarchy for Dispatcher exceptions1.6modifiedkabkhanaspects/src/main/org/jboss/aspects/remoting/ClusterChooserInterceptor.javaException hierarchy for Dispatcher exceptions1.7modifiedpatriot1burkecommon/src/main/org/jboss/xml/binding/SimpleTypeBindings.javaIntellij JDK 5 compiler didn't like the compareTo statements. This change should be compatible with JDK 1.41.2modifiedosdchicagowebservice/test/resources/tools/CustomInterface20.xsdClean up the xsd1.5modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/xsdjava/XSDToJavaTestCase.javaAdded functionality based on the test harness of JBWS-1471.3modifiedosdchicagowebservice/test/resources/tools/xsd/simpletypes/SimpleType.xsdJBWS-147: test harness for xsd-Java conversion.1.2modifiedosdchicagowebservice/test/resources/tools/xsd/complextypes/ComplexType_ElementsOnly.xsdJBWS-147: test harness for xsd-Java conversion.1.1addedosdchicagowebservice/test/resources/tools/xsd/complextypes/ComplexType_MixedContent.xsdJBWS-147: test harness for xsd-Java conversion.1.1addedosdchicagowebservice/test/resources/tools/xsd/complextypes/ComplexTypesOccurence.xsdJBWS-147: test harness for xsd-Java conversion.1.2modifiedosdchicagowebservice/test/resources/tools/xsd/complextypes/CT_EmptyContent.xsdJBWS-147: test harness for xsd-Java conversion.1.2modifiedosdchicagowebservice/test/resources/tools/xsd/complextypes/CT_SequenceGroups.xsdJBWS-147: test harness for xsd-Java conversion.1.7modifiedosdchicagowebservice/src/main/org/jboss/ws/utils/WSDLUtils.javaSome added functionality.1.9modifiedosdchicagowebservice/src/main/org/jboss/ws/tools/SchemaBuilder.javaBetter support for xsd:group, xsd:attribute, xsd:attributegroup, references (element and attribute). Also strengthened conversion of schema types into Java types. Added functionality based on the test harness of JBWS-1471.8modifiedosdchicagowebservice/src/main/org/jboss/ws/tools/WSDLToJava.javaBetter support for xsd:group, xsd:attribute, xsd:attributegroup, references (element and attribute). Also strengthened conversion of schema types into Java types. Added functionality based on the test harness of JBWS-1471.3modifiedosdchicagowebservice/src/main/org/jboss/ws/wsdl/xsd/XSDAttribute.javaAdded functionality based on the test harness of JBWS-1471.5modifiedosdchicagowebservice/src/main/org/jboss/ws/wsdl/xsd/XSDComplexType.javaAdded functionality based on the test harness of JBWS-1471.5modifiedosdchicagowebservice/src/main/org/jboss/ws/wsdl/xsd/XSDElement.javaAdded functionality based on the test harness of JBWS-1471.16modifiedosdchicagowebservice/src/main/org/jboss/ws/wsdl/xsd/XSDSchema.javaAdded functionality based on the test harness of JBWS-1471.2modifiedosdchicagowebservice/src/main/org/jboss/ws/wsdl/xsd/XSDSimpleType.javaAdded functionality based on the test harness of JBWS-1471.1addedosdchicagowebservice/src/main/org/jboss/ws/wsdl/xsd/XSDAny.javaSupport xsd:any and xsd:group constructs.1.1addedosdchicagowebservice/src/main/org/jboss/ws/wsdl/xsd/XSDGroup.javaSupport xsd:any and xsd:group constructs.1.3modifiedovidiufjms/src/main/org/jboss/jms/tools/ServerWrapper.javapre-alpha development1.11modifiedovidiufjms/tests/build.xmlpre-alpha development1.2modifiedovidiufjms/src/main/org/jboss/jms/server/endpoint/Consumer.javapre-alpha
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - JSR-88 DeploymentManager
Hi, I'm a newbie to JBoss. I am trying to use JBoss implementation of JSR-88 and have not been able to get very far. I was able to get an instance of DeploymentManager after instantiating org.jboss.deployment.spi.factories.DeploymentFactoryImpl and passing it the URI jboss-deployer:localhost:8080. But when I made the call deployMgr.getAvailableModules(ModuleType.EAR, deployMgr.getTargets()) on the deploymemt manager, I run into this exception: java.lang.NullPointerException at java.util.Arrays$ArrayList.(Arrays.java:2342) at java.util.Arrays.asList(Arrays.java:2328) at org.jboss.deployment.spi.DeploymentManagerImpl.getAvailableModules(DeploymentManagerImpl.java:231) Any ideas? Thanks for your help. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871963#3871963 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871963 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBREM-94) callback server specific implementation
callback server specific implementation --- Key: JBREM-94 URL: http://jira.jboss.com/jira/browse/JBREM-94 Project: JBoss Remoting Type: Feature Request Components: callbacks Versions: 1.0.2 final Reporter: Tom Elrod Assigned to: Tom Elrod Fix For: 1.2.0 beta Since it is possible to have a callback server that never receives direct invocations and only callbacks, there is no need for the requirement to have a handler registered for the server (since will never be called upon). Therefore, need to add a callback server specific implementation for this behaviour. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Starting a callback server requires unnecessary step
Ahh. Ok. I misunderstood what you were saying originally. For the callback server, if it is not handling any direct invocations, only callbacks, the I agree that there is no need for a handler to be registered (conceptually). However, I don't make a distinction, in the implementation, between a normal remoting server that receives direct invocations and one that only receives callbacks. I think that the best way to accomidate for this it to add a new callback server specific implementation that does not require a invocation handler. Have added it as a task in jira ( JBREM-94). Thanks for following up. Sorry I missed the original point. :) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871965#3871965 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871965 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: JSR-88 DeploymentManager
Further examination of JBoss code seems to indicate the DeploymentManager is not really connected to the appserver. So the JBossTarget.getAvailableModules() will returns null which will get processed by deployMgr.getAvailableModule() (and undoudtedly will encounter NPE). I guess my question now is -- Does JBoss really support JSR-88? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871967#3871967 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871967 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-39) build for jmx
[ http://jira.jboss.com/jira/browse/JBBUILD-39?page=history ] Ryan Campbell resolved JBBUILD-39: -- Resolution: Done all artifacts from this component are being built correctly build for jmx - Key: JBBUILD-39 URL: http://jira.jboss.com/jira/browse/JBBUILD-39 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.455 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050329185154Lbuild.455 BUILD COMPLETE-build.455Date of build:03/29/2005 18:51:54Time to build:38 minutes 36 secondsLast changed:03/29/2005 15:07:31Last log entry:[JBAS-1434] - Backport tests for jms inbound rar from jboss-head Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(31)1.1.2.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/dlq/AbstractDLQHandler.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.2.2.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/JmsActivationSpec.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.2.2.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/JmsActivation.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/resources/messagedriven/jboss-service.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/resources/messagedriven/queuexa/META-INF/ejb-jar.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/resources/messagedriven/queuexa/META-INF/jboss.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/beans/TestMessageDriven.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/main/org/jboss/test/messagedriven/beans/TestMessageDrivenManagement.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/main/org/jboss/test/messagedriven/beans/TestMessageDrivenManagementMBean.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.2modifiedejorttestsuite/src/resources/messagedriven/jmscontainerinvoker/META-INF/ejb-jar.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/resources/messagedriven/jmscontainerinvoker/META-INF/jboss.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.9.2.62modifiedejorttestsuite/imports/test-jars.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.2modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/test/JMSContainerInvokerMessageDrivenUnitTestCase.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/test/SimpleQueueMessageDrivenUnitTestCase.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/test/SimpleTopicMessageDrivenUnitTestCase.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/resources/messagedriven/topicxa/META-INF/ejb-jar.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/resources/messagedriven/topicxa/META-INF/jboss.xml[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/BasicMessageDrivenUnitTest.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/main/org/jboss/test/messagedriven/support/BasicTest.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/CheckJMSDestinationOperation.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/CheckMessageIDOperation.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/CheckMessagePropertyOperation.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/CheckMessageSizeOperation.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.2deletedejorttestsuite/src/main/org/jboss/test/messagedriven/support/JMSContainerInvokerTest.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/Operation.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1deletedejorttestsuite/src/main/org/jboss/test/messagedriven/support/QueueXATest.java[JBAS-1434] - Backport tests for jms inbound rar from jboss-head1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/SendMessageOperation.java[JBAS-1434] - Backport tests for jms inbound rar from
