You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Andrea Zoppello <zo...@tiscali.it> on 2008/01/14 14:53:29 UTC
main.wsdl???
Hi all,
Is there a reason why the wsdl in servicemix-http, must be called
main.wsdl??
BTW, i've deployed some sa where i attach in the service unit wsdl
files that are not called main.wsdl,
and all seem to work correctly. the problem is that wsdl is accessible
from external only if it's called main.wsdl!
I know there's the new CXF-BC, but i need to solve the problem with
servicemix-http.
Any suggestion???
Andrea Zoppello
Re: main.wsdl???
Posted by Andrea Zoppello <zo...@tiscali.it>.
Hi Bruce,
Thank you. As you said i had some error in my wsdl, and now i understand
a little better how
wsdl is handled by http component.
Thanks
Andrea Zoppello
Bruce Snyder ha scritto:
> On Jan 14, 2008 6:53 AM, Andrea Zoppello <zo...@tiscali.it> wrote:
>
>> Hi all,
>>
>>
>> Is there a reason why the wsdl in servicemix-http, must be called
>> main.wsdl??
>>
>> BTW, i've deployed some sa where i attach in the service unit wsdl
>> files that are not called main.wsdl,
>> and all seem to work correctly. the problem is that wsdl is accessible
>> from external only if it's called main.wsdl!
>>
>> I know there's the new CXF-BC, but i need to solve the problem with
>> servicemix-http.
>>
>> Any suggestion???
>>
>
> I'm not exactly sure what you're trying to do but I hazard a guess
> that you're trying to access the WSDL by appending a ?wsdl to the URL,
> correct? If so, the reason why it won't display is that the name of
> the endpoint in the servicemix-http SU's xbean.xml file does not match
> the name of the of the WSDL service/port name. Below is the URL to a
> diagram that shows how an xbean.xml configuration file maps to a WSDL
> file:
>
> http://servicemix.apache.org/5-jbi.html#5.JBI-Concretemodel
>
> Bruce
>
Re: main.wsdl???
Posted by Bruce Snyder <br...@gmail.com>.
On Jan 14, 2008 6:53 AM, Andrea Zoppello <zo...@tiscali.it> wrote:
> Hi all,
>
>
> Is there a reason why the wsdl in servicemix-http, must be called
> main.wsdl??
>
> BTW, i've deployed some sa where i attach in the service unit wsdl
> files that are not called main.wsdl,
> and all seem to work correctly. the problem is that wsdl is accessible
> from external only if it's called main.wsdl!
>
> I know there's the new CXF-BC, but i need to solve the problem with
> servicemix-http.
>
> Any suggestion???
I'm not exactly sure what you're trying to do but I hazard a guess
that you're trying to access the WSDL by appending a ?wsdl to the URL,
correct? If so, the reason why it won't display is that the name of
the endpoint in the servicemix-http SU's xbean.xml file does not match
the name of the of the WSDL service/port name. Below is the URL to a
diagram that shows how an xbean.xml configuration file maps to a WSDL
file:
http://servicemix.apache.org/5-jbi.html#5.JBI-Concretemodel
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/
hello-world-bc not generating MyBootstrap.java
Posted by ma...@uk.bnpparibas.com.
hi all,
i am trying the hello world sample for servicemix......following
instructions here http://servicemix.apache.org/hello-world-bc.html
i ran this maven command
C:\CRDS\servicemix\hello-world-smx>mvn archetype:create
-DarchetypeGroupId=org.a
pache.servicemix.tooling
-DarchetypeArtifactId=servicemix-binding-component -Dar
chetypeVersion=3.2.1 -DgroupId=org.apache.servicemix.samples.helloworld.bc
-Dart
ifactId=hello-world-bc
all i got was this java classes (in src/main)
MyComponent
MyConsumerEndpoiont
MyEndpontType
MyProviderEndpoint
no MyBootstrap...........
THis is my test
public void test() throws Exception {
DefaultServiceMixClient client = new DefaultServiceMixClient(jbi);
InOut me = client.createInOutExchange();
me.setService(new QName("urn:test", "service"));
me.getInMessage().setContent(new StringSource("<hello>THis is my
Test!</hello>"));
client.sendSync(me);
// By default, the endpoint throws an
UnsupportedOperationException
// so do not test anything here
if (me.getStatus() == ExchangeStatus.ERROR) {
if (me.getError() != null) {
throw me.getError();
} else {
fail("Received ERROR status");
}
} else if (me.getFault() != null) {
fail("Received fault: " + new
SourceTransformer().toString(me.getFault().getContent()));
}
System.err.println(new
SourceTransformer().toString(me.getOutMessage().getContent()));
client.done(me);
}
and this is the exception i have in surefire-report
-------------------------------------------------------------------------------
Test set:
org.apache.servicemix.samples.helloworld.bc.MySpringComponentTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.89 sec
<<< FAILURE!
test(org.apache.servicemix.samples.helloworld.bc.MySpringComponentTest)
Time elapsed: 0.813 sec <<< ERROR!
java.lang.UnsupportedOperationException: Unsupported MEP:
http://www.w3.org/2004/08/wsdl/in-out
at
org.apache.servicemix.samples.helloworld.bc.MyProviderEndpoint.processInOut(MyProviderEndpoint.java:55)
at
org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:109)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:610)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:170)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:167)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
docs says
The value of the archetypeVersion parameter in the command above (3.1.2)
may need to be updated to the current ServiceMix version in order for the
command to work correctly. The latest version can always be found in the
top level ServiceMix POM in the <version> element.
i went to chekc in the pom.xm of one of the examples........it shows 3.2.1
anyone could help?
thanks and regards
marco
This communication is confidential, may be privileged and is meant only for the intended recipient. If you are
not the intended recipient, please notify the sender by reply and delete this message from your system. Any
unauthorised dissemination, distribution or copying hereof is prohibited.
BNP Paribas Fund Services UK Limited, BNP Paribas Trust Corporation UK Limited, BNP Paribas UK Limited,
BNP Paribas Commodity Futures Ltd and Investment Fund Services Limited are authorised and regulated by
the Financial Services Authority.
BNP Paribas, BNP Paribas Securities Services and BNP Paribas Private Bank are authorised by the CECEI
and AMF. BNP Paribas London Branch, BNP Paribas Securities Services London Branch and BNP Paribas
Private Bank London Branch are regulated by the Financial Services Authority for the conduct of their UK
business. BNP Paribas Securities Services London Branch is also a member of the London Stock Exchange.