[JBoss-dev] [JBossCache] - Re: Deleting rather than replicating updates
sure, then use remove(key,val) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871579#3871579 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871579 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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-98) delete process instances and process definitions
delete process instances and process definitions Key: JBPM-98 URL: http://jira.jboss.com/jira/browse/JBPM-98 Project: JBoss jBPM Type: Task Reporter: Tom Baeyens Assigned to: Tom Baeyens Priority: Minor Fix For: jBPM 3.0 alpha 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] Closed: (JBPM-98) delete process instances and process definitions
[ http://jira.jboss.com/jira/browse/JBPM-98?page=history ] Tom Baeyens closed JBPM-98: --- Resolution: Done delete process instances and process definitions Key: JBPM-98 URL: http://jira.jboss.com/jira/browse/JBPM-98 Project: JBoss jBPM Type: Task Reporter: Tom Baeyens Assignee: Tom Baeyens Priority: Minor Fix For: jBPM 3.0 alpha 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] Closed: (JBPM-50) support versioned class loading
[ http://jira.jboss.com/jira/browse/JBPM-50?page=history ] Tom Baeyens closed JBPM-50: --- Resolution: Done support versioned class loading --- Key: JBPM-50 URL: http://jira.jboss.com/jira/browse/JBPM-50 Project: JBoss jBPM Type: Task Components: Core Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Priority: Minor Fix For: jBPM 3.0 alpha 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] Created: (JBJMX-86) setAttribute does not find correct method
setAttribute does not find correct method
-
Key: JBJMX-86
URL: http://jira.jboss.com/jira/browse/JBJMX-86
Project: JBoss JMX
Type: Bug
Versions: JBossAS-4.0.1
Reporter: Michael Kopp
The setAttribute searches for a method:
Class[] clArr = null;
if (attribute.getValue() != null)
{
clArr = new Class[]{attribute.getValue().getClass()};
}
Method method = implementation.getClass().getMethod(set +
attribute.getName(), clArr);
This means that if the value is DomElement, the class would be a
org.apache.xerces.dom.DeferredElementImpl. But the Setter would normally
reference org.w3c.dom.Element.
The feature of jboss to support Element in a -service.xml is pretty useless
this way.
I think this should be done in the same way as Java5 does it. search for a
method with the right name and the right number of parameters. for the found
ones, check if the paramters are assignable. This way subclass and
implementations of interfaces can be supported.
--
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: (JBIDE-163) deploy a process archive
deploy a process archive Key: JBIDE-163 URL: http://jira.jboss.com/jira/browse/JBIDE-163 Project: JBoss IDE Type: Feature Request Components: jBPM Designer plugin Reporter: Tom Baeyens Assigned to: Marshall Culpepper -- 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=log20050324105540 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/24/2005 10:55:40Time to build:1,289 minutes 12 secondsLast changed:03/24/2005 08:35:06Last log entry:ported ha local connection factory from HEAD Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(18)1.9.2.60modifiedloubyanskytestsuite/imports/test-jars.xmlported ha local connection factory from HEAD1.2.2.1modifiedloubyanskytestsuite/src/main/org/jboss/test/jca/test/HAConnectionFactoryUnitTestCase.javaported ha local connection factory from HEAD1.1.2.1modifiedloubyanskytestsuite/src/main/org/jboss/test/jca/ejb/HAConnectionSessionBean.javaported ha local connection factory from HEAD1.4.2.3modifiedloubyanskytools/etc/buildmagic/modules.xmlported ha local connection factory from HEAD1.67.2.6modifiedloubyanskyconnector/build.xmlported ha local connection factory from HEAD1.22.2.5modifiedloubyanskyconnector/src/resources/stylesheets/ConnectionFactoryTemplate.xslported ha local connection factory from HEAD1.1.2.4modifiedloubyanskyconnector/src/resources/dtd/jboss-ds_1_5.dtdported ha local connection factory from HEAD1.6.2.1modifiedloubyanskyconnector/src/main/org/jboss/resource/adapter/jdbc/local/HALocalManagedConnectionFactory.javaported ha local connection factory from HEAD1.13.4.2modifiedanddsystem/src/main/org/jboss/system/server/ServerConfig.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console1.9.6.1modifiedanddsystem/src/main/org/jboss/system/server/ServerConfigImpl.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console1.47.2.4modifiedanddsystem/src/main/org/jboss/system/server/ServerImpl.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console1.4.6.1modifiedanddjmx/src/main/org/jboss/mx/util/MBeanServerLocator.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console1.75.2.3modifiedanddjmx/src/main/org/jboss/mx/server/MBeanServerImpl.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and
[JBoss-dev] [Design of JBoss Portal] - Firebird SQL generation problem
Hi all, I try to use Portal 2.0 b1 with Firebird DB. Everithing seams OK but when I try to list users (click on filter button) I've got SQL exception exception and no user listed. in log file I see taht this sql statemnt was generated | 2005-03-25 14:44:46,815 DEBUG [net.sf.hibernate.SQL] select userimpl0_.jbp_uid as x0_0_ from jbp_users userimpl0_ where (userimpl0_.jbp_uname LIKE '%' ? '%' ) rows ? | This statement is wrong. What does it mean rows ? Jan View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871593#3871593 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871593 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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: (JBJMX-86) setAttribute does not find correct method
[ http://jira.jboss.com/jira/browse/JBJMX-86?page=comments#action_12316400
]
Dimitris Andreadis commented on JBJMX-86:
-
Can you be more specific about the use-case you want to implement? Maybe,
provide an example.
setAttribute does not find correct method
-
Key: JBJMX-86
URL: http://jira.jboss.com/jira/browse/JBJMX-86
Project: JBoss JMX
Type: Bug
Versions: JBossAS-4.0.1
Reporter: Michael Kopp
The setAttribute searches for a method:
Class[] clArr = null;
if (attribute.getValue() != null)
{
clArr = new Class[]{attribute.getValue().getClass()};
}
Method method = implementation.getClass().getMethod(set +
attribute.getName(), clArr);
This means that if the value is DomElement, the class would be a
org.apache.xerces.dom.DeferredElementImpl. But the Setter would normally
reference org.w3c.dom.Element.
The feature of jboss to support Element in a -service.xml is pretty useless
this way.
I think this should be done in the same way as Java5 does it. search for a
method with the right name and the right number of parameters. for the found
ones, check if the paramters are assignable. This way subclass and
implementations of interfaces can be supported.
--
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: TreeCache redeploy problem in WebLogic 8.1
Have u tried putting all dependent jars for the cache in the classpath setting in the weblogic startup script? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871594#3871594 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871594 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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] - Own servlet mapping
How can I my map my own servlet in portal (e.g. graphic servlet, that creates diagram)?I know, that there is no direct mapping!? And I have no ideas how to do this. Thank you View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871598#3871598 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871598 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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.453 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050325092955Lbuild.453 BUILD COMPLETE-build.453Date of build:03/25/2005 09:29:55Time to build:34 minutes 9 secondsLast changed:03/25/2005 01:16:13Last log entry:Add the SecurityManagerService attribute for testing the auth cache flushing. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(2)1.1.2.1modifiedstarksmtestsuite/src/resources/test-configs/jacc/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xmlAdd the SecurityManagerService attribute for testing the auth cache flushing.1.9.2.61modifiedstarksmtestsuite/imports/test-jars.xmlAdd the cross-server.jar target
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1619) LoadLibrary should be done through the deployment classloader
LoadLibrary should be done through the deployment classloader - Key: JBAS-1619 URL: http://jira.jboss.com/jira/browse/JBAS-1619 Project: JBoss Application Server Type: Bug Components: Deployment Service Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 Reporter: Adrian Brock LoadLibrary needs to be done the deployment classloader to avoid memory leaks. Currently it is done through the NoAnnotationURLClassLoader (the base classloader) so they will never be garbage collected/unloaded. -- 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_12316401 ] Scott M Stark commented on JBAS-1579: - The diffs in terms of obtaining the serialVersionUID should be encapsulated in the java.io.ObjectStreamClass.getSerialVersionUID used by the org.jboss.tools.SerialVersionUID utility class so there is no need to reproduce this behavior. We should be using the exact same algorithm as the vm so that the serialVersionUID can be calculated by tools such as serialver of the jdk. In terms the comparison of the jbossall-client.jar vs the classes in /lib and /server/all as calculated by the SerialVersionUID there are two problems. 1. The size of the serialVersionUID databases are more than 10x larger. For example, the 4.0.1 jbossall-client.jar vs the testsuite/src/etc/serialVersionUID/401.ser is: 342882 401.ser 4148296 jbossall-client.jar If this is going to be part of the intrinsic testsuite archiving the jbossall-client.jar is too much. 2. All server classes need to be validated for serialVersionUID changes. There are many paths that do not involve clients which still serialize objects that need validation. I would just merge your test result into the existing SerialVersionUIDUnitTestCase. 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] [JBoss JIRA] Created: (JBPM-99) business calender
business calender - Key: JBPM-99 URL: http://jira.jboss.com/jira/browse/JBPM-99 Project: JBoss jBPM Type: Feature Request Components: Core Engine Reporter: Tom Baeyens Assigned to: Tom Baeyens Priority: Minor a business calender would have knowledge about working hours and can do calculations like : 1) what time is it, 4 business hours from now. 2) how much business hours were there between 2 dates. ... in a simple version, the business calender would not now about holidays. in the deluxe version the business calender would be integrated with the organisation component and knows the holidays of the different countries. -- 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-1555) HTTP Status 403 on using org.jboss.web.tomcat.security.JaccAuthorizationRealm
[ http://jira.jboss.com/jira/browse/JBAS-1555?page=history ] Scott M Stark closed JBAS-1555: --- Resolution: Done Fix Version: JBossAS-4.0.2 Final JBossAS-5.0 Alpha HTTP Status 403 on using org.jboss.web.tomcat.security.JaccAuthorizationRealm -- Key: JBAS-1555 URL: http://jira.jboss.com/jira/browse/JBAS-1555 Project: JBoss Application Server Type: Bug Components: Security Versions: JBossAS-4.0.1 SP1 Environment: JBoss 4.0.1 sp1, tomcat 5.0.28 Reporter: Roland R?z Assignee: Scott M Stark Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha Hello, I try to run JBoss Duke Bank application on JBoss 4.0.1 sp1 and it works fine until I'm using org.jboss.web.tomcat.security.JBossSecurityMgrRealm in the server.xml configuration. ... Realm className=org.jboss.web.tomcat.security.JBossSecurityMgrRealm certificatePrincipal=org.jboss.security.auth.certs.SubjectDNMapping/ ... As soon I replace this realm by org.jboss.web.tomcat.security.JaccAuthorizationRealm: Realm className=org.jboss.web.tomcat.security.JaccAuthorizationRealm certificatePrincipal=org.jboss.security.auth.certs.SubjectDNMapping/ the logon is still successful but the every second call to the servlet is responded with HTTP Status 403 - Access to the requested resource has been denied. On debugging I noticed that the Subject in the SecurityAssociation, required by JaccAuthorizationRealm is null, therefore the permission check fails. Kind 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] Closed: (JBAS-1592) JaccAuthorizationRealm always returns false on subsequent requests
[ http://jira.jboss.com/jira/browse/JBAS-1592?page=history ]
Scott M Stark closed JBAS-1592:
---
Resolution: Done
This was specific to FORM-AUTH avoiding reauthentication against the Realm. The
JACC unit tests have been updated to run the FORM-AUTH tests to validate there
are no future regressions due to caching issues.
JaccAuthorizationRealm always returns false on subsequent requests
--
Key: JBAS-1592
URL: http://jira.jboss.com/jira/browse/JBAS-1592
Project: JBoss Application Server
Type: Bug
Components: Deployment Service, Security, Web (Tomcat) service
Versions: JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
Environment: Windows XP SP2
JDK 1.5.0
Reporter: Stephen Kinser
Assignee: Scott M Stark
Priority: Critical
Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha
Original Estimate: 1 day
Remaining: 1 day
After the initial login, the JaccAuthorizationRealm always returns false
because the PolicyContext handler for the Subject is not yet initialized when
the realm is called. To figure out the root of the problem, an understanding
of the calling order is necessary.
The standard pipeline is composed of the following valves, in this order:
- JaccContextValve
- FormAuthenticator (the authenticator valve in my case)
- SecurityAssociationValve
- CustomPrincipalValve
- StandardContextValve
The SecurityAssociationValve is added to the pipeline after the authenticator
valve due to the ordering of the code in the
TomcatDeployer.performDeployInternal method. The SecurityAssociationValve is
added after the init call to the server. The init call results in the
authenticator valve being added to the pipeline.
When a request is received by an authenticated user, the authenticator valve
obtains control before the SecurityAssociationValve. The authenticator valve
calls the JaccAuthorizationRealm for the authorization check. Part of the
check is as follows:
Subject caller = null;
try
{
caller = (Subject) PolicyContext.getContext(SUBJECT_CONTEXT_KEY);
}
catch (PolicyContextException e)
{
if( trace )
log.trace(Failed to get subject from PolicyContext, e);
}
if( caller == null ) //*** is always true!
{
if( trace )
log.trace(Denied, no active subject found in PolicyContext);
return false;
}
The realm expects to have an initialized caller (Subject), but the caller is
always null because it wasn't initialized yet since the
SecurityAssociationValve that initializes the caller (Subject) doesn't
receive control until after the authenticator valve is finished.
--
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-1619) LoadLibrary should be done through the deployment classloader
[ http://jira.jboss.com/jira/browse/JBAS-1619?page=history ] Adrian Brock updated JBAS-1619: --- JBoss Forum Reference: http://www.jboss.org/index.html?module=bbop=viewtopict=61814 LoadLibrary should be done through the deployment classloader - Key: JBAS-1619 URL: http://jira.jboss.com/jira/browse/JBAS-1619 Project: JBoss Application Server Type: Bug Components: Deployment Service Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 Reporter: Adrian Brock LoadLibrary needs to be done the deployment classloader to avoid memory leaks. Currently it is done through the NoAnnotationURLClassLoader (the base classloader) so they will never be garbage collected/unloaded. -- 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-1619) LoadLibrary should be done through the deployment classloader
[ http://jira.jboss.com/jira/browse/JBAS-1619?page=comments#action_12316403 ] Adrian Brock commented on JBAS-1619: I would question that we are even trying to load the libraries for the rar or any deployment. It should be left to the class(es) that use the native code? LoadLibrary should be done through the deployment classloader - Key: JBAS-1619 URL: http://jira.jboss.com/jira/browse/JBAS-1619 Project: JBoss Application Server Type: Bug Components: Deployment Service Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 Reporter: Adrian Brock LoadLibrary needs to be done the deployment classloader to avoid memory leaks. Currently it is done through the NoAnnotationURLClassLoader (the base classloader) so they will never be garbage collected/unloaded. -- 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-1619) LoadLibrary should be done through the deployment classloader
[ http://jira.jboss.com/jira/browse/JBAS-1619?page=comments#action_12316404 ] Scott M Stark commented on JBAS-1619: - Agreed. The JCA spec is very weak on defining how native libs should be loaded. We could either require that the rar load the library or have the option of wrapper that loaded the libraries using the correct class loader. LoadLibrary should be done through the deployment classloader - Key: JBAS-1619 URL: http://jira.jboss.com/jira/browse/JBAS-1619 Project: JBoss Application Server Type: Bug Components: Deployment Service Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 Reporter: Adrian Brock LoadLibrary needs to be done the deployment classloader to avoid memory leaks. Currently it is done through the NoAnnotationURLClassLoader (the base classloader) so they will never be garbage collected/unloaded. -- 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: Problems trying to Install
I tried with the source, recompiling and configuring like the pdf instructs and it worked fine. But the binarie installation did not. Problem solved. Working fine with JDK 1.5 View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871609#3871609 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871609 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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] - Plugin for Eclipse
Is there an Eclipse plugin to make easier the development of a portlet? JBoss IDE does that? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871611#3871611 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871611 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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: (EJBTHREE-24) Migrate to Hibernate's EJB3 annotation facility
[ http://jira.jboss.com/jira/browse/EJBTHREE-24?page=history ] Bill Burke updated EJBTHREE-24: --- Fix Version: Preview 5 (was: EJB 3.0 Beta 1) Migrate to Hibernate's EJB3 annotation facility --- Key: EJBTHREE-24 URL: http://jira.jboss.com/jira/browse/EJBTHREE-24 Project: EJB 3.0 Type: Feature Request Versions: Preview 5 Reporter: Bill Burke Assignee: Bill Burke Fix For: Preview 5 The Hibernate team is currently adding ability to support EJB 3 annotations. JBoss EJB3 impl currently creates an Hibernate XML mapping file to do this. Migrate to the annotation support in Hibernate. FYI: An annotation resolver interface will need to be added because there may be a mix of XML and annotations in the EJB3 deployment. -- 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: Plugin for Eclipse
Not yet. I will be working with the JBoss IDE team in the near future to get something out. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871613#3871613 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871613 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Deleted: (EJBTHREE-22) Unique Constraints
[ http://jira.jboss.com/jira/browse/EJBTHREE-22?page=history ] Bill Burke deleted EJBTHREE-22: --- Unique Constraints -- Key: EJBTHREE-22 URL: http://jira.jboss.com/jira/browse/EJBTHREE-22 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke Assignee: Bill Burke Original Estimate: 1 day Remaining: 1 day -- 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] Deleted: (EJBTHREE-13) proxies must be castable to EJBObject/EJBLocalObject
[ http://jira.jboss.com/jira/browse/EJBTHREE-13?page=history ] Bill Burke deleted EJBTHREE-13: --- proxies must be castable to EJBObject/EJBLocalObject Key: EJBTHREE-13 URL: http://jira.jboss.com/jira/browse/EJBTHREE-13 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke Assignee: Bill Burke Original Estimate: 1 day Remaining: 1 day This should be reviewed because there is talk of removing it from the specification. -- 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] Deleted: (EJBTHREE-86) EntityNotFoundException Missing
[ http://jira.jboss.com/jira/browse/EJBTHREE-86?page=history ] Bill Burke deleted EJBTHREE-86: --- EntityNotFoundException Missing --- Key: EJBTHREE-86 URL: http://jira.jboss.com/jira/browse/EJBTHREE-86 Project: EJB 3.0 Type: Bug Environment: Win XP Reporter: Jim Crume Assignee: Kabir Khan The spec for EntityManager shows an EntityNotFoundException being thrown from the find methods when the bean cannot be found. I do not find the implementation of this class in any of the distribution jars. In addition, the exception thrown is a Hibernate exception, which means I need to include underlying implementation detail. -- 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: (EJBTHREE-25) Persistence XML support
[ http://jira.jboss.com/jira/browse/EJBTHREE-25?page=history ] Bill Burke updated EJBTHREE-25: --- Environment: Fix Version: EJB 3.0 Beta 1 (was: Preview 5) Persistence XML support --- Key: EJBTHREE-25 URL: http://jira.jboss.com/jira/browse/EJBTHREE-25 Project: EJB 3.0 Type: Feature Request Versions: Preview 5 Reporter: Bill Burke Assignee: Bill Burke Fix For: EJB 3.0 Beta 1 EJB 3.0 specification will eventually have XML mapping for persistence metadata. -- 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: (EJBTHREE-104) EntityToHibernateXml: catch NPE and throw a more descriptive Exception
[ http://jira.jboss.com/jira/browse/EJBTHREE-104?page=history ] Bill Burke updated EJBTHREE-104: Fix Version: (was: Preview 5) EntityToHibernateXml: catch NPE and throw a more descriptive Exception -- Key: EJBTHREE-104 URL: http://jira.jboss.com/jira/browse/EJBTHREE-104 Project: EJB 3.0 Type: Feature Request Versions: Preview 4 Environment: Linux, JDK 1.5, JBoss 4.0.1sp1 Reporter: Jens Elkner Assignee: Kabir Khan Priority: Minor Original Estimate: 30 minutes Remaining: 30 minutes jboss.log: ... 02:31:01,786 INFO [Ejb3Module] Found hibernate.properties file in EJB3 jar or ear 02:31:01,797 ERROR [Ejb3Module] Starting failed jboss.j2ee:service=EJB3,module=foo.ejb3 java.lang.NullPointerException at org.jboss.ejb3.entity.EntityToHibernateXml.handleOneToMany(EntityToHibernateXml.java:845) at org.jboss.ejb3.entity.EntityToHibernateXml.iterateProperties(EntityToHibernateXml.java:220) at org.jboss.ejb3.entity.EntityToHibernateXml.handleBasicClass(EntityToHibernateXml.java:1822) ... Would be nice, if the NPE could be caught and re-throw a more descriptive Exception, so that one gets a hint, what might be wrong. In my example it was a typo in the mappedBy value, but who knows, what else might be the cause ... -- 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-104) EntityToHibernateXml: catch NPE and throw a more descriptive Exception
[ http://jira.jboss.com/jira/browse/EJBTHREE-104?page=history ] Bill Burke closed EJBTHREE-104: --- Resolution: Rejected We are merging with Hibernate's EJB3 ANnotation support so this may go away. (Or new bug surface.) EntityToHibernateXml: catch NPE and throw a more descriptive Exception -- Key: EJBTHREE-104 URL: http://jira.jboss.com/jira/browse/EJBTHREE-104 Project: EJB 3.0 Type: Feature Request Versions: Preview 4 Environment: Linux, JDK 1.5, JBoss 4.0.1sp1 Reporter: Jens Elkner Assignee: Kabir Khan Priority: Minor Original Estimate: 30 minutes Remaining: 30 minutes jboss.log: ... 02:31:01,786 INFO [Ejb3Module] Found hibernate.properties file in EJB3 jar or ear 02:31:01,797 ERROR [Ejb3Module] Starting failed jboss.j2ee:service=EJB3,module=foo.ejb3 java.lang.NullPointerException at org.jboss.ejb3.entity.EntityToHibernateXml.handleOneToMany(EntityToHibernateXml.java:845) at org.jboss.ejb3.entity.EntityToHibernateXml.iterateProperties(EntityToHibernateXml.java:220) at org.jboss.ejb3.entity.EntityToHibernateXml.handleBasicClass(EntityToHibernateXml.java:1822) ... Would be nice, if the NPE could be caught and re-throw a more descriptive Exception, so that one gets a hint, what might be wrong. In my example it was a typo in the mappedBy value, but who knows, what else might be the cause ... -- 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] Deleted: (EJBTHREE-36) Full Support for @Embeddable
[ http://jira.jboss.com/jira/browse/EJBTHREE-36?page=history ] Bill Burke deleted EJBTHREE-36: --- Full Support for @Embeddable Key: EJBTHREE-36 URL: http://jira.jboss.com/jira/browse/EJBTHREE-36 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke Assignee: Bill Burke I forgot to implement the case where @Embedddable classes can define @Column's @Table, etc.. on themselves. -- 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-36) Full Support for @Embeddable
[ http://jira.jboss.com/jira/browse/EJBTHREE-36?page=history ] Bill Burke closed EJBTHREE-36: -- Resolution: Rejected We are moving to HIbernate's EJB3 annotation implementation. So this problem may disappear. Full Support for @Embeddable Key: EJBTHREE-36 URL: http://jira.jboss.com/jira/browse/EJBTHREE-36 Project: EJB 3.0 Type: Feature Request Versions: Preview 4 Reporter: Bill Burke Assignee: Bill Burke Fix For: Preview 5 I forgot to implement the case where @Embedddable classes can define @Column's @Table, etc.. on themselves. -- 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] Deleted: (EJBTHREE-59) Use persistence default metadata
[ http://jira.jboss.com/jira/browse/EJBTHREE-59?page=history ] Bill Burke deleted EJBTHREE-59: --- Use persistence default metadata Key: EJBTHREE-59 URL: http://jira.jboss.com/jira/browse/EJBTHREE-59 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke Assignee: Bill Burke The persistence spec has a lot of default values for metadata that need to be applied. Specifically relationships, embedded objects, blobs, clobs, etc... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (EJBTHREE-24) Migrate to Hibernate's EJB3 annotation facility
[ http://jira.jboss.com/jira/browse/EJBTHREE-24?page=history ] Bill Burke updated EJBTHREE-24: --- type: Task (was: Feature Request) Migrate to Hibernate's EJB3 annotation facility --- Key: EJBTHREE-24 URL: http://jira.jboss.com/jira/browse/EJBTHREE-24 Project: EJB 3.0 Type: Task Versions: Preview 5 Reporter: Bill Burke Assignee: Bill Burke Fix For: Preview 5 The Hibernate team is currently adding ability to support EJB 3 annotations. JBoss EJB3 impl currently creates an Hibernate XML mapping file to do this. Migrate to the annotation support in Hibernate. FYI: An annotation resolver interface will need to be added because there may be a mix of XML and annotations in the EJB3 deployment. -- 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: (EJBTHREE-60) Write plugin interface for persistence manager
[ http://jira.jboss.com/jira/browse/EJBTHREE-60?page=history ] Bill Burke updated EJBTHREE-60: --- Fix Version: EJB 3.0 Beta 1 (was: Preview 5) Write plugin interface for persistence manager -- Key: EJBTHREE-60 URL: http://jira.jboss.com/jira/browse/EJBTHREE-60 Project: EJB 3.0 Type: Feature Request Versions: Preview 5 Reporter: Bill Burke Assignee: Bill Burke Fix For: EJB 3.0 Beta 1 Abstract out persistence so that a thirdparty persistence manager can be plugged into JBoss' EJB3 implementation -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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: (EJBTHREE-9) Proper exception handling
[ http://jira.jboss.com/jira/browse/EJBTHREE-9?page=history ] Bill Burke updated EJBTHREE-9: -- Fix Version: EJB 3.0 Beta 1 (was: Preview 5) Moved to beta1 as spec still hasn't defined Proper exception handling - Key: EJBTHREE-9 URL: http://jira.jboss.com/jira/browse/EJBTHREE-9 Project: EJB 3.0 Type: Feature Request Versions: Preview 4 Reporter: Bill Burke Assignee: Bill Burke Fix For: EJB 3.0 Beta 1 Original Estimate: 2 days Remaining: 2 days Need to review all the exception handling that will be in the specification. All the cases needed to be documentented, implemented, and tested. -- 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] Deleted: (EJBTHREE-37) Support for @Column(columnDefinition)
[ http://jira.jboss.com/jira/browse/EJBTHREE-37?page=history ] Bill Burke deleted EJBTHREE-37: --- Support for @Column(columnDefinition) - Key: EJBTHREE-37 URL: http://jira.jboss.com/jira/browse/EJBTHREE-37 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke Assignee: Bill Burke Priority: Minor I think this will require Hibernate 3.0 changes. http://opensource.atlassian.com/projects/hibernate/browse/HHH-61 -- 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: (EJBTHREE-94) Implement EntityManager.createNativeQuery() methods
[ http://jira.jboss.com/jira/browse/EJBTHREE-94?page=history ] Bill Burke updated EJBTHREE-94: --- Fix Version: EJB 3.0 Beta 1 (was: Preview 5) I don't think we'll get to this for Preview 5 Implement EntityManager.createNativeQuery() methods --- Key: EJBTHREE-94 URL: http://jira.jboss.com/jira/browse/EJBTHREE-94 Project: EJB 3.0 Type: Feature Request Versions: Preview 4 Reporter: Kabir Khan Fix For: EJB 3.0 Beta 1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Deleted: (EJBTHREE-44) Sequence Generator SUpport
[ http://jira.jboss.com/jira/browse/EJBTHREE-44?page=history ] Bill Burke deleted EJBTHREE-44: --- Sequence Generator SUpport -- Key: EJBTHREE-44 URL: http://jira.jboss.com/jira/browse/EJBTHREE-44 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke Assignee: Bill Burke -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Reopened: (EJBTHREE-82) Misused Error Messages in EntityToHibernateXml
[ http://jira.jboss.com/jira/browse/EJBTHREE-82?page=history ] Bill Burke reopened EJBTHREE-82: reopening to reject Misused Error Messages in EntityToHibernateXml -- Key: EJBTHREE-82 URL: http://jira.jboss.com/jira/browse/EJBTHREE-82 Project: EJB 3.0 Type: Bug Reporter: Adriano Bonat Assignee: Kabir Khan Priority: Trivial Original Estimate: 5 minutes Remaining: 5 minutes The RuntimeException failed to get ManyToMany is used in other methods (handle*Relationship*) than handleManyToMany. This code could be view in: http://cvs.sourceforge.net/viewcvs.py/jboss/jboss-ejb3/src/main/org/jboss/ejb3/entity/EntityToHibernateXml.java?view=markup -- 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-82) Misused Error Messages in EntityToHibernateXml
[ http://jira.jboss.com/jira/browse/EJBTHREE-82?page=history ] Bill Burke closed EJBTHREE-82: -- Resolution: Rejected We are moving to HIbernate's EJB3 annotation implementation. So this problem may disappear. Misused Error Messages in EntityToHibernateXml -- Key: EJBTHREE-82 URL: http://jira.jboss.com/jira/browse/EJBTHREE-82 Project: EJB 3.0 Type: Bug Reporter: Adriano Bonat Assignee: Kabir Khan Priority: Trivial Original Estimate: 5 minutes Remaining: 5 minutes The RuntimeException failed to get ManyToMany is used in other methods (handle*Relationship*) than handleManyToMany. This code could be view in: http://cvs.sourceforge.net/viewcvs.py/jboss/jboss-ejb3/src/main/org/jboss/ejb3/entity/EntityToHibernateXml.java?view=markup -- 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] Deleted: (EJBTHREE-82) Misused Error Messages in EntityToHibernateXml
[ http://jira.jboss.com/jira/browse/EJBTHREE-82?page=history ] Bill Burke deleted EJBTHREE-82: --- Misused Error Messages in EntityToHibernateXml -- Key: EJBTHREE-82 URL: http://jira.jboss.com/jira/browse/EJBTHREE-82 Project: EJB 3.0 Type: Bug Reporter: Adriano Bonat Assignee: Kabir Khan Priority: Trivial Original Estimate: 5 minutes Remaining: 5 minutes The RuntimeException failed to get ManyToMany is used in other methods (handle*Relationship*) than handleManyToMany. This code could be view in: http://cvs.sourceforge.net/viewcvs.py/jboss/jboss-ejb3/src/main/org/jboss/ejb3/entity/EntityToHibernateXml.java?view=markup -- 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] Deleted: (EJBTHREE-102) @Entity (et al) picking up static fields/methods (PATCH)
[ http://jira.jboss.com/jira/browse/EJBTHREE-102?page=history ]
Bill Burke deleted EJBTHREE-102:
@Entity (et al) picking up static fields/methods (PATCH)
Key: EJBTHREE-102
URL: http://jira.jboss.com/jira/browse/EJBTHREE-102
Project: EJB 3.0
Type: Bug
Reporter: Deborah Hooker
Assignee: Kabir Khan
As far as I can tell, the spec says not to pick up static fields and/or
methods, that they should not be included in the persistent fields of an
@Entity.
This keeps the hibernate-xml translator from including them in the generated
XML.
Index: EntityToHibernateXml.java
===
RCS file:
/cvsroot/jboss/jboss-ejb3/src/main/org/jboss/ejb3/entity/EntityToHibernateXml.java,v
retrieving revision 1.30
diff -u -r1.30 EntityToHibernateXml.java
--- EntityToHibernateXml.java 8 Mar 2005 19:16:56 - 1.30
+++ EntityToHibernateXml.java 9 Mar 2005 07:04:07 -
@@ -46,6 +46,7 @@
import java.io.StringWriter;
import java.lang.reflect.Field;
import java.lang.reflect.Method;
+import java.lang.reflect.Modifier;
import java.util.ArrayList;
import java.util.HashMap;
import java.util.HashSet;
@@ -389,8 +390,10 @@
Method[] methods = clazz.getDeclaredMethods();
for (Method f : methods)
{
- Property p = new Property(f.getDeclaringClass(), f);
- if (p.isAnnotable()) list.add(p);
+ if (!Modifier.isStatic(f.getModifiers())) {
+Property p = new Property(f.getDeclaringClass(), f);
+if (p.isAnnotable()) list.add(p);
+ }
}
Class superclass = clazz.getSuperclass();
@@ -425,8 +428,11 @@
Field[] fields = clazz.getDeclaredFields();
for (Field f : fields)
{
- Property p = new Property(f.getDeclaringClass(), f);
- if (p.isAnnotable()) list.add(p);
+ if (!Modifier.isStatic(f.getModifiers()))
+ {
+Property p = new Property(f.getDeclaringClass(), f);
+if (p.isAnnotable()) list.add(p);
+ }
}
Class superclass = clazz.getSuperclass();
--
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] Deleted: (EJBTHREE-91) access=FIELD + @Version problem
[ http://jira.jboss.com/jira/browse/EJBTHREE-91?page=history ] Bill Burke deleted EJBTHREE-91: --- access=FIELD + @Version problem --- Key: EJBTHREE-91 URL: http://jira.jboss.com/jira/browse/EJBTHREE-91 Project: EJB 3.0 Type: Bug Reporter: Bill Burke -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Deleted: (EJBTHREE-95) wrong @Serialized mapping
[ http://jira.jboss.com/jira/browse/EJBTHREE-95?page=history ] Bill Burke deleted EJBTHREE-95: --- wrong @Serialized mapping - Key: EJBTHREE-95 URL: http://jira.jboss.com/jira/browse/EJBTHREE-95 Project: EJB 3.0 Type: Bug Reporter: Bill Burke See forum for patch -- 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] Deleted: (EJBTHREE-100) Support for Session/MDB XML DDs
[ http://jira.jboss.com/jira/browse/EJBTHREE-100?page=history ] Bill Burke deleted EJBTHREE-100: Support for Session/MDB XML DDs --- Key: EJBTHREE-100 URL: http://jira.jboss.com/jira/browse/EJBTHREE-100 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Deleted: (EJBTHREE-96) DiscriminatorColumn should go after Version
[ http://jira.jboss.com/jira/browse/EJBTHREE-96?page=history ] Bill Burke deleted EJBTHREE-96: --- DiscriminatorColumn should go after Version --- Key: EJBTHREE-96 URL: http://jira.jboss.com/jira/browse/EJBTHREE-96 Project: EJB 3.0 Type: Bug Reporter: Bill Burke see forum post for patch -- 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-1584) Create a unit test for tracking the serialVersionUID across versions using ObjectStreamClass
[ http://jira.jboss.com/jira/browse/JBAS-1584?page=history ] Scott M Stark closed JBAS-1584: --- Resolution: Done org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase has been created. Create a unit test for tracking the serialVersionUID across versions using ObjectStreamClass Key: JBAS-1584 URL: http://jira.jboss.com/jira/browse/JBAS-1584 Project: JBoss Application Server Type: Sub-task Components: Test Suite Reporter: Scott M Stark Assignee: Scott M Stark Priority: Critical Fix For: JBossAS-4.0.2 Final We need a unit test that compares the serialVersionUID of classes in the dist against those from previous versions using ObjectStreamClass.getSerialVersionUID() and a database of previous version/class/serialVersionUID. As of 4.0.2 forward this test should fail there is a change in any serialVersionUID. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-107) Support mixed HB3/EJB3 deployments
Support mixed HB3/EJB3 deployments -- Key: EJBTHREE-107 URL: http://jira.jboss.com/jira/browse/EJBTHREE-107 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke Fix For: Preview 5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1446) org.jboss.resource.deployment.RARDeployment needs TRACE logging
[ http://jira.jboss.com/jira/browse/JBAS-1446?page=history ] Adrian Brock reassigned JBAS-1446: -- Assign To: Adrian Brock org.jboss.resource.deployment.RARDeployment needs TRACE logging --- Key: JBAS-1446 URL: http://jira.jboss.com/jira/browse/JBAS-1446 Project: JBoss Application Server Type: Task Components: JCA service Versions: JBossAS-4.0.1 Final Reporter: Adrian Brock Assignee: Adrian Brock The RARDeployment MBean needs some TRACE logging so we can see what endpoint activation/deactivation requests are being passed to thirdparty rars. -- 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-1446) org.jboss.resource.deployment.RARDeployment needs TRACE logging
[ http://jira.jboss.com/jira/browse/JBAS-1446?page=comments#action_12316412 ] Adrian Brock commented on JBAS-1446: Also need logging for activation spec and admin object construction. org.jboss.resource.deployment.RARDeployment needs TRACE logging --- Key: JBAS-1446 URL: http://jira.jboss.com/jira/browse/JBAS-1446 Project: JBoss Application Server Type: Task Components: JCA service Versions: JBossAS-4.0.1 Final Reporter: Adrian Brock Assignee: Adrian Brock The RARDeployment MBean needs some TRACE logging so we can see what endpoint activation/deactivation requests are being passed to thirdparty rars. -- 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: (JBREM-52) javax.ejb.Handle implementations can't find a target object
[ http://jira.jboss.com/jira/browse/JBREM-52?page=history ] Scott M Stark reassigned JBREM-52: -- Assign To: Scott M Stark (was: Tom Elrod) javax.ejb.Handle implementations can't find a target object --- Key: JBREM-52 URL: http://jira.jboss.com/jira/browse/JBREM-52 Project: JBoss Remoting Type: Bug Environment: JBoss 4.0.1RC2 Reporter: Maxim Karavaev Assignee: Scott M Stark Priority: Critical Handle implementations keeps an empty environment Hashtable for InitialContext. The test is very simple: on my client I put into system properties a wrong URL for server (simulates a situation, when we transfer a bean Handle to some computer, that is not knows, where the real server is). Just try my source: Hashtable env = new Hashtable(); env.putAll( System.getProperties() ); env.put( java.naming.provider.url, System.getProperty( realServerURL ) ); InitialContext ic = new InitialContext( env ); Object ref = ic.lookup( SomeBean ); SomeBeanHome home = ( SomeBeanHome )PortableRemoteObject.narrow( ref, SomeBeanHome.class ); SomeBean beanA = home.create(); Handle bh = beanA.getHandle(); /* * here you will get a javax.naming.CommunicationException: * Receive timed out */ EJBObject beanB = bh.getEJBObject(); System.out.println( beanB.isIdentical( beanA ) ); -- 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] Moved: (JBAS-1620) javax.ejb.Handle implementations can't find a target object
[ http://jira.jboss.com/jira/browse/JBAS-1620?page=history ] Scott M Stark moved JBREM-52 to JBAS-1620: -- Project: JBoss Application Server (was: JBoss Remoting) Key: JBAS-1620 (was: JBREM-52) Version: JBossAS-4.0.2RC1 Security Level: Public javax.ejb.Handle implementations can't find a target object --- Key: JBAS-1620 URL: http://jira.jboss.com/jira/browse/JBAS-1620 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.2RC1 Environment: JBoss 4.0.1RC2 Reporter: Maxim Karavaev Assignee: Scott M Stark Priority: Critical Handle implementations keeps an empty environment Hashtable for InitialContext. The test is very simple: on my client I put into system properties a wrong URL for server (simulates a situation, when we transfer a bean Handle to some computer, that is not knows, where the real server is). Just try my source: Hashtable env = new Hashtable(); env.putAll( System.getProperties() ); env.put( java.naming.provider.url, System.getProperty( realServerURL ) ); InitialContext ic = new InitialContext( env ); Object ref = ic.lookup( SomeBean ); SomeBeanHome home = ( SomeBeanHome )PortableRemoteObject.narrow( ref, SomeBeanHome.class ); SomeBean beanA = home.create(); Handle bh = beanA.getHandle(); /* * here you will get a javax.naming.CommunicationException: * Receive timed out */ EJBObject beanB = bh.getEJBObject(); System.out.println( beanB.isIdentical( beanA ) ); -- 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-1620) javax.ejb.Handle implementations can't find a target object
[ http://jira.jboss.com/jira/browse/JBAS-1620?page=history ] Scott M Stark closed JBAS-1620: --- Resolution: Rejected If you want the handle to remember the JNDI environment tha was in effect when it was created, use the org.jboss.naming.NamingContextFactory version of the InitialContextFactory. The org.jnp.interfaces.NamingContextFactory allows one to override the JNDI environment using a local jndi.properties. javax.ejb.Handle implementations can't find a target object --- Key: JBAS-1620 URL: http://jira.jboss.com/jira/browse/JBAS-1620 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.2RC1 Environment: JBoss 4.0.1RC2 Reporter: Maxim Karavaev Assignee: Scott M Stark Priority: Critical Handle implementations keeps an empty environment Hashtable for InitialContext. The test is very simple: on my client I put into system properties a wrong URL for server (simulates a situation, when we transfer a bean Handle to some computer, that is not knows, where the real server is). Just try my source: Hashtable env = new Hashtable(); env.putAll( System.getProperties() ); env.put( java.naming.provider.url, System.getProperty( realServerURL ) ); InitialContext ic = new InitialContext( env ); Object ref = ic.lookup( SomeBean ); SomeBeanHome home = ( SomeBeanHome )PortableRemoteObject.narrow( ref, SomeBeanHome.class ); SomeBean beanA = home.create(); Handle bh = beanA.getHandle(); /* * here you will get a javax.naming.CommunicationException: * Receive timed out */ EJBObject beanB = bh.getEJBObject(); System.out.println( beanB.isIdentical( beanA ) ); -- 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] - Lock Acquisition Timeouts In JBC 1.2.1
I have been using JBC 1.2 for some time, and our application has a case where multiple threads (many of them) might access the same node in the cache at the same time and/or update a node's children. We are not using transactions. This has worked fine even under high volume. With the introduction of JBC 1.2.1, I now get lock acquisition timeout errors in medium to high volume situations, and I would like to understand how to turn them off. The Javadocs for TreeCache indicate that setting the lock acquisition timeout to zero turns them off, but this only makes the errors I have occur with *much* greater frequency. It appears that a zero setting really means wait zero milliseconds to timeout. I can set this value to an arbitrarily high number, but disabling this would be much better. As I understand it, the reason we want a lock acquisition timeout is to avoid deadlock situations (such as a distributed deadlock), but since I am not using transactions nor a synchronously replicating cache, this should not occur I would not think. Is it not possible to turn these off? I am going try setting the isolation level to NONE from REPEATABLE_READ (the default) to see if it makes any difference. In JBC 1.2, isolation levels did not come into play unless transactions were utilized (that is what I understood to be the case anyway). Has this changed? Posts on this forum and the documentation with the 1.2.1 release seem to suggest that maybe it has. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871627#3871627 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871627 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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-1621) Exploded RAR deployment fails when JBOSS_HOME has a space in it
Exploded RAR deployment fails when JBOSS_HOME has a space in it --- Key: JBAS-1621 URL: http://jira.jboss.com/jira/browse/JBAS-1621 Project: JBoss Application Server Type: Bug Components: JCA service, Deployment Service Versions: JBossAS-4.0.1 SP1 Environment: Windows XP Professional SP2 JDK 1.5.0_01 default server configuration Reporter: Brad Beck It appears that if JBOSS_HOME contains a space (e.g. jboss 4.0.1sp1), deployment of an exploded rar file fails while parsing the ra.xml file. If this same rar is not exploded the error does not occur. The following is the stack trace from the console output... 11:43:09,127 ERROR [MainDeployer] Could not initialise deployment: file:/C:/jboss 4.0.1sp1/server/default/deploy/default-license-rar-10.0.24.0.rar/ org.jboss.deployment.DeploymentException: Error parsing meta data file:/C:/jboss 4.0.1sp1/server/default/deploy/default-license-rar-10.0.24.0.rar/META-INF/ra.xml; - nested throwable: (org.jboss.xml.binding.JBossXBException: Failed to parse document file:/C:/jboss 4.0.1sp1/server/default/deploy/default-license-rar-10.0.24.0.rar/META-INF/ra.xml) at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:39) at org.jboss.deployment.SimpleSubDeployerSupport.parseMetaData(SimpleSubDeployerSupport.java:217) at org.jboss.deployment.SimpleSubDeployerSupport.init(SimpleSubDeployerSupport.java:102) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:828) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:765) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) at sun.reflect.GeneratedMethodAccessor43.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.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) 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 $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277) 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)
[JBoss-dev] jboss-4.0-jdk-matrix build.115 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050325114334Lbuild.115 BUILD COMPLETE-build.115Date of build:03/25/2005 11:43:34Time to build:49 minutes 28 secondsLast changed:03/25/2005 11:17:23Last log entry:Include all deploy/jms content recursively in the jacc test configuration Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(21)1.406.2.47modifiedstarksmtestsuite/build.xmlInclude all deploy/jms content recursively in the jacc test configuration1.1.4.3modifiedstarksmtomcat/src/main/org/jboss/web/tomcat/security/JaccAuthorizationRealm.java- If there is no JACC Subject context handler data when the resource permission check is made, check to see if the request principal is a JBossGenericPrincipal that encapsulates the authenticated user. This is needed for FORM-AUTH which caches the authenticated user as part of the session context and does not reauthenticate to the Realm. Resolves (JBAS-1592) JaccAuthorizationRealm always returns false on subsequent requests.- Fix a problem with the migration to tomcat 5.5.x that broke the isUserInRole call for the JACC Realm.1.10.2.8modifiedstarksmtomcat/src/main/org/jboss/web/tomcat/security/JBossSecurityMgrRealm.javaChange the roleMap to a mapping from the caller principal to the GenericPrincipal rather than just the caller's roles.1.3.4.3modifiedstarksmtomcat/src/main/org/jboss/web/tomcat/security/JBossGenericPrincipal.javaKeep the original SetPrincpal of the user roles in addition to the role names.1.1.2.1modifiedstarksmtestsuite/src/resources/test-configs/jacc/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xmlAdd the SecurityManagerService attribute for testing the auth cache flushing.1.9.2.61modifiedstarksmtestsuite/imports/test-jars.xmlAdd the cross-server.jar target1.9.2.60modifiedloubyanskytestsuite/imports/test-jars.xmlported ha local connection factory from HEAD1.2.2.1modifiedloubyanskytestsuite/src/resources/jca/ha/test-ha-ds.xmlported ha local connection factory from HEAD1.2.2.1modifiedloubyanskytestsuite/src/main/org/jboss/test/jca/test/HAConnectionFactoryUnitTestCase.javaported ha local connection factory from HEAD1.1.2.1modifiedloubyanskytestsuite/src/main/org/jboss/test/jca/ejb/HAConnectionSessionBean.javaported ha local connection factory from HEAD1.4.2.3modifiedloubyanskytools/etc/buildmagic/modules.xmlported ha local connection factory from HEAD1.67.2.6modifiedloubyanskyconnector/build.xmlported ha local connection factory from HEAD1.22.2.5modifiedloubyanskyconnector/src/resources/stylesheets/ConnectionFactoryTemplate.xslported ha local connection factory from HEAD1.1.2.1modifiedloubyanskyconnector/src/resources/ha-local-rar/META-INF/ra.xmlported ha local connection factory from HEAD1.1.2.4modifiedloubyanskyconnector/src/resources/dtd/jboss-ds_1_5.dtdported ha local connection factory from HEAD1.6.2.1modifiedloubyanskyconnector/src/main/org/jboss/resource/adapter/jdbc/local/HALocalManagedConnectionFactory.javaported ha local connection factory from HEAD1.13.4.2modifiedanddsystem/src/main/org/jboss/system/server/ServerConfig.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console1.9.6.1modifiedanddsystem/src/main/org/jboss/system/server/ServerConfigImpl.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console1.47.2.4modifiedanddsystem/src/main/org/jboss/system/server/ServerImpl.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform
[JBoss-dev] [JBoss JIRA] Resolved: (JBMAIL-25) Modify StreamStore to be pluggable MessageStore
[ http://jira.jboss.com/jira/browse/JBMAIL-25?page=history ] Michael Barker resolved JBMAIL-25: -- Resolution: Done The Store is implemented. It is contained within the org.jboss.mail.store package. We have 4 store implementations currently, Hibernate-based (pages data internally), JDBC3 Blob, PostgreSQL LargeObjectAPI and Sleepycat BDB. Modify StreamStore to be pluggable MessageStore --- Key: JBMAIL-25 URL: http://jira.jboss.com/jira/browse/JBMAIL-25 Project: JBoss Mail Type: Sub-task Versions: 1.0-M3 Reporter: Dawie Malan Assignee: Michael Barker Fix For: 1.0-M3 org.jboss.mail.store.* should be moved to org.jboss.mail.msgstore.stream.*, and changed to implement the MessageStore interface. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBMAIL-21) Mail Store tests should check to see if mysql driver is present
[ http://jira.jboss.com/jira/browse/JBMAIL-21?page=history ] Michael Barker resolved JBMAIL-21: -- Resolution: Done JUnit now simply test against configured MBean. Driver is not referenced. Mail Store tests should check to see if mysql driver is present --- Key: JBMAIL-21 URL: http://jira.jboss.com/jira/browse/JBMAIL-21 Project: JBoss Mail Type: Bug Versions: 1.0-M3 Reporter: Andrew Oliver Assignee: Michael Barker Priority: Critical Fix For: 1.0-M3 Original Estimate: 10 minutes Remaining: 10 minutes The MySQL driver is GPL and cannot be redistributed (without making JBMail also GPL) thus the unit tests should merely check to see if the driver is present, if it is not, they should WARN and continue without running the MYSQL dependent tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [TODO -- DEVELOPMENT] - Re: Volunteer for JAXR TestCases
If you want to, I have also another oportunities that you could contribute. Please, send me an e-mail or update your profile with a real e-mail. I have some ideas that if you are interested we could discuss about. Clebert View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871631#3871631 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871631 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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-1621) Exploded RAR deployment fails when JBOSS_HOME has a space in it
[ http://jira.jboss.com/jira/browse/JBAS-1621?page=history ] Scott M Stark closed JBAS-1621: --- Resolution: Duplicate Issue Fix Version: JBossAS-4.0.2RC1 This is a duplicate of JBAS-363 which was fixed in JBossAS-4.0.2RC1 using a system property setting. See that issue for the property to configure. Exploded RAR deployment fails when JBOSS_HOME has a space in it --- Key: JBAS-1621 URL: http://jira.jboss.com/jira/browse/JBAS-1621 Project: JBoss Application Server Type: Bug Components: JCA service, Deployment Service Versions: JBossAS-4.0.1 SP1 Environment: Windows XP Professional SP2 JDK 1.5.0_01 default server configuration Reporter: Brad Beck Fix For: JBossAS-4.0.2RC1 It appears that if JBOSS_HOME contains a space (e.g. jboss 4.0.1sp1), deployment of an exploded rar file fails while parsing the ra.xml file. If this same rar is not exploded the error does not occur. The following is the stack trace from the console output... 11:43:09,127 ERROR [MainDeployer] Could not initialise deployment: file:/C:/jboss 4.0.1sp1/server/default/deploy/default-license-rar-10.0.24.0.rar/ org.jboss.deployment.DeploymentException: Error parsing meta data file:/C:/jboss 4.0.1sp1/server/default/deploy/default-license-rar-10.0.24.0.rar/META-INF/ra.xml; - nested throwable: (org.jboss.xml.binding.JBossXBException: Failed to parse document file:/C:/jboss 4.0.1sp1/server/default/deploy/default-license-rar-10.0.24.0.rar/META-INF/ra.xml) at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:39) at org.jboss.deployment.SimpleSubDeployerSupport.parseMetaData(SimpleSubDeployerSupport.java:217) at org.jboss.deployment.SimpleSubDeployerSupport.init(SimpleSubDeployerSupport.java:102) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:828) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:765) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) at sun.reflect.GeneratedMethodAccessor43.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.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) 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 $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277) 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)
[JBoss-dev] [JBoss JIRA] Commented: (JBIDE-163) deploy a process archive
[ http://jira.jboss.com/jira/browse/JBIDE-163?page=comments#action_12316421 ] Marshall Culpepper commented on JBIDE-163: -- *AR deployment is already working in JBossIDE... this could easily be an integration peice.. thoughts? deploy a process archive Key: JBIDE-163 URL: http://jira.jboss.com/jira/browse/JBIDE-163 Project: JBoss IDE Type: Feature Request Components: jBPM Designer plugin Reporter: Tom Baeyens Assignee: Marshall Culpepper -- 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: (JBXB-7) Create a deployment instance doc illustrating the polymorphism requirements
[ http://jira.jboss.com/jira/browse/JBXB-7?page=history ] Adrian Brock updated JBXB-7: Assign To: Alexey Loubyansky (was: Adrian Brock) Create a deployment instance doc illustrating the polymorphism requirements --- Key: JBXB-7 URL: http://jira.jboss.com/jira/browse/JBXB-7 Project: JBoss XML Binding (JBossXB) Type: Sub-task Reporter: Scott M Stark Assignee: Alexey Loubyansky Please create an xml deployer instance example which shows your polymorphism requirements. -- 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: (JBIDE-163) deploy a process archive
[ http://jira.jboss.com/jira/browse/JBIDE-163?page=comments#action_12316422 ] Tom Baeyens commented on JBIDE-163: --- is there some doc describing what the *ar deployment in jboss ide means. i think jbpm process archive deployment is different from other archive deployments... regards, tom. deploy a process archive Key: JBIDE-163 URL: http://jira.jboss.com/jira/browse/JBIDE-163 Project: JBoss IDE Type: Feature Request Components: jBPM Designer plugin Reporter: Tom Baeyens Assignee: Marshall Culpepper -- 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)] - non-java clients
Hi, I worked on an open protocol for the old jbossmq (http://csil.sourceforge.net), which only runs in jboss3.2. It encodes messages in an xml format, and provides a library for c# to connect to jbossmq. I've been using it in production quite successfully for the past two years. Last time around, I did the design in isolation, and built on top of the UIL, which was replaced by the UIL2 almost at the same time that I finished the first version of the new protocol. I was hoping I could get some additional guidance this time. I and another collaborator were granted cvs access to do this work. Circumstances got the better of us, and we didn't make much progress porting from UIL to UIL2. However, I now have time to work on jbossmq, and I'd like to dive in again (assuming I haven't worn out my welcome). To get started, I have a few questions: First, should I abandon the idea of porting the code I wrote to be based on the UIL2? Secondly, would a language independent protocol be a new facade, or would I add a component to the JMS facade? thanks, fawce View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871639#3871639 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871639 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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-1446) org.jboss.resource.deployment.RARDeployment needs TRACE logging
[ http://jira.jboss.com/jira/browse/JBAS-1446?page=history ] Adrian Brock closed JBAS-1446: -- Resolution: Done Fix Version: JBossAS-4.0.2 Final Done. There is now trace logging for: creating admin objects creating activation specs and the mdb driven operations: createActivationSpec endpointActivation endpointDeactivation org.jboss.resource.deployment.RARDeployment needs TRACE logging --- Key: JBAS-1446 URL: http://jira.jboss.com/jira/browse/JBAS-1446 Project: JBoss Application Server Type: Task Components: JCA service Versions: JBossAS-4.0.1 Final Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossAS-4.0.2 Final The RARDeployment MBean needs some TRACE logging so we can see what endpoint activation/deactivation requests are being passed to thirdparty rars. -- 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: (JBIDE-163) deploy a process archive
[ http://jira.jboss.com/jira/browse/JBIDE-163?page=comments#action_12316424 ] Marshall Culpepper commented on JBIDE-163: -- Basically, JBossIDE will allow you to deploy any file in any project in one of two ways: 1) An actual remote deploy that uploads the file to JBoss which does the actual deploying.. 2) A basic file copy to a certain directory. In most cases this is a copy of your *AR file to $JBOSS_HOME/server/$JBOSS_CONFIG/deploy. If JBoss is running, it will automatically deploy the file if it has changed. This is what you're looking for? (Does jBPM have it's own JBoss Deployer ?) deploy a process archive Key: JBIDE-163 URL: http://jira.jboss.com/jira/browse/JBIDE-163 Project: JBoss IDE Type: Feature Request Components: jBPM Designer plugin Reporter: Tom Baeyens Assignee: Marshall Culpepper -- 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: (JBIDE-164) source and refactor menus disabled
source and refactor menus disabled -- Key: JBIDE-164 URL: http://jira.jboss.com/jira/browse/JBIDE-164 Project: JBoss IDE Type: Bug Versions: 1.5 Preview Environment: win2k, jdk 1.5 Reporter: s s Assigned to: Marshall Culpepper Installed JBossIDE-1.5-Preview-jre1.5.zip. Customized the java perspective to enable Java Coding command subgroup. Source and refactor menus are now present but every option is grayed out. Right-click in the code itself does allow for refactor options. Not sure if this is a bug or user error but can't find any clues to why menus are not functional. Thanks! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2-testsuite build.97 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050325130619Lbuild.97 BUILD COMPLETE-build.97Date of build:03/25/2005 13:06:19Time to build:94 minutes 31 secondsLast changed:03/24/2005 05:34:30Last log entry:JBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console Unit Tests: (1967) Total Errors and Failures: (8)testNoClassDefFoundErrororg.jboss.test.classloader.test.BasicLoaderUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestMDBDeepRunAsorg.jboss.test.security.test.EJBSpecUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestSessionTimeoutorg.jboss.test.cluster.test.SimpleTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCase Modifications since last build:(5)1.6.2.3modifiedanddsystem/src/main/org/jboss/system/server/ServerConfigImpl.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console1.25.2.29modifiedanddsystem/src/main/org/jboss/system/server/ServerImpl.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console1.9.2.4modifiedanddsystem/src/main/org/jboss/system/server/ServerConfig.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console1.24.4.11modifiedanddjmx/src/main/org/jboss/mx/server/MBeanServerImpl.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console1.1.2.4modifiedanddjmx/src/main/org/jboss/mx/util/MBeanServerLocator.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console
[JBoss-dev] [JBoss JIRA] Commented: (JBIDE-163) deploy a process archive
[ http://jira.jboss.com/jira/browse/JBIDE-163?page=comments#action_12316425 ] Tom Baeyens commented on JBIDE-163: --- no jbpm does not have a jboss deployer. still needs to be seen if this makes sense. in case of jbpm, deploying a process archive means that the content is parsed into an object model and that object model is stored in a relational database (with hibernate) there is a jbpm ProcessArchiveDeployer that does this. it's just a matter of finding the right way of getting the classpath to work with jbpm, hibernate and the database driver. eventually, we want to integrate with the hibernate plugin for the management of database drivers and connections. but this task is mainly intended as a quick and dirty solution. the idea was that users should put the database driver somewhere in the classpath of the jbpm designer plugin. koen is still thinking about how to do this in the quickest way. regards, tom. deploy a process archive Key: JBIDE-163 URL: http://jira.jboss.com/jira/browse/JBIDE-163 Project: JBoss IDE Type: Feature Request Components: jBPM Designer plugin Reporter: Tom Baeyens Assignee: Marshall Culpepper -- 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)] - Re: non-java clients
According to sourceforge you still have cvs access: http://sourceforge.net/project/memberlist.php?group_id=22866 For JBossMQ it would be integrated as an IL like you did before, but not using the buggy old UIL code as a basis. For the new JBoss Messaging, I guess it would be done as a facade and probably integrate through JBoss Remoting? I'll leave Ovidiu to discuss it with you. If you are going to add code, you need to support it, or find somebody else that is going to support it. Stuff that is unused/unsupported generally gets removed. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871642#3871642 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871642 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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] - How do I get rollback to occur with remote cache access?
I have JbossCache 1.2.1 deployed on one Jboss instance (3.2.7) and I'm accessing it remotely from another Jboss instance. The client Jboss instance is running a stateless session bean with a container managed transaction, and is looking up the remote cache via JNDI. In testing this, I found that when I threw an EJBException after inserting data into the remote cache, the inserted data did not get rolled back. If the cache is deployed in the same Jboss instance, however, the cache rollback does occur. I also tried going through a stateless session bean on the Jboss instance with the cache, but the rollback still didn't occur when I threw an EJBException on the client Jboss instance. Is there something I need to do differently to get the remote cache rollback to occur, either with direct cache access or through another ejb, or is that not even possible? Thanks, Jason View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871643#3871643 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871643 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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-91) 'isSameRMValue' always gets set to true or false
[ http://jira.jboss.com/jira/browse/JBADMCON-91?page=history ] Charles Crouch reassigned JBADMCON-91: -- Assign To: Charles Crouch 'isSameRMValue' always gets set to true or false -- Key: JBADMCON-91 URL: http://jira.jboss.com/jira/browse/JBADMCON-91 Project: JBoss Admin Console Type: Bug Components: DataSource Versions: 1.0 alpha Reporter: Charles Crouch Assignee: Charles Crouch Fix For: 1.1 alpha Original Estimate: 4 hours Time Spent: 15 minutes Remaining: 3 hours, 45 minutes The 'isSameRMValue' property for an XA DataSource is always being set to either true or false, there is no way to leave it unspecified. -- 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: (JBIDE-163) deploy a process archive
[ http://jira.jboss.com/jira/browse/JBIDE-163?page=history ] Marshall Culpepper reassigned JBIDE-163: Assign To: Koen Aers (was: Marshall Culpepper) deploy a process archive Key: JBIDE-163 URL: http://jira.jboss.com/jira/browse/JBIDE-163 Project: JBoss IDE Type: Feature Request Components: jBPM Designer plugin Reporter: Tom Baeyens Assignee: Koen Aers -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=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-91) 'isSameRMValue' always gets set to true or false
[ http://jira.jboss.com/jira/browse/JBADMCON-91?page=history ] Charles Crouch reassigned JBADMCON-91: -- Assign To: (was: Charles Crouch) 'isSameRMValue' always gets set to true or false -- Key: JBADMCON-91 URL: http://jira.jboss.com/jira/browse/JBADMCON-91 Project: JBoss Admin Console Type: Bug Components: DataSource Versions: 1.0 alpha Reporter: Charles Crouch Fix For: 1.1 alpha Original Estimate: 4 hours Time Spent: 15 minutes Remaining: 3 hours, 45 minutes The 'isSameRMValue' property for an XA DataSource is always being set to either true or false, there is no way to leave it unspecified. -- 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-114) Standalone Build
Standalone Build Key: JBCACHE-114 URL: http://jira.jboss.com/jira/browse/JBCACHE-114 Project: JBoss Cache Type: Task Reporter: Ryan Campbell Assigned to: Bela Ban Ben and I have a plan for moving jboss-cache to a standalone build before the new build system is complete. 1. Bela eliminates dependencies 2. Ben creates basic standalone build.xml and adds jboss-cache.jar to jboss-thirdparty 3. Ryan removes cache from jboss-head, jboss-3.2 and jboss-4.0 cvs aliases 3. Ryan adds nightly jboss-cache standalone build to cruisecontrol Once jboss-cache has non-container tests migrated from testsuite... 1. Ben/Bela add tests to jboss-cache testsuite 2. Ryan adds test target to nightly cruisecontrol Ben said there will eventually be cache integration code in the AS, at which point: 1. Create a the new integration module (jboss-as-cache) 2. Add it to the cvs aliases as cache -- 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: (JBCACHE-114) Standalone Build
[ http://jira.jboss.com/jira/browse/JBCACHE-114?page=history ] Ryan Campbell reassigned JBCACHE-114: - Assign To: Ryan Campbell (was: Bela Ban) Standalone Build Key: JBCACHE-114 URL: http://jira.jboss.com/jira/browse/JBCACHE-114 Project: JBoss Cache Type: Task Reporter: Ryan Campbell Assignee: Ryan Campbell Ben and I have a plan for moving jboss-cache to a standalone build before the new build system is complete. 1. Bela eliminates dependencies 2. Ben creates basic standalone build.xml and adds jboss-cache.jar to jboss-thirdparty 3. Ryan removes cache from jboss-head, jboss-3.2 and jboss-4.0 cvs aliases 3. Ryan adds nightly jboss-cache standalone build to cruisecontrol Once jboss-cache has non-container tests migrated from testsuite... 1. Ben/Bela add tests to jboss-cache testsuite 2. Ryan adds test target to nightly cruisecontrol Ben said there will eventually be cache integration code in the AS, at which point: 1. Create a the new integration module (jboss-as-cache) 2. Add it to the cvs aliases as cache -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Mail Services] - fetchmail
Hi, there is now a fetchmail over pop3 mbean in JbossMail. jboss.mail:name=Popper,type=Fetchmail The operation to fetch mail is pop(). Configuration is done through MBean attributes: | mbean code=org.jboss.mail.fetchmail.Popper | name=jboss.mail:type=Fetchmail,name=Popper | attribute name=Servernamelocalhost/attribute | attribute name=PopPort110/attribute | attribute name=PopUserheiko/attribute | attribute name=Passwordsecret/attribute | attribute name=LocalUser[EMAIL PROTECTED]/attribute | attribute name=DeleteAfterPoptrue/attribute | /mbean | | - Servername: the server to fetch mail from | - PopPort: the pop3 port of the server to fetch mail from | - PopUser: the user account on the pop3 server | - Password: the password on the pop3 server | - LocalUser: the [EMAIL PROTECTED] that the mail should be sent to locally | - DeleteAfterPop: if true, delete the mail on the server. If false, leave it. This has another implication: if true: fetch all mail from the server, if false only fetch new mail. | | | The configuration does not yet support pop over ssl and will also change somewhat in the future. | See also JBMAIL-6 in JIRA. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871645#3871645 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871645 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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-1270) UserTransaction with non default ProviderURL
[ http://jira.jboss.com/jira/browse/JBAS-1270?page=history ]
Scott M Stark closed JBAS-1270:
---
Resolution: Done
Fix Version: JBossAS-5.0 Alpha
If you use the org.jboss.naming.NamingContextFactory as the
Context.INITIAL_CONTEXT_FACTORY value, the ClientUserTransaction has access to
the JNDI env that was used to do the lookup of the UserTransaction and that is
the env used during session creation.
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] jboss-3.2-jdk-matrix build.84 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050325151217Lbuild.84 BUILD COMPLETE-build.84Date of build:03/25/2005 15:12:17Time to build:44 minutes 28 secondsLast changed:03/24/2005 05:34:30Last log entry:JBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(5)1.6.2.3modifiedanddsystem/src/main/org/jboss/system/server/ServerConfigImpl.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console1.25.2.29modifiedanddsystem/src/main/org/jboss/system/server/ServerImpl.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console1.9.2.4modifiedanddsystem/src/main/org/jboss/system/server/ServerConfig.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console1.24.4.11modifiedanddjmx/src/main/org/jboss/mx/server/MBeanServerImpl.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console1.1.2.4modifiedanddjmx/src/main/org/jboss/mx/util/MBeanServerLocator.javaJBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console
[JBoss-dev] [JBossCache] - Re: Lock Acquisition Timeouts In JBC 1.2.1
By setting the isolation level to NONE, I got a different error. Its stacktrace is below. | java.lang.IllegalStateException: addWriter(): owner already existed | at org.jboss.cache.lock.LockMap.addWriter(LockMap.java:112) | at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:175) | at org.jboss.cache.Node.acquireWriteLock(Node.java:483) | at org.jboss.cache.Node.acquire(Node.java:440) | at org.jboss.cache.interceptors.LockInterceptor.lock(LockInterceptor.java:240) | at org.jboss.cache.interceptors.LockInterceptor.invoke(LockInterceptor.java:156) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) | at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:35) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) | at org.jboss.cache.interceptors.ReplicationInterceptor.replicate(ReplicationInterceptor.java:217) | at org.jboss.cache.TreeCache._replicate(TreeCache.java:2682) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:236) | at org.jgroups.blocks.RpcDispatcher.handle(RpcDispatcher.java:220) | at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:615) | at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:512) | at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:326) | at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUp(MessageDispatcher.java:722) | at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.access$300(MessageDispatcher.java:554) | at org.jgroups.blocks.MessageDispatcher$1.run(MessageDispatcher.java:691) | at java.lang.Thread.run(Thread.java:534) | I am not sure what this means beyond the fact the isolation level change did apparently influence how the cache was behaving regardless of the fact that I am not using transactions. Is the answer to handle the lock acquisition timeout exceptions mentioned in the previous post, somehow turn them off (how?), or is there another alternative? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871648#3871648 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871648 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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: Lock Acquisition Timeouts In JBC 1.2.1
One more piece of new information, there is obviously some deadlock going on here. I increased the lock acquisition timeout time to 5 minutes and noticed the following: * the process stopped (did nothing) waiting for 5 minutes after about 500 simultaneous client requests * after this timeout period, more timeout exceptions occurred than when the timeout was set to 15 or 30 seconds I am not sure what to do now as this same code (both client and server) works *fine* when used with JBC 1.2. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871649#3871649 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871649 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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)] - Re: non-java clients
Adrian, Thanks for the direction. I am anxious to move off of the UIL, so perhaps I should start with the UIL2 port? We have to support the library now anyway, as we use it in production. We'd really benefit from broader use, so that issues get flushed out sooner. So, in other words, we're ready for the responsibility. How much life would you say remains for the old jbossmq? I'm just trying to guage whether a UIL2-based protocol will have much of a lifespan. Will the existing jbossmq and UIL2 be in jb4.0? (Is there a place of reference for this, sorry if I am asking a dumb question). Regarding cvs, can I just cut a branch to work from? What should I use as my branch point? On the implementation, my plan was to actually modify UIL2 to not use ObjectStreams, and to accept additional configuration parameters to either use the existing java oriented message encoding, or the new message encoding we would add. Alternatively, I could create a new package and completely separate IL. thanks, fawce View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871650#3871650 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871650 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - Non-Archive Artifacts
We have several different types of non-archive artifacts which need to be
supported - dtds, service.xml descriptors, etc. These need to be included in
the release structure outside of any archive.
| resource id=exception-processor/
|
| artifactdef artifact=sqlexception-service.xml
|include input=exception-processor
| include pattern=sqlexception-service.xml
|/include
| /artifactdef
|
I think we can make this less verbose. If I were following the existing
design, I think I would have to copy it to somewhere like output/lib, assuming
I had the following:
artifacttype id=xml outputtype=lib/
and then in the build targetdef:
xml
| mkdir dir=@{parentDir}/
| copy todir=@{parentDir}
| filesets/
| /copy
|/xml
So the toplevel build can find the file in output/lib instead of
output/resources/exception-processor.
| artifact id=sqlexception-service.xml/
|
I suppose the downsides to this approach are:
1. No grouping of many artifacts, so each file must be listed as a seperate
artifact element. I might like to have an artifact like server.dtds that
allows me to treat *.dtd as a group.
2. We are unnecissarily copying files from output/resources/something to
output/lib.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3871651#3871651
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871651
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds 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)] - Re: non-java clients
fawce wrote : | How much life would you say remains for the old jbossmq? I'm just trying to guage whether a UIL2-based protocol will have much of a lifespan. Will the existing jbossmq and UIL2 be in jb4.0? (Is there a place of reference for this, sorry if I am asking a dumb question). | http://www.jboss.org/wiki/Wiki.jsp?page=JBossMQ anonymous wrote : | Regarding cvs, can I just cut a branch to work from? What should I use as my branch point? | | On the implementation, my plan was to actually modify UIL2 to not use ObjectStreams, and to accept additional configuration parameters to either use the existing java oriented message encoding, or the new message encoding we would add. Alternatively, I could create a new package and completely separate IL. | Just create a UIL3 (or whatever you want to call it) in jboss-head. Under no circumstances should you change the wire format of UIL2. That would break backward compatibility. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871652#3871652 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871652 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - Re: Non-Archive Artifacts
Why can't you just release files from output/resources, output/etc, output/dtd? As long as the artificats are included in the same structure inside the repository I don't see a problem? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871653#3871653 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871653 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - Re: Non-Archive Artifacts
The problem is the top level build will need to know where in output/resources to look for sqlexception-service.xml. In this case, it is under output/resources/exception-processor/sqlexception-service.xml. This would also work: | artifact id=sqlexception-service.xml outputpath=resources/exception-processor release=deploy/ | Perhaps the toplevel build needs to parse each component build to gather details like this? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871655#3871655 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871655 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - Re: Non-Archive Artifacts
Yes, I added the ability to tell the toplevel build that a resource was not in the standard location for slide: | component id=apache-slide | artifact id=webdavlib.jar release=lib outputpath=client/lib/ | /component | I wouldn't worry about it too much. These are legacy details of an untidy build due to a lack of standards. It can be fixed later. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871656#3871656 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871656 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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: Lock Acquisition Timeouts In JBC 1.2.1
Additionally, I have noticed/tried the following: * the lock acquisition timeouts seem only to occur while listing a given node's children and the retrieving information from each of the children * if the isolation level is set to READ_COMMITTED, the lock acquisition timeouts completely go away (I have no idea why) Should a change in isolation level create/alleviate a dead lock situation like this? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871663#3871663 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871663 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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: portlet resource bundles
This appears to be a bug in JBP. The way the portal loads resource files for portlets does not seem to match the standard, or the way it loads for jsp views. So from what i have seen, to load a properties file for portlet (java) access, i must name the file something like com.something.BlahPortlet.properties and place it in the /classes/ directory of the war. That works fine, until i try to access those properties from included jsp files. To access from jsp, the properties file should be in the path /com/something/BlahPortlet.properties JBP fails to find the resource bundle file in the path, for portlet code. I tired the same war on a simple Pluto 1.0.1 install and it worked just fine, for jsp and java code. I've also noticed that JBP failes to load a portlet if javax.portlet.title is defined in the resource bundle and not directly in the portlet.xml file. This is all on Alpha, havent tried on Beta yet. I can get more detailed in bug report if someone doesn't have more info to convince me that it's not a bug. ... .joe View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871667#3871667 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871667 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds 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: portlet resource bundles
this bug has been fixed since alpha View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871670#3871670 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871670 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-108) Support for package-level annotations
Support for package-level annotations - Key: EJBTHREE-108 URL: http://jira.jboss.com/jira/browse/EJBTHREE-108 Project: EJB 3.0 Type: Feature Request Versions: Preview 4 Reporter: Bill Burke Fix For: Preview 5 Need to have Deployer find all package-level annotations so that HB3 AnnotationConfigure can get the package-level metadata they require. -- 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: (EJBTHREE-101) EntityManager not useable in PostConstruct callback of StatelessSessionBean.
[ http://jira.jboss.com/jira/browse/EJBTHREE-101?page=history ] Bill Burke reassigned EJBTHREE-101: --- Assign To: Kabir Khan EntityManager not useable in PostConstruct callback of StatelessSessionBean. Key: EJBTHREE-101 URL: http://jira.jboss.com/jira/browse/EJBTHREE-101 Project: EJB 3.0 Type: Bug Versions: Preview 4 Environment: JBoss-4.0.1sp1, EJB3-Preview4, Windows 2000. Reporter: Shagoon Assignee: Kabir Khan When trying to use the entity manager for a query in a PostConstruct callback in a StatelessSessionBean, execution fails with: Caused by: java.lang.RuntimeException: EntityManager must be access within a transaction at org.jboss.ejb3.entity.HibernateSessionFactory.getSession(HibernateSessionFactory.java:105) at org.jboss.ejb3.entity.EntityManagerImpl.getSession(EntityManagerImpl.java:146) at org.jboss.ejb3.entity.EntityManagerImpl.createQuery(EntityManagerImpl.java:39) at some.package.postConstructCallback(SomeDAOBean.java:99) ... 26 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (EJBTHREE-101) EntityManager not useable in PostConstruct callback of StatelessSessionBean.
[ http://jira.jboss.com/jira/browse/EJBTHREE-101?page=history ] Bill Burke updated EJBTHREE-101: Fix Version: Preview 5 EntityManager not useable in PostConstruct callback of StatelessSessionBean. Key: EJBTHREE-101 URL: http://jira.jboss.com/jira/browse/EJBTHREE-101 Project: EJB 3.0 Type: Bug Versions: Preview 4 Environment: JBoss-4.0.1sp1, EJB3-Preview4, Windows 2000. Reporter: Shagoon Assignee: Kabir Khan Fix For: Preview 5 When trying to use the entity manager for a query in a PostConstruct callback in a StatelessSessionBean, execution fails with: Caused by: java.lang.RuntimeException: EntityManager must be access within a transaction at org.jboss.ejb3.entity.HibernateSessionFactory.getSession(HibernateSessionFactory.java:105) at org.jboss.ejb3.entity.EntityManagerImpl.getSession(EntityManagerImpl.java:146) at org.jboss.ejb3.entity.EntityManagerImpl.createQuery(EntityManagerImpl.java:39) at some.package.postConstructCallback(SomeDAOBean.java:99) ... 26 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-106) Bug in EntityToHibernateXml.java:convert()
[ http://jira.jboss.com/jira/browse/EJBTHREE-106?page=history ]
Bill Burke closed EJBTHREE-106:
---
Resolution: Out of Date
Fixed in CVS, but we merged with HB3 annotations project and
EntityToHibernateXML is no longer being used.
Bug in EntityToHibernateXml.java:convert()
--
Key: EJBTHREE-106
URL: http://jira.jboss.com/jira/browse/EJBTHREE-106
Project: EJB 3.0
Type: Bug
Components: EJB3 Extensions
Versions: Preview 4
Environment: Redhat 9
Reporter: jojo9876
Original Estimate: 5 minutes
Remaining: 5 minutes
Around line 131, I believe it should read:
if (clazz.isAnnotationPresent(GeneratedIdTable.class))
{
GeneratedIdTable gen = (GeneratedIdTable)
clazz.getAnnotation(GeneratedIdTable.class);
generatorTables.put(gen.name(), gen);
}
instead of:
if (clazz.isAnnotationPresent(GeneratedIdTable.class))
{
GeneratedIdTable gen = (GeneratedIdTable)
clazz.getAnnotation(TableGenerator.class);
generatorTables.put(gen.name(), gen);
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-109) Expose Hibernate Query through javax.persistence.Query
Expose Hibernate Query through javax.persistence.Query -- Key: EJBTHREE-109 URL: http://jira.jboss.com/jira/browse/EJBTHREE-109 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke Fix For: Preview 5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (EJBTHREE-72) MDB should support JCA inflow
[ http://jira.jboss.com/jira/browse/EJBTHREE-72?page=history ] Bill Burke updated EJBTHREE-72: --- Fix Version: EJB 3.0 Beta 1 (was: Preview 5) MDB should support JCA inflow - Key: EJBTHREE-72 URL: http://jira.jboss.com/jira/browse/EJBTHREE-72 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke Assignee: Bill Burke Fix For: EJB 3.0 Beta 1 MDB should support JCA 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] Created: (EJBTHREE-110) Expose Hibernate Session through EntityManager interface
Expose Hibernate Session through EntityManager interface Key: EJBTHREE-110 URL: http://jira.jboss.com/jira/browse/EJBTHREE-110 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke Fix For: Preview 5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (EJBTHREE-21) MDB, Session Bean XML support
[ http://jira.jboss.com/jira/browse/EJBTHREE-21?page=history ] Bill Burke updated EJBTHREE-21: --- Environment: Fix Version: EJB 3.0 Beta 1 (was: Preview 5) MDB, Session Bean XML support - Key: EJBTHREE-21 URL: http://jira.jboss.com/jira/browse/EJBTHREE-21 Project: EJB 3.0 Type: Feature Request Versions: Preview 5 Reporter: Bill Burke Assignee: Bill Burke Fix For: EJB 3.0 Beta 1 Original Estimate: 1 week Remaining: 1 week Support EJB 3 spec mandated XML deployment descriptors. This has yet to be defined in the EJB 3 specification though. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (EJBTHREE-12) EJB ENC must be java:comp/env currently it is java.ejb/comp/env
[ http://jira.jboss.com/jira/browse/EJBTHREE-12?page=history ] Bill Burke updated EJBTHREE-12: --- Fix Version: EJB 3.0 Beta 1 (was: Preview 5) EJB ENC must be java:comp/env currently it is java.ejb/comp/env Key: EJBTHREE-12 URL: http://jira.jboss.com/jira/browse/EJBTHREE-12 Project: EJB 3.0 Type: Feature Request Versions: Preview 5 Reporter: Bill Burke Assignee: Bill Burke Fix For: EJB 3.0 Beta 1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
