I haven't used it. Just wanted to make sure you did not miss if it could suit your needs.
Anyway, I've no problems with such a component. On Wed, Feb 11, 2009 at 17:24, <[email protected]> wrote: > Yes, I have already seen this. But : > - the development is not yet very active > - there is some limitation (it's not possible to make a kind of bridge and > connect to the component using pure RMI-IIOP) > - it's not a ServiceMix component :) > > From my point of view, it can be great that ServiceMix provide a large scope > of component (provided by SMX). > > What do you think ? > > Regards > JB > > On Wednesday 11 February 2009 - 17:06, Guillaume Nodet wrote: >> Have you had a look at http://jbi4corba.sourceforge.net/ ? >> >> On Wed, Feb 11, 2009 at 16:45, <[email protected]> wrote: >> > Hi all, >> > >> > I'm coming from a meeting with my development team and I have had an idea >> > (yes it's possible :)). >> > >> > I have two applications : >> > - backoffice >> > - frontoffice >> > >> > Currently, I use CXF-SE component to proxy EJBs from the backoffice and >> > publish it to the outside using HTTP component (it's the exactly what is >> > explained in the "Using EJB inside ServiceMix" tutorial). >> > >> > Now the frontoffice needs to use an EJB from the backoffice. But, to split >> > the stubs dependency, I have think to create a ServiceMix RMI-IIOP >> > component acting as a kind of RMI proxy (mainly for performance >> > reason and avoid mistake around CXF-SE interface writing). >> > >> > This component can work as a consumer or provider and will look like this : >> > >> > <classpath>jboss-all-client.jar</classpath> >> > >> > <rmi:consumer service="myService" >> > endpoint="test1" >> > jndiName="my/ejb" >> > jndiContextFactory="org.jnp.interfaces.NamingContextFactory" >> > jndiProviderUrl="jnp://localhost:1099"/> >> > >> > <rmi:provider service="myService" >> > endpoint="test2" >> > locationUri="rmi://localhost:1199" >> > targetService="myService" >> > targetEndpoint="test1"/> >> > >> > The consumer endpoint will create a NormalizedMessage with a CLOB in >> > content (containing marshaled data). On the other hand, the provider will >> > accept incoming RMI-IIOP connection to get the marshaled data (from >> > a NormalizedMessage provided by a RMI consimer). >> > >> > To be able to give mediation on this component, I have first think about >> > using CXF-SE as for a EJB but connecting localy to the RMI bound port. >> > >> > What do you think of that kind of component ? >> > Is it possible to use CXF directly on the NMR to exposed marshaled clob >> > directly using WSDL/SOAP ? >> > >> > Regards >> > JB >> > >> >> >> >> -- >> Cheers, >> Guillaume Nodet >> ------------------------ >> Blog: http://gnodet.blogspot.com/ >> ------------------------ >> Open Source SOA >> http://fusesource.com > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
