-
1. Re: Problems with Smooks with new ESB from SVN
tfennelly Apr 15, 2008 10:08 AM (in response to standard)Hi.
Daniel was working on this upgrade so he'll be better able to comment. Just make sure your SVN update was successful. -
2. Re: Problems with Smooks with new ESB from SVN
beve Apr 15, 2008 10:26 AM (in response to standard)Hi Andreas,
I'll take a look... Can you try one of the transformation quickstarts, like transform_XML2XML_date_manipulation, against the server built by running "ant dist".
Regards,
Daniel -
3. Re: Problems with Smooks with new ESB from SVN
standard Apr 15, 2008 10:56 AM (in response to standard)Hi,
just run the quickstart, but seems to have the same problem.
Here is the output:16:51:55,859 INFO [STDOUT] [transform_XML2XML_date_manipulation] Message before transformation: 16:51:55,859 INFO [STDOUT] [<Order orderId="1" orderDate="Wed Nov 15 13:45:28 2006" statusCode="0" netAmount="59.97" totalAmount="64.92" tax="4.95"> <Customer userName="user1" firstName="Harry" lastName="Fletcher" state="SD"/> <OrderLines> <OrderLine position="1" quantity="1"> <Product productId="364" title="The 40-Year-Old Virgin " price="29.98"/> </OrderLine> <OrderLine position="2" quantity="1"> <Product productId="299" title="Pulp Fiction" price="29.99"/> </OrderLine> </OrderLines> </Order> ]. 16:51:55,859 ERROR [STDERR] java.lang.NoSuchMethodError: org.milyn.Smooks.createExecutionContext()Lorg/milyn/container/ExecutionContext; 16:51:55,859 ERROR [STDERR] at org.jboss.soa.esb.actions.converters.SmooksTransformer.process(SmooksTransformer.java:327) 16:51:55,859 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) 16:51:55,859 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:519) 16:51:55,875 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) 16:51:55,875 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) 16:51:55,875 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) 16:51:55,890 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_date_manipulation_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 60d6ff24-d3bc-4139-9961-0ebf66bc0745 RelatesTo: jms:correlationID#60d6ff24-d3bc-4139-9961-0ebf66bc0745 ] org.jboss.soa.esb.actions.ActionProcessingException: Message transformation failed. at org.jboss.soa.esb.actions.converters.SmooksTransformer.process(SmooksTransformer.java:359) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:519) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NoSuchMethodError: org.milyn.Smooks.createExecutionContext()Lorg/milyn/container/ExecutionContext; at org.jboss.soa.esb.actions.converters.SmooksTransformer.process(SmooksTransformer.java:327) ... 5 more 16:51:55,906 WARN [ActionProcessingPipeline] No fault address defined for fault message! To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_date_manipulation_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 60d6ff24-d3bc-4139-9961-0ebf66bc0745 RelatesTo: jms:correlationID#60d6ff24-d3bc-4139-9961-0ebf66bc0745
Regards
Andreas -
4. Re: Problems with Smooks with new ESB from SVN
tfennelly Apr 15, 2008 11:03 AM (in response to standard)After rebuilding the ESB, did you undeploy and redeploy all ESB components to your app server?
-
5. Re: Problems with Smooks with new ESB from SVN
standard Apr 15, 2008 11:20 AM (in response to standard)Hi,
I'm using the standalone ESB-server, so no need to do that, or is there?
I've been running the quickstart on a freshly build ESB-server,
without deploying anything on it first (except the quickstart itself of course, and some jms-queues I'm gonna need later).
Regards
Andreas -
6. Re: Problems with Smooks with new ESB from SVN
tfennelly Apr 15, 2008 11:47 AM (in response to standard)OK... this should work for you then... Daniel might be able to shine some light on it.
-
7. Re: Problems with Smooks with new ESB from SVN
beve Apr 15, 2008 12:06 PM (in response to standard)
I'm using the standalone ESB-server,
So, you are building for the trunk and running the server created by the 'ant dist', which is under build/jbossesb-server-4.2.1GA?
I've tried this and I don't see the error you posted.
The error suggests that deploy/smooks.esb/ has not been updated. Can you check the the smook.esb archive contains milyn-smooks-core-1.0-SNAPSHOT.jar?
Thanks,
Daniel -
8. Re: Problems with Smooks with new ESB from SVN
standard Apr 15, 2008 12:20 PM (in response to standard)Hi,
So, you are building for the trunk and running the server created by the 'ant dist', which is under build/jbossesb-server-4.2.1GA?
Yes.
And smook.esb contains milyn-smooks-core-1.0-SNAPSHOT.jar (also milyn-smooks-core-0.9.jar).
I'm always deleting the whole jbossesb-server-4.2.1GA folder before building the server new,
so there shouldn't be any leftovers.
And I don't get any error messages or something, when updating over svn.
Regards
Andreas -
9. Re: Problems with Smooks with new ESB from SVN
beve Apr 15, 2008 12:28 PM (in response to standard)Ok, milyn-smooks-core-0.9.jar should not be there and is probably what is causing your problems.
It might be that that jar and other old ones are still in your directory structure and getting copied when you build the server.
If you run 'svn st' in product/services/smooks/lib/ext, do you some unversioned jars there?
Regards,
Daniel -
10. Re: Problems with Smooks with new ESB from SVN
standard Apr 15, 2008 2:06 PM (in response to standard)Hi,
no, no unversioned files there, and no smooks 0.9 stuff either.
I found the 0.9 archive in the "product\services\smooks\build" folder,
so I deleted the whole folder and rebuild the whole server.
But no good, I still get the 0.9 smooks archive under deploy/smooks.esb.
The only non "build" folder that still contains the archive is
"product\tools\console\exploded-archives\jboss-esb-console.ear".
Really strange.
When nothing else works,
I think I'll just completely delete the whole server and check it out new.
Regards
Andreas -
11. Re: Problems with Smooks with new ESB from SVN
standard Apr 15, 2008 8:18 PM (in response to standard)Hi,
so I did a completely fresh checkout,
and everything works ok now. :-D
Thanks for the help!
Regards
Andreas