> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jung
> , Dr. Christoph
> Sent: Friday, April 05, 2002 2:01 AM
> To: 'Bill Burke'
> Cc: '[EMAIL PROTECTED]'
> Subject: AW: [JBoss-dev] how do ejb proxies get marshalled in jboss.net?
>
>
> Hello Bill,
>
> Currently, there is no standard notion of a "remote reference type" inside
> SOAP. In JBoss.net, we have a means to
> to ship entity bean references as value objects, but that�s it for the
> moment and that goes beyond most of what
> has been presented at JavaOne where they usually restrict to
> plain stateless
> session beans as end-points.
>
> My impression that I already uttered in my talk at JBossOne is that Web
> Services have rarely been used yet to implement anything else besides a
> stock-ticker. The IdooXoap people I think are an exception in
> this respect.
>
> As a resolution to this lack (would certainly be needed to implement
> listener-callback patterns etc), one could imagine several approaches to
> represent remote references:
> - sub-type of URL which points to the web-service port.
> - a UDDI/disco entry
> - URL to the WSDL description of the service
>
> I have a few ideas in that respect, but I guess that this will
> have to wait
> after the JBoss.net 1.0 release.
>
> I�m still wondering what the immediate coupling of SOAP-Provider and
> ContainerInvoker would give you as advantage over
> the currently implemented (ab-)using of the in-VM RMI or IIOP stub
> invocation ... except maybe a bit of performance ...
> the restrictiveness of the Web-Service RPC-capabilities hints me to the
> intuition that maybe SOAP is not
> A full-blown transport in ist own right, but rather an optional
> and "on-top"
> way to go.
>
> Otherwise, if you have a compelling argument there, I�d be happy to help
> with the automatic registration of
> SoapContainerInvokers in the JBoss.net engine - which would give
> you a kind
> of nice Web-Service-on-bean-deployment mode.
> Since there is usually however much more needed to get a working
> Web-Service
> (type-mappings and all that stuff), we currently rather investigate the
> usage of xdoclet to let the web-service.xml and .wsr being generated at
> compile-time for your favourite web-ejbeans ...
>
(Marc, don't mean to speak for you, but I'll try).
I'm trying to work towards Marc vision of having the EJB Container sit on
the JMX invocation bus totally decoupled from the transport. What Marc
wants is the ability for one container to be able to receive requests from
IIOP, RMI, SOAP, XML-RPC, whatever, all at the same time. I think if we can
get this architecture right, JBoss will be able to move quickly and fluidly
in the market place to integrate with any distributed object framework. I
believe this architecture will allow JBoss to be not tied down into the J2EE
world and will allow it to venture into future protocols and distributed
object frameworks like SOAP/Webservices for example. YET, JBoss can also be
a link between future protocols and legacy(or soon to be legacy) protocols
like CORBA or EJB.
I was just pinging you to see how JBoss.net worked so that so that I could
implement the multi-invoker architecture as optimally as possible. In other
words, to make sure that what I'm doing will fit in with SOAP.
BTW, do you see any use integrating XML-RPC as an invoker? I used it
extensively before to pump messages over the internet into my EJBs. Wonder
if it has caught on at all....Its so easy to understand and implement.
Regards,
Bill.
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development