Check that the SA references the two service units,
that the service units are correctly deployed and
started (in the console output or jconsole).
In the log file (at DEBUG level), you should also
have informations on which components / endpoints
are activated.

On 11/15/06, moraleslos <[EMAIL PROTECTED]> wrote:

I don't have anything much different, although my servicemix.xml doesn't
reference anything to the xbean.xml (except for the destinationService
qname)...

####################
<beans
        xmlns:sm="http://servicemix.apache.org/config/1.0";
        xmlns:foo="http://com.test.integration.servicemix";>

        <classpath>
                <location>.</location>
                
<location>lib/servicemix-components-3.0.1-incubating.jar</location>
                <location>lib/commons-net-1.4.1.jar</location>
                <location>lib/oro-2.0.8.jar</location>
                
<location>lib/test-integration-servicemix-1.0-SNAPSHOT.jar</location>
        </classpath>


        <sm:serviceunit id="jbi">
                <sm:activationSpecs>

                        ...
                        <!-- FTP components that forward files to xmlTransformer 
-->

                        <sm:activationSpec
                                componentName="xmlTransformer"
                                service="foo:xmlTransformer"
                                destinationService="foo:xmlUnmarshaller">
                                <sm:component>
                                        <bean 
class="org.apache.servicemix.components.xslt.XsltComponent">
                                        <property
                                                name="xsltResource"
value="classpath:com/test/integration/servicemix/xmlTemplate.xsl"/>
                                        </bean>
                                </sm:component>
                        </sm:activationSpec>


                </sm:activationSpecs>
        </sm:serviceunit>
</beans>
###########################################






gnodet wrote:
>
> Maybe your servicemix.xml config file is bad.
> Could you post the complete one ?
>
> On 11/15/06, moraleslos <[EMAIL PROTECTED]> wrote:
>
>
>
>>
>> Thanks Guillaume.
>>
>> I launched JConsole, went to
>> org.apache.servicemix-->ServiceMix-->Component
>> as well as Endpoint, and my xmlUnmarshaller component is nowhere to be
>> found.  Now, knowing why the component can't be found, how do I have smx
>> register my xmlUnmarshaller?  Thanks.
>>
>> -los
>>
>>
>>
>> gnodet wrote:
>> >
>> > I don't see why it does not work.
>> > Check what endpoints are activated using the log file at DEBUG level
>> > or a jmx console and ensure the needed endpoint is activate and match
>> > the defined route.
>> >
>> > On 11/14/06, moraleslos <[EMAIL PROTECTED]> wrote:
>> >>
>> >> I currently have my SU defined to do some XSLT.  This is my
>> >> servicemix.xml:
>> >>
>> >> #################
>> >> <sm:activationSpec
>> >>         componentName="xmlTransformer"
>> >>         service="foo:xmlTransformer"
>> >>         destinationService="foo:xmlUnmarshaller">
>> >>         <sm:component>
>> >>                 <bean
>> >> class="org.apache.servicemix.components.xslt.XsltComponent">
>> >>                         <property
>> >>                         name="xsltResource"
>> >> value="classpath:com/test/integration/servicemix/xmlTemplate.xsl"/>
>> >>                                         </bean>
>> >>                                 </sm:component>
>> >>                         </sm:activationSpec>
>> >> ###############################
>> >>
>> >> Now, I want the output from the transformation sent to a Jaxb2
>> >> unmarshaller.
>> >> Looking at the examples, I created an xbean definition like this:
>> >>
>> >> ##############################
>> >> <beans
>> >>         xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0";
>> >>         xmlns:foo="http://com.test.integration.servicemix";>
>> >>
>> >>     <classpath>
>> >>                 <location>.</location>
>> >>     </classpath>
>> >>
>> >>         <jsr181:endpoint
>> >>                 service="foo:xmlUnmarshaller"
>> >>                 endpoint="xmlUnmarshaller"
>> >>                 pojoClass="com.test.integration.servicemix.pojo.Root"
>> >>                 typeMapping="jaxb2"/>
>> >>
>> >> </beans>
>> >> ###############################
>> >>
>> >> When deploying the SU that contains the xbean.xml and servicemix.xml,
>> I
>> >> get
>> >> this error:
>> >>
>> >> WARN  - DefaultBroker                  - ServiceName
>> >> ({http://com.test.integration.servicemix}xmlUnmarshaller) specified
>> for
>> >> routing, but can't find it registered
>> >>
>> >>
>> >> So I'm not sure how to connect the output from the transformation into
>> >> the
>> >> jaxb2 unmarshaller.  Thanks in advance.
>> >>
>> >> -los
>> >>
>> >>
>> >>
>> >>
>> >> gnodet wrote:
>> >> >
>> >> > If you want to send the output of the XSLT component to your
>> >> > jsr181 pojo, you can just use the destinationService attribute
>> >> > on the activationSpec for the xslt component and specify
>> >> > the jsr181 pojo service name.
>> >> > I guess I miss your problem ...
>> >> >
>> >> > On 10/27/06, moraleslos <[EMAIL PROTECTED]> wrote:
>> >> >>
>> >> >> I've developed a test domain that has JAXB2-annotated POJOs and the
>> >> >> generation of the schema from these pojos.  Now in my SU, I've
>> >> retrieved
>> >> >> a
>> >> >> file and used the XSLT translator to transform the XML into
>> something
>> >> >> that
>> >> >> can be unmarshalled into my domain POJOs.  My question is, how do I
>> >> >> connect
>> >> >> the output from the XSLT transformation to the jsr-181 endpoint
>> that
>> >> will
>> >> >> unmarshal this xml document into my jaxb2 pojos?  I'm used to
>> seeing
>> >> the
>> >> >> "destination service":
>> >> >>
>> >> >> <sm:activationSpec
>> >> >>   componentName="XSLTTransformer"
>> >> >>   service="foo:XSLTTransformer"
>> >> >>   destinationService="foo:JAXB2Unmarshaller">
>> >> >>   ....
>> >> >>
>> >> >> Now how do I define this destination using the jsr-181 endpoint?  I
>> >> know
>> >> >> this did not work:
>> >> >>
>> >> >> <jsr181:endpoint endpoint="foo:JAXB2Unmarshaller"
>> >> >>                  typeMapping="jaxb2">
>> >> >>   <jsr181:pojo>
>> >> >>     <bean class="test.UnmarshalService" />
>> >> >>   </jsr181:pojo>
>> >> >> </jsr181:endpoint>
>> >> >>
>> >> >> thanks in advance!
>> >> >>
>> >> >> -los
>> >> >>
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/connecting-to-jsr-181-jaxb2-tf2523299.html#a7038693
>> >> >> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> > --
>> >> > Cheers,
>> >> > Guillaume Nodet
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> 
http://www.nabble.com/connecting-to-jsr-181-jaxb2-tf2523299s12049.html#a7347837
>> >> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> >
>> >
>>
>> --
>> View this message in context:
>> 
http://www.nabble.com/connecting-to-jsr-181-jaxb2-tf2523299s12049.html#a7359654
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
>
>

--
View this message in context: 
http://www.nabble.com/connecting-to-jsr-181-jaxb2-tf2523299s12049.html#a7360931
Sent from the ServiceMix - User mailing list archive at Nabble.com.




--
Cheers,
Guillaume Nodet

Reply via email to