You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Ryan Moquin <fr...@gmail.com> on 2007/09/20 02:38:24 UTC
How to get the ComponentContext in CXF SU?
I'm still having a hard time figuring out how to replicated my interservice
communication through the bus between two CXF services in Servicemix. My
latest problem is that this doesn't appear to work:
<cxfse:endpoint>
<cxfse:pojo>
<bean id="cxfServiceBean" class="notification.NotificationServiceImpl
">
<property name="context" ref="context" />
</bean>
</cxfse:pojo>
</cxfse:endpoint>
According to the servicemix docs, it says I should be able to reference the
context which was created as a parent bean.
Is there an xsd I can look at for cxfse? I need to figure out how I can do
interservice communication with it over the bus still.
Re: How to get the ComponentContext in CXF SU?
Posted by Ryan Moquin <fr...@gmail.com>.
Probably should give the error as well just in case, it's a typical spring
one when it can't find a bean:
Cannot resolve reference to bean 'context' while setting bean property
'context'; nested exception is
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
named 'context' is defined
On 9/19/07, Ryan Moquin <fr...@gmail.com> wrote:
>
> I'm still having a hard time figuring out how to replicated my
> interservice communication through the bus between two CXF services in
> Servicemix. My latest problem is that this doesn't appear to work:
>
> <cxfse:endpoint>
> <cxfse:pojo>
> <bean id="cxfServiceBean" class="
> notification.NotificationServiceImpl">
> <property name="context" ref="context" />
> </bean>
> </cxfse:pojo>
> </cxfse:endpoint>
>
> According to the servicemix docs, it says I should be able to reference
> the context which was created as a parent bean.
>
> Is there an xsd I can look at for cxfse? I need to figure out how I can
> do interservice communication with it over the bus still.
>
Re: How to get the ComponentContext in CXF SU?
Posted by Freeman Fang <fr...@gmail.com>.
Sure.
https://issues.apache.org/activemq/browse/SM-1060
Cheers
Freeman
Guillaume Nodet wrote:
> Freeman, I think being able to inject the endpoint DeliveryChannel and
> ComponentContext is a really important feature. Can you raise a JIRA
> for that please ?
>
> On 9/20/07, Freeman Fang <fr...@iona.com> wrote:
>
>> Hi Ryan,
>>
>> Attachment is the schema for servicemix-cxf-se.
>>
>> So far the cxf-se is not exactly same as jsr-181 service engine, so I
>> think now we don't support it.
>> Also I investigate the jsr-181 client proxy issue you mentioned in
>> previous mail, we don't support it in cxf se neither, sorry for
>> misleading previous response.
>> The main purpose we add cxf-bc and cxf-se is leverage cxf ws-* features.
>> You can see the tests and examples how the typical scenario looks like.
>>
>> If you need any feature we don't support now, please fill jira issue.
>>
>> Best Regards
>>
>> Freeman
>>
>> Ryan Moquin wrote:
>>
>>> I'm still having a hard time figuring out how to replicated my interservice
>>> communication through the bus between two CXF services in Servicemix. My
>>> latest problem is that this doesn't appear to work:
>>>
>>> <cxfse:endpoint>
>>> <cxfse:pojo>
>>> <bean id="cxfServiceBean" class="notification.NotificationServiceImpl
>>> ">
>>> <property name="context" ref="context" />
>>> </bean>
>>> </cxfse:pojo>
>>> </cxfse:endpoint>
>>>
>>> According to the servicemix docs, it says I should be able to reference the
>>> context which was created as a parent bean.
>>>
>>> Is there an xsd I can look at for cxfse? I need to figure out how I can do
>>> interservice communication with it over the bus still.
>>>
>>>
>>>
>>
>>
>
>
>
Re: How to get the ComponentContext in CXF SU?
Posted by Guillaume Nodet <gn...@gmail.com>.
Freeman, I think being able to inject the endpoint DeliveryChannel and
ComponentContext is a really important feature. Can you raise a JIRA
for that please ?
On 9/20/07, Freeman Fang <fr...@iona.com> wrote:
> Hi Ryan,
>
> Attachment is the schema for servicemix-cxf-se.
>
> So far the cxf-se is not exactly same as jsr-181 service engine, so I
> think now we don't support it.
> Also I investigate the jsr-181 client proxy issue you mentioned in
> previous mail, we don't support it in cxf se neither, sorry for
> misleading previous response.
> The main purpose we add cxf-bc and cxf-se is leverage cxf ws-* features.
> You can see the tests and examples how the typical scenario looks like.
>
> If you need any feature we don't support now, please fill jira issue.
>
> Best Regards
>
> Freeman
>
> Ryan Moquin wrote:
> > I'm still having a hard time figuring out how to replicated my interservice
> > communication through the bus between two CXF services in Servicemix. My
> > latest problem is that this doesn't appear to work:
> >
> > <cxfse:endpoint>
> > <cxfse:pojo>
> > <bean id="cxfServiceBean" class="notification.NotificationServiceImpl
> > ">
> > <property name="context" ref="context" />
> > </bean>
> > </cxfse:pojo>
> > </cxfse:endpoint>
> >
> > According to the servicemix docs, it says I should be able to reference the
> > context which was created as a parent bean.
> >
> > Is there an xsd I can look at for cxfse? I need to figure out how I can do
> > interservice communication with it over the bus still.
> >
> >
>
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: How to get the ComponentContext in CXF SU?
Posted by Freeman Fang <fr...@iona.com>.
Hi Ryan,
Some system test code which maybe helpful is in servicemix-cxf-bc
bindingcomponent.
Best Regards
Freeman
Ryan Moquin wrote:
> Great, thanks. I decided to grab the servicemix source and start looking
> through it (I was doing it on the web which was a pain). I'm noticing that
> there are a lot of differences between the jsr181 and cxf se. I only
> noticed one unit test for cxf se, and it didn't seem to do much, so I'm not
> sure if there is another area in Servicemix I should be looking at.
>
> I'll go ahead and file a jira report for things as I find I really need
> them. As of this point, I converted all my jsr181 SUs to CXF and I'm not
> sure that was a good idea since I now lost all the features I thought I
> would retain when I upgraded. I think I might be ok though, but I think I
> can still send notifications from my CXF services like this:
>
> try {
> ClientFactory factory = (ClientFactory) new InitialContext().lookup(
> ClientFactory.DEFAULT_JNDI_NAME);
> this.client = factory.createClient();
> this.wsnBroker = new NotificationBroker(client);
> }catch(Exception ne) {
> LOGGER.error("Couldn't look up the servicemix client, notifications
> will be unavailable.", ne);
> }
>
> Trying it out now, I'm hoping that it will work so I can finally get to
> trying to receive the notifications.
>
> On 9/19/07, Freeman Fang <fr...@iona.com> wrote:
>
>> Hi Ryan,
>>
>> Attachment is the schema for servicemix-cxf-se.
>>
>> So far the cxf-se is not exactly same as jsr-181 service engine, so I
>> think now we don't support it.
>> Also I investigate the jsr-181 client proxy issue you mentioned in
>> previous mail, we don't support it in cxf se neither, sorry for
>> misleading previous response.
>> The main purpose we add cxf-bc and cxf-se is leverage cxf ws-* features.
>> You can see the tests and examples how the typical scenario looks like.
>>
>> If you need any feature we don't support now, please fill jira issue.
>>
>> Best Regards
>>
>> Freeman
>>
>> Ryan Moquin wrote:
>>
>>> I'm still having a hard time figuring out how to replicated my
>>>
>> interservice
>>
>>> communication through the bus between two CXF services in
>>>
>> Servicemix. My
>>
>>> latest problem is that this doesn't appear to work:
>>>
>>> <cxfse:endpoint>
>>> <cxfse:pojo>
>>> <bean id="cxfServiceBean" class="
>>>
>> notification.NotificationServiceImpl
>>
>>> ">
>>> <property name="context" ref="context" />
>>> </bean>
>>> </cxfse:pojo>
>>> </cxfse:endpoint>
>>>
>>> According to the servicemix docs, it says I should be able to reference
>>>
>> the
>>
>>> context which was created as a parent bean.
>>>
>>> Is there an xsd I can look at for cxfse? I need to figure out how I can
>>>
>> do
>>
>>> interservice communication with it over the bus still.
>>>
>>>
>>>
>>
>>
>
>
Re: How to get the ComponentContext in CXF SU?
Posted by Ryan Moquin <fr...@gmail.com>.
Great, thanks. I decided to grab the servicemix source and start looking
through it (I was doing it on the web which was a pain). I'm noticing that
there are a lot of differences between the jsr181 and cxf se. I only
noticed one unit test for cxf se, and it didn't seem to do much, so I'm not
sure if there is another area in Servicemix I should be looking at.
I'll go ahead and file a jira report for things as I find I really need
them. As of this point, I converted all my jsr181 SUs to CXF and I'm not
sure that was a good idea since I now lost all the features I thought I
would retain when I upgraded. I think I might be ok though, but I think I
can still send notifications from my CXF services like this:
try {
ClientFactory factory = (ClientFactory) new InitialContext().lookup(
ClientFactory.DEFAULT_JNDI_NAME);
this.client = factory.createClient();
this.wsnBroker = new NotificationBroker(client);
}catch(Exception ne) {
LOGGER.error("Couldn't look up the servicemix client, notifications
will be unavailable.", ne);
}
Trying it out now, I'm hoping that it will work so I can finally get to
trying to receive the notifications.
On 9/19/07, Freeman Fang <fr...@iona.com> wrote:
>
> Hi Ryan,
>
> Attachment is the schema for servicemix-cxf-se.
>
> So far the cxf-se is not exactly same as jsr-181 service engine, so I
> think now we don't support it.
> Also I investigate the jsr-181 client proxy issue you mentioned in
> previous mail, we don't support it in cxf se neither, sorry for
> misleading previous response.
> The main purpose we add cxf-bc and cxf-se is leverage cxf ws-* features.
> You can see the tests and examples how the typical scenario looks like.
>
> If you need any feature we don't support now, please fill jira issue.
>
> Best Regards
>
> Freeman
>
> Ryan Moquin wrote:
> > I'm still having a hard time figuring out how to replicated my
> interservice
> > communication through the bus between two CXF services in
> Servicemix. My
> > latest problem is that this doesn't appear to work:
> >
> > <cxfse:endpoint>
> > <cxfse:pojo>
> > <bean id="cxfServiceBean" class="
> notification.NotificationServiceImpl
> > ">
> > <property name="context" ref="context" />
> > </bean>
> > </cxfse:pojo>
> > </cxfse:endpoint>
> >
> > According to the servicemix docs, it says I should be able to reference
> the
> > context which was created as a parent bean.
> >
> > Is there an xsd I can look at for cxfse? I need to figure out how I can
> do
> > interservice communication with it over the bus still.
> >
> >
>
>
>
Re: How to get the ComponentContext in CXF SU?
Posted by Freeman Fang <fr...@iona.com>.
Hi Ryan,
Attachment is the schema for servicemix-cxf-se.
So far the cxf-se is not exactly same as jsr-181 service engine, so I
think now we don't support it.
Also I investigate the jsr-181 client proxy issue you mentioned in
previous mail, we don't support it in cxf se neither, sorry for
misleading previous response.
The main purpose we add cxf-bc and cxf-se is leverage cxf ws-* features.
You can see the tests and examples how the typical scenario looks like.
If you need any feature we don't support now, please fill jira issue.
Best Regards
Freeman
Ryan Moquin wrote:
> I'm still having a hard time figuring out how to replicated my interservice
> communication through the bus between two CXF services in Servicemix. My
> latest problem is that this doesn't appear to work:
>
> <cxfse:endpoint>
> <cxfse:pojo>
> <bean id="cxfServiceBean" class="notification.NotificationServiceImpl
> ">
> <property name="context" ref="context" />
> </bean>
> </cxfse:pojo>
> </cxfse:endpoint>
>
> According to the servicemix docs, it says I should be able to reference the
> context which was created as a parent bean.
>
> Is there an xsd I can look at for cxfse? I need to figure out how I can do
> interservice communication with it over the bus still.
>
>