[tfennelly]

OK I think I have this sorted out now. Do an update from SVN. There's an additional deployment step in order to work around this issue with JBossWS 2.0.0GA. I've updated the readmes to reflect this + comments re the existing instructions.

[tobysaville]

that looks good Tom, the examples worked for me. I did get the following exception though:

10:19:23,026 WARN [FilterManager] GatewayFilter encountered problem during JDBC config check.
org.jboss.soa.esb.ConfigurationException: Missing or invalid <URL> attribute
 at org.jboss.soa.esb.listeners.ListenerUtil.obtainAtt(ListenerUtil.java:342)
 at org.jboss.internal.soa.esb.message.filter.GatewayFilter.onOutput(GatewayFilter.java:77)
 at org.jboss.soa.esb.filter.FilterManager.doOutputWork(FilterManager.java:81)
 at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doRun(JmsGatewayListener.java:156)
 at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
 at java.lang.Thread.run(Thread.java:595)

also, i had to copy jbossesb-soap.jar from the built version at jbossesb-src\product\build\jbossesb-server-4.2MR2\server\default\deploy\soap.esb

it didnt seem to be deployed as part of the esb build. is this correct or do you think i did something wrong?

also the readme points to the file jbossesb/extras/jaxbintros/jboss-jaxb-intros.jar but this isnt present. Its actually in jbossesb/extras/jaxbintros/target. does this file now get generated as part of the esb build or do you need to include instructions to build it?

thanks again for your help and speeding patch work!

tobes

[tfennelly]

"tobysaville" wrote:
that looks good Tom, the examples worked for me. I did get the following exception though:

10:19:23,026 WARN [FilterManager] GatewayFilter encountered problem during JDBC config check.
org.jboss.soa.esb.ConfigurationException: Missing or invalid <URL> attribute
 at org.jboss.soa.esb.listeners.ListenerUtil.obtainAtt(ListenerUtil.java:342)
 at org.jboss.internal.soa.esb.message.filter.GatewayFilter.onOutput(GatewayFilter.java:77)
 at org.jboss.soa.esb.filter.FilterManager.doOutputWork(FilterManager.java:81)
 at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doRun(JmsGatewayListener.java:156)
 at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
 at java.lang.Thread.run(Thread.java:595)

As far as I can see, this is just noise. I emailed the group about it yesterday and I'll turn it off soon if I don't hear anything more.

"tobysaville" wrote:
also, i had to copy jbossesb-soap.jar from the built version at jbossesb-src\product\build\jbossesb-server-4.2MR2\server\default\deploy\soap.esb

it didnt seem to be deployed as part of the esb build. is this correct or do you think i did something wrong?

OK, I assume you did read the README.txt? If you look at 5.d and 5.e you'll see that you need to patch JBossWS in this way.

"tobysaville" wrote:
also the readme points to the file jbossesb/extras/jaxbintros/jboss-jaxb-intros.jar but this isn't present. Its actually in jbossesb/extras/jaxbintros/target. does this file now get generated as part of the esb build or do you need to include instructions to build it?

OK, it's starting to sound to me like you're not working out of the distro i.e. product/build/jbossesb after running "ant clean dist". If you do this you should see this file in the distro. The READMEs are always worded in the context of the distro i.e. the product/build/jbossesb.

"tobysaville" wrote:
thanks again for your help and speeding patch work!

No probs :-)

[marklittle]

"tfennelly" wrote:

"tobysaville" wrote:
that looks good Tom, the examples worked for me. I did get the following exception though:

10:19:23,026 WARN [FilterManager] GatewayFilter encountered problem during JDBC config check.
org.jboss.soa.esb.ConfigurationException: Missing or invalid <URL> attribute
 at org.jboss.soa.esb.listeners.ListenerUtil.obtainAtt(ListenerUtil.java:342)
 at org.jboss.internal.soa.esb.message.filter.GatewayFilter.onOutput(GatewayFilter.java:77)
 at org.jboss.soa.esb.filter.FilterManager.doOutputWork(FilterManager.java:81)
 at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doRun(JmsGatewayListener.java:156)
 at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
 at java.lang.Thread.run(Thread.java:595)

As far as I can see, this is just noise. I emailed the group about it yesterday and I'll turn it off soon if I don't hear anything more.

I didn't see any email concerning this. There was a JIRA from Kurt ;-)

Anyway, that was fixed last night.

[tobysaville]

Hi Tom,

yeah, i did read the readme and i was aware that i had to copy the soap jar, my question was more about the source location to copy it from - and deciding between the built distribution or the version deployed to my AS (which im working from).

thanks for the clarification on the jaxb jar, i guess i was getting confused with the old instructions.

its all clear to me now.

thanks again!
tobes