-
1. Re: Message store implementation class problem
marklittle Mar 22, 2007 6:07 PM (in response to derek.adams)Are you looking at the trunk?
-
2. Re: Message store implementation class problem
kurtstam Mar 22, 2007 6:36 PM (in response to derek.adams)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/product/docs/GettingStarted.odt
Hope that helps.
--Kurt -
3. Re: Message store implementation class problem
derek.adams Mar 22, 2007 6:36 PM (in response to 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.
-
4. Re: Message store implementation class problem
kurtstam Mar 22, 2007 6:44 PM (in response to derek.adams)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/jbossesb-properties.xml
--Kurt -
5. Re: Message store implementation class problem
marklittle Mar 22, 2007 6:48 PM (in response to derek.adams)Looks like Daniel missed something before he left. Can you create a JIRA for this? You should have svn access now, so if you've got a fix ...
-
6. Re: Message store implementation class problem
kurtstam Mar 22, 2007 6:51 PM (in response to derek.adams)I think it may simply be replacing the referenced classes in the jbossesb-properties.xml of our clients. So it may just be a matter of documenting it.
-
7. Re: Message store implementation class problem
marklittle Mar 22, 2007 6:59 PM (in response to derek.adams)Not sure what you mean. The jbossesb-properties.xml file in install/conf talks about org.jboss.soa.esb.persistence.manager.MessageStoreFactoryImpl when that doesn't exist. That's definitely a bug.