Not sure which version of the ESB you're using, but Daniel Bevenius has just added a new quickstart to the SVN trunk that demonstrates how you could do this. I think he had to do something similar to you in that he had to pass the file name instead of a stream (which was a bit of a pain - will be sorted in v4.3 I hope). This quickstart is still a work in progress I think (correct me if I'm wrong Dan). It uses Smooks v1.0, which has added SAX support as well as some new routing features and more...
Please try this stuff out and let us know what you think!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139762#4139762
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139762
I'm currently maintaining a separate assembly for the repackaging of jbossall-client.jar in the EJB3 Installer component, used when the EJB3 Plugin is run.
Much like centralizing the dependencies between AS and AS component consumers, we'll need a similar mechanism defining the makeup of jbossall-client, else consumers fall out of sync.
Two suggestions:
1) We externalize the includes into a separate file
2) We revisit the use of the manifest's Class-Path entry and share a common .mf file
Option 2) is more implementation-independent; Option 1) integrates well with Ant "includesfile".
Defining task is:
http://jira.jboss.com/jira/browse/EJBTHREE-1240
Other ideas?
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139745#4139745
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139745