[JBoss-dev] jboss-head build.936 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050407014408Lbuild.936 BUILD COMPLETE - build.936Date of build: 04/07/2005 01:44:08Time to build: 30 minutes 59 secondsLast changed: 04/07/2005 01:13:55Last log entry: upgrade to latest HibernateExt Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (11)1.5modifiedpatriot1burkethirdparty/hibernate/lib/hibernate-annotations.jarupgrade to latest HibernateExt1.5modifiedpatriot1burkeejb3/docs/tutorial/blob/blob.wikiupgrade to latest HibernateExt1.1addedpatriot1burkeejb3/docs/tutorial/blob/src/org/jboss/tutorial/blob/bean/BlobEntity2.javaupgrade to latest HibernateExt1.2modifiedpatriot1burkeejb3/docs/tutorial/blob/src/org/jboss/tutorial/blob/bean/LobTester.javaupgrade to latest HibernateExt1.6modifiedpatriot1burkeejb3/docs/tutorial/blob/src/org/jboss/tutorial/blob/bean/LobTesterBean.javaupgrade to latest HibernateExt1.2modifiedpatriot1burkeejb3/docs/tutorial/blob/src/org/jboss/tutorial/blob/client/Client.javaupgrade to latest HibernateExt1.4modifiedpatriot1burkethirdparty/hibernate/lib/hibernate-annotations.jarupdate docs1.2modifiedpatriot1burkeaspects/RELEASE_NOTES.htmlupdate docs1.36modifiedpatriot1burkeaspects/build.xmlupdate docs1.2modifiedpatriot1burkeaop/docs/reference/reference/en/modules/installing.xmlupdate docs1.15modifiedpatriot1burkeaop/docs/reference/reference/en/modules/running.xmlupdate docs
[JBoss-dev] jboss-3.2-testsuite build.104 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050407001844Lbuild.104 BUILD COMPLETE - build.104Date of build: 04/07/2005 00:18:44Time to build: 68 minutes 8 secondsLast changed: 04/05/2005 23:59:11Last log entry: Remove the jdk1.4 exception initCause method usage Unit Tests: (1967) Total Errors and Failures: (10)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.StatefulSessionUnitTestCasetestEvictionorg.jboss.test.cache.test.eviction.ReplicatedLRUPolicyUnitTestCasetestConcurrentAccessWithRWLockorg.jboss.test.cache.test.local.ConcurrentTransactionalUnitTestCasetestSessionTimeoutorg.jboss.test.cluster.test.SimpleTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCase Modifications since last build: (1)1.1.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/security/ejb/SecurityContextBean.javaRemove the jdk1.4 exception initCause method usage
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-98) Use latest Hibernate distribution
[ http://jira.jboss.com/jira/browse/EJBTHREE-98?page=history ] Bill Burke closed EJBTHREE-98: -- Resolution: Done > Use latest Hibernate distribution > - > > Key: EJBTHREE-98 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-98 > Project: EJB 3.0 > Type: Task > Reporter: Bill Burke > Assignee: 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.935 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050406232007Lbuild.935 BUILD COMPLETE - build.935Date of build: 04/06/2005 23:20:07Time to build: 22 minutes 55 secondsLast changed: 04/06/2005 22:28:25Last log entry: don't addUrl if shutting down. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (7)1.5modifiedpatriot1burkeaspects/src/main/org/jboss/aop/deployment/JBossClassPoolFactory.javadon't addUrl if shutting down.1.35modifiedpatriot1burkeaspects/build.xmlFix JBoss 3.2 Integration1.4modifiedpatriot1burkeaspects/src/main/org/jboss/aop/deployment/JBossClassPool32.javaFix JBoss 3.2 Integration1.4modifiedpatriot1burkeaspects/src/main/org/jboss/aop/deployment/JBossClassPoolFactory32.javaFix JBoss 3.2 Integration1.1addedpatriot1burkeaspects/src/jdk15/org/jboss/aop/deployment/AspectManagerService32JDK5.javaFix JBoss 3.2 Integration1.34modifiedpatriot1burkeaop/src/main/org/jboss/aop/instrument/Instrumentor.javaBetter error messages.1.2modifiedpatriot1burkej2se/src/main/org/jboss/mx/loading/RepositoryClassLoader.javachange name so it is compatible with JBoss 3.2 UnifiedClassLoader method name
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1667) Unit test failure: bringing up the test suite (RemoteDSUnitTestCase) fails
[ http://jira.jboss.com/jira/browse/JBAS-1667?page=history ] Scott M Stark closed JBAS-1667: --- Resolution: Done The jca/remote-jdbc/remote-ds.xml resource had not been merged from head. It runs fine after do the merge. one-test: [mkdir] Created dir: C:\cvs\JBoss4.0\jboss-4.0\testsuite\output\log [junit] Running org.jboss.test.jca.test.RemoteDSUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.922 sec > Unit test failure: bringing up the test suite (RemoteDSUnitTestCase) fails > -- > > Key: JBAS-1667 > URL: http://jira.jboss.com/jira/browse/JBAS-1667 > Project: JBoss Application Server > Type: Bug > Components: JCA service > Environment: win xp, linux > Reporter: Pushkala Iyer > > > Test Case: org.jboss.test.jca.test.RemoteDSUnitTestCase > We're seeing this test fail in multiple environments, can you please take a > look at it. This is for the 4.0.2 Final release. Thanks, > Bringing up the test suite fails: > This is the line in the code > (org.jboss.test.jca.test.RemoteDSUnitTestCase.java) that seems to fail: > return getDeploySetup(RemoteDSUnitTestCase.class,resURL.toString()); > Stack Trace: > java.lang.reflect.InvocationTargetException at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > Caused by: java.lang.NullPointerException at > org.jboss.test.jca.test.RemoteDSUnitTestCase.suite(RemoteDSUnitTestCase.java:87) > ... 8 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1667) Unit test failure: bringing up the test suite (RemoteDSUnitTestCase) fails
[ http://jira.jboss.com/jira/browse/JBAS-1667?page=history ] Pushkala Iyer updated JBAS-1667: Component: JCA service > Unit test failure: bringing up the test suite (RemoteDSUnitTestCase) fails > -- > > Key: JBAS-1667 > URL: http://jira.jboss.com/jira/browse/JBAS-1667 > Project: JBoss Application Server > Type: Bug > Components: JCA service > Environment: win xp, linux > Reporter: Pushkala Iyer > > > Test Case: org.jboss.test.jca.test.RemoteDSUnitTestCase > We're seeing this test fail in multiple environments, can you please take a > look at it. This is for the 4.0.2 Final release. Thanks, > Bringing up the test suite fails: > This is the line in the code > (org.jboss.test.jca.test.RemoteDSUnitTestCase.java) that seems to fail: > return getDeploySetup(RemoteDSUnitTestCase.class,resURL.toString()); > Stack Trace: > java.lang.reflect.InvocationTargetException at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > Caused by: java.lang.NullPointerException at > org.jboss.test.jca.test.RemoteDSUnitTestCase.suite(RemoteDSUnitTestCase.java:87) > ... 8 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1666) Unit Test Failure: testSRPLoginWithAuxChallenge
[ http://jira.jboss.com/jira/browse/JBAS-1666?page=history ] Pushkala Iyer updated JBAS-1666: Description: We are seeing this test fail in multiple environments. As this is required for the 4.0.2 Final release, can you please take a look at it? Thanks, Test Case: org.jboss.test.security.test.SRPLoginModuleUnitTestCase Test : testSRPLoginWithAuxChallenge StackTrace: Unable to complete login: Failed to complete SRP login, msg=Failed to encrypt aux challenge junit.framework.AssertionFailedError: Unable to complete login: Failed to complete SRP login, msg=Failed to encrypt aux challenge at org.jboss.test.security.test.SRPLoginModuleUnitTestCase.testSRPLoginWithAuxChallenge(SRPLoginModuleUnitTestCase.java:128) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) was: We are seeing this test fail in multiple environments. As this is required for the 4.0.2 Final release, can you please take a look at it? Thanks, Test Case: org.jboss.test.security.test.SRPLoginModuleUnitTestCase Test : testSRPLoginWithAuxChallenge StackTrace: Unable to complete login: Failed to complete SRP login, msg=Failed to encrypt aux challenge junit.framework.AssertionFailedError: Unable to complete login: Failed to complete SRP login, msg=Failed to encrypt aux challenge at org.jboss.test.security.test.SRPLoginModuleUnitTestCase.testSRPLoginWithAuxChallenge(SRPLoginModuleUnitTestCase.java:128) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Component: Security > Unit Test Failure: testSRPLoginWithAuxChallenge > --- > > Key: JBAS-1666 > URL: http://jira.jboss.com/jira/browse/JBAS-1666 > Project: JBoss Application Server > Type: Bug > Components: Security > Environment: win xp, linux > Reporter: Pushkala Iyer > > > We are seeing this test fail in multiple environments. As this is required > for the 4.0.2 Final release, can you please take a look at it? Thanks, > Test Case: org.jboss.test.security.test.SRPLoginModuleUnitTestCase > Test : testSRPLoginWithAuxChallenge > > StackTrace: > Unable to complete login: Failed to complete SRP login, msg=Failed to encrypt > aux challenge > junit.framework.AssertionFailedError: Unable to complete login: Failed to > complete SRP login, msg=Failed to encrypt aux challenge > at > org.jboss.test.security.test.SRPLoginModuleUnitTestCase.testSRPLoginWithAuxChallenge(SRPLoginModuleUnitTestCase.java:128) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) > at junit.extensions.TestSetup$1.protect(TestSetup.java:19) > at junit.extensions.TestSetup.run(TestSetup.java:23) > -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1668) Unit test failure: testJBossEditors (PropertyEditorsUnitTestCase)
Unit test failure: testJBossEditors (PropertyEditorsUnitTestCase) - Key: JBAS-1668 URL: http://jira.jboss.com/jira/browse/JBAS-1668 Project: JBoss Application Server Type: Bug Environment: win xp, linux Reporter: Pushkala Iyer We're seeing this test fail in multiple environments, can you please take a look at it. This is for the 4.0.2 Final release. The testJBossEditors test of the org.jboss.test.util.test.PropertyEditorsUnitTestCase fails due to an assertion failure. StackTrace: junit.framework.AssertionFailedError: Transform of Tue Jan 4 23:38:21 PST 2005 equals Tue Jan 04 23:38:21 CST 2005, output=Wed Jan 05 01:38:21 CST 2005 at org.jboss.test.util.test.PropertyEditorsUnitTestCase.doTests(PropertyEditorsUnitTestCase.java:226) at org.jboss.test.util.test.PropertyEditorsUnitTestCase.testJBossEditors(PropertyEditorsUnitTestCase.java:200) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1667) Unit test failure: bringing up the test suite (RemoteDSUnitTestCase) fails
Unit test failure: bringing up the test suite (RemoteDSUnitTestCase) fails -- Key: JBAS-1667 URL: http://jira.jboss.com/jira/browse/JBAS-1667 Project: JBoss Application Server Type: Bug Environment: win xp, linux Reporter: Pushkala Iyer Test Case: org.jboss.test.jca.test.RemoteDSUnitTestCase We're seeing this test fail in multiple environments, can you please take a look at it. This is for the 4.0.2 Final release. Thanks, Bringing up the test suite fails: This is the line in the code (org.jboss.test.jca.test.RemoteDSUnitTestCase.java) that seems to fail: return getDeploySetup(RemoteDSUnitTestCase.class,resURL.toString()); Stack Trace: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) Caused by: java.lang.NullPointerException at org.jboss.test.jca.test.RemoteDSUnitTestCase.suite(RemoteDSUnitTestCase.java:87) ... 8 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAOP-105) Allow JDK5 javaagent load-time transformation on JBoss 3.2.7
[ http://jira.jboss.com/jira/browse/JBAOP-105?page=history ] Bill Burke closed JBAOP-105: Resolution: Done > Allow JDK5 javaagent load-time transformation on JBoss 3.2.7 > > > Key: JBAOP-105 > URL: http://jira.jboss.com/jira/browse/JBAOP-105 > Project: JBoss AOP > Type: Feature Request > Versions: 1.1.1 > Reporter: Bill Burke > Fix For: 1.1.2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAOP-101) JBoss 3.2.6 is broken
[ http://jira.jboss.com/jira/browse/JBAOP-101?page=history ] Bill Burke closed JBAOP-101: Resolution: Done works/tested on 3.2.7 > JBoss 3.2.6 is broken > - > > Key: JBAOP-101 > URL: http://jira.jboss.com/jira/browse/JBAOP-101 > Project: JBoss AOP > Type: Bug > Versions: 1.1.1 > Reporter: Bill Burke > Fix For: 1.1.2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-105) Allow JDK5 javaagent load-time transformation on JBoss 3.2.7
Allow JDK5 javaagent load-time transformation on JBoss 3.2.7 Key: JBAOP-105 URL: http://jira.jboss.com/jira/browse/JBAOP-105 Project: JBoss AOP Type: Feature Request Versions: 1.1.1 Reporter: Bill Burke Fix For: 1.1.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: injboss example doesn't seem to work
The 'ant deploy-ear-aop' works fine for me with scoped classloading, JDK5, javaagent, JBOss 4.0.1sp1. Maybe sp1 is the difference. | | | dot.com:loader=unique-archive-name | | java2ParentDelegaton=false | | | | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872984#3872984 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872984 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: injboss example doesn't seem to work
That target works fine with isolated class loading disabled. With it enabled, the example doesn't work. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872982#3872982 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872982 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1298) HAR Deployer JBCache config
[ http://jira.jboss.com/jira/browse/JBAS-1298?page=comments#action_12316747 ] Steve Ebersole commented on JBAS-1298: -- That last comment is a little ambigious as I read back over it. Hibernate2 support will be getting removed from JBoss, and replaced with Hibernate3... > HAR Deployer JBCache config > > > Key: JBAS-1298 > URL: http://jira.jboss.com/jira/browse/JBAS-1298 > Project: JBoss Application Server > Type: Feature Request > Components: Hibernate service > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final > Reporter: Andrew Oliver > Assignee: Steve Ebersole > > Original Estimate: 6 hours > Remaining: 6 hours > > Presently HAR deployer picks up JBCache config from its classloader. It does > not use an MBean. It should use an MBean (and we should be able to get stats > from it). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: injboss example doesn't seem to work
Does it work with the 'ant deploy-ear-aop' target? This actually embedds an .aop file within the .ear file. I'll try this out myself. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872980#3872980 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872980 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head-jdk-matrix build.102 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050406221547Lbuild.102 BUILD COMPLETE - build.102Date of build: 04/06/2005 22:15:47Time to build: 22 minutes 20 secondsLast changed: 04/06/2005 22:09:22Last log entry: Fix JBoss 3.2 Integration Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (65)1.35modifiedpatriot1burkeaspects/build.xmlFix JBoss 3.2 Integration1.4modifiedpatriot1burkeaspects/src/main/org/jboss/aop/deployment/JBossClassPool32.javaFix JBoss 3.2 Integration1.4modifiedpatriot1burkeaspects/src/main/org/jboss/aop/deployment/JBossClassPoolFactory32.javaFix JBoss 3.2 Integration1.1addedpatriot1burkeaspects/src/jdk15/org/jboss/aop/deployment/AspectManagerService32JDK5.javaFix JBoss 3.2 Integration1.34modifiedpatriot1burkeaop/src/main/org/jboss/aop/instrument/Instrumentor.javaBetter error messages.1.2modifiedpatriot1burkej2se/src/main/org/jboss/mx/loading/RepositoryClassLoader.javachange name so it is compatible with JBoss 3.2 UnifiedClassLoader method name1.3modifiedreverbeltransaction/src/main/org/jboss/tm/XidFactoryMBean.javaForgot to extend ServiceMBean.1.10modifiedstarksmthirdparty/licenses/thirdparty-licenses.xmlFor each license type, add the acceptable source code license headers for validation agains the codebase. This is used by the org.jboss.tools.license.ValidateLicenseHeaders utility to determine which source files have invalid license headers.1.2modifiedstarksmvaria/src/main/org/jboss/tools/license/ValidateLicenseHeaders.javaIgnore _Stub.java files1.1addedstarksmvaria/src/main/org/jboss/tools/license/ValidateLicenseHeaders.javabranches: 1.1.2;A utility which scans all java source files in the cvs tree and validates the license header prior to the package statement for headers that match those declared in thirdparty/licenses/thirdparty-licenses.xml1.34modifiedpatriot1burkeaspects/build.xml1.1.2. Also make usable in JBoss 3.2 environment.1.22modifiedpatriot1burkeaspects/src/main/org/jboss/aop/deployment/AspectDeployer.java1.1.2. Also make usable in JBoss 3.2 environment.1.3modifiedpatriot1burkeaspects/src/main/org/jboss/aop/deployment/JBossClassLoaderValidator32.java1.1.2. Also make usable in JBoss 3.2 environment.1.3modifiedpatriot1burkeaspects/src/main/org/jboss/aop/deployment/JBossClassPool32.java1.1.2. Also make usable in JBoss 3.2 environment.1.3modifiedpatriot1burkeaspects/src/main/org/jboss/aop/deployment/JBossClassPoolFactory32.java1.1.2. Also make usable in JBoss 3.2 environment.1.73modifiedpatriot1burkeaop/build.xml1.1.21.3modifiedreverbeliiop/src/main/org/jboss/tm/iiop/CorbaTransactionService.javaDTM-related changes.1.4modifiedreverbeliiop/src/main/org/jboss/tm/iiop/TransactionServiceImpl.javaDTM-related changes.1.2modifiedreverbeliiop/src/idl/TransactionService.idlDTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/TransactionNotPreparedException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/server/DTMServant.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicHazardException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicMixedException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicRollbackException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/TransactionInactiveException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/Invocation.javaAssorted DTM-related changes.1.14modifiedreverbeltransaction/src/main/org/jboss/tm/XidFactory.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/XidFactoryMBean.javaAssorted DTM-related changes.1.8modifiedreverbeltransaction/src/main/org/jboss/tm/XidImpl.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/TransactionPropagationContextUtil.javaAssorted DTM-related changes.1.23modifiedreverbeltransaction/src/main/org/jboss/tm/TxManager.javaAssorted DTM-related changes.1.7modifiedreverbeltransaction/src/main/org/jboss/tm/GlobalId.javaAssorted DTM-related changes.1.7modifiedreverbeltransaction/src/main/org/jboss/tm/JBossXAException.javaAssorted DTM-related changes.1.41modifiedreverbeltransaction/src/main/org/jboss/tm/TransactionImpl.javaAssorted DTM-related changes.1.5modifiedanddsystem/src/main/org/jboss/system/pm/XMLAttributePersistenceManager.javafix logging1.49modifiedanddsystem/src/main/org/jboss/system/ServiceController.javafix logging1.34modifiedanddsystem/src/main/org/jboss/system/ServiceConfigurator.javafix logging1.9modifiedanddsystem/src/main/org/jboss/system/Lis
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP on JBoss 3.2
FYI, JBoss AOP can run standalone outside of app server. But, if you are running within JBoss Application Server, it cannot be independent. Why you ask? The problem is hot-deployment and how it iteracts with class transformation. I don't want to get into details, just please accept my explanation as is. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872979#3872979 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872979 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: Applying AOP with a Web app
http://docs.jboss.org/aop/1.1/aspect-framework/reference/en/html/running.html You will have to follow the standalone directions on setting this up. (AOPC, bootclasspath for JDK 1.4, or use the javaagent for JDK 5). FYI, Jsps are a special case. If you don't use the bootclasspath or javaagent load-time instrumentation procedure and instead decide to use the AOP Compiler, then you'll have to precompile your JSPS and then run AOPC on them. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872978#3872978 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872978 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: injboss example doesn't seem to work
Ok, Jedi, I was unable to reproduce your problem on JBoss 4.0.1SP1. I think I know what your problem is though. You must run 'ant deploy-ear'. This target will deploy the aopexample.ear file AS WELL AS a 'jboss-aop.xml' file to the deploy directory. If you run the 'ant deploy-ear-aop' target, it will create an EAR with a aopexample.aop jar file within the ear. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872977#3872977 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872977 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=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: JBPTL-17: Theme API food for thought II
Sounds too good :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872976#3872976 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872976 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: injboss example doesn't seem to work
Thanks for the reply Bill. I figured out what my problem was. In ear-deployer.xml, I had the "Isolated" attribute set to true. Setting it back to false made all of the AOP stuff start working. Is there any way to use JBoss AOP with isolated class loaders enabled? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872975#3872975 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872975 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-12) HibernateContext JDBC Connection
[ http://jira.jboss.com/jira/browse/HIBERNATE-12?page=comments#action_12316746 ] Stephen Pearson commented on HIBERNATE-12: -- Thanks for your feedback Steve. Currently I am using a modified version of the TransactionSync class, which does close the JDBC connection, and this works quite well. Can't wait to see how JBoss 4.02 and hibernate 3 will improve my application. > HibernateContext JDBC Connection > > > Key: HIBERNATE-12 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-12 > Project: Hibernate > Type: Bug > Environment: Mac OSX, JBoss 4.01sp1 > Reporter: Stephen Pearson > Assignee: Steve Ebersole > > Original Estimate: 1 hour > Remaining: 1 hour > > When using the HibernateContext getSession() function call, all works well > until the function call has finished, and then the underlying JDBC connection > is not closed. Therefore with each call to getSession within my EJB I > promptly receieve a "Closing a connection for you. Please close them > yourself." warning from the CachedConnectionManager. > Can the TransactionSynch call please close the JDBC connection when it > flushes and closes the Hibernate Session. -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (HIBERNATE-6) HibernateContext Interceptor
[ http://jira.jboss.com/jira/browse/HIBERNATE-6?page=history ]
Steve Ebersole closed HIBERNATE-6:
--
Assign To: Steve Ebersole (was: Gavin King)
Resolution: Done
> HibernateContext Interceptor
>
>
> Key: HIBERNATE-6
> URL: http://jira.jboss.com/jira/browse/HIBERNATE-6
> Project: Hibernate
> Type: Feature Request
> Environment: All
> Reporter: JesÃs MarÃn
> Assignee: Steve Ebersole
>
>
> is there a way to assign an Interceptor to a HibernateContext?
> I suppose that overloading getSession, getunmanagedSession and
> generateSession is worth the effort. Like this:
>public static Session getUnmanagedSession(String name, Interceptor
> interceptor) throws HibernateException, IllegalStateException
>{
> final Session managedSession = lookupSession(name);
> if (managedSession == null)
> {
> throw new IllegalStateException("No managed sessions found for
> current context");
> }
> return managedSession.getSessionFactory().openSession(
> managedSession.connection(), interceptor );
>}
>public static Session getSession(String name)
>{
> return getSession(name, null);
>}
>public static Session getSession(String name, Interceptor interceptor)
>{
> try
> {
> // Determine whether a session is already bound to the current
> transaction.
> // If so, return that session; otherwise generate a new session,
> bind, and
> // return it
> Session currentSession = lookupSession(name);
> if (currentSession == null)
> {
> currentSession = generateSession(name, interceptor);
> prepareSession(name, currentSession);
> bind(name, currentSession);
> }
> return currentSession;
> }
> catch(HibernateException e)
> {
> throw new NestedRuntimeException("Could not recover session", e);
> }
>}
>private static Session generateSession(String name, Interceptor
> interceptor) throws HibernateException
>{
> // Make sure there is an ongoing transaction prior to generating
> // a session in order to provide a usefull error message...
> checkTransactionStatus();
> SessionFactory factory = locateSessionFactory(name);
> if (interceptor == null) {
> return factory.openSession();
> } else {
> return factory.openSession(interceptor);
> }
>}
> Perhaps there is a better way to chain an interceptor into a SessionFactory
> using the current HibernateContext and I do not know how?
--
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_ide95&alloc_id396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-6) HibernateContext Interceptor
[
http://jira.jboss.com/jira/browse/HIBERNATE-6?page=comments#action_12316745 ]
Steve Ebersole commented on HIBERNATE-6:
Also note that session-scoped interceptors *do not* make sense in this type of
"managed session" environment.
> HibernateContext Interceptor
>
>
> Key: HIBERNATE-6
> URL: http://jira.jboss.com/jira/browse/HIBERNATE-6
> Project: Hibernate
> Type: Feature Request
> Environment: All
> Reporter: JesÃs MarÃn
> Assignee: Gavin King
>
>
> is there a way to assign an Interceptor to a HibernateContext?
> I suppose that overloading getSession, getunmanagedSession and
> generateSession is worth the effort. Like this:
>public static Session getUnmanagedSession(String name, Interceptor
> interceptor) throws HibernateException, IllegalStateException
>{
> final Session managedSession = lookupSession(name);
> if (managedSession == null)
> {
> throw new IllegalStateException("No managed sessions found for
> current context");
> }
> return managedSession.getSessionFactory().openSession(
> managedSession.connection(), interceptor );
>}
>public static Session getSession(String name)
>{
> return getSession(name, null);
>}
>public static Session getSession(String name, Interceptor interceptor)
>{
> try
> {
> // Determine whether a session is already bound to the current
> transaction.
> // If so, return that session; otherwise generate a new session,
> bind, and
> // return it
> Session currentSession = lookupSession(name);
> if (currentSession == null)
> {
> currentSession = generateSession(name, interceptor);
> prepareSession(name, currentSession);
> bind(name, currentSession);
> }
> return currentSession;
> }
> catch(HibernateException e)
> {
> throw new NestedRuntimeException("Could not recover session", e);
> }
>}
>private static Session generateSession(String name, Interceptor
> interceptor) throws HibernateException
>{
> // Make sure there is an ongoing transaction prior to generating
> // a session in order to provide a usefull error message...
> checkTransactionStatus();
> SessionFactory factory = locateSessionFactory(name);
> if (interceptor == null) {
> return factory.openSession();
> } else {
> return factory.openSession(interceptor);
> }
>}
> Perhaps there is a better way to chain an interceptor into a SessionFactory
> using the current HibernateContext and I do not know how?
--
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_ide95&alloc_id396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-6) HibernateContext Interceptor
[
http://jira.jboss.com/jira/browse/HIBERNATE-6?page=comments#action_12316744 ]
Steve Ebersole commented on HIBERNATE-6:
Sure, just use the SessionFactoryInterceptor managed attribute on the
org.jboss.hibernate.jmx.Hibernate mbean.
> HibernateContext Interceptor
>
>
> Key: HIBERNATE-6
> URL: http://jira.jboss.com/jira/browse/HIBERNATE-6
> Project: Hibernate
> Type: Feature Request
> Environment: All
> Reporter: JesÃs MarÃn
> Assignee: Gavin King
>
>
> is there a way to assign an Interceptor to a HibernateContext?
> I suppose that overloading getSession, getunmanagedSession and
> generateSession is worth the effort. Like this:
>public static Session getUnmanagedSession(String name, Interceptor
> interceptor) throws HibernateException, IllegalStateException
>{
> final Session managedSession = lookupSession(name);
> if (managedSession == null)
> {
> throw new IllegalStateException("No managed sessions found for
> current context");
> }
> return managedSession.getSessionFactory().openSession(
> managedSession.connection(), interceptor );
>}
>public static Session getSession(String name)
>{
> return getSession(name, null);
>}
>public static Session getSession(String name, Interceptor interceptor)
>{
> try
> {
> // Determine whether a session is already bound to the current
> transaction.
> // If so, return that session; otherwise generate a new session,
> bind, and
> // return it
> Session currentSession = lookupSession(name);
> if (currentSession == null)
> {
> currentSession = generateSession(name, interceptor);
> prepareSession(name, currentSession);
> bind(name, currentSession);
> }
> return currentSession;
> }
> catch(HibernateException e)
> {
> throw new NestedRuntimeException("Could not recover session", e);
> }
>}
>private static Session generateSession(String name, Interceptor
> interceptor) throws HibernateException
>{
> // Make sure there is an ongoing transaction prior to generating
> // a session in order to provide a usefull error message...
> checkTransactionStatus();
> SessionFactory factory = locateSessionFactory(name);
> if (interceptor == null) {
> return factory.openSession();
> } else {
> return factory.openSession(interceptor);
> }
>}
> Perhaps there is a better way to chain an interceptor into a SessionFactory
> using the current HibernateContext and I do not know how?
--
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_ide95&alloc_id396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (HIBERNATE-8) configuration property for naming strategy
[ http://jira.jboss.com/jira/browse/HIBERNATE-8?page=history ] Steve Ebersole resolved HIBERNATE-8: Assign To: Steve Ebersole (was: Gavin King) Resolution: Rejected Until the Hibernate JIRA is transferred over to this JIRA box, all requests for Hibernate-specific enhancements should be created in Hibernate's JIRA. > configuration property for naming strategy > -- > > Key: HIBERNATE-8 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-8 > Project: Hibernate > Type: Feature Request > Reporter: Tom Baeyens > Assignee: Steve Ebersole > Priority: Minor > > > currently, it's only possible to specify a naming strategy programmatically. > it would be nice to have a configuration property for it. > regards, tom. -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (HIBERNATE-9) local application of naming strategy
[ http://jira.jboss.com/jira/browse/HIBERNATE-9?page=history ] Steve Ebersole closed HIBERNATE-9: -- Assign To: Steve Ebersole (was: Gavin King) Resolution: Rejected Until the Hibernate JIRA is transferred over to this JIRA box, all requests for Hibernate-specific enhancements should be created in Hibernate's JIRA. > local application of naming strategy > > > Key: HIBERNATE-9 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-9 > Project: Hibernate > Type: Feature Request > Reporter: Tom Baeyens > Assignee: Steve Ebersole > Priority: Minor > > > It would be nice if users could apply a naming strategy on e.g. a hibernate > mapping file. Now, the naming strategy can only be applied globally to the > whole configuration. More general, it would be nice if users could specify > multiple naming strategies and for each strategy on which mappings they > apply. Consider supporting multiple ways of specifying on which mappings a > naming strategy applies : by putting it in a mapping file, by specifying > class names or table name prefixes, -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-11) DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1
[ http://jira.jboss.com/jira/browse/HIBERNATE-11?page=comments#action_12316741 ] Steve Ebersole commented on HIBERNATE-11: - As I mentioned previously, this is fixed in my local saandbox. It will be committed after 4.0.2 is released. > DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1 > - > > Key: HIBERNATE-11 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-11 > Project: Hibernate > Type: Bug > Reporter: youngm > Assignee: Steve Ebersole > Attachments: hibernate-cache.diff > > > When retrieving JBossCache from JNDI DeployedTreeCacheProvider must cast the > returned instance to org.jboss.cache.TreeCacheMBean not > org.jboss.cache.TreeCache. > Mike > See stacktrace below: > 13:25:29,883 ERROR [Hibernate] Starting failed > jboss.har:service=am_data/HibernateFactory > net.sf.hibernate.HibernateException: Could not instantiate Cache > at > net.sf.hibernate.cfg.Configuration.configureCaches(Configuration.java:1138) > at > net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:795) > at > org.jboss.hibernate.jmx.Hibernate.buildSessionFactory(Hibernate.java:583) > at org.jboss.hibernate.jmx.Hibernate.startService(Hibernate.java:551) > at > org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) > at > org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) > at sun.reflect.GeneratedMethodAccessor42.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:644) > at > org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:911) > at $Proxy0.start(Unknown Source) > at org.jboss.system.ServiceController.start(ServiceController.java:416) > at sun.reflect.GeneratedMethodAccessor5.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:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > at $Proxy4.start(Unknown Source) > at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273) > at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964) > at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) > 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: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:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > at $Proxy7.deploy(Unknown Source) > at > org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325) > at > org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:483) > at > org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractD
[JBoss-dev] [JBoss JIRA] Assigned: (HIBERNATE-11) DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1
[ http://jira.jboss.com/jira/browse/HIBERNATE-11?page=history ] Steve Ebersole reassigned HIBERNATE-11: --- Assign To: Steve Ebersole (was: Gavin King) > DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1 > - > > Key: HIBERNATE-11 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-11 > Project: Hibernate > Type: Bug > Reporter: youngm > Assignee: Steve Ebersole > Attachments: hibernate-cache.diff > > > When retrieving JBossCache from JNDI DeployedTreeCacheProvider must cast the > returned instance to org.jboss.cache.TreeCacheMBean not > org.jboss.cache.TreeCache. > Mike > See stacktrace below: > 13:25:29,883 ERROR [Hibernate] Starting failed > jboss.har:service=am_data/HibernateFactory > net.sf.hibernate.HibernateException: Could not instantiate Cache > at > net.sf.hibernate.cfg.Configuration.configureCaches(Configuration.java:1138) > at > net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:795) > at > org.jboss.hibernate.jmx.Hibernate.buildSessionFactory(Hibernate.java:583) > at org.jboss.hibernate.jmx.Hibernate.startService(Hibernate.java:551) > at > org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) > at > org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) > at sun.reflect.GeneratedMethodAccessor42.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:644) > at > org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:911) > at $Proxy0.start(Unknown Source) > at org.jboss.system.ServiceController.start(ServiceController.java:416) > at sun.reflect.GeneratedMethodAccessor5.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:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > at $Proxy4.start(Unknown Source) > at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273) > at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964) > at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) > 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: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:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > at $Proxy7.deploy(Unknown Source) > at > org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325) > at > org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:483) > at > org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204) > at > org.jboss.deployment.scanner.AbstractDeploymentS
[JBoss-dev] [Design of JBoss Portal] - JBPTL-17: Theme API food for thought II
As I mentioned in the first post, the separation of content and the rest via css is a good thing. The portlet spec defines a set of css classes and ids , taken from the wsrp 1.0 spec, that fit nicely with this approach. WSRP 2.0 is completing this set of classes and ids. So I'd like to propose to follow this approach, and define a set of classes and ids , by taking what is in wsrp 2.0 , and completing it if necessary. The portal will render a set of div and span tags with these class and id attributes. The css from the theme can then handle the rest (position, color, font, etc.) If you can't go with this approach for whatever reason, you can still create your own layouts, render set and themes and just use the infrastructure in the portal. But wouldn't it be nice if it just worked ? and putting it all on the foundation of an emerging and strong standard like wsrp is a good thing, I beliefe .. what do you think ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872971#3872971 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872971 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-12) HibernateContext JDBC Connection
[ http://jira.jboss.com/jira/browse/HIBERNATE-12?page=comments#action_12316740 ] Steve Ebersole commented on HIBERNATE-12: - Its not that it does not close the Connection; its that the Connection gets closed too late. This only happens when you nest ejb calls where the first ejb gets the session (the connection has not yet been obtained) and then call into another ejb which gets the session and uses it. The JBoss CCM sees that the connection was obtained during ejb2's call, but was not returned to the data source prior to ejb2's return. I am in the process of upgrading the inetgration code to Hibernate3, where we implemented releasing of the jdbc connections much more eagerly in JTA environment. This new code will be available in CVS after JBoss 4.0.2 is released. > HibernateContext JDBC Connection > > > Key: HIBERNATE-12 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-12 > Project: Hibernate > Type: Bug > Environment: Mac OSX, JBoss 4.01sp1 > Reporter: Stephen Pearson > Assignee: Steve Ebersole > > Original Estimate: 1 hour > Remaining: 1 hour > > When using the HibernateContext getSession() function call, all works well > until the function call has finished, and then the underlying JDBC connection > is not closed. Therefore with each call to getSession within my EJB I > promptly receieve a "Closing a connection for you. Please close them > yourself." warning from the CachedConnectionManager. > Can the TransactionSynch call please close the JDBC connection when it > flushes and closes the Hibernate Session. -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (HIBERNATE-12) HibernateContext JDBC Connection
[ http://jira.jboss.com/jira/browse/HIBERNATE-12?page=history ] Steve Ebersole reassigned HIBERNATE-12: --- Assign To: Steve Ebersole (was: Gavin King) > HibernateContext JDBC Connection > > > Key: HIBERNATE-12 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-12 > Project: Hibernate > Type: Bug > Environment: Mac OSX, JBoss 4.01sp1 > Reporter: Stephen Pearson > Assignee: Steve Ebersole > > Original Estimate: 1 hour > Remaining: 1 hour > > When using the HibernateContext getSession() function call, all works well > until the function call has finished, and then the underlying JDBC connection > is not closed. Therefore with each call to getSession within my EJB I > promptly receieve a "Closing a connection for you. Please close them > yourself." warning from the CachedConnectionManager. > Can the TransactionSynch call please close the JDBC connection when it > flushes and closes the Hibernate Session. -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-10) DeployedTreeCacheProvider doesn't work with Hibernate 2.1.8+
[ http://jira.jboss.com/jira/browse/HIBERNATE-10?page=comments#action_12316739 ] Steve Ebersole commented on HIBERNATE-10: - As I mentoned on the forum, the DeployedTreeCacheProvider has been reworked. The code will be committed after JBoss 4.0.2 is released. > DeployedTreeCacheProvider doesn't work with Hibernate 2.1.8+ > > > Key: HIBERNATE-10 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-10 > Project: Hibernate > Type: Bug > Reporter: youngm > Assignee: Steve Ebersole > > > DeployedTreeCacheProvider must be updated to support interface changes made > to net.sf.hibernate.cache.CacheProvider in 2.1.8. > http://forum.hibernate.org/viewtopic.php?t=940501 -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (HIBERNATE-5) jmx transaction flush swallows exception
[ http://jira.jboss.com/jira/browse/HIBERNATE-5?page=history ] Steve Ebersole reassigned HIBERNATE-5: -- Assign To: Steve Ebersole (was: Gavin King) > jmx transaction flush swallows exception > > > Key: HIBERNATE-5 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-5 > Project: Hibernate > Type: Bug > Environment: jboss-4.0.1 > winxp > postgresql > Reporter: Ben Litchfield > Assignee: Steve Ebersole > > > A database exception, such as constraint violation, doesn't happen until a > session.flush(). In the JMX code this happens in the > org.jboss.hibernate.session.TransactionSynch.beforeCompletion() method, but > the exception is swallowed. > This needs to be changed to throw an exception to the user. Otherwise no > exception is thrown to the user. > Ben -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (HIBERNATE-10) DeployedTreeCacheProvider doesn't work with Hibernate 2.1.8+
[ http://jira.jboss.com/jira/browse/HIBERNATE-10?page=history ] Steve Ebersole reassigned HIBERNATE-10: --- Assign To: Steve Ebersole (was: Gavin King) > DeployedTreeCacheProvider doesn't work with Hibernate 2.1.8+ > > > Key: HIBERNATE-10 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-10 > Project: Hibernate > Type: Bug > Reporter: youngm > Assignee: Steve Ebersole > > > DeployedTreeCacheProvider must be updated to support interface changes made > to net.sf.hibernate.cache.CacheProvider in 2.1.8. > http://forum.hibernate.org/viewtopic.php?t=940501 -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1304) Abillity to add DB-specific "hints" into Hibernate
[ http://jira.jboss.com/jira/browse/JBAS-1304?page=comments#action_12316738 ] Steve Ebersole commented on JBAS-1304: -- We already have an existing jira task to add this support. > Abillity to add DB-specific "hints" into Hibernate > -- > > Key: JBAS-1304 > URL: http://jira.jboss.com/jira/browse/JBAS-1304 > Project: JBoss Application Server > Type: Feature Request > Components: Hibernate service > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final > Reporter: Andrew Oliver > Assignee: Steve Ebersole > > Original Estimate: 1 day > Remaining: 1 day > > Customer has requested abillity to add hints to the underbelly of hibernate > esp for use with MViews. -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-7) CLONE -PropertyNotFoundException on runtime HAR deployment
[ http://jira.jboss.com/jira/browse/HIBERNATE-7?page=comments#action_12316737 ] Steve Ebersole commented on HIBERNATE-7: I have never been able to reproduce this. The testsuite also now contains tests specifically testing a hot redploy; it passes. I am also not able to reproduce this by manually deploying/redeploying the test ear file. I need some more info on your exact app setup. Is it a stand-alone HAR you drop in deploy? Do you access the "bound" session factory from another app then? Is that other app dependant on the har? etc > CLONE -PropertyNotFoundException on runtime HAR deployment > -- > > Key: HIBERNATE-7 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-7 > Project: Hibernate > Type: Bug > Reporter: Chris Buckley > Assignee: Steve Ebersole > > > SourceForge Submitter: treinar . > OS: Linux 2.4.22-36mdkenterprise (i386) > JVM: 1.4.2_06-b03 > I have a HAR archive, with one class: Pesticide.class > and its hibernate mapping file. Pesticide class has to > properties: id and name (with getter/setter methods). A > META-INF/hibernate-service.xml is also provided. > When deploying a HAR archive when JBoss runs, the > deployment fails. The following Exception is thrown: > net.sf.hibernate.PropertyNotFoundException: Could not > find a setter for property name in class > no.planteforsk.pvmdb.persistent.Pesticide > However, when JBoss is restarted, the HAR deploys fine. > The Exception is thrown in > net.sf.hibernate.property.BasicPropertyAccessor, in the > method getSetter. The cause of the exception is that no > match between set method (setName) and property (name) > is found in method setterMethod. > I inserted a few debug outputs in > BasicPropertyAccessor, and it turns out that when the > HAR is deployed at runtime, the method setName in > Pesticide is wrongly assumed to take no parameters, > (methods[i].getParameterTypes().length returns 0). When > jboss is restarted, and the deployment takes place on > the same HAR file, setName is assumed to take 1 > parameter, which of course is correct. > I'm not sure if this is a Java error or a JBoss error, > or even a Hibernate error, but maybe you do. It does > concern JBoss, however. -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.934 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050406212903Lbuild.934 BUILD COMPLETE - build.934Date of build: 04/06/2005 21:29:03Time to build: 16 minutes 59 secondsLast changed: 04/06/2005 21:00:24Last log entry: Forgot to extend ServiceMBean. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (4)1.3modifiedreverbeltransaction/src/main/org/jboss/tm/XidFactoryMBean.javaForgot to extend ServiceMBean.1.10modifiedstarksmthirdparty/licenses/thirdparty-licenses.xmlFor each license type, add the acceptable source code license headers for validation agains the codebase. This is used by the org.jboss.tools.license.ValidateLicenseHeaders utility to determine which source files have invalid license headers.1.2modifiedstarksmvaria/src/main/org/jboss/tools/license/ValidateLicenseHeaders.javaIgnore _Stub.java files1.1addedstarksmvaria/src/main/org/jboss/tools/license/ValidateLicenseHeaders.javabranches: 1.1.2;A utility which scans all java source files in the cvs tree and validates the license header prior to the package statement for headers that match those declared in thirdparty/licenses/thirdparty-licenses.xml
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1298) HAR Deployer JBCache config
[ http://jira.jboss.com/jira/browse/JBAS-1298?page=comments#action_12316736 ] Steve Ebersole commented on JBAS-1298: -- This is all done in my local sandbox, and will get committed after 4.0.2 is released. It will (actually is already) also get applied to jboss-head. Note that the new integration code will upgrade hibernate support to Hibernate3 also... > HAR Deployer JBCache config > > > Key: JBAS-1298 > URL: http://jira.jboss.com/jira/browse/JBAS-1298 > Project: JBoss Application Server > Type: Feature Request > Components: Hibernate service > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final > Reporter: Andrew Oliver > Assignee: Steve Ebersole > > Original Estimate: 6 hours > Remaining: 6 hours > > Presently HAR deployer picks up JBCache config from its classloader. It does > not use an MBean. It should use an MBean (and we should be able to get stats > from it). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - JBPTL-17: Theme API food for thought
I commited a first draft of the new feature today. don't go crazy, it's still very early on, but here is the general idea, and my motivations: themes, layouts, skins , branding . they all have a lot in common, in fact : I don't know where one ends and the other one begins. So I tried to come up with the most flexible approach. I really like the clean separation of duties that is outlined in css zengarden (http://www.csszengarden.com/) . It separates content from the rest, and gives the web designer the most power over the look and feel. You can find a sample app attached to the JIRA issue (JBTL-17) So here is what a typical portal request looks like: * the portal determines the portal page to render, and calls the portlet container for each portlet on that page * once the portlet content is rendered, the theme takes over * themes are split into three major components: a layout, a theme, and a render set * a layout is a JSP or a Servlet that the portal can request dispatch to. It is the piece that creates the root tag of the response (like HTML) * in case of a jsp. there are tags to render a region of the page, or a particular portlet, and one to inject the theme * in case of a servlet, there is an API to get the same task done (the same API the tags are using) * the region tag gets the list of results containing the rendered portlet content for the portlets on that page region. It then determines the render set for the current content type. * a render set is a collection of classes that implement a defined interface * there are 4 renderer interfaces in a render set (region, portlet window, decoration, and portlet content) * the theme is a set of css, js, and binary files. When the theme tag is injecting the theme content, it actually injects link and script tags * the layout, the renderer set and the theme all work together to get the final markup. * There are some dependencies between all of them, but for now there are no rules: each piece can be switched independently I'll be providing more examples in the next days themes are in core/src/main/org/jboss/portal/core/theme/* View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872970#3872970 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872970 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1576) Hibernate TransactionSynch should rollback transaction on session.flush exception
[
http://jira.jboss.com/jira/browse/JBAS-1576?page=comments#action_12316735 ]
Steve Ebersole commented on JBAS-1576:
--
The TransactionSynch is no longer needed in the new integration code. The new
code will upgrade to Hibernate3, where we added the capability inside Hibernate
itself to track "current" session (by transsaction).
The needed work is all done in my local sandbox, but unfortunately I cannot
commit it until after 4.0.2 has been released. I'll leave this case open util
after I can commit this new stuff.
> Hibernate TransactionSynch should rollback transaction on session.flush
> exception
> -
>
> Key: JBAS-1576
> URL: http://jira.jboss.com/jira/browse/JBAS-1576
> Project: JBoss Application Server
> Type: Bug
> Components: Hibernate service
> Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1RC1, JBossAS-4.0.1 Final,
> JBossAS-4.0.0 Final
> Environment: jboss 4, hibernate 2.2
> Reporter: Armin Haaf
> Assignee: Steve Ebersole
>
>
> org.jboss.hibernate.session.TransactionSynch only logs a error on session
> flush in beforeCompletion:
> try
> {
> log.trace("Flushing Session");
> session.flush();
> }
> catch(Throwable t)
> {
> log.warn("Error flushing session");
> }
> This leads to inconsistent transactions. A transaction is commited, but
> should be rollbacked on a session.flush problem. In my opinion it should
> throw a RuntimeException to rollback the transaction.
--
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1372) HIbernateContext does not work well with CachedConnectionManager
[ http://jira.jboss.com/jira/browse/JBAS-1372?page=comments#action_12316732 ] Steve Ebersole commented on JBAS-1372: -- This will be fixed in the next release of the Hibernate integration code. The integration code will be getting upgraded to support Hibernate3. Two things we did in Hibernate3 will come into play here: 1) release connections eagerly in JTA environments (basically after every use); 2) ability to track "current" sessions (by transaction) in Hibernate itself in JTA environments. All the required changes are sitting in my local sandbox and will get commited after JBoss 4.0.2 gets released. > HIbernateContext does not work well with CachedConnectionManager > > > Key: JBAS-1372 > URL: http://jira.jboss.com/jira/browse/JBAS-1372 > Project: JBoss Application Server > Type: Bug > Components: JCA service, Hibernate service > Versions: JBossAS-4.0.1 Final > Environment: Jboss 4.0.1 > Windows 2000 > JDK 1.5 > Reporter: janssk1 > Assignee: Steve Ebersole > > > I'm trying to use the HibernateContext to create an hibernate session that > will be automatically flushed on JTA transaction commit. This works well but > the jboss log files are getting filled with warning messages from the > CachedConnectionManager. see below for a log file > I have a simple CMT SSB that gets the hibernate session using > HibernateContext, updates an object and that' s it. My code does not do any > transaction management or explicit hibernate flush. > After the method is finished, the transaction invoker will kick in and commit > the transaction. Since the transaction contains some synchronization > listeners, these will be notified appropriatly. Two listeners are available. > One listener attached by the HibernateContext (this one will flush and close > the session) and another one added by the CachedConnectionManager. This one > will try to close the connection if it was not properly closed. When the > hibernate listener tries to close the session, the cachedconnectionmanager > will be notified that the connection is closed. This should normally remove > the connection from its internal caches and also remove the automatic close > on transaction termination from the current transaction. Since the connection > is explicity closed, it does not need to be closed implicitly anymore. > However, this does not work as expected (see the trace). A looked a bit in > the code and the problem seems to be related to the interceptor stack. In a > standard jboss installation, an ejb is configured with (among others) a > transaction interceptor followed by a cachedconnectioninterceptor. The > cachedconnectioninterceptor sets some context (metaAwareObject = bean) on the > cachedconnectionmanager. However, in the finally block of the transaction > interceptor, the cachcedconnection interceptor is already finished and the > context is no longer available. This explains the 'Trying to return an > unknown connection' exception. The 'Closing connection for you' message is > related (i think) to the fact that the current transaction is no longer > active when the cachedconnection manager is notified of the connection close. > It the transaction is not active anymore, the cachedconnection manager does > not remove the automatic close on transaction termination. So after the > hibernate listener is finshed (connection closed), the other listener > attached by the cached connection manager kicks in and closes it once more. > I was able to get rid of all the (unnecessary) warning by simply removing the > cached connection interceptor. However, i would like to keep it since it > provides me basic stupidy protection. -- 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_ide95&alloc_id396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1666) Unit Test Failure: testSRPLoginWithAuxChallenge
Unit Test Failure: testSRPLoginWithAuxChallenge Key: JBAS-1666 URL: http://jira.jboss.com/jira/browse/JBAS-1666 Project: JBoss Application Server Type: Bug Environment: win xp, linux Reporter: Pushkala Iyer We are seeing this test fail in multiple environments. As this is required for the 4.0.2 Final release, can you please take a look at it? Thanks, Test Case: org.jboss.test.security.test.SRPLoginModuleUnitTestCase Test : testSRPLoginWithAuxChallenge StackTrace: Unable to complete login: Failed to complete SRP login, msg=Failed to encrypt aux challenge junit.framework.AssertionFailedError: Unable to complete login: Failed to complete SRP login, msg=Failed to encrypt aux challenge at org.jboss.test.security.test.SRPLoginModuleUnitTestCase.testSRPLoginWithAuxChallenge(SRPLoginModuleUnitTestCase.java:128) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1523) JBAS-30 - txtimers created via Servlet init get duplicated
[ http://jira.jboss.com/jira/browse/JBAS-1523?page=history ] Ivelin Ivanov reassigned JBAS-1523: --- Assign To: Alexey Loubyansky (was: Ivelin Ivanov) > JBAS-30 - txtimers created via Servlet init get duplicated > -- > > Key: JBAS-1523 > URL: http://jira.jboss.com/jira/browse/JBAS-1523 > Project: JBoss Application Server > Type: Support Patch > Versions: JBossAS-4.0.0 Final > Reporter: Luc Texier > Assignee: Alexey Loubyansky > Attachments: jboss_jar-patched.jar > > > Some customers have expressed the wish to get the issue fixed in JBossAS 4.0.0 -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1523) JBAS-30 - txtimers created via Servlet init get duplicated
[ http://jira.jboss.com/jira/browse/JBAS-1523?page=history ] Ivelin Ivanov reassigned JBAS-1523: --- Assign To: Ivelin Ivanov (was: Alexey Loubyansky) > JBAS-30 - txtimers created via Servlet init get duplicated > -- > > Key: JBAS-1523 > URL: http://jira.jboss.com/jira/browse/JBAS-1523 > Project: JBoss Application Server > Type: Support Patch > Versions: JBossAS-4.0.0 Final > Reporter: Luc Texier > Assignee: Ivelin Ivanov > Attachments: jboss_jar-patched.jar > > > Some customers have expressed the wish to get the issue fixed in JBossAS 4.0.0 -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: injboss example doesn't seem to work
Jedi. I was talking to drakonis. I'll see if I can reproduce your problem with JDK5/JB4/pluggable_instrumentor View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872969#3872969 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872969 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPTL-17) Theme API
[ http://jira.jboss.com/jira/browse/JBPTL-17?page=history ] Martin Holzner updated JBPTL-17: Attachment: zengarden.ear This is a sample application containing portlets, a portal page definition, a layout, and several themes. Note: the local themes only work in FireFox, not in IE > Theme API > - > > Key: JBPTL-17 > URL: http://jira.jboss.com/jira/browse/JBPTL-17 > Project: JBoss Portal > Type: Feature Request > Reporter: Julien Viet > Assignee: Martin Holzner > Fix For: 2.0 RC > Attachments: PortalScreenShots.doc, zengarden.ear > > > Define a theme API > The Portal Container will procude during an invocation a result > which is a set of page fragment. These page fragment will all inherit the > same class > but will have various custom properties (for instance a Portlet window has a > PortletMode). > We need to find the right architecture for theming here. A fragment should be > rendered > on screen by a general mechanism and let room for customized renderers. > Also we need a way to package and deploy new theme (ThemeDeployer ?) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPTL-17) Theme API
[ http://jira.jboss.com/jira/browse/JBPTL-17?page=history ] Martin Holzner updated JBPTL-17: Attachment: PortalScreenShots.doc here is a set of screen shots. What you see is the content of www.csszengarden.com split into a layout, three portlets, and several themes/ once screen shot per theme. > Theme API > - > > Key: JBPTL-17 > URL: http://jira.jboss.com/jira/browse/JBPTL-17 > Project: JBoss Portal > Type: Feature Request > Reporter: Julien Viet > Assignee: Martin Holzner > Fix For: 2.0 RC > Attachments: PortalScreenShots.doc > > > Define a theme API > The Portal Container will procude during an invocation a result > which is a set of page fragment. These page fragment will all inherit the > same class > but will have various custom properties (for instance a Portlet window has a > PortletMode). > We need to find the right architecture for theming here. A fragment should be > rendered > on screen by a general mechanism and let room for customized renderers. > Also we need a way to package and deploy new theme (ThemeDeployer ?) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: injboss example doesn't seem to work
Already read those docs, and I do have EnableTransformer set to "true". I'm using JBoss 4.0.1. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872968#3872968 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872968 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=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: New Build - Standalone module - multiple builds
For the export functionality, we want to keep the syntax as simple as possible.
So to include the jmx project in your classpath you would want to do:
|
|
This would look for a component-info.xml first in ../jmx and then in
../thirdparty/jmx. The component-info would need to have an export declaration:
|
|
|
|
|
|
So that jboss-jmx.jar would be included in the classpath of the compilation.
However, I think you will still want the ability to use artifacts or other
includes besides the exported ones:
|
|
| This would cause the parsing as above, but would use the designated
reference id instead of the component's exports. So the export statement is
the default, but you retain the ability to reference an abitrary input.
To do this, I will need to add a component-info.xml for thirdparty/* in cvs. I
assme there is no problem with this? We'll need these eventually, anyway.
Basically, it will involve copying the existing thirdparty component
declarations from jbossas/jbossbuild.xml into the component-info.xml and
changing the {includes} to {export}.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872967#3872967
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872967
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.933 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050406191318Lbuild.933 BUILD COMPLETE - build.933Date of build: 04/06/2005 19:13:18Time to build: 21 minutes 46 secondsLast changed: 04/06/2005 18:11:05Last log entry: 1.1.2. Also make usable in JBoss 3.2 environment. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (42)1.34modifiedpatriot1burkeaspects/build.xml1.1.2. Also make usable in JBoss 3.2 environment.1.22modifiedpatriot1burkeaspects/src/main/org/jboss/aop/deployment/AspectDeployer.java1.1.2. Also make usable in JBoss 3.2 environment.1.3modifiedpatriot1burkeaspects/src/main/org/jboss/aop/deployment/JBossClassLoaderValidator32.java1.1.2. Also make usable in JBoss 3.2 environment.1.3modifiedpatriot1burkeaspects/src/main/org/jboss/aop/deployment/JBossClassPool32.java1.1.2. Also make usable in JBoss 3.2 environment.1.3modifiedpatriot1burkeaspects/src/main/org/jboss/aop/deployment/JBossClassPoolFactory32.java1.1.2. Also make usable in JBoss 3.2 environment.1.73modifiedpatriot1burkeaop/build.xml1.1.21.3modifiedreverbeliiop/src/main/org/jboss/tm/iiop/CorbaTransactionService.javaDTM-related changes.1.4modifiedreverbeliiop/src/main/org/jboss/tm/iiop/TransactionServiceImpl.javaDTM-related changes.1.2modifiedreverbeliiop/src/idl/TransactionService.idlDTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/TransactionNotPreparedException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/server/DTMServant.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicHazardException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicMixedException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicRollbackException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/TransactionInactiveException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/Invocation.javaAssorted DTM-related changes.1.14modifiedreverbeltransaction/src/main/org/jboss/tm/XidFactory.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/XidFactoryMBean.javaAssorted DTM-related changes.1.8modifiedreverbeltransaction/src/main/org/jboss/tm/XidImpl.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/TransactionPropagationContextUtil.javaAssorted DTM-related changes.1.23modifiedreverbeltransaction/src/main/org/jboss/tm/TxManager.javaAssorted DTM-related changes.1.7modifiedreverbeltransaction/src/main/org/jboss/tm/GlobalId.javaAssorted DTM-related changes.1.7modifiedreverbeltransaction/src/main/org/jboss/tm/JBossXAException.javaAssorted DTM-related changes.1.41modifiedreverbeltransaction/src/main/org/jboss/tm/TransactionImpl.javaAssorted DTM-related changes.1.5modifiedanddsystem/src/main/org/jboss/system/pm/XMLAttributePersistenceManager.javafix logging1.49modifiedanddsystem/src/main/org/jboss/system/ServiceController.javafix logging1.34modifiedanddsystem/src/main/org/jboss/system/ServiceConfigurator.javafix logging1.9modifiedanddsystem/src/main/org/jboss/system/ListenerServiceMBeanSupport.javafix logging1.16modifiedanddsystem/src/main/org/jboss/deployment/scanner/AbstractDeploymentScanner.javafix logging1.7modifiedanddsystem/src/main/org/jboss/deployment/scanner/HttpURLDeploymentScanner.javafix logging1.34modifiedanddsystem/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.javafix logging1.9modifiedanddsystem/src/main/org/jboss/deployment/cache/DeploymentCache.javafix logging1.19modifiedanddsystem/src/main/org/jboss/deployment/XSLSubDeployer.javafix logging1.2modifiedandddeployment/src/main/org/jboss/deployment/spi/DeploymentManagerImpl.javafix logging1.10modifiedanddvaria/src/main/org/jboss/web/loadbalancer/Loadbalancer.javafix logging1.7modifiedanddvaria/src/main/org/jboss/web/loadbalancer/scheduler/AbstractScheduler.javafix logging1.5modifiedanddvaria/src/main/org/jboss/services/deployment/DeploymentManager.javafix logging1.16modifiedanddvaria/src/main/org/jboss/mail/MailService.javafix logging1.3modifiedanddvaria/src/main/org/jboss/mq/il/http/servlet/HTTPServerILServlet.javafix logging1.4modifiedanddvaria/src/main/org/jboss/jmx/adaptor/snmp/trapd/TrapReceiver.javafix logging1.8modifiedanddvaria/src/main/org/jboss/jmx/adaptor/snmp/agent/TrapFactorySupport.javafix logging1.8modifiedanddvaria/src/main/org/jboss/jmx/adaptor/snmp/agent/SnmpAgentService.javafix logging
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: injboss example doesn't seem to work
Please read our documentation. It comes with both the distribution and is online here: http://docs.jboss.org/aop/1.1/aspect-framework/reference/en/html/running.html The JBoss 3.2.x integration is broken with 1.1.1. It will be fixed with 1.1.2. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872966#3872966 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872966 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: injboss example doesn't seem to work
I may need to suscribe to the same problem, although i'm kinda new to jboss and total beginer with aop, but it kinda lacks any first stepts into jboss aop. Was following the docs on http://docs.jboss.org/aop/1.1/aspect-framework/examples/injboss/aopInJbossPackaging.html . There it says anonymous wrote : | All the examples shown here use loadtime transformations, so you will need to modify your jboss/server/--yourconfig--/conf/jboss-service.xml as outlined in Running with JBoss Application Server | The running with Jboss Application Server is a dead link however. Points to http://docs.jboss.org/aop/1.1/aspect-framework/misc/running_jboss.html which is missing on the site and in the doc. that come with jboss-aop_1.1.1.zip too. So i may belive that the answer to the question lies with that and will be forever lost to us mere mortals:). I modified the build xml to go for the default starting of the server. Went for ant deploy-basic-lt-war which at the end says "Classes have not been aop'ed - run JBoss with enable transformations = true" Did a google on that, nothing was found. However in a post i found that someone set EnableTransformer to true in the /default/conf/jboss-service.xml . I myself have not any EnableTransformer in jboss-service.xml to be set. But javajedi if u'll be kind to answer where did u read about the pluggable-instrumentor.jar . I have not found any reference to it. Is it necesary? Well hope someone has any answers. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872965#3872965 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872965 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1644) Cleanup the license headers in the source code
[ http://jira.jboss.com/jira/browse/JBAS-1644?page=history ] Scott M Stark closed JBAS-1644: --- Resolution: Done The validation utility has been added to varia as org.jboss.tools.license.ValidateLicenseHeaders, and the The current 4.0 branch output shows no invalid or missing headers: [EMAIL PROTECTED] varia]$ java -cp output/classes org.jboss.tools.license.ValidateLicenseHeaders /cvs/JBoss4.0/jboss-4.0 Apr 6, 2005 4:29:58 PM org.jboss.tools.license.ValidateLicenseHeaders main INFO: Processed 6402 Apr 6, 2005 4:29:58 PM org.jboss.tools.license.ValidateLicenseHeaders main INFO: Files with no headers: 0 Apr 6, 2005 4:29:58 PM org.jboss.tools.license.ValidateLicenseHeaders main INFO: Files with invalid headers: 0 This needs to be repeated for head and 3.2. > Cleanup the license headers in the source code > -- > > Key: JBAS-1644 > URL: http://jira.jboss.com/jira/browse/JBAS-1644 > Project: JBoss Application Server > Type: Task > Components: Build System > Reporter: Scott M Stark > Assignee: Scott M Stark > Priority: Critical > Fix For: JBossAS-4.0.2 Final > Attachments: InvalidHeaders.txt, NoHeaders.txt > > Original Estimate: 1 day > Remaining: 1 day > > To prevent invalid license terms from showin up in the source files I have > added copyright child elements to the > thirdparty/licenses/thirdparty-licenses.xml file under the license elements. > For example, some of the lgpl copyright headers are: > > > JBoss, the OpenSource J2EE webOS > Distributable under LGPL license. > See terms of license at gnu.org. > > > JBoss, the OpenSource EJB server > Distributable under LGPL license. > See terms of license at gnu.org. > > ... > There is also a org.jboss.tools.copyright.ValidateCopyrightHeaders utility > which validates all header files found in a cvs source tree for conformance > against the valid headers. The current output for the 4.0 branch is: > Apr 4, 2005 9:39:39 PM org.jboss.tools.copyright.ValidateCopyrightHeaders main > INFO: Processed 6441 > Apr 4, 2005 9:39:39 PM org.jboss.tools.copyright.ValidateCopyrightHeaders main > INFO: Files with no headers: 900 > Apr 4, 2005 9:39:39 PM org.jboss.tools.copyright.ValidateCopyrightHeaders main > INFO: Files with invalid headers: 904 > The files with no headers and those with invalid headers are attached as > InvalidHeaders.txt and NoHeaders.txt -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite?log=log20050406171631 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: 04/06/2005 17:16:31Time to build: 97 minutes 24 secondsLast changed: 04/06/2005 16:56:15Last log entry: DTM-related changes. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (77)1.3modifiedreverbeliiop/src/main/org/jboss/tm/iiop/CorbaTransactionService.javaDTM-related changes.1.4modifiedreverbeliiop/src/main/org/jboss/tm/iiop/TransactionServiceImpl.javaDTM-related changes.1.2modifiedreverbeliiop/src/idl/TransactionService.idlDTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/TransactionNotPreparedException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/server/DTMServant.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicHazardException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicMixedException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicRollbackException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/TransactionInactiveException.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/Invocation.javaAssorted DTM-related changes.1.14modifiedreverbeltransaction/src/main/org/jboss/tm/XidFactory.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/XidFactoryMBean.javaAssorted DTM-related changes.1.8modifiedreverbeltransaction/src/main/org/jboss/tm/XidImpl.javaAssorted DTM-related changes.1.2modifiedreverbeltransaction/src/main/org/jboss/tm/TransactionPropagationContextUtil.javaAssorted DTM-related changes.1.23modifiedreverbeltransaction/src/main/org/jboss/tm/TxManager.javaAssorted DTM-related changes.1.7modifiedreverbeltransaction/src/main/org/jboss/tm/GlobalId.javaAssorted DTM-related changes.1.7modifiedreverbeltransaction/src/main/org/jboss/tm/JBossXAException.javaAssorted DTM-related changes.1.41modifiedreverbeltransaction/src/main/org/jboss/tm/TransactionImpl.javaAssorted DTM-related changes.1.5modifiedanddsystem/src/main/org/jboss/system/pm/XMLAttributePersistenceManager.javafix logging1.49modifiedanddsystem/src/main/org/jboss/system/ServiceController.javafix logging1.34modifiedanddsystem/src/main/org/jboss/system/ServiceConfigurator.javafix logging1.9modifiedanddsystem/src/main/org/jboss/system/ListenerServiceMBeanSupport.javafix logging1.16modifiedanddsystem/src/main/org/jboss/deployment/scanner/AbstractDeploymentScanner.javafix logging1.7modifiedanddsystem/src/main/org/jboss/deployment/scanner/HttpURLDeploymentScanner.javafix logging1.34modifiedanddsystem/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.javafix logging1.9modifiedanddsystem/src/main/org/jboss/deployment/cache/DeploymentCache.javafix logging1.19modifiedanddsystem/src/main/org/jboss/deployment/XSLSubDeployer.javafix logging1.2modifiedandddeployment/src/main/org/jboss/deployment/spi/DeploymentManagerImpl.javafix logging1.10modifiedanddvaria/src/main/org/jboss/web/loadbalancer/Loadbalancer.javafix logging1.7modifiedanddvaria/src/main/org/jboss/web/loadbalancer/scheduler/AbstractScheduler.javafix logging1.5modifiedanddvaria/src/main/org/jboss/services/deployment/DeploymentManager.javafix logging1.16modifiedanddvaria/src/main/org/jboss/mail/MailService.javafix logging1.3modifiedanddvaria/src/main/org/jboss/mq/il/http/servlet/HTTPServerILServlet.javafix logging1.4modifiedanddvaria/src/main/org/jboss/jmx/adaptor/snmp/trapd/TrapReceiver.javafix logging1.8modifiedanddvaria/src/main/org/jboss/jmx/adaptor/snmp/agent/TrapFactorySupport.javafix logging1.8modifiedanddvaria/src/main/org/jboss/jmx/adaptor/snmp/agent/SnmpAgentService.javafix logging1.12modifiedanddmanagement/src/main/org/jboss/management/j2ee/JTAResource.javafix logging1.12modifiedanddmanagement/src/main/org/jboss/management/j2ee/RMI_IIOPResource.javafix logging1.11modifiedanddmanagement/src/main/org/jboss/management/j2ee/URLResource.javafix logging1.21modifiedanddaspects/src/main/org/jboss/aop/deployment/AspectDeployer.javafix logging1.18modifiedanddconsole/src/main/org/jboss/console/twiddle/Twiddle.javafix logging1.5modifiedanddmedia/src/main/org/jboss/media/engine/MediaEngineDeployer.javafix logging1.8modifiedanddmedia/src/main/org/jboss/media/entity/MediaEntityBean.javafix logging1.1addedosdchicago
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1665) EJB-QL compiler (parser) confused by "Order" abstract-schema
EJB-QL compiler (parser) confused by "Order" abstract-schema Key: JBAS-1665 URL: http://jira.jboss.com/jira/browse/JBAS-1665 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.2RC1 Environment: Intel, Linux 2.6 Reporter: Mike Sowka Follow this forum "monologue": http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872960 It seems that the JBoss EJB-QL parser/compiler gets confused by the use of "Order" as the abstract-schema. I would get the following error when trying query "SELECT COUNT(o) FROM Order o": org.jboss.deployment.DeploymentException: Error compiling EJB-QL statement 'SELECT COUNT(o) FROM Order o'; - nested throwable: (org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered "Order" at line 1, column 22. What I believe is happening is that JBoss mistankenly parses "Order" as the query keword ORDER. Initially I thought this was the fault of my query statement which I pulled out of the EJB2.1 Spec. I contacted the spec contact, and Linda DeMichiel replied to me noting that in fact "Order" should be OK for the abstract-schema and is only restriced in use as an identifier. -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - injboss example doesn't seem to work
Sorry for the newbie question. I've spent the better part of a day playing with this and still haven't had any success. I'm running JBoss 4.0.1 under JDK 1.5 on Linux. I downloaded jboss-aop 1.1.1. I replaced jboss-aop.deployer in my deploy directory with jboss-aop-jdk50.deployer. I placed pluggable-instrumentor.jar in my bin directory and added "-javaagent:pluggable-instrumentor.jar" to run.conf (the docs have a typo, BTW. They specify -javaagent= instead of -javaagent:.) I found the injboss example and ran "ant ear". I then copied aopexample.ear into my deploy directory. So far so good, it looks like it deployed fine. When I go to http://localhost:8080/aopexample, I see the following sent to stdout: [STDOUT] ExampleValue.getMessage() When I hit "Submit Query", I get the following to stdout: [STDOUT] EarExampleServlet.service() [STDOUT] *** ExampleSessionBean.getValue() [STDOUT] ExampleValue String Constructor [STDOUT] ExampleValue String Constructor [STDOUT] ExampleValue.getMessage() Shouldn't I be seeing the "<<< Entering SimpleInterceptor:" messages? Any idea what I'm doing wrong? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872952#3872952 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872952 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (HIBERNATE-13) testEjbInterception Unit Test failure
[ http://jira.jboss.com/jira/browse/HIBERNATE-13?page=history ] Ryan Campbell updated HIBERNATE-13: --- Description: The following test is failing in the 4.0 branch and needs to be resolved before the 4.0.2 Final release. We've tested this in multiple environments and received the same error. Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase Test : testEjbInterception Stack Trace: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:534) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) at $Proxy2.storeUser(Unknown Source) at org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624) at org.jboss.ejb.Container.invoke(Container.java:873) at sun.reflect.GeneratedMethodAccessor315.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) 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:644) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:805) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:406) at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261) at sun.rmi.transport.Transport$1.run(Transport
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Applying AOP with a Web app
I am pretty new to this, but here is what I would like to do. I have a web app distributed as a *.war file. This file contains a bunch of servlets, some filters, and such. I would like to (1) run this app withing a servlet container and (2) instrument some of the web app's methods to collect statistics of various sorts. Is this possible with JBoss/JBoss AOP? What steps are involved? Could you please point me at some documentaiton or anything at all that would allow me to get the basics working? Thanks. -Ben View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872949#3872949 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872949 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (HIBERNATE-13) testEjbInterception Unit Test failure
testEjbInterception Unit Test failure - Key: HIBERNATE-13 URL: http://jira.jboss.com/jira/browse/HIBERNATE-13 Project: Hibernate Type: Bug Environment: win xp sp2 Reporter: Pushkala Iyer Assigned to: Gavin King Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase Test : testEjbInterception Stack Trace: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:534) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) at $Proxy2.storeUser(Unknown Source) at org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624) at org.jboss.ejb.Container.invoke(Container.java:873) at sun.reflect.GeneratedMethodAccessor315.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) 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:644) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:805) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:406) at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261) at sun.rmi.transport.Transport$1.run(Transport.java:148
[JBoss-dev] [Design of Messaging on JBoss (Messaging/JBoss)] - ClosedInterceptor and HierarchyInterceptor
Hi All- I've implemented the ClosedInterceptor and new HierarchyInterceptor and added a set of tests to Connection Test to test this plus some other Connection related tests. It all seems to be working. I can send a patch now if you like, or I can wait until I've done the next task. There is one omission for now: The hierarchy interceptor does not maintain MessageConsumers. This is because there is currently no ConsumerDelegate class (the class returned from ServerSessionDelegate is a Consumer). Any proxy that's closed by the ClosedInterceptor needs to implement close() and closing() which the Consumer class doesn't. I could add a ConsumerDelegate class to make it more symmetrical but not sure it it's worth it right now or fits in with the grander design. For the next task, I was thinking of looking at JBossSession. WDYT? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872941#3872941 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872941 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.932 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050406140852Lbuild.932 BUILD COMPLETE - build.932Date of build: 04/06/2005 14:08:52Time to build: 37 minutes 9 secondsLast changed: 04/06/2005 13:43:51Last log entry: fix logging Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (11)1.12modifiedanddmanagement/src/main/org/jboss/management/j2ee/JTAResource.javafix logging1.12modifiedanddmanagement/src/main/org/jboss/management/j2ee/RMI_IIOPResource.javafix logging1.11modifiedanddmanagement/src/main/org/jboss/management/j2ee/URLResource.javafix logging1.21modifiedanddaspects/src/main/org/jboss/aop/deployment/AspectDeployer.javafix logging1.18modifiedanddconsole/src/main/org/jboss/console/twiddle/Twiddle.javafix logging1.5modifiedanddmedia/src/main/org/jboss/media/engine/MediaEngineDeployer.javafix logging1.8modifiedanddmedia/src/main/org/jboss/media/entity/MediaEntityBean.javafix logging1.1addedosdchicagowebservice/test/java/org/jboss/test/ws/tools/sourcecomp/XMLCompareTestCase.javaTestcase that tests XMLUnit 's capability to do XML file comparison1.17modifiedosdchicagotools/etc/buildmagic/libraries.xmlAdd xmlunit from sourceforge that gives the capability to compare twom xml files1.60modifiedosdchicagotools/etc/buildmagic/libraries.entAdd xmlunit from sourceforge that gives the capability to compare twom xml files1.37modifiedosdchicagowebservice/test/build.xmlAdd xmlunit lib as we need a mechanism to compare two xml files.
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1337) Thread Pool improvements on the server
[ http://jira.jboss.com/jira/browse/JBAS-1337?page=history ] Ivelin Ivanov updated JBAS-1337: Original Estimate: 864000 (was: 60) Remaining Estimate: 864000 (was: 60) > Thread Pool improvements on the server > -- > > Key: JBAS-1337 > URL: http://jira.jboss.com/jira/browse/JBAS-1337 > Project: JBoss Application Server > Type: Task > Components: JMS service > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Adrian Brock > > Original Estimate: 6 weeks > Remaining: 6 weeks > > There are a number of different components on the server that use thread > pools. > 1) Invocation Layers > 2) Client Consumer for delivering messages > 3) Scheduled delivery/message expiration > These need to be combined to share threads and minimize context switching > where possible. > The thread pool should be based on the BasicThreadPool from jboss-common -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1337) Thread Pool improvements on the server
[ http://jira.jboss.com/jira/browse/JBAS-1337?page=history ] Ivelin Ivanov updated JBAS-1337: Description: There are a number of different components on the server that use thread pools. 1) Invocation Layers 2) Client Consumer for delivering messages 3) Scheduled delivery/message expiration These need to be combined to share threads and minimize context switching where possible. The thread pool should be based on the BasicThreadPool from jboss-common was: There are a number of different components on the server that use thread pools. 1) Invocation Layers 2) Client Consumer for delivering messages 3) Scheduled delivery/message expiration These need to be combined to share threads and minimize context switching where possible. The thread pool should be based on the BasicThreadPool from jboss-common Environment: Original Estimate: 60 Remaining Estimate: 60 > Thread Pool improvements on the server > -- > > Key: JBAS-1337 > URL: http://jira.jboss.com/jira/browse/JBAS-1337 > Project: JBoss Application Server > Type: Task > Components: JMS service > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Adrian Brock > > Original Estimate: 1 minute > Remaining: 1 minute > > There are a number of different components on the server that use thread > pools. > 1) Invocation Layers > 2) Client Consumer for delivering messages > 3) Scheduled delivery/message expiration > These need to be combined to share threads and minimize context switching > where possible. > The thread pool should be based on the BasicThreadPool from jboss-common -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.477 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050406113907Lbuild.477 BUILD COMPLETE - build.477Date of build: 04/06/2005 11:39:07Time to build: 76 minutes 55 secondsLast changed: 04/06/2005 11:26:23Last log entry: Remove the unused examples Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (4)1.1.30.1deletedstarksmmessaging/src/examples/TestSelectorParser.javaRemove the unused examples1.1.26.1deletedstarksmcluster/src/tests/slsb.javaRemove the unused tests dir and junit refs from the build.xml1.1.26.1deletedstarksmcluster/src/tests/jnditester.javaRemove the unused tests dir and junit refs from the build.xml1.1.10.1deletedstarksmcluster/src/tests/aop/cluster/build.xmlRemove the unused tests dir and junit refs from the build.xml
[JBoss-dev] [Design of JBoss Build System] - Re: New Build - Standalone module - multiple builds
Ok, here is the plan for the standalone remoting build: 1. Implement the export/import funcationality described above. 2. Add remoting's thirdparty deps to cruisecontrol.jboss.com/repository 3. Create a standalone remoting cvs alias which includes remoting and tools (for jbossbuild) 4. Create a release.xml in the jboss-remoting module which describes the release structure of remoting. This will allow Tom to create a standalone release of remoting. I think all of this will take about a week. This doesn't address the issue of integrating the remoting jar back into head. As far as I can tell, this will have to wait until the new build is complete in head and is downloading dependencies. This looks like the beginning of May to me (milestone-3). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872913#3872913 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872913 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Eclipse IDE (dev)] - Re: JBossIDE 1.5M1 + Eclipse3.1M6
no we hope to get a jbosside out that works with M6 but since we are also cleaning up and migrating to use eclipse WTP i cannot promise when... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872909#3872909 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872909 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Eclipse IDE (dev)] - Re: JBossIDE 1.5M1 + Eclipse3.1M6
So we're going to have to wait until M7 for a new JBossIDE? It's frustrating that the edge is where all the latest plugins seem to be and 3.0 has performance issues (or doesn't support the plugins I'd like to play with). Sigh, I'm looking forward to a stable 3.1, feels like it's been forever in coming. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872905#3872905 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872905 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1639) Integrate Critical JBWS bug fixes
[ http://jira.jboss.com/jira/browse/JBAS-1639?page=history ] Jason T. Greene resolved JBAS-1639: --- Resolution: Done All critical bugs resolved. Ready for 4.0.2. > Integrate Critical JBWS bug fixes > - > > Key: JBAS-1639 > URL: http://jira.jboss.com/jira/browse/JBAS-1639 > Project: JBoss Application Server > Type: Bug > Components: Web Services service > Reporter: Scott M Stark > Assignee: Thomas Diesler > Priority: Critical > Fix For: JBossAS-4.0.2 Final > > > This issue links to the outstanding JBWS project issues that need to be > included into JBAS 4.0.2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0-jdk-matrix build.122 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050406095712Lbuild.122 BUILD COMPLETE - build.122Date of build: 04/06/2005 09:57:12Time to build: 56 minutes 39 secondsLast changed: 04/05/2005 23:07:59Last log entry: Preserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-157 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (55)1.13.4.4modifiednihilitywebservice/src/resources/META-INF/jboss-service.xmlPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.18.2.13modifiednihilitywebservice/src/main/org/jboss/webservice/ServiceDeployer.javaPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.19.4.4modifiednihilitywebservice/src/main/org/jboss/webservice/metadata/WebserviceDescriptionMetaData.javaPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.1.2.2modifiednihilitytestsuite/src/resources/webservice/wsdlimport/absolute/WEB-INF/wsdl/Hello.wsdlPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.1.1.1.4.3modifiednihilitytestsuite/src/resources/webservice/wsdlimport/simplefile/SimpleFile.wsdlPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.35.4.12modifiednihilitywebservice/src/main/org/jboss/webservice/AxisService.javaPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.1.2.2modifiednihilitytestsuite/src/resources/webservice/jbws153/WEB-INF/wsdl/OrderSOAP.wsdlPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.1.1.1.4.2modifiednihilitytestsuite/src/resources/webservice/ws4eesimple/META-INF/wsdl/Hello.wsdlPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.1.2.1modifiednihilitytestsuite/src/resources/webservice/addressrewrite/WEB-INF/HelloMapping.xmlPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.1.2.1modifiednihilitytestsuite/src/resources/webservice/addressrewrite/WEB-INF/web.xmlPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-1571.1.2.1modifiednihilitytestsuite/src/resources/webservice/addressrewrite/WEB-INF/webservices.xmlPreserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS
[JBoss-dev] [JBoss JIRA] Resolved: (JBPTL-34) JSR-168 API javadoc
[ http://jira.jboss.com/jira/browse/JBPTL-34?page=history ] Julien Viet resolved JBPTL-34: -- Resolution: Done > JSR-168 API javadoc > --- > > Key: JBPTL-34 > URL: http://jira.jboss.com/jira/browse/JBPTL-34 > Project: JBoss Portal > Type: Task > Reporter: Julien Viet > Assignee: Julien Viet > Priority: Minor > Fix For: 2.0 RC > > > Add the javadoc to the javax.portlet package -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1602) Can't use container level taglibs
[
http://jira.jboss.com/jira/browse/JBAS-1602?page=comments#action_12316718 ]
Scott M Stark commented on JBAS-1602:
-
Yes, please commit the patched jar.
> Can't use container level taglibs
> -
>
> Key: JBAS-1602
> URL: http://jira.jboss.com/jira/browse/JBAS-1602
> Project: JBoss Application Server
> Type: Bug
> Components: Web (Tomcat) service
> Reporter: Stan Silvert
> Assignee: Scott M Stark
> Priority: Critical
> Fix For: JBossAS-4.0.2 Final
> Attachments: EmbeddedServletOptions.java, TldLocationsCache.java
>
>
> JBoss/Tomcat needs a way to install tag libraries globally so they are
> available to all web applications. This functionality is mentioned in the
> JSP 2.0 spec section 7.3.5. In Tomcat standalone, you can do this, but it
> doesn?t work in JBoss/Tomcat.
> The way this works is that the Jasper TldLocationsCache ?Scans all JARs
> accessible to the webapp's classloader and its parent classloaders for TLDs.?
> If I put my jar into Tomcat standalone?s common/lib directory then the tag
> library will be shared across all web apps. I?ve tried putting the jar in
> several ?well known? locations in JBoss/Tomcat and nothing seems to work.
> For Reference, I?ve attached the TldLocationsCache source code from Tomcat
> 5.5.8.
> Concerning TldLocationsCache, Scott Stark says:
> "This class is useless for non-URLClassLoaders and URLClassLoaders that do
> not expose their classpath via getURLs which is what we currently do because
> of an old bad behavior with annotated codebases of rmi classes. "
> Remy Maucherat offered this as a possible solution:
> Would it be possible to have the ENCLoader facade return more interesting
> things ?
>/**
> * A trival extension of URLClassLoader that uses an empty URL[] as its
> * classpath so that all work is delegated to its parent.
> */
>static class ENCLoader extends URLClassLoader
>{
> private URL[] urllist = new URL[0];
> ENCLoader(ClassLoader parent)
> {
> super(new URL[0], parent);
> }
> void addURLInternal(URL url)
> {
> URL[] result = new URL[urllist.length + 1];
> for (int i = 0; i < urllist.length; i++)
> result[i] = urllist[i];
> result[urllist.length] = url;
> urllist = result;
> }
> public URL[] getURLs()
> {
> return urllist;
> }
>}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JGRP-50) Release 2.2.8 final
Release 2.2.8 final --- Key: JGRP-50 URL: http://jira.jboss.com/jira/browse/JGRP-50 Project: JGroups Type: Task Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.2.8 -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-125) Release 1.2.3 final
Release 1.2.3 final --- Key: JBCACHE-125 URL: http://jira.jboss.com/jira/browse/JBCACHE-125 Project: JBoss Cache Type: Task Reporter: Bela Ban Assigned to: Bela Ban Fix For: 1.2.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1284) SOAP SAAJ JBOSS implementation attachments bug
[ http://jira.jboss.com/jira/browse/JBAS-1284?page=history ] Ryan Campbell reassigned JBAS-1284: --- Assign To: Jason T. Greene (was: Jason T. Greene) > SOAP SAAJ JBOSS implementation attachments bug > -- > > Key: JBAS-1284 > URL: http://jira.jboss.com/jira/browse/JBAS-1284 > Project: JBoss Application Server > Type: Feature Request > Components: Web Services service > Versions: JBossAS-4.0.1 Final > Environment: Windows-XP SP2 > Reporter: Frank Balba > Assignee: Jason T. Greene > Priority: Minor > > > Using JBOSS-SAAJ implementation, no attachments could get through within a > SOAP message. > Creating attachments and adding them to a SOAP message will result a fine > SOAP message on the client side however once it arrives to a dedicated > servlet the received attachmentpart returns 'null' for > attachmentPart.getContentType(). Using another SAAJ package (not the one > included with JBOSS 4.0.1) eliminates this problem. > Frank -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBPORTAL-71) Last login date
[ http://jira.jboss.com/jira/browse/JBPORTAL-71?page=history ] Julien Viet resolved JBPORTAL-71: - Resolution: Done > Last login date > --- > > Key: JBPORTAL-71 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-71 > Project: JBoss Portal > Type: Sub-task > Components: Portal Core > Versions: 2.0 Alpha > Reporter: Thomas Heute > Assignee: Julien Viet > Fix For: 2.0 RC > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPORTAL-233) User metadata
User metadata - Key: JBPORTAL-233 URL: http://jira.jboss.com/jira/browse/JBPORTAL-233 Project: JBoss Portal Type: Task Reporter: Julien Viet The portal defines itw own way to manipulate user. The current interface definition is capable to manipulate users. In particular it is possible to use user properties in a dynamic way. However it is not possible to know what properties are supported. Therefore we need to add metadata to the module in order to know informations about the properties available and supported by the portal. -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBIDE-124) Hotdeployment fails with StringIndexOutOfBounds Exception
[ http://jira.jboss.com/jira/browse/JBIDE-124?page=comments#action_12316715 ] Jasper Kalkers commented on JBIDE-124: -- I have had this problem too. I noticed my war-package contained a directory starting with a slash. I removed the slash in the packaging configuration and ran the packaging task again. Deployment was successful after that. > Hotdeployment fails with StringIndexOutOfBounds Exception > - > > Key: JBIDE-124 > URL: http://jira.jboss.com/jira/browse/JBIDE-124 > Project: JBoss IDE > Type: Bug > Environment: Windows XP, Sun JDK 1.4.2_05 > Reporter: larswunderlich > > > Deploying the sample application as described in JBoss IDE documentation > 1.3.0 with 1.4.0 plugin fails with the following error. This happens in every > configuration (default as well as all). I don't know how to solve the bug, > the exception does not provide any further information what's going on. > The EAR file structure, as well as the WAR and EJB structure seems just fine. > 18:43:28,986 INFO [Server] JBoss (MX MicroKernel) [4.0.1 (build: > CVSTag=JBoss_4_0_1 date=200412230944)] Started in 22s:753ms > 18:43:48,574 INFO [EARDeployer] Init J2EE application: > file:/D:/jboss-4.0.1/server/default/deploy/FiboApp.ear > 18:43:48,824 ERROR [Tomcat5] Problem in init > java.lang.StringIndexOutOfBoundsException: String index out of range: 0 > at java.lang.String.charAt(String.java:444) > at org.jboss.util.file.JarUtils.unjar(JarUtils.java:252) > at > org.jboss.web.AbstractWebContainer.init(AbstractWebContainer.java:262) > at org.jboss.deployment.MainDeployer.init(MainDeployer.java:828) > at org.jboss.deployment.MainDeployer.init(MainDeployer.java:848) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:765) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) > at sun.reflect.GeneratedMethodAccessor46.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > 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$ScannerThread.loop(AbstractDeploymentScanner.java:215) > at > org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:194) > 18:43:48,844 ERROR [MainDeployer] Could not initialise deployment: > file:/D:/jboss-4.0.1/server/default/deploy/FiboApp.ear > org.jboss.deployment.DeploymentException: String index out of range: 0; - > nested throwable: (java.lang.StringIndexOutOfBoundsException: String index > out of range: 0) > at > org.jboss.web.AbstractWebContainer.init(AbstractWebContainer.java:312) > at org.jboss.deployment.MainDeployer.init(MainDeployer.java:828) > at org.jboss.deployment.MainDeployer.init(MainDeployer.java:848) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:765) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) > at sun.reflect.GeneratedMethodAccessor46.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > 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.Invo
[JBoss-dev] [TODO -- DEVELOPMENT] - Re: Want to contribute?
did not check the date however :) ... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872862#3872862 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872862 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [TODO -- DEVELOPMENT] - Re: Want to contribute?
Will test the test suite too ... if that is all right... and still needed Thanks Shankar View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872861#3872861 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872861 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JTA and JTS on JBoss] - Integration JOTM with JBoss
I've followed the documentation to attach a foreign TM (JOTM) to JBoss but with not that much luck: Here are the steps 1. Created MBean --> JOTMTransactionManagerService extends ServiceMBeanSupport implements ObjectFactory, | JOTMTransactionManagerServiceMBean 2. In the startService, : i. Created respective objects ts = new Jotm(true, true);// TMService | tm = ts.getTransactionManager(); //TransactionManager | ut = ts.getUserTransaction(); // user tx | ii. Bound the TPCImpl and TPCFactory along wiht TM | bindRef(JNDI_NAME,"org.objectweb.transaction.jta.TransactionManager"); | bindRef(JNDI_IMPORTER,"com.mizuho.london.cmi2.framework.transaction.TPCImporter"); | bindRef(JNDI_EXPORTER,"com.mizuho.london.cmi2.framework.transaction.TPCFactory"); | (Note: TPCImporter and TPCFactory implement Jboss's interfaces with null return implementations. No specific code in there yet.) 3. in the conf/jboss-service.xml file, I commented the in memory TM and added the following code for my JOTM Tx Manager. | 300 | true | jboss:service=XidFactory | | When the server started, it's complaining about JDBCStateManager: 2005-04-06 13:47:41,492 TRACE [framework.transaction.JOTMTransactionManagerService] Constructing | 2005-04-06 13:47:41,570 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true | 2005-04-06 13:47:41,570 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false | 2005-04-06 13:47:41,570 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true | 2005-04-06 13:47:41,570 ERROR [org.jboss.mq.sm.jdbc.JDBCStateManager] Starting failed jboss.mq:service=StateManager | org.jboss.mq.SpyJMSException: Error creating connection to the database.; - nested throwable: (java.lang.NullPointerException) | at org.jboss.mq.sm.jdbc.JDBCStateManager$JDBCSession.(JDBCStateManager.java:542) | at org.jboss.mq.sm.jdbc.JDBCStateManager.initDB(JDBCStateManager.java:432) | at org.jboss.mq.sm.jdbc.JDBCStateManager.startService(JDBCStateManager.java:399) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java | etc etc.. It looks like the in the JDBCStateManager code where it calls the begin method on tm (tm.begin()), the tm is null. I'm not quite sure though. If I'm doing wrongly, can anyone advise me? If not, can anyone tell me what's going on? (note that the I've serialised JOTM's TransactionFactoryImpl and bound it to JNDI) I could see the TransactionManager and TPC stull bound royally to the JNDI though! Thanks /M View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872858#3872858 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872858 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1602) Can't use container level taglibs
[
http://jira.jboss.com/jira/browse/JBAS-1602?page=comments#action_12316714 ]
Remy Maucherat commented on JBAS-1602:
--
I have applied the patch allowing configuring the servlet options. However, I
don't recommend upgrading the Tomcat binary to one built from CVS, due to
current instability after the inclusion of some risky changes (including among
other things Java 5 compatibility for JSPs).
If this feature is needed for JBoss 4.0.2, I can provide a patched Jasper
binary based on Tomcat 5.5.9.
> Can't use container level taglibs
> -
>
> Key: JBAS-1602
> URL: http://jira.jboss.com/jira/browse/JBAS-1602
> Project: JBoss Application Server
> Type: Bug
> Components: Web (Tomcat) service
> Reporter: Stan Silvert
> Assignee: Scott M Stark
> Priority: Critical
> Fix For: JBossAS-4.0.2 Final
> Attachments: EmbeddedServletOptions.java, TldLocationsCache.java
>
>
> JBoss/Tomcat needs a way to install tag libraries globally so they are
> available to all web applications. This functionality is mentioned in the
> JSP 2.0 spec section 7.3.5. In Tomcat standalone, you can do this, but it
> doesn?t work in JBoss/Tomcat.
> The way this works is that the Jasper TldLocationsCache ?Scans all JARs
> accessible to the webapp's classloader and its parent classloaders for TLDs.?
> If I put my jar into Tomcat standalone?s common/lib directory then the tag
> library will be shared across all web apps. I?ve tried putting the jar in
> several ?well known? locations in JBoss/Tomcat and nothing seems to work.
> For Reference, I?ve attached the TldLocationsCache source code from Tomcat
> 5.5.8.
> Concerning TldLocationsCache, Scott Stark says:
> "This class is useless for non-URLClassLoaders and URLClassLoaders that do
> not expose their classpath via getURLs which is what we currently do because
> of an old bad behavior with annotated codebases of rmi classes. "
> Remy Maucherat offered this as a possible solution:
> Would it be possible to have the ENCLoader facade return more interesting
> things ?
>/**
> * A trival extension of URLClassLoader that uses an empty URL[] as its
> * classpath so that all work is delegated to its parent.
> */
>static class ENCLoader extends URLClassLoader
>{
> private URL[] urllist = new URL[0];
> ENCLoader(ClassLoader parent)
> {
> super(new URL[0], parent);
> }
> void addURLInternal(URL url)
> {
> URL[] result = new URL[urllist.length + 1];
> for (int i = 0; i < urllist.length; i++)
> result[i] = urllist[i];
> result[urllist.length] = url;
> urllist = result;
> }
> public URL[] getURLs()
> {
> return urllist;
> }
>}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: jboss-4.0-testsuite Build Failed
I don't understand the error relative to the subject. This says its a 4.0 branch testsuite build, but clearly this is a build of the jboss-head module. The errors are in the build of the hibernate deployer module: /scratch/cruisecontrol/checkout/jboss-head/hibernate/src/main/org/jboss/hibernate/cache/DeployedTreeCacheProvider.java:59: cannot resolve symbol symbol : class CacheException location: class org.jboss.hibernate.cache.DeployedTreeCacheProvider throw new CacheException( "Unable to locate TreeCache MBean under object name [" + configObjectName + "]" ); ^ /scratch/cruisecontrol/checkout/jboss-head/hibernate/src/main/org/jboss/hibernate/cache/DeployedTreeCacheProvider.java:85: package org.hibernate.cache does not exist return new org.hibernate.cache.TreeCache( deployedTreeCache, name ); ^ /scratch/cruisecontrol/checkout/jboss-head/hibernate/src/main/org/jboss/hibernate/jmx/Hibernate.java:632: cannot resolve symbol symbol : variable NAMESPACE_PROP_NAME location: class org.jboss.hibernate.cache.DeployedTreeCacheProvider setUnlessNull(props, DeployedTreeCacheProvider.NAMESPACE_PROP_NAME, deployedTreeCacheJndiName); From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 06, 2005 12:43 AMTo: jboss-development@lists.sourceforge.net; QASubject: jboss-4.0-testsuite Build FailedImportance: High View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050406015757 BUILD FAILED Ant 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: 04/06/2005 01:57:57 Time to build: 91 minutes 15 seconds Last changed: 04/05/2005 23:07:59 Last log entry: Preserve the wsdl specified soap:address if it is a valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean which can be usedto switch to the previous behavior of always rewritingFix several tests that had invalid urlsAdd a addressrewrite test to verify new behaviorFix JBWS-157 Unit Tests: (0) Total Errors and Failures: (0)
[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-124) Concurrent access problem in Node
[ http://jira.jboss.com/jira/browse/JBCACHE-124?page=history ] Bela Ban resolved JBCACHE-124: -- Resolution: Done Made it a ConcurrentReaderHashMap > Concurrent access problem in Node > - > > Key: JBCACHE-124 > URL: http://jira.jboss.com/jira/browse/JBCACHE-124 > Project: JBoss Cache > Type: Bug > Versions: 1.2.1 > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.2.3 > > > Problem: Node.data is a HashMap, not a ConcurrentReaderHashMap -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-124) Concurrent access problem in Node
Concurrent access problem in Node - Key: JBCACHE-124 URL: http://jira.jboss.com/jira/browse/JBCACHE-124 Project: JBoss Cache Type: Bug Versions: 1.2.1 Reporter: Bela Ban Assigned to: Bela Ban Fix For: 1.2.3 Problem: Node.data is a HashMap, not a ConcurrentReaderHashMap -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPM-109) add a document variable type
add a document variable type Key: JBPM-109 URL: http://jira.jboss.com/jira/browse/JBPM-109 Project: JBoss jBPM Type: Feature Request Components: Core Engine Reporter: Tom Baeyens Assigned to: Tom Baeyens the document variable type should store the binary form of a document (in a bytearray) combined with a version and history information. -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPM-108) configurable notifications
configurable notifications -- Key: JBPM-108 URL: http://jira.jboss.com/jira/browse/JBPM-108 Project: JBoss jBPM Type: Feature Request Components: Core Engine Reporter: Tom Baeyens Assigned to: Tom Baeyens Priority: Minor add preference information in the identity model about how the user wants to be notified (email, sms, IM or a combination) then we can write a NotificationActionHandler that uses that information to send out notifications. some form of templating must be provided. meaning that it must be possible to use process variables in the message. but this should be kept as simple as possible e.g. with a set of default formatters. maybe the locale should also be added to the user. -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Eclipse IDE (dev)] - Re: JBossIDE 1.5M1 + Eclipse3.1M6
yes we don't try to say anything otherwise ;) M4->M5 (they changed some classloader mechanisms that made e.g. xerces usage kinda impossible) M5->M6 (they undoed the M4->M5 and they changed how codecompletion works for java types) ...so yes we are paying for living on the edge ;) (but they promise that it will be better in the next release since that is an API freeze ,) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872823#3872823 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872823 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-51) Create standalone CVS version of JBossCache
[ http://jira.jboss.com/jira/browse/JBCACHE-51?page=history ] Bela Ban resolved JBCACHE-51: - Resolution: Done New module is "JBossCache", check out: cvs co JBossCache > Create standalone CVS version of JBossCache > --- > > Key: JBCACHE-51 > URL: http://jira.jboss.com/jira/browse/JBCACHE-51 > Project: JBoss Cache > Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.2.3 > > Original Estimate: 1 week > Remaining: 1 week > > Goals: > - Standalone CVS version of JBossCache --> extract code into a different > location in the src > tree > - Create the integration code inside the JBossAS src tree -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBCACHE-123) Get rid of JBoss-dependent libs
[ http://jira.jboss.com/jira/browse/JBCACHE-123?page=history ] Bela Ban closed JBCACHE-123: Resolution: Done This task will be done later (in 1.3, when we convert to interfaces) > Get rid of JBoss-dependent libs > --- > > Key: JBCACHE-123 > URL: http://jira.jboss.com/jira/browse/JBCACHE-123 > Project: JBoss Cache > Type: Sub-task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.2.3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-122) Convert JBoss Logger to commons-logging
[ http://jira.jboss.com/jira/browse/JBCACHE-122?page=history ] Bela Ban resolved JBCACHE-122: -- Resolution: Done > Convert JBoss Logger to commons-logging > --- > > Key: JBCACHE-122 > URL: http://jira.jboss.com/jira/browse/JBCACHE-122 > Project: JBoss Cache > Type: Sub-task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.2.3 > > > get rid of jboss-common -- 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=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
