Cool !
Could one of you write a little summary of the
steps involved so that we can put in on the web
site ?  Or if you send a CLA, we can grant you
access to it ....
Thanks a lot.

On 2/13/07, jlbarrera <[EMAIL PROTECTED]> wrote:

Problem solved!
I only have deleted the "provides" tag and all worked fine!

OK, i have created my first SA in ServiceMix and I got deploy it in Open
ESB.

Thanks for your help, it's has been very suscessfull


jlbarrera wrote:
>
> Yes this is a problem that i solved, and i had created a jbi.xml file. But
> now, when all should run ok, i received an error:
>
> "The Service Assembly rsswsJar.zip could not be added to the
> repository.  Error details : Schema validation failed for
> rsswshttp-su.zip : jbi.xml.  tag name "provides" is not allowed.
> Possible tag names are: elements of "" namespace, and more."
>
> And i found a post in Open-ESB forums:
> 
https://open-esb.dev.java.net/servlets/ProjectForumMessageView?forumID=1689&messageID=11893
>
> This is my Service Assembly:  http://www.nabble.com/file/6462/rsswsJar.zip
> rsswsJar.zip
>
> Thanks by all
>
>
> jlo_gestalt wrote:
>>
>> Yeah I received that same error. I guess I should have posted all my
>> findings after I got the SM stuff working in OpenESB.
>>
>> The problem probably is that your Service Units don't contain a jbi.xml.
>> According to the spec, this is required. However SM doesn't require it.
>> There maven2 jbi plugin I think creates one automatically. But since we
>> are on maven 1.x, we didn't have one either.
>>
>> The jbi.xml needs to contain a provides/consumes tags.
>>
>> Here is an example.
>> <?xml version="1.0" encoding="UTF-8"?>
>> <jbi version="1.0"
>>      xmlns="http://java.sun.com/xml/ns/jbi";
>>      xmlns:jbi="http://java.sun.com/xml/ns/jbi";
>>      xmlns:ns1="http://nettoolkit.gestalt.com/httpeip";>
>>     <!-- Service Unit Descriptor required by Spec (see 6.3.4) -->
>>     <!-- However it seems only needed for tooling -->
>>     <!-- Contents are not used at runtime by container -->
>>     <!-- Consequently for now just put place holder information -->
>>   <services binding-component="false">
>>     <provides interface-name="ns1:HttProxySa"
>> service-name="ns1:HttProxySa" endpoint-name="HttProxySa"/>
>>   </services>
>> </jbi>
>>
>
>

--
View this message in context: 
http://www.nabble.com/ServiceMix-in-other-JBI-Containers-tf3188098s12049.html#a8943140
Sent from the ServiceMix - User mailing list archive at Nabble.com.




--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/

Reply via email to