[ 
https://wso2.org/jira/browse/ESBJAVA-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19699#action_19699
 ] 

Saliya Ekanayake commented on ESBJAVA-573:
------------------------------------------

Hi all,

ESB 1.7.1 ships Axis2 1.4. The issue of not generating the JMS endpoint in the 
WSDL is an error of Axis2 1.4. See 
https://issues.apache.org/jira/browse/AXIS2-3961

I tested with Axis2 1.4, 1.4.1, and the SNAPSHOT yet, only 1.4 gives this 
error. The next ESB release will be based on a version newer than 1.4 for 
Axis2. I came up with a work around for this but at the moment I have done some 
other changes to the configurations which has broken my work around. I will 
give the steps to setup a the samples with what you want ASAP.

Thanks,
Saliya

> Sample WSDL SimpleStockQuoteService doesnt display JMS endpoint - ESB v1.7
> --------------------------------------------------------------------------
>
>                 Key: ESBJAVA-573
>                 URL: https://wso2.org/jira/browse/ESBJAVA-573
>             Project: WSO2 ESB
>          Issue Type: Bug
>          Components: Samples, Sequences Management
>    Affects Versions: 1.7.1
>         Environment: Win XP, Apache ActiveMQ 5.1.0, Axis2, WSO2 ESB v1.7.1
>            Reporter: Ravi Banavara
>            Assignee: Ruwan Linton
>         Attachments: SnapshotsAndLogs.zip
>
>
> A problem I am facing is that the WSDL for the service 
> "SimpleStockQuoteService" is not displaying the JMS endpoint. I am following 
> the instructions exactly like in your tutorial. All components start up ok, 
> and I can see new queue "SimpleStockQuoteService" also being created by Axis. 
> After building the service, I try to browse the WSDL for the JMS endpoint, 
> and it is not available.
> PS:
> When I start up Axis 2 (after uncommenting the "JMS" section), I do observe 
> that Axis does not recognize the SimpleStockQuoteService queue (even though 
> it exists) and it seems to be creating the queue afresh.
> The example runs successfully when I use ESB version v1.6 and Active MQ 
> version 4.1.1 (per tutorial). But the example does not run successfully when 
> I use ESB version v1.7.1 and ActiveMQ version 5.1.0. I am stuck because the 
> WSDL does not show me the JMS address location, which I need to create the 
> endpoint on the ESB...That is the first difficulty.
> I did browse through the JMX console. I have attached the snapshot of the AMQ 
> JMX console.
> Here are some observations:
> 1. When I start up the Axis2 server bundled with ESB v1.7.1, I can see the 
> jms-listener for the SimpleStockQuoteService. The address is also correct. 
> But WSDL doesnt show the JMS address. See jmx console snapshot for 
> "apache-synapse" when running esbv1.7.1
> 2. When I start up the Axis2 server bundled with ESB v1.6, and open the JMX 
> console, I dont see the "jms-listener" (see snapshot). But I can see the JMS 
> address in the WSDL. See jmx console snapshot for "apache-synapse" when 
> running esbv1.6
> The issue seems to be with Axis2 creating the runtime WSDL.
> Also, I tried one more thing. I started up AMQ v1.5 and Axis2Server bundled 
> with esb1.6 and took the JMS address shown in the WSDL. Then I started up ESB 
> v1.7.1, and tried to create an endpoint. It errored out saying the following:
> [com.ctc.wstx.exc.WstxLazyException] 
> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '=' (code 
> 61); expected a semi-colon after the reference for entity 
> 'transport.jms.ConnectionFactoryJNDIName' at [row,col {unknown-source}]: 
> [1,1007]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

_______________________________________________
Esb-java-dev mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev

Reply via email to