You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by ib22841 <ew...@sneakemail.com> on 2007/04/05 16:46:44 UTC
Re: Anybody successful with ServiceMix under LogicBlaze Fuse 1.3
As I've understood, you don't need to synchronize your project with maven
manually anymore as it gets done automatically at build time. And if you
have your ServiceMix server defined in Eclipse and published the assembly
there, it will be also automatically republished.
regards,
Ilja
Jeetal wrote:
>
>
>
>
> Randy H wrote:
>>
>>
>> I can't figure out how to deploy a ServiceUnit to the server
>>
>>
>
> You will have to package the service unit into a service assembly to
> deploy it to the server.
>
>
>
> Randy H wrote:
>>
>>
>> I've been trying to get the simple ServiceMix ServiceEngine example
>> running that's illustrated in the the LogicBlaze FUSE Eclipse IDE
>> tutorial (version 1.3).
>>
>>
>
>
> I tried the Pricing Service tutorial and could not get it running. Also,
> the Fuse IDE v1.3 did not list the "Synchronize with Maven" option which
> is shown in the tutorial. Did you try that example?
>
>
>
>
>
--
View this message in context: http://www.nabble.com/Anybody-successful-with-ServiceMix-under-LogicBlaze-Fuse-1.3-tf3436332s12049.html#a9857236
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Success on wsdl-first on person.wsdl
Posted by Dan Connelly <ds...@adelphia.net>.
ok, I finally did the Russian doll analysis.
Problem with FUSE tooling for wsdl-first of person.wsdl is that the WSDL
specifies SOAP style "document" but the FUSE tooling puts 'wrapped"
(default) in xbean.xml in jsr181:endpoint.
--
View this message in context: http://www.nabble.com/Anybody-successful-with-ServiceMix-under-LogicBlaze-Fuse-1.3-tf3436332s12049.html#a9880011
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: Anybody successful with ServiceMix under LogicBlaze Fuse 1.3
Posted by Dan Connelly <ds...@adelphia.net>.
I believe that Maven2>"Update Source Folders" on the context menu of the
Project also forces a Maven synchronization.
You might consider (as an easier trial than Pricing) trying to "fuse" the
wsdl-first sample (person.wsdl) from the SMX samples.
The wsdl-first assembly that ships with SMX works fine on SMX Server, but I
found when I created a functionally identical assembly myself using the FUSE
tooling, this did not work on either FUSE or SMX servers. (Addressing now
the original question of whether anyone has had "success" using the FUSE
tooling creating SMX service assemblies.)
It should be possible to do Russian doll comparison on the two assemblies
(sample and FUSE'd) to see why the "sample" one works and my FUSE'd one does
not. (Considering just the SMX server in both cases.) But I have not
done this.
The only diagnosis I have so far is from the SMX log. The "wsdl-first"
application is a simple SOAP service, of course. Both the SMX sample and
the fuse'd wsdl-first appear to pass an incorrect operation namespace
(endpoint name) from the http su to the jsr181 su. However, the sample's
use of XFire Aegis in jsr181 is such that it dynamically finds the correct
operation to invoke while my Fuse'd wsdl-first appears to lack the setup for
this dynamic search. If fails with a "Invalid operation" SOAP fault.
Of course, since I am using only SMX, the FUSE jars do not enter into this
problem. It is essentially an SMX problem that gets exposed due to some
quirk of the FUSE tooling.
Being as much as I know of Fuse success on SMX at this point,
-- Dan
--
View this message in context: http://www.nabble.com/Anybody-successful-with-ServiceMix-under-LogicBlaze-Fuse-1.3-tf3436332s12049.html#a9860667
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: Anybody successful with ServiceMix under LogicBlaze Fuse 1.3
Posted by Dan Connelly <ds...@adelphia.net>.
I believe that Maven2>Update Source Folders on the Project context menu also
forces a synchronization.
You might consider testing the FUSE tooling with the "wsdl-first" sample
(person.wsdl) from the SMX samples.
The wsdl-first assembly that ships with SMX works fine on SMX Server, but I
found when I created a functionally identical assembly myself using the FUSE
tooling, this did not work on either FUSE or SMX servers. (I have
returned to the original question of whether anyone has had "success" using
the FUSE tooling creating SMX service assemblies.)
It should be possible to do Russian doll comparison on the two assemblies
(sample and FUSE'd) to see why the "sample" one works and my FUSE'd one does
not. (Considering just the SMX server in both cases.)
The only diagnosis I have so far is from the SMX log. The "wsdl-first"
application is a simple SOAP service, of course. Both the SMX sample and
the fuse'd wsdl-first appear to pass an incorrect operation namespace
(endpoint name) from the http su to the jsr181 su. However, the sample's
use of XFire Aegis in jsr181 is such that it dynamically finds the correct
operation to invoke while my Fuse'd wsdl-first appears to lack the setup for
this dynamic search. If fails with a "Invalid operation" SOAP fault.
Being as much as I know of Fuse success on SMX at this point,
-- Dan
--
View this message in context: http://www.nabble.com/Anybody-successful-with-ServiceMix-under-LogicBlaze-Fuse-1.3-tf3436332s12049.html#a9860659
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.