dims,
Ok, will try to make this clearer :-). The JSR181 spec states in chapter
7 'Mapping JSR-181 to the J2EE 1.4 Runtime
Environment' exactly the scenarios that I was having in mind:
Example: I have an existing Session EJB and want to expose two of its
public methods as a Web service. Currently I have to write/generate the
service endpoint interface, the WSDL file, the webservices.xml
deployment descriptor, the jax-rpc-mapping.xml deployment descriptor and
entries in the ejb-jar.xml manually which is quite error-prone and
time-consuming.
Since the JSR181 was proposed to ease this complex process by
auto-generating the above artefacts, I was wondering if Beehive
currently supports this feature. Citation: "The JSR-181 processor
examines the annotations in each Web Service file
and uses this information to generate a JSR-109 deployment unit (EAR or
WAR file)."
Here is an code example I would think of (a simple Session EJB):
/
@WebService(targetNamespace="http://www.openuri.org/MyNamespace";
name="StaffDirectory")
public class StaffDirectoryEJBBean implements SessionBean {
private SessionContext _context;
public void ejbCreate() {}
public void ejbActivate() {}
public void ejbPassivate() {}
public void ejbRemove() {}
public void setSessionContext(SessionContext ctx) {
_context = ctx;
}
@WebMethod(operationName="GetStaffByDepartment")
public StaffBean[] getStaffByDepartment(String department) {
.... //StaffBean is a simple JavaBean (data container)
}
@WebMethod(operationName="SetStaffDetails")
public void setStaffDetails(StaffBean person) {
....
}
}/
Is it possible by simply adding those @WebService/@WebMethod annotations
to the EJB to generate an EAR archive containing all interfaces,
deployment descriptors and mappings required by J2EE 1.4?
As far as I am aware Geronimo currently integrates Axis as a module to
provide J2EE 1.4-compliant Web services support. Using Axis as a
standalone application within Geronimo (I believe that's what happens
with Tomcat/Axis at the moment) is not what I had in mind.
I hope this is clearer :-).
Thanks,
Stefan
Davanum Srinivas wrote:
Stefan,
Beehive contains an implementation of JSR181 based on Axis. It does
not do any of the J2EE stuff like JSR 109. Am still confused on what
exactly you need. WSS4J does implement WS-Security for use with Axis.
Binary attachments are already in Axis. We have some code in EWS
project that can generate axis wsdd given a jaxrpc mapping file (and
maybe a bunch of ther related things as well). Please explain in
simple terms what you are looking for. Example: we have POJO's that
needs to be exposed as web services, we may need to deploy the code
independent of the soap stack used internally in any J2EE container
(?)
thanks,
dims
On 6/29/05, Stefan Schmidt <[EMAIL PROTECTED]> wrote:
Thanks Eddie and Jeremy for the information. So I gather that Beehive is
currently not supported due to the VM restraints. I hope that this is
going to change soon :-).
Eddie: I think that since Geronimo is looking at full J2EE 1.4
compliance JAX-RPC is definetely the way to go here, but I am not a
specialist in Geronimo matters. Is Beehive currently able to generate
all JAX-RPC required artefacts such as:
* a WSDL document
* a JAX-RPC mapping file
* a Web service descriptor file (webservices.xml)
Also, does Beehive currently support both, EJB endpoints and JAX-RPC
service endpoints (witch reside in front of a servlet or POJO)? What
about Web services that make usage of more complex structures such as
JavaBeans or Arrays of JavaBeans, binary attachments and WS-Security -
does Beehive support these (more advanced) features as well? I am
especially looking for the auto-generation of JAX-RPC mapping files in
this case because they tend to become quite complex when using those
features.
Stefan
Jeremy Boynes wrote:
Eddie ONeil wrote:
From the Geronimo side, how well is the Java 5 VM supported?
Right now it isn't due to issues with CORBA. We hope to fix this soon.
--
Jeremy
