Re: Basic cxf-tomcat-example.html: need explaination. 1M Thanks.

2011-11-06 Thread Willem Jiang

On 11/7/11 1:26 AM, H Paul wrote:

In this example  http://camel.apache.org/cxf-tomcat-example.html
http://camel.apache.org/cxf-tomcat-example.html

No problem with web.xml
No problem with CamelRoute.java

Not sure How thing tie together?

camel-config.xml

This file is just create a camel context which loads the CamelRoute.


and
http://localhost:8080/camel-example-cxf-tomcat-2.8.1/webservices/incident?wsdl
As Glen said 
"cxf:/incident?serviceClass=org.apache.camel.example.cxf.incident.IncidentService
" is the magic, you can also cxfEndpoint to define the CXF endpoint as 
you do with jaxws:endpoint in CXF.




how incident (incident?wsdl) come into the picture? (some thing is implicit
that I can not see or read properly)

(I can see the tie in the Apache CXF web service without using Camel)


Yes, it is exactly.


--
View this message in context: 
http://camel.465427.n5.nabble.com/Basic-cxf-tomcat-example-html-need-explaination-1M-Thanks-tp4969057p4969057.html
Sent from the Camel - Users mailing list archive at Nabble.com.




--
Willem
--
FuseSource
Web: http://www.fusesource.com
Blog:http://willemjiang.blogspot.com (English)
 http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang


Re: Basic cxf-tomcat-example.html: need explaination. 1M Thanks.

2011-11-06 Thread Glen Mazza
Hi, for a CXF-only web service hosted on Tomcat (sans Camel), Note #2 
here: http://www.jroller.com/gmazza/entry/web_service_tutorial#notes 
shows how the URL is constructed.  With Camel, (A), (B), and (C) are the 
same, but for (D), one of the links that you gave 
(http://camel.apache.org/cxf-tomcat-example.html) has this text:


"All we have to do is to define an endpoint uri in the format

cxf:/incident?serviceClass=org.apache.camel.example.cxf.incident.IncidentService

This means Camel will expose the web service using the relative address 
/incident..."


So if you look in CamelRoute.java, that from(uri) statement is what 
causes "/incident" to be used as part of the URL string.  "?wsdl" is the 
JAX-WS default, the URL to access to obtain a WSDL from the web service 
provider.


HTH,
Glen


On 11/06/2011 12:26 PM, H Paul wrote:

In this example  http://camel.apache.org/cxf-tomcat-example.html
http://camel.apache.org/cxf-tomcat-example.html

No problem with web.xml
No problem with CamelRoute.java

Not sure How thing tie together?

camel-config.xml
and
http://localhost:8080/camel-example-cxf-tomcat-2.8.1/webservices/incident?wsdl

how incident (incident?wsdl) come into the picture? (some thing is implicit
that I can not see or read properly)

(I can see the tie in the Apache CXF web service without using Camel)

--
View this message in context: 
http://camel.465427.n5.nabble.com/Basic-cxf-tomcat-example-html-need-explaination-1M-Thanks-tp4969057p4969057.html
Sent from the Camel - Users mailing list archive at Nabble.com.



--
Glen Mazza
Talend - http://www.talend.com/apache
Blog - http://www.jroller.com/gmazza/
Twitter - glenmazza



Basic cxf-tomcat-example.html: need explaination. 1M Thanks.

2011-11-06 Thread H Paul
In this example  http://camel.apache.org/cxf-tomcat-example.html
http://camel.apache.org/cxf-tomcat-example.html 

No problem with web.xml
No problem with CamelRoute.java

Not sure How thing tie together?

camel-config.xml
and
http://localhost:8080/camel-example-cxf-tomcat-2.8.1/webservices/incident?wsdl

how incident (incident?wsdl) come into the picture? (some thing is implicit
that I can not see or read properly)

(I can see the tie in the Apache CXF web service without using Camel)

--
View this message in context: 
http://camel.465427.n5.nabble.com/Basic-cxf-tomcat-example-html-need-explaination-1M-Thanks-tp4969057p4969057.html
Sent from the Camel - Users mailing list archive at Nabble.com.