Thank you, Guillaume, for the fast action. I'll check it out and if any problems, will let you know. Does your bug fix extend to the bean component as well? IOW, will proxy without an explicit context also work in the bean-se or is just cxf-se?
Garry gnodet wrote: > > Well, it seems the proxy factory can accept other ways > to pass the context but due to a bug, these are not used at all. > Unfortunately, there is a small bug which prevents this use. > I've just fixed it so could you try building a snapshot of the cxf-se > component, install it, and try again using without the > context="#context" > attribute at all ? > > On Thu, Feb 21, 2008 at 11:50 PM, Garry <[EMAIL PROTECTED]> wrote: >> >> Well, I can only agree with you guys that consistency >> across the proxies would be great. I'm sure I don't >> understand all the issues involved, but it would be >> most convenient if the proxy context-injection >> happened automatically and the user didn't have to >> configure it at all. >> >> I'm getting my cxf-se information from this document >> http://servicemix.apache.org/servicemix-cxf-se.html. >> It says: >> >> You can use it from one of you client bean, or from >> inside another component, and call the JBI endpoint >> as a plain Java object. >> >> From a cxfse Service Unit, it could be used as >> following: ... >> >> which lead me to believe the example would work >> equally well (without change) in a non-cxfse container. >> Perhaps you could add a sentence making it clear the >> technique shown in the example works *only* in the >> cxf-se component? Might save the next person some >> time ... >> >> Thanks, Garry >> >> >> >> >> >> bsnyder wrote: >> > >> > On Thu, Feb 21, 2008 at 10:18 AM, Guillaume Nodet <[EMAIL PROTECTED]> >> > wrote: >> >> The problem is that the #context bean is not defined in >> servicemix-bean. >> >> We really need to make things a bit easier by having a homogeneous >> way >> >> to set up things in servicemix-bean, servicemix-cxf-se and >> >> servicemix-jsr181. >> >> It also involves injecting resources into beans, using >> @PostConstruct >> >> and >> >> @PreDestroy, etc. >> >> >> >> Anyway, to create a context, I'm not sure if there is a simple way >> >> currently but to >> >> create a spring factory bean that could create a valid one. Imho, >> it >> >> would be >> >> better to fix the #context problem instead. >> >> >> >> Look at how this is done in jsr181 or cxf-se: >> >> >> >> >> http://svn.apache.org/viewvc/servicemix/smx3/trunk/deployables/serviceengines/servicemix-jsr181/src/main/java/org/apache/servicemix/jsr181/Jsr181XBeanDeployer.java?view=markup >> >> >> >> >> http://svn.apache.org/viewvc/servicemix/smx3/trunk/deployables/serviceengines/servicemix-cxf-se/src/main/java/org/apache/servicemix/cxfse/CxfSeXBeanDeployer.java?revision=602826&view=markup >> >> >> >> It should be easy to do the same in servicemix-bean, and even have a >> >> single class to do that, or even do that for all components. >> > >> > Yeah it would be a nicer solution if we could do this for all >> > components so that it's consistent and not implemented in many places. >> > >> > Bruce >> > -- >> > perl -e 'print >> > unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" >> > );' >> > >> > Apache ActiveMQ - http://activemq.org/ >> > Apache Camel - http://activemq.org/camel/ >> > Apache ServiceMix - http://servicemix.org/ >> > Apache Geronimo - http://geronimo.apache.org/ >> > >> > Blog: http://bruceblog.org/ >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Can-use-cxf-proxy-outside-cxf-se-container--tp15604370s12049p15622032.html >> >> >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/Can-use-cxf-proxy-outside-cxf-se-container--tp15604370s12049p15657434.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
