Yes francisco. You may have to massage your code a bit. I haven't look at your code, but I did notice you checked it into the old directory structure and may have tied your IIOP stuff to the old way of invoking on an EJB.
Bill > -----Original Message----- > From: marc fleury [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, March 20, 2002 10:55 AM > To: Bill Burke; Scott M Stark; [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] Multiple server configurations > > > oh good point, but that doesn't require "top level" > configuration, just drop > the iiop and jrmp and webservices and bla bla bla and it is all invocable, > it won't require configuration... > > good point, missed my own vision :) > > in other words francisco the 3.0 implementation of detached invokers > superseeds this, it needs a few tweeks in the factories (as we need > multiple homes) but we are almost there, > > he he > > marcf > > > > |-----Original Message----- > |From: [EMAIL PROTECTED] > |[mailto:[EMAIL PROTECTED]]On Behalf Of Bill > |Burke > |Sent: Wednesday, March 20, 2002 7:47 AM > |To: Scott M Stark; [EMAIL PROTECTED] > |Subject: RE: [JBoss-dev] Multiple server configurations > | > | > |In other words, one EJB can be accessible through IIOP, RMI, > SOAP, XML-RPC > |all at the same time. This is the future. Multiple MBean > |invokers, 1 MBean > |as per Marc's vision. > | > |Bill > | > |> -----Original Message----- > |> From: [EMAIL PROTECTED] > |> [mailto:[EMAIL PROTECTED]]On > Behalf Of Scott > |> M Stark > |> Sent: Wednesday, March 20, 2002 10:33 AM > |> To: [EMAIL PROTECTED] > |> Subject: Re: [JBoss-dev] Multiple server configurations > |> > |> > |> We will support multiple container invokers such that any > |> number of access protocols are available so being able to > |> run multiple configurations is not how this should be done. > |> > |> xxxxxxxxxxxxxxxxxxxxxxxx > |> Scott Stark > |> Chief Technology Officer > |> JBoss Group, LLC > |> xxxxxxxxxxxxxxxxxxxxxxxx > |> ----- Original Message ----- > |> From: "Francisco Reverbel" <[EMAIL PROTECTED]> > |> To: <[EMAIL PROTECTED]> > |> Sent: Tuesday, March 19, 2002 3:10 PM > |> Subject: [JBoss-dev] Multiple server configurations > |> > |> > |> > While working on the IIOP module, I have used an "IIOP server > |> > configuration" that turns IIOP into the default. > |> > > |> > Let me put it more clearly: by default, EJBs are deployed in a > |> > JRMP container. If I want an EJB to be deployed in an IIOP container, > |> > I must add to its jboss.xml file an element like > |> > > |> > <configuration-name>IIOP Stateless SessionBean</configuration-name> > |> > > |> > To avoid doing this for many EJBs, I created a special server > |> > configuration. This configuration has a modified standardjboss.xml, > |> > in which IIOP container configurations have "standard" > |> > container-names: "Standard Stateless SessionBean", and so on. > |> > JRMP container configurations have "non-standard" container-names: > |> > "JRMP Stateless SessionBean", and so on. > |> > > |> > |> > |> > |> _______________________________________________ > |> Jboss-development mailing list > |> [EMAIL PROTECTED] > |> https://lists.sourceforge.net/lists/listinfo/jboss-development > | > | > |_______________________________________________ > |Jboss-development mailing list > |[EMAIL PROTECTED] > |https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
