March 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss ESB] - Re: Message store implementation class problem

by kurt.stam＠jboss.com

Yes those classes seem to have changed to support using a datasource. Take a look at the dbstore section in: http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/install/conf/jb... --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030873#4030873 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030873

19 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Message store implementation class problem

by derek.adams

Yep. I am still seeing "org.jboss.soa.esb.persistence.manager.MessageStoreFactoryImpl" as the property value in the trunk and do not see that class there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030869#4030869 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030869

19 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Message store implementation class problem

by kurt.stam＠jboss.com

Yeah, that's what it sounds like to me. On the trunk (as well as the 4.0 MP1 branch) everything is in one jbossesb.sar now, and the configuration files need to be in the sar too. ant dist will build that sar for you. Next you deploy your custom code to it using '.esb' archives. See also http://anonsvn.labs.jboss.com/labs/jbossesb/branches/JBESB_4_0_MP1/produc... Hope that helps. --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030868#4030868 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030868

19 years

1
0
0 / 0

[Design of EJB 3.0] - Re: Funky config needed for extended PersistenceContext repl

by bstansberry＠jboss.com

http://opensource.atlassian.com/projects/hibernate/browse/HHH-2513 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030867#4030867 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030867

19 years

1
0
0 / 0

[Design of EJB 3.0] - JBossDDObjectFactory use of SystemPropertiesService

by bstansberry＠jboss.com

JBossDDObjectFactory.getValue is attempting to invoke on the SystemPropertiesService in order to do system property substitution. This is failing in Branch_4_2: | 2007-03-22 16:42:15,859 WARN [org.jboss.ejb3.metamodel.JBossDDObjectFactory] Unable to look up property service for jboss.xml element partition-name with value ${jboss.partition.name:DefaultPartition}. Caused by class javax.management.InstanceNotFoundException jboss:type=Service,name=SystemProperties is not registered. | This particular example works out OK, because later code meant to handle ${jboss.partition.name:DefaultPartition} as the value for @Clustered(partitionName=...) performs the substitution using org.jboss.util.StringPropertyReplacer. But other property substitutions will fail. So, 1) Any reason JBossDDObjectFactory doesn't just use org.jboss.util.StringPropertyReplacer? It's not clear to me what the benefit of calling on the SystemPropertiesService is. 2) If there's a reason to call the SystemPropertiesService I suppose we should get it to work in Branch_4_2 for 4.2.0.GA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030866#4030866 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030866

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: org.jboss.test.cts.test.MDBUnitTestCase

by scott.stark＠jboss.org

There are also still basic client side errors like the following: | java.lang.ArrayIndexOutOfBoundsException: 0 | at org.jboss.jms.client.container.SessionAspect.handleCreateTextMessage(SessionAspect.java:689) | at org.jboss.jms.client.delegate.JoinPoint_createTextMessage2320081262968295190_9.invokeNext(JoinPoint_createTextMessage2320081262968295190_9.java) | at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:171) | at org.jboss.jms.client.delegate.JoinPoint_createTextMessage2320081262968295190_9.invokeNext(JoinPoint_createTextMessage2320081262968295190_9.java) | at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71) | at org.jboss.jms.client.delegate.JoinPoint_createTextMessage2320081262968295190_9.invokeNext(JoinPoint_createTextMessage2320081262968295190_9.java) | at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107) | at org.jboss.jms.client.delegate.JoinPoint_createTextMessage2320081262968295190_9.invokeNext(JoinPoint_createTextMessage2320081262968295190_9.java) | at org.jboss.jms.client.delegate.JoinPoint_createTextMessage2320081262968295190_9.invokeJoinpoint(JoinPoint_createTextMessage2320081262968295190_9.java) | at org.jboss.jms.client.delegate.ClientSessionDelegate$ClientSessionDelegateAdvisor.createTextMessage2320081262968295190(ClientSessionDelegate$ClientSessionDelegateAdvisor.java) | at org.jboss.jms.client.delegate.ClientSessionDelegate$ClientSessionDelegateInstanceAdvisor.createTextMessage2320081262968295190(ClientSessionDelegate$ClientSessionDelegateInstanceAdvisor.java) | at org.jboss.jms.client.delegate.ClientSessionDelegate.createTextMessage(ClientSessionDelegate.java) | at org.jboss.jms.client.JBossSession.createTextMessage(JBossSession.java:144) | at org.jboss.test.mdb.test.MDBUnitTestCase.testQueue(MDBUnitTestCase.java:136) | 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 junit.framework.TestCase.runTest(TestCase.java:154) | at junit.framework.TestCase.runBare(TestCase.java:127) | at junit.framework.TestResult$1.protect(TestResult.java:106) | at junit.framework.TestResult.runProtected(TestResult.java:124) | at junit.framework.TestResult.run(TestResult.java:109) | at junit.framework.TestCase.run(TestCase.java:118) | at junit.framework.TestSuite.runTest(TestSuite.java:208) | at junit.framework.TestSuite.run(TestSuite.java:203) | at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) | at junit.extensions.TestSetup$1.protect(TestSetup.java:19) | at junit.framework.TestResult.runProtected(TestResult.java:124) | at junit.extensions.TestSetup.run(TestSetup.java:23) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030865#4030865 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030865

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: org.jboss.test.cts.test.MDBUnitTestCase

by scott.stark＠jboss.org

Its at least running, but there are many errors. 3/10 tests in the testcase are passing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030864#4030864 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030864

19 years

1
0
0 / 0

[Design of POJO Server] - Re: trunk testsuite status

by scott.stark＠jboss.org

Can't say I understand what the resulting hprof memory dump is indicating. It shows 311Mb of byte[]/byte[][] instances, but claims these are root objects. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030862#4030862 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030862

19 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Message store implementation class problem

by mark.little＠jboss.com

Are you looking at the trunk? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030857#4030857 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030857

19 years

1
0
0 / 0

[Design of EJB 3.0] - Re: Move *HibernateSession to a Proxy implementation

by epbernard

Where is ExtendedPersistenceContext.getFactory() (return an ManagedEntityManagerFactory) used? EJB 3.0 does not seem to use it and it conflicts with o.h.e.SessionImplementor.getFactory() (returns a SessionFactoryImplementor) Can I get rid of it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030856#4030856 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030856

19 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums March 2007