You are right with the jsr181-component, but I am not using this
component in the LightWeight example.
I copied the fragment configuration from the LightWeight example that
expose the http endpoint.
<sm:activationSpec>
<sm:component>
<http:component>
<http:endpoints>
<http:endpoint service="test:dummy"
endpoint="dummy"
role="consumer"
soap="true"
locationURI="http://localhost:8192/";
defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; />
<http:endpoint service="test:MyProviderService"
endpoint="myProvider"
role="provider"
locationURI="http://localhost:8192/"; />
</http:endpoints>
</http:component>
</sm:component>
</sm:activationSpec>
Thanks,
Robert
[EMAIL PROTECTED] wrote:
If I learned the lesson this is because the jsr181-component cannot be
configured with the servicemix.xml-file, it has to be configured with a
xbean.xml-file. As in the soap-binding example and not as in the
loan-broekr example.
/Tomas
Hi All,
I tried the soap-binding example, but not luck to get the wsdl
externally even when I
modified the bean.xml file to reflect the example in here
(http://www.servicemix.org/servicemix-http) and specified the wsdl files.
Trying the lightweight mode version gives me the below error:
'servicemix ./conf/lw-servicemix.xml'
My ServiceMix is included in the path.
See attachment for configuration file.
How should I run the lw mode?
Thanks,
Robert
---------------------------- output -------------------
INFO - JBIContainer.init(508) | ServiceMix JBI Container
(http://servicemix.org/) name: ServiceMix running version: 3.0-SNAPSHOT
Caught: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'jbi' defined in file
[/home/ralmonte/workspace/lightweight-servicemix/./conf/lw-servicemix.xml]:
Initialization of bean failed; nested exception is
java.lang.IllegalArgumentException: Component name: lw-component is
bound to an object which is not a JBI component, it is of type:
javax.xml.namespace.QName
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'jbi' defined in file
[/home/ralmonte/workspace/lightweight-servicemix/./conf/lw-servicemix.xml]:
Initialization of bean failed; nested exception is
java.lang.IllegalArgumentException: Component name: lw-component is
bound to an object which is not a JBI component, it is of type:
javax.xml.namespace.QName
java.lang.IllegalArgumentException: Component name: lw-component is
bound to an object which is not a JBI component, it is of type:
javax.xml.namespace.QName
at
org.apache.servicemix.jbi.container.JBIContainer.activateComponent(JBIContainer.java:885)
at
org.apache.servicemix.jbi.container.SpringJBIContainer.afterPropertiesSet(SpringJBIContainer.java:67
Guillaume Nodet wrote:
This can be the case if you have specified an enpoint name in the xml,
but
the
generated WSDL has not the same name for the endpoint.
Try removing the endpoint attribute on the jsr181:endpoint.
This may also be the reason why the http component can not find the WSDL.
Cheers,
Guillaume Nodet
On 3/17/06, Tomas Olsson <[EMAIL PROTECTED]> wrote:
Now I saw that I got this warning when starting ServiceMix:
WARN - Jsr181Endpoint.registerService(279) | The endpoint name defined
in the wsdl (slaManagerJBIPort) does not match the endpoint name defined
in the endpoint spec (slaManager). WSDL description may be unusable.
I thought the WSDL was generated based on my input? I have exactly
copied the soap-binding example.
/Tomas
Tomas Olsson wrote:
When I try this:
http://localhost:9080/SLAManagerService//?WSDL
I get (even though I can see that internally there is a WSDL for my
jsr181-component):
------------
HTTP ERROR: 404
No wsdl is available for this service
RequestURI=/SLAManagerService/
/Powered by Jetty:// <http://jetty.mortbay.org>/
------------
Maybe this patch is not in the latest SNAPSHOT?
/Tomas
Guillaume Nodet wrote:
The servicemix-http component is also able to retrieve the wsdl from
the
target JBI endpoint and to expose it (adding binding informations),
if none
is provided with the wsdlResource attribute. Currently, it only adds
the
http or soap address to the port of the service, but this is a
beginning ...
Cheers,
Guillaume Nodet
On 3/17/06, Eric Dofonsou <[EMAIL PROTECTED]> wrote:
I too had the same issue,
Right now I build my own endpoint that wraps around
the current endpoint and provide a mechanism to expose
WSDL when it receives a ?WSDL request on the
servicemix BC. However, the new servicemix-http
component has a way to expose WSDL via a wsdlResource
attribute (see :
http://docs.codehaus.org/display/SM/servicemix-http).
But this implies that you have a static WSDL file as a
spring ressource.
--- Robert Almonte <[EMAIL PROTECTED]> wrote:
Hi ServiceMix team,
I would like to know if it is possible to expose a
Web Service
externally (WSDL) using a BC that host the service
(using what
servicemix already provides).
I have been checking the soap-binding and
xfire-binding example, but I
still cannot get a whole picture to tie these two
together.
My scenario will be a Web Service that receives SOAP
requests for some
data and delegates internally using the NMR to other
components.
(e.i,: Soap-over-HTTP with WSDL exposed to client,
everything contained
by servicemix except the client)
Client <--> WebService{BC}<-->NMR---Other components
My scenario is close to the soap-binding example,
but this one doesn't
expose the WSDL externally.
The xfire-binding example exposes the WSDL
externally, but it is hosted
outside the servicemix.
Somebody posted about creating an Axis2 BC, but I
couldn't find more info.
Can anybody give me some guidance how I could do
this with the current
servicemix?
Thanks,
Robert
All information contained in this email is
confidential and may be used by the intended
recipient only.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
All information contained in this email is confidential and may be used by
the intended recipient only.
All information contained in this email is confidential and may be used by the
intended recipient only.
