Hi Jm,
please note that JBOSS-ZOAP is not longer supported ...
-----Urspr�ngliche Nachricht-----
>Von: Jm Seigneur [mailto:[EMAIL PROTECTED]]
>Gesendet: Donnerstag, 26. Juli 2001 09:47
>An: [EMAIL PROTECTED]
>Betreff: [JBoss-user] JBOSS-ZOAP: questions on its features
>Hello,
>My question is about the features of the JBOSS-ZOAP features, so called:
>+ "Automatic-Mode" for Generating Deployment Meta-Data via Java Reflection.
>+ "Bootstrapping-Mode" for Reading Deployment Meta-Data.
>Does it mean that I don't need to deploy manually the SOAP service that
will
>interact with its related EJB?
right. By including the right container invoker (SoapContainerInvoker) into
your bean configuration, the bean
will be automatically registered and exported by the SOAP-HTTP-Server (and
unregistered, when the bean is undeployed). This holds for both modes. The
difference is that in the automatic mode, there is no additional mapping
data that must be specified in order to convert Java classes into XML and
vice versa (this is a default mapping generated by Java reflection). In the
bootstrap-mode, you deploy such mapping information with your bean jar and
the
container invoker will read it ...
>Put it another way, say I create a new EJB "myEJB", have I to create and
>deploy its
>SOAP service counterpart or not?
no, see above.
>By the way, what will be the equivalent of the normal client mode code
below
>in the
>SOAP client mode?
>Normal mode:
> ... myEJB = myEJBHome.findByPrimaryKey("myEJB.id");
> ... myEJB.doSomething();
>ZOAP mode:
> ... ??
If we would support entities, it would look the same, because the invocation
layer is RMI-compatible (kind of RMI-SOAP as opposed to RMI-JRMP or RMI-IIOP
;-) and hence transparent. But the frozen version of ZOAP only support
stateless beans
(see the documentation in CVS).
Best,
CGJ
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
