You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Guillaume Nodet <gu...@worldonline.fr> on 2006/04/09 14:58:04 UTC
[VOTE] Servicemix 3.0 M1
Hi everybody,
I have compiled a M1 release yesterday. Please take some time to
download and test it under your environment before voting it.
The maven artifacts are available at
http://people.apache.org/~gnodet/incubator-servicemix-3.0-M1/incubator-servicemix/distributions/
and the tag is at
http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.0-M1/
[ ] +1 Release the binary as ServiceMix 3.0-M1
[ ] -1 Veto the release (provide specific comments)
If the vote passes, next step will be to ask the Incubator PMC blessing...
Cheers,
Guillaume Nodet
Re: [VOTE] Servicemix 3.0 M1
Posted by Charles Souillard <Ch...@ext.bull.net>.
+1
Guillaume Nodet wrote:
> Hi everybody,
>
> I have compiled a M1 release yesterday. Please take some time to
> download and test it under your environment before voting it.
> The maven artifacts are available at
>
> http://people.apache.org/~gnodet/incubator-servicemix-3.0-M1/incubator-servicemix/distributions/
>
> and the tag is at
>
> http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.0-M1/
>
>
> [ ] +1 Release the binary as ServiceMix 3.0-M1
> [ ] -1 Veto the release (provide specific comments)
>
> If the vote passes, next step will be to ask the Incubator PMC
> blessing...
>
> Cheers,
> Guillaume Nodet
>
>
>
>
Re: [VOTE] Servicemix 3.0 M1
Posted by Dain Sundstrom <da...@iq80.com>.
+1
-dain
On Apr 9, 2006, at 5:58 AM, Guillaume Nodet wrote:
> Hi everybody,
>
> I have compiled a M1 release yesterday. Please take some time to
> download and test it under your environment before voting it.
> The maven artifacts are available at
> http://people.apache.org/~gnodet/incubator-servicemix-3.0-M1/
> incubator-servicemix/distributions/
> and the tag is at
> http://svn.apache.org/repos/asf/incubator/servicemix/tags/
> servicemix-3.0-M1/
>
> [ ] +1 Release the binary as ServiceMix 3.0-M1
> [ ] -1 Veto the release (provide specific comments)
>
> If the vote passes, next step will be to ask the Incubator PMC
> blessing...
>
> Cheers,
> Guillaume Nodet
>
>
Re: [VOTE] Servicemix 3.0 M1
Posted by Dan Diephouse <da...@envoisolutions.com>.
Guillaume Nodet wrote:
> * Which website is supposed to be the right one?
>> http://servicemix.org/ or http://incubator.apache.org/servicemix/ ?
>
>
>
>I guess http://incubator.apache.org/servicemix/, we need to fix some links.
>
>
>
Can we get servicemix.org to redirect to the incubator site then? One is
codehaus, one is apache...
>Well, the XFire example sources are still available at
>http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-assembly/src/sandbox/xfire-binding/
>I removed it from the distribution because this is a pure XFire sample
>and is in no way related to ServiceMix (it may be better to put it in
>XFire distribution ;) )
>
>
Yeah, IIRC, Hiram just copied this from XFire CVS at one point, so I
think we have it. I wanted to put together a true example that shows how
to do some more stuff with xfire.
>I guess we could write a pure xfire binding component: there are a
>couple of enhancements that xfire would need to keep up with
>servicemix-http ;) like jett6 continuations, accessing directly a stax
>based jaxp source, use of commons-httpclient pooling on the client
>side. This would enable to use xfire handlers like the WS-Security
>one directly. But this deserves another thread ...
>
>
>
OK, yeah this does deserve another thread. I'll take a look into some of
these issues soon and see what I can do.
>>None of these are necessariliy blockers as its a M1 release, so I am +0.
>>I would like to see SM-393 addressed and the soap binding link fixed,
>>but don't have time to do it myself at the moment.
>>
>>
>
>I will fix the link (which is not a bad link actually, the doc has not
>been written).
>
>
Ok, cool. Cheers,
- Dan
--
Dan Diephouse
(616) 971-2053
Envoi Solutions LLC
http://netzooid.com
Re: [VOTE] Servicemix 3.0 M1
Posted by Guillaume Nodet <gn...@gmail.com>.
On 4/10/06, Dan Diephouse <da...@envoisolutions.com> wrote:
> Seems OK, but I noticed a couple things:
>
> * SM-393: problems occur if you have spaces in the folder that
> contains the servicemix install.
Thanks for testing and reporting that,
> * soap-binding: http://servicemix.org/soap+binding+example doesn't
> exist but is referenced in the README.txt
Yeah, need to write this one...
> * Which website is supposed to be the right one?
> http://servicemix.org/ or http://incubator.apache.org/servicemix/ ?
I guess http://incubator.apache.org/servicemix/, we need to fix some links.
> * XFire example still doesn't exist even though its listed on the
> examples page. I know the JSR-181 component exists, but I think
> the xfire binding is still probably needed for things like
> WS-Security or people with existing services. I will put this
> together for 3.0-M2 (SM-394 - how can I assign this to myself?)
Well, the XFire example sources are still available at
http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-assembly/src/sandbox/xfire-binding/
I removed it from the distribution because this is a pure XFire sample
and is in no way related to ServiceMix (it may be better to put it in
XFire distribution ;) )
I guess we could write a pure xfire binding component: there are a
couple of enhancements that xfire would need to keep up with
servicemix-http ;) like jett6 continuations, accessing directly a stax
based jaxp source, use of commons-httpclient pooling on the client
side. This would enable to use xfire handlers like the WS-Security
one directly. But this deserves another thread ...
>
> None of these are necessariliy blockers as its a M1 release, so I am +0.
> I would like to see SM-393 addressed and the soap binding link fixed,
> but don't have time to do it myself at the moment.
I will fix the link (which is not a bad link actually, the doc has not
been written).
Cheers,
Guillaume
>
> Cheers,
>
> - Dan
>
> Guillaume Nodet wrote:
>
> > Hi everybody,
> >
> > I have compiled a M1 release yesterday. Please take some time to
> > download and test it under your environment before voting it.
> > The maven artifacts are available at
> >
> > http://people.apache.org/~gnodet/incubator-servicemix-3.0-M1/incubator-servicemix/distributions/
> >
> > and the tag is at
> >
> > http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.0-M1/
> >
> >
> > [ ] +1 Release the binary as ServiceMix 3.0-M1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > If the vote passes, next step will be to ask the Incubator PMC
> > blessing...
> >
> > Cheers,
> > Guillaume Nodet
> >
> >
> >
>
>
> --
> Dan Diephouse
> (616) 971-2053
> Envoi Solutions LLC
> http://netzooid.com
>
>
Re: [VOTE] Servicemix 3.0 M1
Posted by Dan Diephouse <da...@envoisolutions.com>.
Seems OK, but I noticed a couple things:
* SM-393: problems occur if you have spaces in the folder that
contains the servicemix install.
* soap-binding: http://servicemix.org/soap+binding+example doesn't
exist but is referenced in the README.txt
* Which website is supposed to be the right one?
http://servicemix.org/ or http://incubator.apache.org/servicemix/ ?
* XFire example still doesn't exist even though its listed on the
examples page. I know the JSR-181 component exists, but I think
the xfire binding is still probably needed for things like
WS-Security or people with existing services. I will put this
together for 3.0-M2 (SM-394 - how can I assign this to myself?)
None of these are necessariliy blockers as its a M1 release, so I am +0.
I would like to see SM-393 addressed and the soap binding link fixed,
but don't have time to do it myself at the moment.
Cheers,
- Dan
Guillaume Nodet wrote:
> Hi everybody,
>
> I have compiled a M1 release yesterday. Please take some time to
> download and test it under your environment before voting it.
> The maven artifacts are available at
>
> http://people.apache.org/~gnodet/incubator-servicemix-3.0-M1/incubator-servicemix/distributions/
>
> and the tag is at
>
> http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.0-M1/
>
>
> [ ] +1 Release the binary as ServiceMix 3.0-M1
> [ ] -1 Veto the release (provide specific comments)
>
> If the vote passes, next step will be to ask the Incubator PMC
> blessing...
>
> Cheers,
> Guillaume Nodet
>
>
>
--
Dan Diephouse
(616) 971-2053
Envoi Solutions LLC
http://netzooid.com
Re: [VOTE] Servicemix 3.0 M1
Posted by Guillaume Nodet <gn...@gmail.com>.
I forgot to vote ...
+1
On 4/9/06, Guillaume Nodet <gu...@worldonline.fr> wrote:
> Hi everybody,
>
> I have compiled a M1 release yesterday. Please take some time to
> download and test it under your environment before voting it.
> The maven artifacts are available at
>
> http://people.apache.org/~gnodet/incubator-servicemix-3.0-M1/incubator-servicemix/distributions/
> and the tag is at
>
> http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.0-M1/
>
> [ ] +1 Release the binary as ServiceMix 3.0-M1
> [ ] -1 Veto the release (provide specific comments)
>
> If the vote passes, next step will be to ask the Incubator PMC blessing...
>
> Cheers,
> Guillaume Nodet
>
>
>
>
Re: [VOTE] Servicemix 3.0 M1
Posted by Bruce Snyder <br...@gmail.com>.
On 4/9/06, Guillaume Nodet <gu...@worldonline.fr> wrote:
> Hi everybody,
>
> I have compiled a M1 release yesterday. Please take some time to
> download and test it under your environment before voting it.
> The maven artifacts are available at
>
> http://people.apache.org/~gnodet/incubator-servicemix-3.0-M1/incubator-servicemix/distributions/
> and the tag is at
>
> http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.0-M1/
>
> [ ] +1 Release the binary as ServiceMix 3.0-M1
> [ ] -1 Veto the release (provide specific comments)
+1
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://incubator.apache.org/activemq/
Apache ServiceMix - http://incubator.apache.org/servicemix/
Castor - http://castor.org/
Re: [VOTE] Servicemix 3.0 M1
Posted by Guillaume Nodet <gn...@gmail.com>.
Change the geronimo.properties entry in the ./gplan/project.properties to the
geronimo version you want to use (1.0 I guess).
Cheers,
Guillaume Nodet
On 4/11/06, kahon <ka...@sohu.com> wrote:
> Guillaume Nodet <guillaume.nodet <at> worldonline.fr> writes:
>
> >
> > Hi everybody,
> >
> > I have compiled a M1 release yesterday. Please take some time to
> > download and test it under your environment before voting it.
> > The maven artifacts are available at
> >
> > http://people.apache.org/~gnodet/incubator-servicemix-3.0-M1/incubator-
> servicemix/distributions/
> > and the tag is at
> >
> > http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.0-M1/
> >
> > [ ] +1 Release the binary as ServiceMix 3.0-M1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > If the vote passes, next step will be to ask the Incubator PMC blessing...
> >
> > Cheers,
> > Guillaume Nodet
> >
> >
>
> I download it and test the GBean deploy,it says:
> -----------
> Unable to load first parent of configuration servicemix/3.0-M1/car
> No configuration with id: geronimo/j2ee-deployer/1.2-SNAPSHOT/car
> ------
> what's the problem?
>
>
>
Re: [VOTE] Servicemix 3.0 M1
Posted by kahon <ka...@sohu.com>.
Guillaume Nodet <guillaume.nodet <at> worldonline.fr> writes:
>
> Hi everybody,
>
> I have compiled a M1 release yesterday. Please take some time to
> download and test it under your environment before voting it.
> The maven artifacts are available at
>
> http://people.apache.org/~gnodet/incubator-servicemix-3.0-M1/incubator-
servicemix/distributions/
> and the tag is at
>
> http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.0-M1/
>
> [ ] +1 Release the binary as ServiceMix 3.0-M1
> [ ] -1 Veto the release (provide specific comments)
>
> If the vote passes, next step will be to ask the Incubator PMC blessing...
>
> Cheers,
> Guillaume Nodet
>
>
I download it and test the GBean deploy,it says:
-----------
Unable to load first parent of configuration servicemix/3.0-M1/car
No configuration with id: geronimo/j2ee-deployer/1.2-SNAPSHOT/car
------
what's the problem?
Re: [VOTE] Servicemix 3.0 M1
Posted by James Strachan <ja...@gmail.com>.
+1
On 4/9/06, Guillaume Nodet <gu...@worldonline.fr> wrote:
> Hi everybody,
>
> I have compiled a M1 release yesterday. Please take some time to
> download and test it under your environment before voting it.
> The maven artifacts are available at
>
> http://people.apache.org/~gnodet/incubator-servicemix-3.0-M1/incubator-servicemix/distributions/
> and the tag is at
>
> http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.0-M1/
>
> [ ] +1 Release the binary as ServiceMix 3.0-M1
> [ ] -1 Veto the release (provide specific comments)
>
> If the vote passes, next step will be to ask the Incubator PMC blessing...
>
> Cheers,
> Guillaume Nodet
>
>
>
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: [VOTE] Servicemix 3.0 M1
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
+1
Regards,
Alan
Guillaume Nodet wrote, On 4/9/2006 5:58 AM:
> Hi everybody,
>
> I have compiled a M1 release yesterday. Please take some time to
> download and test it under your environment before voting it.
> The maven artifacts are available at
>
> http://people.apache.org/~gnodet/incubator-servicemix-3.0-M1/incubator-servicemix/distributions/
>
> and the tag is at
>
> http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.0-M1/
>
>
> [ ] +1 Release the binary as ServiceMix 3.0-M1
> [ ] -1 Veto the release (provide specific comments)
>
> If the vote passes, next step will be to ask the Incubator PMC
> blessing...
>
> Cheers,
> Guillaume Nodet
>
>
>
Re: [VOTE] Servicemix 3.0 M1
Posted by Hiram Chirino <hi...@hiramchirino.com>.
+1
On 4/9/06, Guillaume Nodet <gu...@worldonline.fr> wrote:
> Hi everybody,
>
> I have compiled a M1 release yesterday. Please take some time to
> download and test it under your environment before voting it.
> The maven artifacts are available at
>
> http://people.apache.org/~gnodet/incubator-servicemix-3.0-M1/incubator-servicemix/distributions/
> and the tag is at
>
> http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.0-M1/
>
> [ ] +1 Release the binary as ServiceMix 3.0-M1
> [ ] -1 Veto the release (provide specific comments)
>
> If the vote passes, next step will be to ask the Incubator PMC blessing...
>
> Cheers,
> Guillaume Nodet
>
>
>
>
--
Regards,
Hiram
Re: [VOTE] Servicemix 3.0 M1
Posted by Guillaume Nodet <gn...@gmail.com>.
For those that are not subscribed to the Apache incubator mailing list,
just a word to say that the release has been vetoed for legal reasons
(missing NOTICE file and third party licenses...)
I 'm working on that and I hope we will be able to cut another M1 soon.
Cheers,
Guillaume Nodet
On 4/9/06, Guillaume Nodet <gu...@worldonline.fr> wrote:
> Hi everybody,
>
> I have compiled a M1 release yesterday. Please take some time to
> download and test it under your environment before voting it.
> The maven artifacts are available at
>
> http://people.apache.org/~gnodet/incubator-servicemix-3.0-M1/incubator-servicemix/distributions/
> and the tag is at
>
> http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.0-M1/
>
> [ ] +1 Release the binary as ServiceMix 3.0-M1
> [ ] -1 Veto the release (provide specific comments)
>
> If the vote passes, next step will be to ask the Incubator PMC blessing...
>
> Cheers,
> Guillaume Nodet
>
>
>
>
Re: Need help for auto-deploying Service Assemblies
Posted by Guillaume Nodet <gn...@gmail.com>.
Glad it now works ...
Guillaume Nodet
On 4/11/06, Soumadeep <so...@infravio.com> wrote:
> Re-wrote all the required xml files (jbi.xml,servicemix-sa.xml and
> servicemix.xml)and it works fine :-)
>
> -----Original Message-----
> From: Soumadeep [mailto:soumadeep@infravio.com]
> Sent: Monday, April 10, 2006 11:10 PM
> To: servicemix-dev@geronimo.apache.org
> Subject: RE: Need help for auto-deploying Service Assemblies
>
>
> Hi Guillaume,
>
> I have tried all that you suggested but I still get the following error.
> Any idea when does this happen.
>
> Thanks
> Soumadeep
>
> ERROR:
>
> java.lang.Exception: <?xml version="1.0" encoding="UTF-8"?>
> <jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message"
> version="1.0
> ">
> <jbi-task-result>
> <frmwk-task-result>
> <frmwk-task-result-details>
> <task-result-details>
> <task-id>deploy</task-id>
> <task-result>FAILED</task-result>
> <message-type>ERROR</message-type>
> </task-result-details>
> </frmwk-task-result-details>
> </frmwk-task-result>
> <component-task-result
> xmlns="http://java.sun.com/xml/ns/jbi/management-message"
> >
> <component-name>servicemix-lwcontainer</component-name>
> <component-task-result-details>
> <task-result-details>
> <task-id>deploy</task-id>
> <task-result>FAILED</task-result>
> <message-type>ERROR</message-type>
> <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Could not deploy xbean service unit</loc-message>
> </msg-loc-info>
> </task-status-msg>
> <exception-info>
> <nesting-level>1</nesting-level>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Can not find 'jbi'
> bean</lo
> c-message>
> <stack-trace><![CDATA[java.lang.Runt
> imeE
> xception: Can not find 'jbi' bean
> at
> org.apache.servicemix.lwcontainer.LwContainerXBeanDeployer.getService
> s(LwContainerXBeanDeployer.java:49)
> at
> org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(Abstr
> actXBeanDeployer.java:95)
> at
> org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServ
> iceUnitManager.java:87)
> at
> org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServic
> eUnitManager.java:68)
> at
> org.apache.servicemix.jbi.framework.DeploymentService.deployServiceAs
> sembly(DeploymentService.java:526)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchi
> ve(AutoDeploymentService.java:257)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService$2.run(AutoD
> eploymentService.java:507)
> at
> org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.ja
> va:291)
> at
> EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown So
> urce)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: org.apache.xbean.kernel.ServiceNotFoundException
> at
> org.apache.xbean.kernel.standard.ServiceManagerRegistry.getServiceMan
> ager(ServiceManagerRegistry.java:201)
> at
> org.apache.xbean.kernel.standard.StandardKernel.getServiceManager(Sta
> ndardKernel.java:442)
> at
> org.apache.xbean.kernel.standard.StandardKernel.getService(StandardKe
> rnel.java:358)
> at
> org.apache.servicemix.lwcontainer.LwContainerXBeanDeployer.getService
> s(LwContainerXBeanDeployer.java:40)
> ... 9 more
> ]]></stack-trace>
> </msg-loc-info>
> </exception-info>
> </task-result-details>
> </component-task-result-details>
> </component-task-result>
> </jbi-task-result>
> </jbi-task>
>
>
>
>
>
> -----Original Message-----
> From: Guillaume Nodet [mailto:gnodet@gmail.com]
> Sent: Monday, April 10, 2006 2:34 AM
> To: servicemix-dev@geronimo.apache.org
> Subject: Re: Need help for auto-deploying Service Assemblies
>
>
> If you are writing a lightweight component (inheriting the
> ComponentSupport base class), you have to deploy your service unit
> onto the servicemix-lwcontainer component.
> So:
> 1) make sure the servicemix-lwcontainer is installed (you can just
> copy the servicemix-lwcontainer zip to the install dir)
> 2) you have to specify servicemix-lwcontainer as the target
> component in your SA jbi descriptor
>
> <service-unit>
> <identification>
> <name>xxx-su</name>
> <description>xxx-su components</description>
> </identification>
> <target>
> <artifacts-zip>xxx-su.zip</artifacts-zip>
>
> <component-name>servicemix-lwcontainer</component-name>
> </target>
> </service-unit>
>
> Cheers,
> Guillaume Nodet
>
> On 4/9/06, Soumadeep <so...@infravio.com> wrote:
> > Hi,
> > Need some help with auto-deploying service assemblies. Is there a proper
> doc
> > somewhere, which I can refer to?
> > This is what I tried.
> > Structure of the xxx-sa.zip
> > xxx-sa.zip
> > |----------- META-IN
> > |------------- jbi.xml
> > |----------- xxx-su.zip
> > |------------- component
> > | |-----------------Xyz.class
> > |------------- servicemix.xml
> >
> >
> > The class Xyz extends ComponentSupport and implements
> > MessageExchangeListener. It works fine if I change the element
> > <sm:serviceunit id="jbi"> to <sm:container id="jbi"> in the servicemix.xml
> > and put it in the root dir of the new sample component that I have made.
> >
> > Would appreciate if anyone could help.
> >
> > Thanks
> > Soumadeep
> >
> > Console output
> > ============
> > INFO - ComponentMBeanImpl.init(184) | Initializing component:
> > #SubscriptionManag
> > er#
> > INFO - DeploymentService.buildState(683) | Restoring service assemblies
> > INFO - JBIContainer.init(508) | ServiceMix JBI Container
> > (http://servicemix.org/
> > ) name: ServiceMix running version: 3.0-SNAPSHOT
> > INFO - ComponentMBeanImpl.setInitialRunningState(335) | Setting running
> > state fo
> > r Component: servicemix-lwcontainer to Started
> > INFO - ComponentMBeanImpl.init(184) | Initializing component:
> > servicemix-lwconta
> > iner
> > INFO - AutoDeploymentService$2.run(504) | Directory: deploy: Archive
> > changed: pr
> > ocessing xxx-sa.zip ...
> > INFO - AutoDeploymentService.updateArchive(264) | Components xyz are not
> in
> > stalled yet - adding ServiceAssembly xxx-sa to pending list
> > INFO - AutoDeploymentService$2.run(508) | Directory: deploy: Finished
> > installati
> > on of archive: xbroker-sa.zip
> >
> >
> >
> >
> > JBI File:
> > ======
> > <?xml version="1.0" encoding="UTF-8"?>
> > <jbi xmlns="http://java.sun.com/xml/ns/jbi" version="1.0"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xsi:schemaLocation="http://java.sun.com/xml/ns/jbi
> > C:\servicemix-test-file\jbi.xsd">
> > <service-assembly>
> > <identification>
> > <name>xxx-sa</name>
> > <description>xxx-sa</description>
> > </identification>
> > <service-unit>
> > <identification>
> > <name>xxx-su</name>
> > <description>xxx-su
> components</description>
> > </identification>
> > <target>
> > <artifacts-zip>xxx-su.zip</artifacts-zip>
> > <component-name>xyz</component-name>
> > </target>
> > </service-unit>
> > </service-assembly>
> > </jbi>
> >
> > Servicemix.xml
> > =============
> > <?xml version="1.0" encoding="UTF-8"?>
> > <beans xmlns="http://xbean.org/schemas/spring/1.0"
> > xmlns:sm="http://servicemix.org/config/1.0"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:foo="http://servicemix.org/demo/">
> >
> > <classpath>
> > <location>.</location>
> > </classpath>
> >
> > <!-- the JBI container -->
> > <sm:serviceunit id="jbi">
> >
> > <sm:activationSpecs>
> >
> > <!-- Create a http server binding on port 8912 and have
> it forward to the
> > foo:stockQuote -->
> > <sm:activationSpec componentName="httpReceiver"
> >
> service="foo:httpBinding"
> >
> destinationService="foo:xyz">
> > <sm:component>
> > <bean
> class="org.apache.servicemix.components.http.HttpConnector">
> > <!-- <property name="host" value="localhost"/> -->
> > <property name="host" value="localhost"/>
> > <property name="port" value="8912"/>
> > </bean>
> > </sm:component>
> > </sm:activationSpec>
> >
> > <!-- This just invokes another service -->
> > <sm:activationSpec componentName="xyz"
> > service="foo:xyz"
> >
> destinationService="foo:stockQuote">>
> > <sm:component>
> > <bean class="component.Xyz">
> > </bean>
> > </sm:component>
> > </sm:activationSpec>
> > <!-- This just invokes another service -->
> > <sm:activationSpec componentName="stockQuote"
> >
> service="foo:stockQuote">
> > <sm:component>
> > <bean
> class="org.apache.servicemix.components.saaj.SaajBinding">
> > <property name="soapEndpoint">
> > <bean
> class="javax.xml.messaging.URLEndpoint">
> > <constructor-arg
> value="http://64.124.140.30/soap"/>
> > </bean>
> > </property>
> > </bean>
> > </sm:component>
> >
> > </sm:activationSpec>
> > </sm:activationSpecs>
> >
> > </sm:serviceunit>
> >
> > </beans>
> >
> > servicemix.xml - for the root directory when used with auto-deploy/ ant
> task
> > =======================================================
> > <?xml version="1.0" encoding="UTF-8"?>
> > <beans xmlns:sm="http://servicemix.apache.org/config/1.0">
> >
> > <!-- the JBI container -->
> > <sm:container id="jbi"
> > useMBeanServer="true"
> > createMBeanServer="true"
> > installationDirPath="./install"
> > deploymentDirPath="./deploy"
> > monitorInstallationDirectory="true"
> > dumpStats="true"
> > statsInterval="10">
> >
> > <sm:activationSpecs>
> > </sm:activationSpecs>
> > </sm:container>
> >
> > </beans>
> >
> >
> >
> >
>
>
>
>
>
RE: Need help for auto-deploying Service Assemblies
Posted by Soumadeep <so...@infravio.com>.
Re-wrote all the required xml files (jbi.xml,servicemix-sa.xml and
servicemix.xml)and it works fine :-)
-----Original Message-----
From: Soumadeep [mailto:soumadeep@infravio.com]
Sent: Monday, April 10, 2006 11:10 PM
To: servicemix-dev@geronimo.apache.org
Subject: RE: Need help for auto-deploying Service Assemblies
Hi Guillaume,
I have tried all that you suggested but I still get the following error.
Any idea when does this happen.
Thanks
Soumadeep
ERROR:
java.lang.Exception: <?xml version="1.0" encoding="UTF-8"?>
<jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message"
version="1.0
">
<jbi-task-result>
<frmwk-task-result>
<frmwk-task-result-details>
<task-result-details>
<task-id>deploy</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
</task-result-details>
</frmwk-task-result-details>
</frmwk-task-result>
<component-task-result
xmlns="http://java.sun.com/xml/ns/jbi/management-message"
>
<component-name>servicemix-lwcontainer</component-name>
<component-task-result-details>
<task-result-details>
<task-id>deploy</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
<task-status-msg>
<msg-loc-info>
<loc-token/>
<loc-message>Could not deploy xbean service unit</loc-message>
</msg-loc-info>
</task-status-msg>
<exception-info>
<nesting-level>1</nesting-level>
<msg-loc-info>
<loc-token/>
<loc-message>Can not find 'jbi'
bean</lo
c-message>
<stack-trace><![CDATA[java.lang.Runt
imeE
xception: Can not find 'jbi' bean
at
org.apache.servicemix.lwcontainer.LwContainerXBeanDeployer.getService
s(LwContainerXBeanDeployer.java:49)
at
org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(Abstr
actXBeanDeployer.java:95)
at
org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServ
iceUnitManager.java:87)
at
org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServic
eUnitManager.java:68)
at
org.apache.servicemix.jbi.framework.DeploymentService.deployServiceAs
sembly(DeploymentService.java:526)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchi
ve(AutoDeploymentService.java:257)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService$2.run(AutoD
eploymentService.java:507)
at
org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.ja
va:291)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown So
urce)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.xbean.kernel.ServiceNotFoundException
at
org.apache.xbean.kernel.standard.ServiceManagerRegistry.getServiceMan
ager(ServiceManagerRegistry.java:201)
at
org.apache.xbean.kernel.standard.StandardKernel.getServiceManager(Sta
ndardKernel.java:442)
at
org.apache.xbean.kernel.standard.StandardKernel.getService(StandardKe
rnel.java:358)
at
org.apache.servicemix.lwcontainer.LwContainerXBeanDeployer.getService
s(LwContainerXBeanDeployer.java:40)
... 9 more
]]></stack-trace>
</msg-loc-info>
</exception-info>
</task-result-details>
</component-task-result-details>
</component-task-result>
</jbi-task-result>
</jbi-task>
-----Original Message-----
From: Guillaume Nodet [mailto:gnodet@gmail.com]
Sent: Monday, April 10, 2006 2:34 AM
To: servicemix-dev@geronimo.apache.org
Subject: Re: Need help for auto-deploying Service Assemblies
If you are writing a lightweight component (inheriting the
ComponentSupport base class), you have to deploy your service unit
onto the servicemix-lwcontainer component.
So:
1) make sure the servicemix-lwcontainer is installed (you can just
copy the servicemix-lwcontainer zip to the install dir)
2) you have to specify servicemix-lwcontainer as the target
component in your SA jbi descriptor
<service-unit>
<identification>
<name>xxx-su</name>
<description>xxx-su components</description>
</identification>
<target>
<artifacts-zip>xxx-su.zip</artifacts-zip>
<component-name>servicemix-lwcontainer</component-name>
</target>
</service-unit>
Cheers,
Guillaume Nodet
On 4/9/06, Soumadeep <so...@infravio.com> wrote:
> Hi,
> Need some help with auto-deploying service assemblies. Is there a proper
doc
> somewhere, which I can refer to?
> This is what I tried.
> Structure of the xxx-sa.zip
> xxx-sa.zip
> |----------- META-IN
> |------------- jbi.xml
> |----------- xxx-su.zip
> |------------- component
> | |-----------------Xyz.class
> |------------- servicemix.xml
>
>
> The class Xyz extends ComponentSupport and implements
> MessageExchangeListener. It works fine if I change the element
> <sm:serviceunit id="jbi"> to <sm:container id="jbi"> in the servicemix.xml
> and put it in the root dir of the new sample component that I have made.
>
> Would appreciate if anyone could help.
>
> Thanks
> Soumadeep
>
> Console output
> ============
> INFO - ComponentMBeanImpl.init(184) | Initializing component:
> #SubscriptionManag
> er#
> INFO - DeploymentService.buildState(683) | Restoring service assemblies
> INFO - JBIContainer.init(508) | ServiceMix JBI Container
> (http://servicemix.org/
> ) name: ServiceMix running version: 3.0-SNAPSHOT
> INFO - ComponentMBeanImpl.setInitialRunningState(335) | Setting running
> state fo
> r Component: servicemix-lwcontainer to Started
> INFO - ComponentMBeanImpl.init(184) | Initializing component:
> servicemix-lwconta
> iner
> INFO - AutoDeploymentService$2.run(504) | Directory: deploy: Archive
> changed: pr
> ocessing xxx-sa.zip ...
> INFO - AutoDeploymentService.updateArchive(264) | Components xyz are not
in
> stalled yet - adding ServiceAssembly xxx-sa to pending list
> INFO - AutoDeploymentService$2.run(508) | Directory: deploy: Finished
> installati
> on of archive: xbroker-sa.zip
>
>
>
>
> JBI File:
> ======
> <?xml version="1.0" encoding="UTF-8"?>
> <jbi xmlns="http://java.sun.com/xml/ns/jbi" version="1.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/jbi
> C:\servicemix-test-file\jbi.xsd">
> <service-assembly>
> <identification>
> <name>xxx-sa</name>
> <description>xxx-sa</description>
> </identification>
> <service-unit>
> <identification>
> <name>xxx-su</name>
> <description>xxx-su
components</description>
> </identification>
> <target>
> <artifacts-zip>xxx-su.zip</artifacts-zip>
> <component-name>xyz</component-name>
> </target>
> </service-unit>
> </service-assembly>
> </jbi>
>
> Servicemix.xml
> =============
> <?xml version="1.0" encoding="UTF-8"?>
> <beans xmlns="http://xbean.org/schemas/spring/1.0"
> xmlns:sm="http://servicemix.org/config/1.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:foo="http://servicemix.org/demo/">
>
> <classpath>
> <location>.</location>
> </classpath>
>
> <!-- the JBI container -->
> <sm:serviceunit id="jbi">
>
> <sm:activationSpecs>
>
> <!-- Create a http server binding on port 8912 and have
it forward to the
> foo:stockQuote -->
> <sm:activationSpec componentName="httpReceiver"
>
service="foo:httpBinding"
>
destinationService="foo:xyz">
> <sm:component>
> <bean
class="org.apache.servicemix.components.http.HttpConnector">
> <!-- <property name="host" value="localhost"/> -->
> <property name="host" value="localhost"/>
> <property name="port" value="8912"/>
> </bean>
> </sm:component>
> </sm:activationSpec>
>
> <!-- This just invokes another service -->
> <sm:activationSpec componentName="xyz"
> service="foo:xyz"
>
destinationService="foo:stockQuote">>
> <sm:component>
> <bean class="component.Xyz">
> </bean>
> </sm:component>
> </sm:activationSpec>
> <!-- This just invokes another service -->
> <sm:activationSpec componentName="stockQuote"
>
service="foo:stockQuote">
> <sm:component>
> <bean
class="org.apache.servicemix.components.saaj.SaajBinding">
> <property name="soapEndpoint">
> <bean
class="javax.xml.messaging.URLEndpoint">
> <constructor-arg
value="http://64.124.140.30/soap"/>
> </bean>
> </property>
> </bean>
> </sm:component>
>
> </sm:activationSpec>
> </sm:activationSpecs>
>
> </sm:serviceunit>
>
> </beans>
>
> servicemix.xml - for the root directory when used with auto-deploy/ ant
task
> =======================================================
> <?xml version="1.0" encoding="UTF-8"?>
> <beans xmlns:sm="http://servicemix.apache.org/config/1.0">
>
> <!-- the JBI container -->
> <sm:container id="jbi"
> useMBeanServer="true"
> createMBeanServer="true"
> installationDirPath="./install"
> deploymentDirPath="./deploy"
> monitorInstallationDirectory="true"
> dumpStats="true"
> statsInterval="10">
>
> <sm:activationSpecs>
> </sm:activationSpecs>
> </sm:container>
>
> </beans>
>
>
>
>
RE: Need help for auto-deploying Service Assemblies
Posted by Soumadeep <so...@infravio.com>.
Hi Guillaume,
I have tried all that you suggested but I still get the following error.
Any idea when does this happen.
Thanks
Soumadeep
ERROR:
java.lang.Exception: <?xml version="1.0" encoding="UTF-8"?>
<jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message"
version="1.0
">
<jbi-task-result>
<frmwk-task-result>
<frmwk-task-result-details>
<task-result-details>
<task-id>deploy</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
</task-result-details>
</frmwk-task-result-details>
</frmwk-task-result>
<component-task-result
xmlns="http://java.sun.com/xml/ns/jbi/management-message"
>
<component-name>servicemix-lwcontainer</component-name>
<component-task-result-details>
<task-result-details>
<task-id>deploy</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
<task-status-msg>
<msg-loc-info>
<loc-token/>
<loc-message>Could not deploy xbean service unit</loc-message>
</msg-loc-info>
</task-status-msg>
<exception-info>
<nesting-level>1</nesting-level>
<msg-loc-info>
<loc-token/>
<loc-message>Can not find 'jbi'
bean</lo
c-message>
<stack-trace><![CDATA[java.lang.Runt
imeE
xception: Can not find 'jbi' bean
at
org.apache.servicemix.lwcontainer.LwContainerXBeanDeployer.getService
s(LwContainerXBeanDeployer.java:49)
at
org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(Abstr
actXBeanDeployer.java:95)
at
org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServ
iceUnitManager.java:87)
at
org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServic
eUnitManager.java:68)
at
org.apache.servicemix.jbi.framework.DeploymentService.deployServiceAs
sembly(DeploymentService.java:526)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchi
ve(AutoDeploymentService.java:257)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService$2.run(AutoD
eploymentService.java:507)
at
org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.ja
va:291)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown So
urce)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.xbean.kernel.ServiceNotFoundException
at
org.apache.xbean.kernel.standard.ServiceManagerRegistry.getServiceMan
ager(ServiceManagerRegistry.java:201)
at
org.apache.xbean.kernel.standard.StandardKernel.getServiceManager(Sta
ndardKernel.java:442)
at
org.apache.xbean.kernel.standard.StandardKernel.getService(StandardKe
rnel.java:358)
at
org.apache.servicemix.lwcontainer.LwContainerXBeanDeployer.getService
s(LwContainerXBeanDeployer.java:40)
... 9 more
]]></stack-trace>
</msg-loc-info>
</exception-info>
</task-result-details>
</component-task-result-details>
</component-task-result>
</jbi-task-result>
</jbi-task>
-----Original Message-----
From: Guillaume Nodet [mailto:gnodet@gmail.com]
Sent: Monday, April 10, 2006 2:34 AM
To: servicemix-dev@geronimo.apache.org
Subject: Re: Need help for auto-deploying Service Assemblies
If you are writing a lightweight component (inheriting the
ComponentSupport base class), you have to deploy your service unit
onto the servicemix-lwcontainer component.
So:
1) make sure the servicemix-lwcontainer is installed (you can just
copy the servicemix-lwcontainer zip to the install dir)
2) you have to specify servicemix-lwcontainer as the target
component in your SA jbi descriptor
<service-unit>
<identification>
<name>xxx-su</name>
<description>xxx-su components</description>
</identification>
<target>
<artifacts-zip>xxx-su.zip</artifacts-zip>
<component-name>servicemix-lwcontainer</component-name>
</target>
</service-unit>
Cheers,
Guillaume Nodet
On 4/9/06, Soumadeep <so...@infravio.com> wrote:
> Hi,
> Need some help with auto-deploying service assemblies. Is there a proper
doc
> somewhere, which I can refer to?
> This is what I tried.
> Structure of the xxx-sa.zip
> xxx-sa.zip
> |----------- META-IN
> |------------- jbi.xml
> |----------- xxx-su.zip
> |------------- component
> | |-----------------Xyz.class
> |------------- servicemix.xml
>
>
> The class Xyz extends ComponentSupport and implements
> MessageExchangeListener. It works fine if I change the element
> <sm:serviceunit id="jbi"> to <sm:container id="jbi"> in the servicemix.xml
> and put it in the root dir of the new sample component that I have made.
>
> Would appreciate if anyone could help.
>
> Thanks
> Soumadeep
>
> Console output
> ============
> INFO - ComponentMBeanImpl.init(184) | Initializing component:
> #SubscriptionManag
> er#
> INFO - DeploymentService.buildState(683) | Restoring service assemblies
> INFO - JBIContainer.init(508) | ServiceMix JBI Container
> (http://servicemix.org/
> ) name: ServiceMix running version: 3.0-SNAPSHOT
> INFO - ComponentMBeanImpl.setInitialRunningState(335) | Setting running
> state fo
> r Component: servicemix-lwcontainer to Started
> INFO - ComponentMBeanImpl.init(184) | Initializing component:
> servicemix-lwconta
> iner
> INFO - AutoDeploymentService$2.run(504) | Directory: deploy: Archive
> changed: pr
> ocessing xxx-sa.zip ...
> INFO - AutoDeploymentService.updateArchive(264) | Components xyz are not
in
> stalled yet - adding ServiceAssembly xxx-sa to pending list
> INFO - AutoDeploymentService$2.run(508) | Directory: deploy: Finished
> installati
> on of archive: xbroker-sa.zip
>
>
>
>
> JBI File:
> ======
> <?xml version="1.0" encoding="UTF-8"?>
> <jbi xmlns="http://java.sun.com/xml/ns/jbi" version="1.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/jbi
> C:\servicemix-test-file\jbi.xsd">
> <service-assembly>
> <identification>
> <name>xxx-sa</name>
> <description>xxx-sa</description>
> </identification>
> <service-unit>
> <identification>
> <name>xxx-su</name>
> <description>xxx-su
components</description>
> </identification>
> <target>
> <artifacts-zip>xxx-su.zip</artifacts-zip>
> <component-name>xyz</component-name>
> </target>
> </service-unit>
> </service-assembly>
> </jbi>
>
> Servicemix.xml
> =============
> <?xml version="1.0" encoding="UTF-8"?>
> <beans xmlns="http://xbean.org/schemas/spring/1.0"
> xmlns:sm="http://servicemix.org/config/1.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:foo="http://servicemix.org/demo/">
>
> <classpath>
> <location>.</location>
> </classpath>
>
> <!-- the JBI container -->
> <sm:serviceunit id="jbi">
>
> <sm:activationSpecs>
>
> <!-- Create a http server binding on port 8912 and have
it forward to the
> foo:stockQuote -->
> <sm:activationSpec componentName="httpReceiver"
>
service="foo:httpBinding"
>
destinationService="foo:xyz">
> <sm:component>
> <bean
class="org.apache.servicemix.components.http.HttpConnector">
> <!-- <property name="host" value="localhost"/> -->
> <property name="host" value="localhost"/>
> <property name="port" value="8912"/>
> </bean>
> </sm:component>
> </sm:activationSpec>
>
> <!-- This just invokes another service -->
> <sm:activationSpec componentName="xyz"
> service="foo:xyz"
>
destinationService="foo:stockQuote">>
> <sm:component>
> <bean class="component.Xyz">
> </bean>
> </sm:component>
> </sm:activationSpec>
> <!-- This just invokes another service -->
> <sm:activationSpec componentName="stockQuote"
>
service="foo:stockQuote">
> <sm:component>
> <bean
class="org.apache.servicemix.components.saaj.SaajBinding">
> <property name="soapEndpoint">
> <bean
class="javax.xml.messaging.URLEndpoint">
> <constructor-arg
value="http://64.124.140.30/soap"/>
> </bean>
> </property>
> </bean>
> </sm:component>
>
> </sm:activationSpec>
> </sm:activationSpecs>
>
> </sm:serviceunit>
>
> </beans>
>
> servicemix.xml - for the root directory when used with auto-deploy/ ant
task
> =======================================================
> <?xml version="1.0" encoding="UTF-8"?>
> <beans xmlns:sm="http://servicemix.apache.org/config/1.0">
>
> <!-- the JBI container -->
> <sm:container id="jbi"
> useMBeanServer="true"
> createMBeanServer="true"
> installationDirPath="./install"
> deploymentDirPath="./deploy"
> monitorInstallationDirectory="true"
> dumpStats="true"
> statsInterval="10">
>
> <sm:activationSpecs>
> </sm:activationSpecs>
> </sm:container>
>
> </beans>
>
>
>
>
Re: Need help for auto-deploying Service Assemblies
Posted by Guillaume Nodet <gn...@gmail.com>.
If you are writing a lightweight component (inheriting the
ComponentSupport base class), you have to deploy your service unit
onto the servicemix-lwcontainer component.
So:
1) make sure the servicemix-lwcontainer is installed (you can just
copy the servicemix-lwcontainer zip to the install dir)
2) you have to specify servicemix-lwcontainer as the target
component in your SA jbi descriptor
<service-unit>
<identification>
<name>xxx-su</name>
<description>xxx-su components</description>
</identification>
<target>
<artifacts-zip>xxx-su.zip</artifacts-zip>
<component-name>servicemix-lwcontainer</component-name>
</target>
</service-unit>
Cheers,
Guillaume Nodet
On 4/9/06, Soumadeep <so...@infravio.com> wrote:
> Hi,
> Need some help with auto-deploying service assemblies. Is there a proper doc
> somewhere, which I can refer to?
> This is what I tried.
> Structure of the xxx-sa.zip
> xxx-sa.zip
> |----------- META-IN
> |------------- jbi.xml
> |----------- xxx-su.zip
> |------------- component
> | |-----------------Xyz.class
> |------------- servicemix.xml
>
>
> The class Xyz extends ComponentSupport and implements
> MessageExchangeListener. It works fine if I change the element
> <sm:serviceunit id="jbi"> to <sm:container id="jbi"> in the servicemix.xml
> and put it in the root dir of the new sample component that I have made.
>
> Would appreciate if anyone could help.
>
> Thanks
> Soumadeep
>
> Console output
> ============
> INFO - ComponentMBeanImpl.init(184) | Initializing component:
> #SubscriptionManag
> er#
> INFO - DeploymentService.buildState(683) | Restoring service assemblies
> INFO - JBIContainer.init(508) | ServiceMix JBI Container
> (http://servicemix.org/
> ) name: ServiceMix running version: 3.0-SNAPSHOT
> INFO - ComponentMBeanImpl.setInitialRunningState(335) | Setting running
> state fo
> r Component: servicemix-lwcontainer to Started
> INFO - ComponentMBeanImpl.init(184) | Initializing component:
> servicemix-lwconta
> iner
> INFO - AutoDeploymentService$2.run(504) | Directory: deploy: Archive
> changed: pr
> ocessing xxx-sa.zip ...
> INFO - AutoDeploymentService.updateArchive(264) | Components xyz are not in
> stalled yet - adding ServiceAssembly xxx-sa to pending list
> INFO - AutoDeploymentService$2.run(508) | Directory: deploy: Finished
> installati
> on of archive: xbroker-sa.zip
>
>
>
>
> JBI File:
> ======
> <?xml version="1.0" encoding="UTF-8"?>
> <jbi xmlns="http://java.sun.com/xml/ns/jbi" version="1.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/jbi
> C:\servicemix-test-file\jbi.xsd">
> <service-assembly>
> <identification>
> <name>xxx-sa</name>
> <description>xxx-sa</description>
> </identification>
> <service-unit>
> <identification>
> <name>xxx-su</name>
> <description>xxx-su components</description>
> </identification>
> <target>
> <artifacts-zip>xxx-su.zip</artifacts-zip>
> <component-name>xyz</component-name>
> </target>
> </service-unit>
> </service-assembly>
> </jbi>
>
> Servicemix.xml
> =============
> <?xml version="1.0" encoding="UTF-8"?>
> <beans xmlns="http://xbean.org/schemas/spring/1.0"
> xmlns:sm="http://servicemix.org/config/1.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:foo="http://servicemix.org/demo/">
>
> <classpath>
> <location>.</location>
> </classpath>
>
> <!-- the JBI container -->
> <sm:serviceunit id="jbi">
>
> <sm:activationSpecs>
>
> <!-- Create a http server binding on port 8912 and have it forward to the
> foo:stockQuote -->
> <sm:activationSpec componentName="httpReceiver"
> service="foo:httpBinding"
> destinationService="foo:xyz">
> <sm:component>
> <bean class="org.apache.servicemix.components.http.HttpConnector">
> <!-- <property name="host" value="localhost"/> -->
> <property name="host" value="localhost"/>
> <property name="port" value="8912"/>
> </bean>
> </sm:component>
> </sm:activationSpec>
>
> <!-- This just invokes another service -->
> <sm:activationSpec componentName="xyz"
> service="foo:xyz"
> destinationService="foo:stockQuote">>
> <sm:component>
> <bean class="component.Xyz">
> </bean>
> </sm:component>
> </sm:activationSpec>
> <!-- This just invokes another service -->
> <sm:activationSpec componentName="stockQuote"
> service="foo:stockQuote">
> <sm:component>
> <bean class="org.apache.servicemix.components.saaj.SaajBinding">
> <property name="soapEndpoint">
> <bean class="javax.xml.messaging.URLEndpoint">
> <constructor-arg value="http://64.124.140.30/soap"/>
> </bean>
> </property>
> </bean>
> </sm:component>
>
> </sm:activationSpec>
> </sm:activationSpecs>
>
> </sm:serviceunit>
>
> </beans>
>
> servicemix.xml - for the root directory when used with auto-deploy/ ant task
> =======================================================
> <?xml version="1.0" encoding="UTF-8"?>
> <beans xmlns:sm="http://servicemix.apache.org/config/1.0">
>
> <!-- the JBI container -->
> <sm:container id="jbi"
> useMBeanServer="true"
> createMBeanServer="true"
> installationDirPath="./install"
> deploymentDirPath="./deploy"
> monitorInstallationDirectory="true"
> dumpStats="true"
> statsInterval="10">
>
> <sm:activationSpecs>
> </sm:activationSpecs>
> </sm:container>
>
> </beans>
>
>
>
>
Need help for auto-deploying Service Assemblies
Posted by Soumadeep <so...@infravio.com>.
Hi,
Need some help with auto-deploying service assemblies. Is there a proper doc
somewhere, which I can refer to?
This is what I tried.
Structure of the xxx-sa.zip
xxx-sa.zip
|----------- META-IN
|------------- jbi.xml
|----------- xxx-su.zip
|------------- component
| |-----------------Xyz.class
|------------- servicemix.xml
The class Xyz extends ComponentSupport and implements
MessageExchangeListener. It works fine if I change the element
<sm:serviceunit id="jbi"> to <sm:container id="jbi"> in the servicemix.xml
and put it in the root dir of the new sample component that I have made.
Would appreciate if anyone could help.
Thanks
Soumadeep
Console output
============
INFO - ComponentMBeanImpl.init(184) | Initializing component:
#SubscriptionManag
er#
INFO - DeploymentService.buildState(683) | Restoring service assemblies
INFO - JBIContainer.init(508) | ServiceMix JBI Container
(http://servicemix.org/
) name: ServiceMix running version: 3.0-SNAPSHOT
INFO - ComponentMBeanImpl.setInitialRunningState(335) | Setting running
state fo
r Component: servicemix-lwcontainer to Started
INFO - ComponentMBeanImpl.init(184) | Initializing component:
servicemix-lwconta
iner
INFO - AutoDeploymentService$2.run(504) | Directory: deploy: Archive
changed: pr
ocessing xxx-sa.zip ...
INFO - AutoDeploymentService.updateArchive(264) | Components xyz are not in
stalled yet - adding ServiceAssembly xxx-sa to pending list
INFO - AutoDeploymentService$2.run(508) | Directory: deploy: Finished
installati
on of archive: xbroker-sa.zip
JBI File:
======
<?xml version="1.0" encoding="UTF-8"?>
<jbi xmlns="http://java.sun.com/xml/ns/jbi" version="1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/jbi
C:\servicemix-test-file\jbi.xsd">
<service-assembly>
<identification>
<name>xxx-sa</name>
<description>xxx-sa</description>
</identification>
<service-unit>
<identification>
<name>xxx-su</name>
<description>xxx-su components</description>
</identification>
<target>
<artifacts-zip>xxx-su.zip</artifacts-zip>
<component-name>xyz</component-name>
</target>
</service-unit>
</service-assembly>
</jbi>
Servicemix.xml
=============
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://xbean.org/schemas/spring/1.0"
xmlns:sm="http://servicemix.org/config/1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:foo="http://servicemix.org/demo/">
<classpath>
<location>.</location>
</classpath>
<!-- the JBI container -->
<sm:serviceunit id="jbi">
<sm:activationSpecs>
<!-- Create a http server binding on port 8912 and have it forward to the
foo:stockQuote -->
<sm:activationSpec componentName="httpReceiver"
service="foo:httpBinding"
destinationService="foo:xyz">
<sm:component>
<bean class="org.apache.servicemix.components.http.HttpConnector">
<!-- <property name="host" value="localhost"/> -->
<property name="host" value="localhost"/>
<property name="port" value="8912"/>
</bean>
</sm:component>
</sm:activationSpec>
<!-- This just invokes another service -->
<sm:activationSpec componentName="xyz"
service="foo:xyz"
destinationService="foo:stockQuote">>
<sm:component>
<bean class="component.Xyz">
</bean>
</sm:component>
</sm:activationSpec>
<!-- This just invokes another service -->
<sm:activationSpec componentName="stockQuote"
service="foo:stockQuote">
<sm:component>
<bean class="org.apache.servicemix.components.saaj.SaajBinding">
<property name="soapEndpoint">
<bean class="javax.xml.messaging.URLEndpoint">
<constructor-arg value="http://64.124.140.30/soap"/>
</bean>
</property>
</bean>
</sm:component>
</sm:activationSpec>
</sm:activationSpecs>
</sm:serviceunit>
</beans>
servicemix.xml - for the root directory when used with auto-deploy/ ant task
=======================================================
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns:sm="http://servicemix.apache.org/config/1.0">
<!-- the JBI container -->
<sm:container id="jbi"
useMBeanServer="true"
createMBeanServer="true"
installationDirPath="./install"
deploymentDirPath="./deploy"
monitorInstallationDirectory="true"
dumpStats="true"
statsInterval="10">
<sm:activationSpecs>
</sm:activationSpecs>
</sm:container>
</beans>
RE: CGI headers missing
Posted by Soumadeep <so...@infravio.com>.
Done
Thanks
Soumadeep
-----Original Message-----
From: Guillaume Nodet [mailto:gnodet@gmail.com]
Sent: Monday, April 10, 2006 12:52 AM
To: servicemix-dev@geronimo.apache.org
Subject: Re: CGI headers missing
Could you please raise a JIRA and attach your patch ?
This is not a big deal, but this allows keeping track of issues /
patches / contributors, aso...
Thanks,
Guillaume Nodet
On 4/9/06, Soumadeep <so...@infravio.com> wrote:
> Hi Everybody,
>
> Some of the CGI headers are missing in the HttpConnector component. The
> HttpMarshaler.java file could include the following piece of code: This
> would help in the identification of clients.
>
> Best regards
> Soumadeep
>
> Class: HttpMarshaler.java
>
> Method 1:
> protected void addNmsProperties(MessageExchange exchange,
> HttpServletRequest request) {
> Enumeration enumeration = request.getHeaderNames();
> while (enumeration.hasMoreElements()) {
> String name = (String) enumeration.nextElement();
> String value = request.getHeader(name);
> exchange.setProperty(name, value);
> }
>
exchange.setProperty("REMOTE_ADDR",request.getRemoteAddr());
>
exchange.setProperty("REMOTE_HOST",request.getRemoteHost());
>
exchange.setProperty("REMOTE_USER",request.getRemoteUser());
> }
>
> Method 2:
> public void toNMS(MessageExchange exchange, NormalizedMessage
inMessage,
> HttpServletRequest request) throws IOException, MessagingException {
> addNmsProperties(exchange, request);
> String method = request.getMethod();
> if (method != null && method.equalsIgnoreCase("POST")) {
> inMessage.setContent(new
> StreamSource(request.getInputStream()));
> }
> else {
> Enumeration enumeration = request.getParameterNames();
> while (enumeration.hasMoreElements()) {
> String name = (String) enumeration.nextElement();
> String value = request.getParameter(name);
> inMessage.setProperty(name, value);
> }
>
inMessage.setProperty("REMOTE_ADDR",request.getRemoteAddr());
>
inMessage.setProperty("REMOTE_HOST",request.getRemoteHost());
>
inMessage.setProperty("REMOTE_USER",request.getRemoteUser());
> inMessage.setContent(EMPTY_CONTENT);
> }
> }
>
>
>
Re: CGI headers missing
Posted by Guillaume Nodet <gn...@gmail.com>.
Could you please raise a JIRA and attach your patch ?
This is not a big deal, but this allows keeping track of issues /
patches / contributors, aso...
Thanks,
Guillaume Nodet
On 4/9/06, Soumadeep <so...@infravio.com> wrote:
> Hi Everybody,
>
> Some of the CGI headers are missing in the HttpConnector component. The
> HttpMarshaler.java file could include the following piece of code: This
> would help in the identification of clients.
>
> Best regards
> Soumadeep
>
> Class: HttpMarshaler.java
>
> Method 1:
> protected void addNmsProperties(MessageExchange exchange,
> HttpServletRequest request) {
> Enumeration enumeration = request.getHeaderNames();
> while (enumeration.hasMoreElements()) {
> String name = (String) enumeration.nextElement();
> String value = request.getHeader(name);
> exchange.setProperty(name, value);
> }
> exchange.setProperty("REMOTE_ADDR",request.getRemoteAddr());
> exchange.setProperty("REMOTE_HOST",request.getRemoteHost());
> exchange.setProperty("REMOTE_USER",request.getRemoteUser());
> }
>
> Method 2:
> public void toNMS(MessageExchange exchange, NormalizedMessage inMessage,
> HttpServletRequest request) throws IOException, MessagingException {
> addNmsProperties(exchange, request);
> String method = request.getMethod();
> if (method != null && method.equalsIgnoreCase("POST")) {
> inMessage.setContent(new
> StreamSource(request.getInputStream()));
> }
> else {
> Enumeration enumeration = request.getParameterNames();
> while (enumeration.hasMoreElements()) {
> String name = (String) enumeration.nextElement();
> String value = request.getParameter(name);
> inMessage.setProperty(name, value);
> }
> inMessage.setProperty("REMOTE_ADDR",request.getRemoteAddr());
> inMessage.setProperty("REMOTE_HOST",request.getRemoteHost());
> inMessage.setProperty("REMOTE_USER",request.getRemoteUser());
> inMessage.setContent(EMPTY_CONTENT);
> }
> }
>
>
>
CGI headers missing
Posted by Soumadeep <so...@infravio.com>.
Hi Everybody,
Some of the CGI headers are missing in the HttpConnector component. The
HttpMarshaler.java file could include the following piece of code: This
would help in the identification of clients.
Best regards
Soumadeep
Class: HttpMarshaler.java
Method 1:
protected void addNmsProperties(MessageExchange exchange,
HttpServletRequest request) {
Enumeration enumeration = request.getHeaderNames();
while (enumeration.hasMoreElements()) {
String name = (String) enumeration.nextElement();
String value = request.getHeader(name);
exchange.setProperty(name, value);
}
exchange.setProperty("REMOTE_ADDR",request.getRemoteAddr());
exchange.setProperty("REMOTE_HOST",request.getRemoteHost());
exchange.setProperty("REMOTE_USER",request.getRemoteUser());
}
Method 2:
public void toNMS(MessageExchange exchange, NormalizedMessage inMessage,
HttpServletRequest request) throws IOException, MessagingException {
addNmsProperties(exchange, request);
String method = request.getMethod();
if (method != null && method.equalsIgnoreCase("POST")) {
inMessage.setContent(new
StreamSource(request.getInputStream()));
}
else {
Enumeration enumeration = request.getParameterNames();
while (enumeration.hasMoreElements()) {
String name = (String) enumeration.nextElement();
String value = request.getParameter(name);
inMessage.setProperty(name, value);
}
inMessage.setProperty("REMOTE_ADDR",request.getRemoteAddr());
inMessage.setProperty("REMOTE_HOST",request.getRemoteHost());
inMessage.setProperty("REMOTE_USER",request.getRemoteUser());
inMessage.setContent(EMPTY_CONTENT);
}
}