You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Vinod Chhabria <vc...@sterlingtesting.com> on 2007/02/23 15:33:19 UTC
issue with setting properties in two service units of same type in one sa
Hi,
I have a service assembly that has two servicemix-jsr181 service units
using servicemix-3.0.1.
They deploy fine as long as the xbean contains the following
definitions.
==========
Su1\xbean.xml
==========
<jsr181:endpoint
pojoClass="com.sterling.ifactory.service.ExampleServiceImpl"
annotations="none"
service="ifactory:ExampleService"
endpoint="ExampleService"
style="wrapped"
typeMapping="xmlbeans"
/>
==========
Su2\xbean.xml
==========
<jsr181:endpoint
pojoClass="com.sterling.ifactory.service.SampleService"
annotations="none"
service="ifactory:SampleService"
endpoint="SampleService"
style="wrapped"
/>
==========
However when I change the bean definition in the service units to take
the context as a property, I get the popular error - "The service unit
does not have a dependency which is packaged as a jbi-component or a
project property 'componentName'"
Below are my modified bean definitions:
==========
Su1\xbean.xml
==========
<jsr181:endpoint annotations="none"
service="ifactory:ExampleService" endpoint="ExampleService"
style="wrapped" typeMapping="xmlbeans">
<jsr181:pojo>
<bean
class="com.sterling.ifactory.service.ExampleServiceImpl">
<property
name="context">
<ref
bean="context"/>
</property>
</bean>
</jsr181:pojo>
</jsr181:endpoint>
==========
Su2\xbean.xml
==========
<jsr181:endpoint annotations="none" service="ifactory:
SampleService " endpoint=" SampleService " style="wrapped">
<jsr181:pojo>
<bean
class="com.sterling.ifactory.service. SampleService">
<property
name="context">
<ref
bean="context"/>
</property>
</bean>
</jsr181:pojo>
</jsr181:endpoint>
==========
I know there are two issues already logged in JIRA. My question is:
1. Is this the same as those issues, because in my case they work fine
till I set properties on both.
2. The two issues in JIRA are not clear as to when this has been
resolved:
SM-694 - has comments that it is fixed in 3.1
SM-545 - has fixed version has 3.0
I want to confirm if what I am facing is indeed the same issue and if it
has been fixed in 3.0, 3.0.1 or 3.1 ?
Regards,
Vinod.
<http://dataexchange.sterlingtesting.com/images/sigs/image001.gif>
<http://dataexchange.sterlingtesting.com/images/sigs/image000.gif>
Vinod H. Chhabria :: Senior Developer, Integration Services
Sterling Testing Systems :: 249 West 17th Street :: 6th Floor :: New
York :: NY :: 10011
646-435-2208 (t) :: 646-435-2281 (f)
www.sterlingtesting.com <http://www.sterlingtesting.com>
This email (and any attachments) is intended only for the use of the individual or entity named above and may contain information that is privileged and confidential. If you are not the intended recipient, or have unauthorized access, you are hereby notified that copying, disseminating, distributing or taking any action in reliance on this email is strictly prohibited<br />
Opinions, conclusions and other information in this message that do not relate to the official business of our firm shall be understood as neither given nor endorsed by it.
Re: issue with setting properties in two service units of same type
in one sa
Posted by Gert Vanthienen <ge...@skynet.be>.
L.S.,
This sometimes happens when you add two SU of the same type in a single
SA. The easy workaround is to add a property
<componentName>servicemix-cxf-bc</componentName> to the <properties/>
section of your SUs pom.xml.
Regards,
Gert
Fullocto wrote:
> up, I am facing the same issues with cxf bc sus
>
Re: issue with setting properties in two service units of same type
in one sa
Posted by Fullocto <br...@fr.thalesgroup.com>.
up, I am facing the same issues with cxf bc sus
--
View this message in context: http://www.nabble.com/issue-with-setting-properties-in-two-service-units-of-same-type-in-one-sa-tp9119658p18807046.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.