You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jaxme-dev@ws.apache.org by Davanum Srinivas <di...@yahoo.com> on 2004/02/03 19:03:19 UTC
RE: Status of code in EWS
CC'ing jaxme-dev.
Ias, can you please send jochen enough information to recreate the problem?
thanks,
dims
--- Ias <ia...@tmax.co.kr> wrote:
> > Thanks for help dims;
> >
> > Ias what do you think about jaxme, I will replace our JAXB
> > code with JAXME.
>
> I tested schema-binding compiling the JAX-RPC mapping schema with the latest
> (CVS) JaxMe. I fixed some bug related to handling QName thanks to the test.
> Unfortunately, we have one missing part from the generated codes.
>
> Sun's JAXB RI 1.0 generates JavaWsdlMappingType like
>
> public interface JavaWsdlMappingType {
> java.util.List
> getServiceInterfaceMappingAndServiceEndpointInterfaceMapping();
> java.util.List getExceptionMapping();
> java.math.BigDecimal getVersion();
> void setVersion(java.math.BigDecimal value);
> java.util.List getPackageMapping();
> java.util.List getJavaXmlTypeMapping();
> java.lang.String getId();
> void setId(java.lang.String value);
> public interface ServiceEndpointInterfaceMapping
> extends javax.xml.bind.Element,
> org.apache.axis.jaxrpcmapping.descriptor.ServiceEndpointInterfaceMappingType
> {
>
>
> }
> public interface ServiceInterfaceMapping
> extends javax.xml.bind.Element,
> org.apache.axis.jaxrpcmapping.descriptor.ServiceInterfaceMappingType
> {
>
>
> }
>
> }
>
> On the other hand, in case of JaxMe,
>
> public interface JavaWsdlMappingType {
> public java.math.BigDecimal getVersion();
> public void setVersion(java.math.BigDecimal pVersion);
> public java.lang.String getId();
> public void setId(java.lang.String pId);
> public java.util.List getPackageMapping();
> public java.util.List getJavaXmlTypeMapping();
> public java.util.List getExceptionMapping();
> public
> org.apache.axis.jaxrpcmapping.descriptor.ServiceInterfaceMappingType
> getServiceInterfaceMapping();
> public void
> setServiceInterfaceMapping(org.apache.axis.jaxrpcmapping.descriptor.ServiceI
> nterfaceMappingType pServiceInterfaceMapping);
> public java.util.List getServiceEndpointInterfaceMapping();
> }
>
> There's a crucial difference between them regarding
> ServiceEndpointInterfaceMapping and ServiceInterfaceMapping. In order for
> JaxMe to catch up with RI, we need to implement more JAXB stuffs on JaxMe.
> In that sense I think JAXB 1.0 TCK helps us a lot since usually concrete
> assertions and test cases are clearer than an abstract spec with regard to
> understanding a technology in question.
>
> Thanks,
>
> Ias
>
> >
> > I add the brif info to the wiki. I will wait for Richard and
> > raised the issue of architecure in the geranimo dev list.
> >
> > Thanks
> >
> > Srinath
> >
> >
> > > Srinath,
> > >
> > > i'd say replace JAXB with JaxMe and report bugs to
> > jaxme-dev@ mailing
> > > list. don't worry about releases just yet. use the code in
> > jaxme cvs.
> > >
> > > thanks,
> > > dims
> > >
> > > --- Srinath Perera <he...@opensource.lk> wrote:
> > >>
> > >> > We need to make the process visible to others, even the work-in
> > >> progress documents should be on public view. Can you
> > please add the
> > >> current thoughts to wiki?
> > >> > (http://wiki.apache.org/geronimo/EnterpriseWebServices) Also,
> > >> > please
> > >> use geronimo-dev mailing list to discuss details of the
> > >> implementation.
> > >>
> > >> Thanks for point it out, yap I have been lonely for some time with
> > >> this. I will add current thoughts to wiki
> > >>
> > >> > Question: does code in contrib module depend in any way on the
> > >> jax-rpc-mapper? (when we generated code? or at runtime?)
> > >>
> > >> yes(generated code) , to genarate Ws ws4j2ee use jaxrpc-mapper
> > >> instead of WSDL2Java as it needs the jaxrpc mapping
> > support. But code
> > >> uses JAXB .. we have to wait to JAXME to come out.
> > >>
> > >> thanks
> > >>
> > >> Srinath
> > >>
> > >>
> > >> > --- Srinath Perera <he...@opensource.lk> wrote:
> > >> >> Hi Dims;
> > >> >>
> > >> >> I will brief the contrib module, (To my knowladge the
> > jaxrpcmapper
> > >> is WSDL2Java with the jaxrpcmapping support, :) )
> > >> >>
> > >> >> the code at ws4j2ee cover the server side JSR109 to great deal.
> > >> (there are lot of refactoring to be done.) I will give brief
> > >> description in the bottem about it.
> > >> >>
> > >> >> But as pointed out by Richard, acsessing the ejb though
> > the remote
> > >> interface seem to be a mistake. So we might need to find way to
> > >> acsess the directly using the geranimo internals. So the
> > state of the
> > >> project depend on that decission.
> > >> >>
> > >> >> I cc the reply to Richard and let us add him in to this
> > discussion
> > >> as well.
> > >> >>
> > >> >> the adjusemnt I am going to discuss with Richard is avalible in
> > >> http://ws.apache.org/~hemapani/jsr109/docs/revisedProposal.html
> > >> (please note this doc is just temory thing and still not
> > ready to go
> > >> to public.)
> > >> >>
> > >> >> Thanks
> > >> >>
> > >> >> Srinath
> > >> >>
> > >> >>
> > >> >> --------------------------------contrib module
> > >> >> ---------------------------- the ws4j2ee will be a tool that
> > >> genarates the ejb and webservices classes and the deployment
> > >> discriptors starting fom a WSDL and other DD or ejb.
> > >> >>
> > >> >> 1) (webservice.xml + jaxrpcmapper + wsdlfile)
> > --ws4j2ee-> ejb + ws
> > >> + deploy.wsdd + ejb-jar.xml
> > >> >> Parse the webservice xml, find other DD and wsdl call
> > the jaxrpc
> > >> >> mapper to genarte the ws classes populate the information taken
> > >> >> form the DD in the j2eeWsContext
> > >> using the populated information generate the rest of the
> > classes DD's
> > >> >>
> > >> >>
> > >> >> 2) ejb + ejb-jar.xml + command line options --ws4j2ee->
> > >> >> (webservice.xml + jaxrpcmapper + wsdlfile) + ws + deploy.wsdd
> > >> >> using
> > >> the ejb generate the WSDL file
> > >> >> using the populate information and + command line options infer
> > >> >> the
> > >> DD. the information that can't infer will assumed.
> > >> >> generate the DD
> > >> >> generate the ws using the jaxrpcmapper with wsdl there
> > will be a
> > >> >> build file generated that would automate the
> > >> packaging
> > >> -------------------------------------------------------------------
> > >> >>
> > >> >>
> > >> >> > Srinath, Ias,
> > >> >> >
> > >> >> > i see two modules contrib and jax-rpc-mapper in ews's CVS. can
> > >> you
> > >> >> guys please give me a short overview of each, how they relate to
> > >> one another and what work is left to be done.
> > >> >> >
> > >> >> > Thanks,
> > >> >> > dims
> > >> >> >
> > >> >> > =====
> > >> >> > Davanum Srinivas - http://webservices.apache.org/~dims/
> > >> >>
> > >> >>
> > >> >> ------------------------------------
> > >> >> Lanka Sofware Foundation
> > >> >> ------------------------------------
> > >> >>
> > >> >>
> > >> >
> > >> >
> > >> > =====
> > >> > Davanum Srinivas - http://webservices.apache.org/~dims/
>
=== message truncated ===
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
Re: Status of code in EWS
Posted by Jochen Wiedmann <jo...@ispsoft.de>.
Davanum Srinivas wrote:
> While we are at it....There's one more suite -
> http://www.w3.org/2001/05/xmlschema-test-collection/ this has xsd's from SUN and MSFT as well. It
> has xsd's and sample xml's conforming to those xsd's.
I remember that we discussed that. The examples it has would be much better
for validating a parser, because they also contain examples that the parser
should reject.
The problem with that is, that it does not contain automatically readable
files that tell you, whether a given example should fail or not. It does
contain manually readable documentation, but nothing else. I've been sending
mail twice to Henry Thompson, the test collections maintainer, but did not
get a response.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
Re: Status of code in EWS
Posted by Davanum Srinivas <di...@yahoo.com>.
While we are at it....There's one more suite -
http://www.w3.org/2001/05/xmlschema-test-collection/ this has xsd's from SUN and MSFT as well. It
has xsd's and sample xml's conforming to those xsd's.
-- dims
--- Jochen Wiedmann <jo...@ispsoft.de> wrote:
>
> Hi, Dims,
>
> Davanum Srinivas wrote:
>
> > Have you taken a peek at the Schema parsing code in XmlSchema?
> > (http://cvs.apache.org/viewcvs.cgi/ws-axis/proposals/XmlSchema/) FYI, The code is able to LOAD
> AND
> > SAVE all the NIST schema test cases i keep point you to :)
>
> that doesn't impress me too much. I have just committed a test case for
> parsing the NIST xsd files and JaxMeXS parses all 1177 files very well.
> However, the NIST test is not so much a test for parsing an instance of XML
> Schema, but for validating conforming (or non conforming) instances. In
> other words: Parsing these files is almost trivial.
>
> IMO XmlSchema is rather close to JaxMeXS, perhaps with a little bit
> more emphasis on strictness and the ability to save a schema. (In
> other words, for usability in an XML Schema editor.) On the other
> hand, it lacks the logical layer of JaxMeXS with features like
> canonicalization and the ability to extend the language.
>
>
> Jochen
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
Re: Status of code in EWS
Posted by Jochen Wiedmann <jo...@ispsoft.de>.
Hi, Dims,
Davanum Srinivas wrote:
> Have you taken a peek at the Schema parsing code in XmlSchema?
> (http://cvs.apache.org/viewcvs.cgi/ws-axis/proposals/XmlSchema/) FYI, The code is able to LOAD AND
> SAVE all the NIST schema test cases i keep point you to :)
that doesn't impress me too much. I have just committed a test case for
parsing the NIST xsd files and JaxMeXS parses all 1177 files very well.
However, the NIST test is not so much a test for parsing an instance of XML
Schema, but for validating conforming (or non conforming) instances. In
other words: Parsing these files is almost trivial.
IMO XmlSchema is rather close to JaxMeXS, perhaps with a little bit
more emphasis on strictness and the ability to save a schema. (In
other words, for usability in an XML Schema editor.) On the other
hand, it lacks the logical layer of JaxMeXS with features like
canonicalization and the ability to extend the language.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
Re: Status of code in EWS
Posted by Davanum Srinivas <di...@yahoo.com>.
Jochen,
Have you taken a peek at the Schema parsing code in XmlSchema?
(http://cvs.apache.org/viewcvs.cgi/ws-axis/proposals/XmlSchema/) FYI, The code is able to LOAD AND
SAVE all the NIST schema test cases i keep point you to :)
-- dims
--- Jochen Wiedmann <jo...@ispsoft.de> wrote:
> Ias wrote:
>
> > Note that
> > particularly this difference happens when a nested model group (sequence,
> > choice, all) has minOccurs=0 or maxOccurs>1. For example,
>
> I know that nested groups are still a problem. (Had the experience
> just yesterday.) However, IMO, we won't be able to attach this problem
> without a simple parser generator. This applies to handling of wildcard
> elements as well as nested groups.
>
> If someone advices me on the generation of an (event driven!) state
> machine, I'll be happy to take it and go that way. If anyone has
> a suggestion how to create the state machine manually, fine for me.
> It is just that I find these things to complex for saying "Hej, I
> support flat sequences and choices and nested groups, if they mach
> that certain category."
>
>
> Sorry,
>
> Jochen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: jaxme-dev-help@ws.apache.org
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
Re: Status of code in EWS
Posted by Jochen Wiedmann <jo...@ispsoft.de>.
Ias wrote:
> Note that
> particularly this difference happens when a nested model group (sequence,
> choice, all) has minOccurs=0 or maxOccurs>1. For example,
I know that nested groups are still a problem. (Had the experience
just yesterday.) However, IMO, we won't be able to attach this problem
without a simple parser generator. This applies to handling of wildcard
elements as well as nested groups.
If someone advices me on the generation of an (event driven!) state
machine, I'll be happy to take it and go that way. If anyone has
a suggestion how to create the state machine manually, fine for me.
It is just that I find these things to complex for saying "Hej, I
support flat sequences and choices and nested groups, if they mach
that certain category."
Sorry,
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
RE: Status of code in EWS
Posted by Ias <ia...@tmax.co.kr>.
> > > There's a crucial difference between them regarding
> > > ServiceEndpointInterfaceMapping and
> > ServiceInterfaceMapping. In order
> > > for JaxMe to catch up with RI, we need to implement more
> > JAXB stuffs on JaxMe.
Note that
particularly this difference happens when a nested model group (sequence,
choice, all) has minOccurs=0 or maxOccurs>1. For example,
<xsd:sequence>
<xsd:element name="package-mapping"
type="j2ee:package-mappingType"
minOccurs="1" maxOccurs="unbounded"/>
<xsd:element name="java-xml-type-mapping"
type="j2ee:java-xml-type-mappingType"
minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="exception-mapping"
type="j2ee:exception-mappingType"
minOccurs="0" maxOccurs="unbounded"/>
<xsd:sequence minOccurs="0" maxOccurs="unbounded">
<xsd:element name="service-interface-mapping"
type="j2ee:service-interface-mappingType"
minOccurs="0" maxOccurs="1"/>
<xsd:element name="service-endpoint-interface-mapping"
type="j2ee:service-endpoint-interface-mappingType"
minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:sequence>
lead to the difference I pointed out. Very interestingly, if the above model
is
<xsd:sequence>
<xsd:element name="package-mapping"
type="j2ee:package-mappingType"
minOccurs="1" maxOccurs="unbounded"/>
<xsd:element name="java-xml-type-mapping"
type="j2ee:java-xml-type-mappingType"
minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="exception-mapping"
type="j2ee:exception-mappingType"
minOccurs="0" maxOccurs="unbounded"/>
<xsd:sequence>
<xsd:element name="service-interface-mapping"
type="j2ee:service-interface-mappingType"
minOccurs="0" maxOccurs="1"/>
<xsd:element name="service-endpoint-interface-mapping"
type="j2ee:service-endpoint-interface-mappingType"
minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:sequence>
The difference disappears. :-)
JAXB 1.0 spec Appendix C.4 doesn't talk about such a situation, but actually
works for it. I'd like to ask JAXB spec and RI folks about the issue.
Thanks,
Ias
> > > In that sense I think JAXB 1.0 TCK helps us a lot since usually
> > > concrete assertions and test cases are clearer than an
> > abstract spec
> > > with regard to understanding a technology in question.
> > >
> > > Thanks,
> > >
> > > Ias
> > >
> > > >
> > > > I add the brif info to the wiki. I will wait for Richard
> > and raised
> > > > the issue of architecure in the geranimo dev list.
> > > >
> > > > Thanks
> > > >
> > > > Srinath
> > > >
> > > >
> > > > > Srinath,
> > > > >
> > > > > i'd say replace JAXB with JaxMe and report bugs to
> > > > jaxme-dev@ mailing
> > > > > list. don't worry about releases just yet. use the code in
> > > > jaxme cvs.
> > > > >
> > > > > thanks,
> > > > > dims
> > > > >
> > > > > --- Srinath Perera <he...@opensource.lk> wrote:
> > > > >>
> > > > >> > We need to make the process visible to others, even
> > the work-in
> > > > >> progress documents should be on public view. Can you
> > > > please add the
> > > > >> current thoughts to wiki?
> > > > >> >
> > (http://wiki.apache.org/geronimo/EnterpriseWebServices) Also,
> > > > >> > please
> > > > >> use geronimo-dev mailing list to discuss details of the
> > > > >> implementation.
> > > > >>
> > > > >> Thanks for point it out, yap I have been lonely for
> some time
> > > > >> with this. I will add current thoughts to wiki
> > > > >>
> > > > >> > Question: does code in contrib module depend in any
> > way on the
> > > > >> jax-rpc-mapper? (when we generated code? or at runtime?)
> > > > >>
> > > > >> yes(generated code) , to genarate Ws ws4j2ee use
> jaxrpc-mapper
> > > > >> instead of WSDL2Java as it needs the jaxrpc mapping
> > > > support. But code
> > > > >> uses JAXB .. we have to wait to JAXME to come out.
> > > > >>
> > > > >> thanks
> > > > >>
> > > > >> Srinath
> > > > >>
> > > > >>
> > > > >> > --- Srinath Perera <he...@opensource.lk> wrote:
> > > > >> >> Hi Dims;
> > > > >> >>
> > > > >> >> I will brief the contrib module, (To my knowladge the
> > > > jaxrpcmapper
> > > > >> is WSDL2Java with the jaxrpcmapping support, :) )
> > > > >> >>
> > > > >> >> the code at ws4j2ee cover the server side JSR109 to
> > great deal.
> > > > >> (there are lot of refactoring to be done.) I will give brief
> > > > >> description in the bottem about it.
> > > > >> >>
> > > > >> >> But as pointed out by Richard, acsessing the ejb though
> > > > the remote
> > > > >> interface seem to be a mistake. So we might need to
> > find way to
> > > > >> acsess the directly using the geranimo internals. So the
> > > > state of the
> > > > >> project depend on that decission.
> > > > >> >>
> > > > >> >> I cc the reply to Richard and let us add him in to this
> > > > discussion
> > > > >> as well.
> > > > >> >>
> > > > >> >> the adjusemnt I am going to discuss with Richard is
> > avalible
> > > > >> >> in
> > > > >>
> http://ws.apache.org/~hemapani/jsr109/docs/revisedProposal.html
> > > > >> (please note this doc is just temory thing and still not
> > > > ready to go
> > > > >> to public.)
> > > > >> >>
> > > > >> >> Thanks
> > > > >> >>
> > > > >> >> Srinath
> > > > >> >>
> > > > >> >>
> > > > >> >> --------------------------------contrib module
> > > > >> >> ---------------------------- the ws4j2ee will be
> a tool that
> > > > >> genarates the ejb and webservices classes and the deployment
> > > > >> discriptors starting fom a WSDL and other DD or ejb.
> > > > >> >>
> > > > >> >> 1) (webservice.xml + jaxrpcmapper + wsdlfile)
> > > > --ws4j2ee-> ejb + ws
> > > > >> + deploy.wsdd + ejb-jar.xml
> > > > >> >> Parse the webservice xml, find other DD and wsdl call
> > > > the jaxrpc
> > > > >> >> mapper to genarte the ws classes populate the information
> > > > >> >> taken form the DD in the j2eeWsContext
> > > > >> using the populated information generate the rest of the
> > > > classes DD's
> > > > >> >>
> > > > >> >>
> > > > >> >> 2) ejb + ejb-jar.xml + command line options --ws4j2ee->
> > > > >> >> (webservice.xml + jaxrpcmapper + wsdlfile) + ws +
> > deploy.wsdd
> > > > >> >> using
> > > > >> the ejb generate the WSDL file
> > > > >> >> using the populate information and + command line options
> > > > >> >> infer the
> > > > >> DD. the information that can't infer will assumed.
> > > > >> >> generate the DD
> > > > >> >> generate the ws using the jaxrpcmapper with wsdl there
> > > > will be a
> > > > >> >> build file generated that would automate the
> > > > >> packaging
> > > > >>
> > -----------------------------------------------------------------
> > > > >> --
> > > > >> >>
> > > > >> >>
> > > > >> >> > Srinath, Ias,
> > > > >> >> >
> > > > >> >> > i see two modules contrib and jax-rpc-mapper in
> > ews's CVS.
> > > > >> >> > can
> > > > >> you
> > > > >> >> guys please give me a short overview of each, how
> > they relate
> > > > >> >> to
> > > > >> one another and what work is left to be done.
> > > > >> >> >
> > > > >> >> > Thanks,
> > > > >> >> > dims
> > > > >> >> >
> > > > >> >> > =====
> > > > >> >> > Davanum Srinivas - http://webservices.apache.org/~dims/
> > > > >> >>
> > > > >> >>
> > > > >> >> ------------------------------------
> > > > >> >> Lanka Sofware Foundation
> > > > >> >> ------------------------------------
> > > > >> >>
> > > > >> >>
> > > > >> >
> > > > >> >
> > > > >> > =====
> > > > >> > Davanum Srinivas - http://webservices.apache.org/~dims/
> > >
> > === message truncated ===
> >
> >
> > =====
> > Davanum Srinivas - http://webservices.apache.org/~dims/
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: jaxme-dev-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: jaxme-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
RE: Status of code in EWS
Posted by Ias <ia...@tmax.co.kr>.
> Ias, can you please send jochen enough information to
> recreate the problem?
>
I just finished the environment of the recreation. Please check out
"jax-rpc-mapper" module from http://sourceforge.net/cvs/?group_id=93657 ,
update jaxme.properties at src/bind for your PC and run ant at
src/bind/jaxme. Note that you need to resolve QName problem described at
http://marc.theaimsgroup.com/?l=jaxme-dev&m=107580898830873&w=2 if you want
to compile the generated source codes.
Ias
> thanks,
> dims
>
> --- Ias <ia...@tmax.co.kr> wrote:
> > > Thanks for help dims;
> > >
> > > Ias what do you think about jaxme, I will replace our
> JAXB code with
> > > JAXME.
> >
> > I tested schema-binding compiling the JAX-RPC mapping
> schema with the
> > latest
> > (CVS) JaxMe. I fixed some bug related to handling QName
> thanks to the test.
> > Unfortunately, we have one missing part from the generated codes.
> >
> > Sun's JAXB RI 1.0 generates JavaWsdlMappingType like
> >
> > public interface JavaWsdlMappingType {
> > java.util.List
> > getServiceInterfaceMappingAndServiceEndpointInterfaceMapping();
> > java.util.List getExceptionMapping();
> > java.math.BigDecimal getVersion();
> > void setVersion(java.math.BigDecimal value);
> > java.util.List getPackageMapping();
> > java.util.List getJavaXmlTypeMapping();
> > java.lang.String getId();
> > void setId(java.lang.String value);
> > public interface ServiceEndpointInterfaceMapping
> > extends javax.xml.bind.Element,
> >
> org.apache.axis.jaxrpcmapping.descriptor.ServiceEndpointInterf
> aceMappingType
> > {
> >
> >
> > }
> > public interface ServiceInterfaceMapping
> > extends javax.xml.bind.Element,
> > org.apache.axis.jaxrpcmapping.descriptor.ServiceInterfaceMappingType
> > {
> >
> >
> > }
> >
> > }
> >
> > On the other hand, in case of JaxMe,
> >
> > public interface JavaWsdlMappingType {
> > public java.math.BigDecimal getVersion();
> > public void setVersion(java.math.BigDecimal pVersion);
> > public java.lang.String getId();
> > public void setId(java.lang.String pId);
> > public java.util.List getPackageMapping();
> > public java.util.List getJavaXmlTypeMapping();
> > public java.util.List getExceptionMapping();
> > public
> > org.apache.axis.jaxrpcmapping.descriptor.ServiceInterfaceMappingType
> > getServiceInterfaceMapping();
> > public void
> >
> setServiceInterfaceMapping(org.apache.axis.jaxrpcmapping.descriptor.Se
> > rviceI nterfaceMappingType pServiceInterfaceMapping);
> > public java.util.List getServiceEndpointInterfaceMapping();
> > }
> >
> > There's a crucial difference between them regarding
> > ServiceEndpointInterfaceMapping and
> ServiceInterfaceMapping. In order
> > for JaxMe to catch up with RI, we need to implement more
> JAXB stuffs on JaxMe.
> > In that sense I think JAXB 1.0 TCK helps us a lot since usually
> > concrete assertions and test cases are clearer than an
> abstract spec
> > with regard to understanding a technology in question.
> >
> > Thanks,
> >
> > Ias
> >
> > >
> > > I add the brif info to the wiki. I will wait for Richard
> and raised
> > > the issue of architecure in the geranimo dev list.
> > >
> > > Thanks
> > >
> > > Srinath
> > >
> > >
> > > > Srinath,
> > > >
> > > > i'd say replace JAXB with JaxMe and report bugs to
> > > jaxme-dev@ mailing
> > > > list. don't worry about releases just yet. use the code in
> > > jaxme cvs.
> > > >
> > > > thanks,
> > > > dims
> > > >
> > > > --- Srinath Perera <he...@opensource.lk> wrote:
> > > >>
> > > >> > We need to make the process visible to others, even
> the work-in
> > > >> progress documents should be on public view. Can you
> > > please add the
> > > >> current thoughts to wiki?
> > > >> >
> (http://wiki.apache.org/geronimo/EnterpriseWebServices) Also,
> > > >> > please
> > > >> use geronimo-dev mailing list to discuss details of the
> > > >> implementation.
> > > >>
> > > >> Thanks for point it out, yap I have been lonely for some time
> > > >> with this. I will add current thoughts to wiki
> > > >>
> > > >> > Question: does code in contrib module depend in any
> way on the
> > > >> jax-rpc-mapper? (when we generated code? or at runtime?)
> > > >>
> > > >> yes(generated code) , to genarate Ws ws4j2ee use jaxrpc-mapper
> > > >> instead of WSDL2Java as it needs the jaxrpc mapping
> > > support. But code
> > > >> uses JAXB .. we have to wait to JAXME to come out.
> > > >>
> > > >> thanks
> > > >>
> > > >> Srinath
> > > >>
> > > >>
> > > >> > --- Srinath Perera <he...@opensource.lk> wrote:
> > > >> >> Hi Dims;
> > > >> >>
> > > >> >> I will brief the contrib module, (To my knowladge the
> > > jaxrpcmapper
> > > >> is WSDL2Java with the jaxrpcmapping support, :) )
> > > >> >>
> > > >> >> the code at ws4j2ee cover the server side JSR109 to
> great deal.
> > > >> (there are lot of refactoring to be done.) I will give brief
> > > >> description in the bottem about it.
> > > >> >>
> > > >> >> But as pointed out by Richard, acsessing the ejb though
> > > the remote
> > > >> interface seem to be a mistake. So we might need to
> find way to
> > > >> acsess the directly using the geranimo internals. So the
> > > state of the
> > > >> project depend on that decission.
> > > >> >>
> > > >> >> I cc the reply to Richard and let us add him in to this
> > > discussion
> > > >> as well.
> > > >> >>
> > > >> >> the adjusemnt I am going to discuss with Richard is
> avalible
> > > >> >> in
> > > >> http://ws.apache.org/~hemapani/jsr109/docs/revisedProposal.html
> > > >> (please note this doc is just temory thing and still not
> > > ready to go
> > > >> to public.)
> > > >> >>
> > > >> >> Thanks
> > > >> >>
> > > >> >> Srinath
> > > >> >>
> > > >> >>
> > > >> >> --------------------------------contrib module
> > > >> >> ---------------------------- the ws4j2ee will be a tool that
> > > >> genarates the ejb and webservices classes and the deployment
> > > >> discriptors starting fom a WSDL and other DD or ejb.
> > > >> >>
> > > >> >> 1) (webservice.xml + jaxrpcmapper + wsdlfile)
> > > --ws4j2ee-> ejb + ws
> > > >> + deploy.wsdd + ejb-jar.xml
> > > >> >> Parse the webservice xml, find other DD and wsdl call
> > > the jaxrpc
> > > >> >> mapper to genarte the ws classes populate the information
> > > >> >> taken form the DD in the j2eeWsContext
> > > >> using the populated information generate the rest of the
> > > classes DD's
> > > >> >>
> > > >> >>
> > > >> >> 2) ejb + ejb-jar.xml + command line options --ws4j2ee->
> > > >> >> (webservice.xml + jaxrpcmapper + wsdlfile) + ws +
> deploy.wsdd
> > > >> >> using
> > > >> the ejb generate the WSDL file
> > > >> >> using the populate information and + command line options
> > > >> >> infer the
> > > >> DD. the information that can't infer will assumed.
> > > >> >> generate the DD
> > > >> >> generate the ws using the jaxrpcmapper with wsdl there
> > > will be a
> > > >> >> build file generated that would automate the
> > > >> packaging
> > > >>
> -----------------------------------------------------------------
> > > >> --
> > > >> >>
> > > >> >>
> > > >> >> > Srinath, Ias,
> > > >> >> >
> > > >> >> > i see two modules contrib and jax-rpc-mapper in
> ews's CVS.
> > > >> >> > can
> > > >> you
> > > >> >> guys please give me a short overview of each, how
> they relate
> > > >> >> to
> > > >> one another and what work is left to be done.
> > > >> >> >
> > > >> >> > Thanks,
> > > >> >> > dims
> > > >> >> >
> > > >> >> > =====
> > > >> >> > Davanum Srinivas - http://webservices.apache.org/~dims/
> > > >> >>
> > > >> >>
> > > >> >> ------------------------------------
> > > >> >> Lanka Sofware Foundation
> > > >> >> ------------------------------------
> > > >> >>
> > > >> >>
> > > >> >
> > > >> >
> > > >> > =====
> > > >> > Davanum Srinivas - http://webservices.apache.org/~dims/
> >
> === message truncated ===
>
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: jaxme-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org