You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Davanum Srinivas <di...@yahoo.com> on 2004/02/01 18:22:20 UTC
[EWS] jax-rpc-mapper
Ias,
Just checked in a few mods to the jax-rpc-mapper module:
- Checking in dependent libs.
- Fix classpaths in build.xml's
- Fix code to work with latest axis.
- "ant all" builds everything
- Fix Clean target
Notes:
- Currently ONLY the JAXB-RI stuff works. We need to be able to work with just JaxMe (without
needing JAXB-RI)
- Can we please integrate the ws4j2ee and the jax-rpc-mapper into one single source tree with an
integrated build (BUT generate 2 jars if you so wish)
Thanks,
dims
PS: PLEASE use geronimo-dev for ALL discussion w.r.t EWS.
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: duplicate code in EWS and AXIS
Posted by Davanum Srinivas <di...@yahoo.com>.
Jongjin,
Am all for it. Please open a bug report with the "cvs diff -u" before Ias commits the code to the
Axis code base.
thanks,
dims
--- gunsnroz <gu...@hotmail.com> wrote:
> Hi, ews and axis people!
>
> After comparing the codes in EWS and AXIS, I found that many of them are
> duplicated.
> Specially, the following codes are very similar.
>
> - J2eeEmitter <--> org.apache.axis.wsdl.tojava.Emitter
> - J2eeGeneratorFactory <-->
> org.apache.axis.wsdl.tojava.JavaGeneratorFactory
>
> The other codes such as J2eexxxWriter are deprecated in EWS because the
> equivalent ones in Axis
> can be used. Like this, some modification in the axis Emitter and
> JavaGeneratorFactory
> makes the Axis code reusable and ews code simpler.
>
> The basic idea is adding some codes that override the Axis' default Java
> <--> wsdl nampping in derived classes.
> Here is the example, (details omitted for brevity)
>
> JavaGeneratorFactory.java from Axis
>
> protected void determineInterfaceName(SymbolTable symbolTable) {
> // ...
> if (entry instanceof BindingEntry) {
>
> PortTypeEntry = ...
> seiName = ptEntry.getName();
> bEntry.setDynamicVar(JavaBindingWriter.INTERFACE_NAME,
> seiName);
> }
> // ...
> }
>
> If we add some way to override Axis' default name mapping (ptEntry.getName()
> in above example) like this:
>
>
> ///////////////////// JavaGeneratorFactory in Axis
> protected void determineInterfaceName(SymbolTable symbolTable) {
> // ...
> if (entry instanceof BindingEntry) {
>
> PortTypeEntry = ...
> seiName = getServiceEndpointInterfaceJavaNameHook(ptEntry,
> bEntry);
> if (seiName == null) {
> seiName = ptEntry.getName();
> }
> bEntry.setDynamicVar(JavaBindingWriter.INTERFACE_NAME,
> seiName);
> }
> // ...
> }
>
> protected String getServiceEndpointInterfaceJavaNameHook(PortTypeEntry
> ptEntry, BindingEntry bEntry) {
> return null;
> }
>
> The J2eeGeneratorFactory in ews look like this:
>
> /////////////////////// J2eeGeneratorFactory in EWS
>
> class J2eeGeneratorFactory extends
> org.apache.axis.wsdl.tojava.JavaGeneratorFactory {
> // determinedInterfaceName() : no more needed.
>
> // add new method
> protected String getServiceEndpointInterfaceJavaNameHook(PortTypeEntry
> ptEntry, BindingEntry bEntry) {
> if (mapper == null)
> return null;
> return mapper.getServiceEndpointInterfaceName(ptEntry, bEntry);
> }
> // ...
> }
>
> I have modified the codes in ews and axis and
> it seems that almost duplicate codes in J2eeEmitter and J2eeGeneratorFactory
> can be removed.
>
> Uhm... I think there are pros and cons in this way.
> The cons:
> - Tightly coupling in the Axis code and ews (or other) codes
>
> The pros:
> - Simpler ews codes
> - The Axis code can be reused in other Java <--> WSDL mapping case (like
> JSR-181)
>
> I will discuss it more with Ias who is the Axis and ews committer. (He and I
> are working in the same company)
> I think that the code change in Axis like this should be with the consent of
> other Axis committers.
>
> Any comment?
>
> Jongjin/
>
> ---------------------------------------------------
> Webservices Team in Tmax Soft.
> JSR-208 EG member.
> ---------------------------------------------------
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: duplicate code in EWS and AXIS
Posted by Davanum Srinivas <di...@yahoo.com>.
Jongjin,
Am all for it. Please open a bug report with the "cvs diff -u" before Ias commits the code to the
Axis code base.
thanks,
dims
--- gunsnroz <gu...@hotmail.com> wrote:
> Hi, ews and axis people!
>
> After comparing the codes in EWS and AXIS, I found that many of them are
> duplicated.
> Specially, the following codes are very similar.
>
> - J2eeEmitter <--> org.apache.axis.wsdl.tojava.Emitter
> - J2eeGeneratorFactory <-->
> org.apache.axis.wsdl.tojava.JavaGeneratorFactory
>
> The other codes such as J2eexxxWriter are deprecated in EWS because the
> equivalent ones in Axis
> can be used. Like this, some modification in the axis Emitter and
> JavaGeneratorFactory
> makes the Axis code reusable and ews code simpler.
>
> The basic idea is adding some codes that override the Axis' default Java
> <--> wsdl nampping in derived classes.
> Here is the example, (details omitted for brevity)
>
> JavaGeneratorFactory.java from Axis
>
> protected void determineInterfaceName(SymbolTable symbolTable) {
> // ...
> if (entry instanceof BindingEntry) {
>
> PortTypeEntry = ...
> seiName = ptEntry.getName();
> bEntry.setDynamicVar(JavaBindingWriter.INTERFACE_NAME,
> seiName);
> }
> // ...
> }
>
> If we add some way to override Axis' default name mapping (ptEntry.getName()
> in above example) like this:
>
>
> ///////////////////// JavaGeneratorFactory in Axis
> protected void determineInterfaceName(SymbolTable symbolTable) {
> // ...
> if (entry instanceof BindingEntry) {
>
> PortTypeEntry = ...
> seiName = getServiceEndpointInterfaceJavaNameHook(ptEntry,
> bEntry);
> if (seiName == null) {
> seiName = ptEntry.getName();
> }
> bEntry.setDynamicVar(JavaBindingWriter.INTERFACE_NAME,
> seiName);
> }
> // ...
> }
>
> protected String getServiceEndpointInterfaceJavaNameHook(PortTypeEntry
> ptEntry, BindingEntry bEntry) {
> return null;
> }
>
> The J2eeGeneratorFactory in ews look like this:
>
> /////////////////////// J2eeGeneratorFactory in EWS
>
> class J2eeGeneratorFactory extends
> org.apache.axis.wsdl.tojava.JavaGeneratorFactory {
> // determinedInterfaceName() : no more needed.
>
> // add new method
> protected String getServiceEndpointInterfaceJavaNameHook(PortTypeEntry
> ptEntry, BindingEntry bEntry) {
> if (mapper == null)
> return null;
> return mapper.getServiceEndpointInterfaceName(ptEntry, bEntry);
> }
> // ...
> }
>
> I have modified the codes in ews and axis and
> it seems that almost duplicate codes in J2eeEmitter and J2eeGeneratorFactory
> can be removed.
>
> Uhm... I think there are pros and cons in this way.
> The cons:
> - Tightly coupling in the Axis code and ews (or other) codes
>
> The pros:
> - Simpler ews codes
> - The Axis code can be reused in other Java <--> WSDL mapping case (like
> JSR-181)
>
> I will discuss it more with Ias who is the Axis and ews committer. (He and I
> are working in the same company)
> I think that the code change in Axis like this should be with the consent of
> other Axis committers.
>
> Any comment?
>
> Jongjin/
>
> ---------------------------------------------------
> Webservices Team in Tmax Soft.
> JSR-208 EG member.
> ---------------------------------------------------
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
duplicate code in EWS and AXIS
Posted by gunsnroz <gu...@hotmail.com>.
Hi, ews and axis people!
After comparing the codes in EWS and AXIS, I found that many of them are
duplicated.
Specially, the following codes are very similar.
- J2eeEmitter <--> org.apache.axis.wsdl.tojava.Emitter
- J2eeGeneratorFactory <-->
org.apache.axis.wsdl.tojava.JavaGeneratorFactory
The other codes such as J2eexxxWriter are deprecated in EWS because the
equivalent ones in Axis
can be used. Like this, some modification in the axis Emitter and
JavaGeneratorFactory
makes the Axis code reusable and ews code simpler.
The basic idea is adding some codes that override the Axis' default Java
<--> wsdl nampping in derived classes.
Here is the example, (details omitted for brevity)
JavaGeneratorFactory.java from Axis
protected void determineInterfaceName(SymbolTable symbolTable) {
// ...
if (entry instanceof BindingEntry) {
PortTypeEntry = ...
seiName = ptEntry.getName();
bEntry.setDynamicVar(JavaBindingWriter.INTERFACE_NAME,
seiName);
}
// ...
}
If we add some way to override Axis' default name mapping (ptEntry.getName()
in above example) like this:
///////////////////// JavaGeneratorFactory in Axis
protected void determineInterfaceName(SymbolTable symbolTable) {
// ...
if (entry instanceof BindingEntry) {
PortTypeEntry = ...
seiName = getServiceEndpointInterfaceJavaNameHook(ptEntry,
bEntry);
if (seiName == null) {
seiName = ptEntry.getName();
}
bEntry.setDynamicVar(JavaBindingWriter.INTERFACE_NAME,
seiName);
}
// ...
}
protected String getServiceEndpointInterfaceJavaNameHook(PortTypeEntry
ptEntry, BindingEntry bEntry) {
return null;
}
The J2eeGeneratorFactory in ews look like this:
/////////////////////// J2eeGeneratorFactory in EWS
class J2eeGeneratorFactory extends
org.apache.axis.wsdl.tojava.JavaGeneratorFactory {
// determinedInterfaceName() : no more needed.
// add new method
protected String getServiceEndpointInterfaceJavaNameHook(PortTypeEntry
ptEntry, BindingEntry bEntry) {
if (mapper == null)
return null;
return mapper.getServiceEndpointInterfaceName(ptEntry, bEntry);
}
// ...
}
I have modified the codes in ews and axis and
it seems that almost duplicate codes in J2eeEmitter and J2eeGeneratorFactory
can be removed.
Uhm... I think there are pros and cons in this way.
The cons:
- Tightly coupling in the Axis code and ews (or other) codes
The pros:
- Simpler ews codes
- The Axis code can be reused in other Java <--> WSDL mapping case (like
JSR-181)
I will discuss it more with Ias who is the Axis and ews committer. (He and I
are working in the same company)
I think that the code change in Axis like this should be with the consent of
other Axis committers.
Any comment?
Jongjin/
---------------------------------------------------
Webservices Team in Tmax Soft.
JSR-208 EG member.
---------------------------------------------------
duplicate code in EWS and AXIS
Posted by gunsnroz <gu...@hotmail.com>.
Hi, ews and axis people!
After comparing the codes in EWS and AXIS, I found that many of them are
duplicated.
Specially, the following codes are very similar.
- J2eeEmitter <--> org.apache.axis.wsdl.tojava.Emitter
- J2eeGeneratorFactory <-->
org.apache.axis.wsdl.tojava.JavaGeneratorFactory
The other codes such as J2eexxxWriter are deprecated in EWS because the
equivalent ones in Axis
can be used. Like this, some modification in the axis Emitter and
JavaGeneratorFactory
makes the Axis code reusable and ews code simpler.
The basic idea is adding some codes that override the Axis' default Java
<--> wsdl nampping in derived classes.
Here is the example, (details omitted for brevity)
JavaGeneratorFactory.java from Axis
protected void determineInterfaceName(SymbolTable symbolTable) {
// ...
if (entry instanceof BindingEntry) {
PortTypeEntry = ...
seiName = ptEntry.getName();
bEntry.setDynamicVar(JavaBindingWriter.INTERFACE_NAME,
seiName);
}
// ...
}
If we add some way to override Axis' default name mapping (ptEntry.getName()
in above example) like this:
///////////////////// JavaGeneratorFactory in Axis
protected void determineInterfaceName(SymbolTable symbolTable) {
// ...
if (entry instanceof BindingEntry) {
PortTypeEntry = ...
seiName = getServiceEndpointInterfaceJavaNameHook(ptEntry,
bEntry);
if (seiName == null) {
seiName = ptEntry.getName();
}
bEntry.setDynamicVar(JavaBindingWriter.INTERFACE_NAME,
seiName);
}
// ...
}
protected String getServiceEndpointInterfaceJavaNameHook(PortTypeEntry
ptEntry, BindingEntry bEntry) {
return null;
}
The J2eeGeneratorFactory in ews look like this:
/////////////////////// J2eeGeneratorFactory in EWS
class J2eeGeneratorFactory extends
org.apache.axis.wsdl.tojava.JavaGeneratorFactory {
// determinedInterfaceName() : no more needed.
// add new method
protected String getServiceEndpointInterfaceJavaNameHook(PortTypeEntry
ptEntry, BindingEntry bEntry) {
if (mapper == null)
return null;
return mapper.getServiceEndpointInterfaceName(ptEntry, bEntry);
}
// ...
}
I have modified the codes in ews and axis and
it seems that almost duplicate codes in J2eeEmitter and J2eeGeneratorFactory
can be removed.
Uhm... I think there are pros and cons in this way.
The cons:
- Tightly coupling in the Axis code and ews (or other) codes
The pros:
- Simpler ews codes
- The Axis code can be reused in other Java <--> WSDL mapping case (like
JSR-181)
I will discuss it more with Ias who is the Axis and ews committer. (He and I
are working in the same company)
I think that the code change in Axis like this should be with the consent of
other Axis committers.
Any comment?
Jongjin/
---------------------------------------------------
Webservices Team in Tmax Soft.
JSR-208 EG member.
---------------------------------------------------
Re: [EWS] ws4j2ee
Posted by Davanum Srinivas <di...@yahoo.com>.
Srinath,
sf.net does give you a shell :) it's at shell.sourceforge.net
(http://www.google.com/search?q=shell.sourceforge.net+site%3Asourceforge.net)
thanks,
dims
--- Srinath Perera <he...@opensource.lk> wrote:
> Thanks Dims; I will look in to issues you address. (sorry for late reply)
>
> for the frst time I am having trouble keep up the the ews :) it seems to
> moving real fast. (Since the sf.net do not give a ssh shell .. I can't
> commit in ususal way from unv using http tunneling . I got to go to some
> other place and commit. it might take take bit time.) + I have not work
> with maven before.
> (will catch up soon)
>
> Thanks
>
> Srinath
>
>
> > Srinath,
> >
> > Just checked in a few mods to the ws4jeee module:
> > - Checking in dependent libs.
> > - Fix classpaths in build.xml's
> > - Fix Clean target
> >
> > Notes:
> > - Currently ONLY the JAXB-RI is supported. We need to be able to work
> > with just JaxMe (without needing JAXB-RI/JWSDP)
> > - Can we please integrate the ws4j2ee and the jax-rpc-mapper into one
> > single source tree with an integrated build (BUT generate 2 jars if you
> > so wish)
> yes ..
>
> > - Please add a target to run the sample in the main build.xml itself. -
> > Replace org.apache.x.ws4j2ee with (org.apache.geronimo.ws or
> > org.apache.geronimo.ws4j2ee)
> I think org.apache.geronimo.ws good
>
> >
> > Thanks,
> > dims
> >
> > PS: Please use geronimo-dev mailing list for all discussions.
> >
> > =====
> > Davanum Srinivas - http://webservices.apache.org/~dims/
>
>
> ------------------------------------
> Lanka Sofware Foundation
>
>
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: [EWS] ws4j2ee
Posted by Srinath Perera <he...@opensource.lk>.
Thanks Dims; I will look in to issues you address. (sorry for late reply)
for the frst time I am having trouble keep up the the ews :) it seems to
moving real fast. (Since the sf.net do not give a ssh shell .. I can't
commit in ususal way from unv using http tunneling . I got to go to some
other place and commit. it might take take bit time.) + I have not work
with maven before.
(will catch up soon)
Thanks
Srinath
> Srinath,
>
> Just checked in a few mods to the ws4jeee module:
> - Checking in dependent libs.
> - Fix classpaths in build.xml's
> - Fix Clean target
>
> Notes:
> - Currently ONLY the JAXB-RI is supported. We need to be able to work
> with just JaxMe (without needing JAXB-RI/JWSDP)
> - Can we please integrate the ws4j2ee and the jax-rpc-mapper into one
> single source tree with an integrated build (BUT generate 2 jars if you
> so wish)
yes ..
> - Please add a target to run the sample in the main build.xml itself. -
> Replace org.apache.x.ws4j2ee with (org.apache.geronimo.ws or
> org.apache.geronimo.ws4j2ee)
I think org.apache.geronimo.ws good
>
> Thanks,
> dims
>
> PS: Please use geronimo-dev mailing list for all discussions.
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
------------------------------------
Lanka Sofware Foundation
Re: Idea
Posted by Richard Monson-Haefel <Ri...@Monson-Haefel.com>.
Sorry. As I mentioned once before (I think) I can't find that adapter.
I'm pretty sure it used the RpcHandler rather than the EjbHandler
because it could then convert the method call into an InvocationObject
and pass it into the Geronimo call stack.
----
Richard Monson-Haefel
http://www.monson-haefel.com
On Feb 25, 2004, at 5:25 AM, Srinath Perera wrote:
> Hi Richard;
> Can you let me have the adepter you mentioned, I think it would give
> me a
> starting point to look in to the geranimo. I am trying to decide on how
> the Impl of the ejb should be called from the ws.
> Thanks
> Srinath
>
>> Hi, I actually had an adapter written up but now I can't find it ...
>> Very
>> weird. Anyway, if memory serves I used the ApacheRpcAdapter (something
>> like
>> that) because this delivered the invocation in the form of that could
>> be
>> easily translated into an Invocation object as used in the Geronimo
>> call
>> stack. I think this is the best way to go, as it lets us introduce the
>> functionality we need for handlers in the Geronimo call stack after
>> the
>> transaction and security interceptors have been called, but before the
>> call
>> in delegated to the bean instance.
>>
>> I'm going on vacation and won't be around next week. I hope this
>> helps ...
>> I'm working off of memory and trying to tie loose ends before I leave
>> (read:
>> in a rush!)
>>
>> Richard
>> --
>> Richard Monson-Haefel
>> http://www.Monson-Haefel.com
>>
>>
>>
>
>
> ------------------------------------
> Lanka Sofware Foundation
> ------------------------------------
>
Re: Idea
Posted by Srinath Perera <he...@opensource.lk>.
Hi Richard;
Can you let me have the adepter you mentioned, I think it would give me a
starting point to look in to the geranimo. I am trying to decide on how
the Impl of the ejb should be called from the ws.
Thanks
Srinath
> Hi, I actually had an adapter written up but now I can't find it ... Very
> weird. Anyway, if memory serves I used the ApacheRpcAdapter (something
> like
> that) because this delivered the invocation in the form of that could be
> easily translated into an Invocation object as used in the Geronimo call
> stack. I think this is the best way to go, as it lets us introduce the
> functionality we need for handlers in the Geronimo call stack after the
> transaction and security interceptors have been called, but before the
> call
> in delegated to the bean instance.
>
> I'm going on vacation and won't be around next week. I hope this helps ...
> I'm working off of memory and trying to tie loose ends before I leave
> (read:
> in a rush!)
>
> Richard
> --
> Richard Monson-Haefel
> http://www.Monson-Haefel.com
>
>
>
------------------------------------
Lanka Sofware Foundation
------------------------------------
Re: [EWS] maven-ized ews module
Posted by Jules Gosnell <ju...@coredevelopers.net>.
Guillaume Sauthier wrote:
> Ias wrote:
>
>
>>I revised J2eeGeneratorFactory to support full java-xml-type-mappings. Now
>>you can get exactly what you intend with the mapping file. I added your WSDL
>>and JAX-RPC mapping file to ews/src/samples/mapper/google and added a test
>>case to MapperTest. Please check out codes from EWS CVS, run "maven" and see
>>target/generated/samples/mapper/google directory. MyGoogleSearchResult must
>>exist. :-)
>>
>>Thanks very much,
>>
>>Ias
>
>
> OK Thanks
> It works great :)
> I'll try to complicate this mapping file :)
>
> I'm looking at your code.
> I tried to get GenerateTest working. I made a few changes in
> o.a.g.ews.ws4j2ee.context.webservices.server package (lot of
> Node.toString() changed into Node.getNodeValue())!
> After theses changes, GeneratorTest is working. (no more
> FileNotFOundExceptions)
>
> I also add a JOnASDDWriter which is almost the same as JBossDDWriter ...
Guillaume,
Firstly - Great Work !
Secondly - In the light of JBG's recent accusations, we need, as I'm
sure you realize, to be extremely careful not only, not to put any JBoss
code into Geronimo, but also not to say anything that might later be
used to imply that we had. That was how the last fight got started :-)
Do you think you could just post a followup mail, clarifying exactly
what you put into cvs and demonstrating that whilst it might be
functionally similar to the JBoss equivalent, because similar
functionality is required, no cut-n-pasting of code has occurred between
repositories, or will do so.
Sorry to be a boring politician.
Jules
>
> Can I commit thses changes or are you working on theses files ???
>
> Regards
> Guillaume
--
/**********************************
* Jules Gosnell
* Partner
* Core Developers Network (Europe)
*
* www.coredevelopers.net
*
* Open Source Training & Support.
* Web/Cluster: 23 Feb London
* Enterprise J2EE: 8 March London
**********************************/
Re: [EWS] maven-ized ews module
Posted by Guillaume Sauthier <Gu...@Objectweb.org>.
Srinath Perera wrote:
>
> yes please, Just one thing .. this code use the xml parser to perse the
> webservice.xml file and we decided that we should use JAXB here as well
> as other places. So we decide to replace the code with JAXB gen code.
cross post :) I was thinking about this :)
>
> It is done; We (myself and Chatura) still not get chance to merge it ..
> Anyway the interfaces will not change.
So I stop looking at this :)
>
> You mention you have sample webservice.xml files and jaxpcmapper.xml files
> ... Do you mind adding them to the genarate test as well. (Or I can do it
> for you). I almost done with GenarateTest but there is a problem with
> wsdl genaration with new axis code. I will fix it and come back
they come from jonas webservices exmaples
I have added a time ws (jaxrpc/time) I just add wsdl, and *.xml
And I added a more complicated mapping test (mapper/frenchzip) It was a
WSDL I found on xmethods. And It have hawfull names :) So I add a
complex mapping ...
-> It seems to work :)
I look at the existing samples. Found something strange in
sample/jaxrpc/book :
in META-INF, the ejb-jar.xml declare interfaces for a CalculatorBean but
we are in the jwsbook exmaple! strange no ?
Regards
Guillaume
>
> Thanks
>
> Srinath
>
> ------------------------------------
> Lanka Sofware Foundation
> ------------------------------------
Re: [EWS] maven-ized ews module
Posted by Srinath Perera <he...@opensource.lk>.
> I'm looking at your code.
> I tried to get GenerateTest working. I made a few changes in
> o.a.g.ews.ws4j2ee.context.webservices.server package (lot of
> Node.toString() changed into Node.getNodeValue())!
> After theses changes, GeneratorTest is working. (no more
> FileNotFOundExceptions)
yes please, Just one thing .. this code use the xml parser to perse the
webservice.xml file and we decided that we should use JAXB here as well
as other places. So we decide to replace the code with JAXB gen code.
It is done; We (myself and Chatura) still not get chance to merge it ..
Anyway the interfaces will not change.
>I also add a JOnASDDWriter which is almost the same as JBossDDWriter ...
that would be nice ...
You mention you have sample webservice.xml files and jaxpcmapper.xml files
... Do you mind adding them to the genarate test as well. (Or I can do it
for you). I almost done with GenarateTest but there is a problem with
wsdl genaration with new axis code. I will fix it and come back
Thanks
Srinath
------------------------------------
Lanka Sofware Foundation
------------------------------------
Re: [EWS] maven-ized ews module
Posted by Jules Gosnell <ju...@coredevelopers.net>.
Guillaume Sauthier wrote:
> Ias wrote:
>
>
>>I revised J2eeGeneratorFactory to support full java-xml-type-mappings. Now
>>you can get exactly what you intend with the mapping file. I added your WSDL
>>and JAX-RPC mapping file to ews/src/samples/mapper/google and added a test
>>case to MapperTest. Please check out codes from EWS CVS, run "maven" and see
>>target/generated/samples/mapper/google directory. MyGoogleSearchResult must
>>exist. :-)
>>
>>Thanks very much,
>>
>>Ias
>
>
> OK Thanks
> It works great :)
> I'll try to complicate this mapping file :)
>
> I'm looking at your code.
> I tried to get GenerateTest working. I made a few changes in
> o.a.g.ews.ws4j2ee.context.webservices.server package (lot of
> Node.toString() changed into Node.getNodeValue())!
> After theses changes, GeneratorTest is working. (no more
> FileNotFOundExceptions)
>
> I also add a JOnASDDWriter which is almost the same as JBossDDWriter ...
I may have jumped without looking :-)
If the JBossDDWriter is Geronimo code, then there is no problem here and
I am barking up the wrong tree and apologise...
I just saw the word JBoss and saw red !
my bad,
Jules
>
> Can I commit thses changes or are you working on theses files ???
>
> Regards
> Guillaume
--
/**********************************
* Jules Gosnell
* Partner
* Core Developers Network (Europe)
*
* www.coredevelopers.net
*
* Open Source Training & Support.
* Web/Cluster: 23 Feb London
* Enterprise J2EE: 8 March London
**********************************/
Re: [EWS] Geronimo - EWS Deployment Team
Posted by Jeremy Boynes <je...@coredevelopers.net>.
knight@adsl.tie.cl wrote:
> So we are in charge of the generation of Service's impl's code. And thinking
> about it it's right, this is a provider specific task.
>
>
> Thanks
>
> Luis Avila
>
> PD: what do you think about the idea to do a deployment planner in charge
> of do the ws-deployment?
>
>
>>-- Original Message --
>>Reply-To: geronimo-dev@incubator.apache.org
>>Date: Thu, 5 Feb 2004 05:35:26 -0800 (PST)
>>From: Davanum Srinivas <di...@yahoo.com>
>>Reply-To: dims@yahoo.com
>>Subject: Re: [EWS] Geronimo - EWS Deployment Team
>>To: geronimo-dev@incubator.apache.org
>>
>>
>>Luis,
>>
>>Let us step back a bit. There are two stages
>>
>>Stage #1: Design/Coding Phase
>>Stage #2: Runtime
>>
>>In stage #1, the web services developer will use the tools (the ones in
>
> EWS
>
>>repository NOW) to
>>generate JSR 109 compliant artifacts like (All these items are packed into
>>the EAR):
>>- webservices.xml
>>- jaxrpcmapping.xml
>>- implementation of handlers
>>- implementation of server-side code
>>
>>Note that the developer may choose to use a tool from a different vendor
>>to generate the EAR with
>>the exact same stuff. Ias and Srinath are working on tools for generating
>>the stuff for stage #1.
>>
>>In stage #2, This is where you jump in, you will need to extract information
>
>>from the EAR and use
>
>>those information to hook up Geronimo and Axis.
>>
>>TIP: If you look at org.apache.axis.deployment.wsdd package in Axis, you
>>will see how Axis
>>currently uses information present in WSDD files to deploy the service.
>
You should also look in Geronimo's deployment module to see how its
JSR88 provider is working. You should be able to perform Geronimo/Axis
specific configuration using DDBean/DConfigBean operations. Given the
incorporation of web-services into all the module types, it might be
worth having a general purpose set of DConfigBeans available that any
module deployer can use.
JSR88 does not provide you with a mechanism for modifying the EAR's
content (or that of any other module) - everything you need should be
incorporated in the deployment plan that gets written out by the
DConfigBeans. There is one plan for each root module, so you will need a
method for nesting per-module definitions inside the plan for an EAR.
>
>>TIP: If you look at EJBProvider in Axis, you will see how EJB's are currently
>>invoked from Axis
>>
I had a look at that previously and it seemed to be invoking using the
remote interface. I don't think this works in a compliant application.
EJB2.1 has different container semantics for remote- and service-
invocations and you will need to inject information into the call for it
to to this.
You should hook up with David Blevins about hooking into the proxy
system for EJB's. A way to do this would be by providing a hook on the
EJB deployer that allows it to return a web-service specific proxy to you.
--
Jeremy
Re: [EWS] Geronimo - EWS Deployment Team
Posted by Davanum Srinivas <di...@yahoo.com>.
Yes. and +1 to a deployment planner for ws.
--- knight@adsl.tie.cl wrote:
> So we are in charge of the generation of Service's impl's code. And thinking
> about it it's right, this is a provider specific task.
>
>
> Thanks
>
> Luis Avila
>
> PD: what do you think about the idea to do a deployment planner in charge
> of do the ws-deployment?
>
> >-- Original Message --
> >Reply-To: geronimo-dev@incubator.apache.org
> >Date: Thu, 5 Feb 2004 05:35:26 -0800 (PST)
> >From: Davanum Srinivas <di...@yahoo.com>
> >Reply-To: dims@yahoo.com
> >Subject: Re: [EWS] Geronimo - EWS Deployment Team
> >To: geronimo-dev@incubator.apache.org
> >
> >
> >Luis,
> >
> >Let us step back a bit. There are two stages
> >
> >Stage #1: Design/Coding Phase
> >Stage #2: Runtime
> >
> >In stage #1, the web services developer will use the tools (the ones in
> EWS
> >repository NOW) to
> >generate JSR 109 compliant artifacts like (All these items are packed into
> >the EAR):
> >- webservices.xml
> >- jaxrpcmapping.xml
> >- implementation of handlers
> >- implementation of server-side code
> >
> >Note that the developer may choose to use a tool from a different vendor
> >to generate the EAR with
> >the exact same stuff. Ias and Srinath are working on tools for generating
> >the stuff for stage #1.
> >
> >In stage #2, This is where you jump in, you will need to extract information
> >from the EAR and use
> >those information to hook up Geronimo and Axis.
> >
> >TIP: If you look at org.apache.axis.deployment.wsdd package in Axis, you
> >will see how Axis
> >currently uses information present in WSDD files to deploy the service.
>
> >TIP: If you look at EJBProvider in Axis, you will see how EJB's are currently
> >invoked from Axis
> >
> >See http://www-106.ibm.com/developerworks/webservices/library/ws-jsrart/
> >for additional
> >information.
> >
> >Thanks,
> >dims
> >
> >--- knight@adsl.tie.cl wrote:
> >>
> >> Hi all,
> >>
> >> Recently i sent a mail to Srinath bec me and Jeremy were a little confused
> >> about our role in the Geronimo - JSR-109 Integration. Srinath told me
> that
> >> we present a proposal to the list.
> >>
> >> We were thinking about what we need to do. And our conclusion was that
> >we
> >> must be involved in the deployment of WS over geronimo.
> >>
> >> Our proposal consists in two steps and we show them to you:
> >>
> >> 1.- Get the neccesary files from the ear, war, ejb-jar and give it to
> the
> >> ews code for generate the files neccesary's to do the ws-deployment (service
> >> impl,s, service endpoint Interface impl's, stubs, xml's, etc.)
> >>
> >> 2.- With the result obtained from ews we will deploy the ws over a web-app
> >> who will contain only one servlet who will receive the soap requests.
> This
> >> implies the bindings too.
> >>
> >> Our job will concentrate in two sides:
> >>
> >> 1.- Do a WS-deployment planner who will do the steps 1 and 2 from the
> geronimo
> >> deployment side and
> >>
> >> 2.- Add code to the axis-servlet to do the ws deployment.
> >>
> >> We'd really appreciate our comments please.
> >>
> >> Cheers.
> >>
> >> Luis Avila
> >>
> >>
> >>
> >>
> >>
> >
> >
> >=====
> >Davanum Srinivas - http://webservices.apache.org/~dims/
>
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: [EWS] Geronimo - EWS Deployment Team
Posted by kn...@adsl.tie.cl.
So we are in charge of the generation of Service's impl's code. And thinking
about it it's right, this is a provider specific task.
Thanks
Luis Avila
PD: what do you think about the idea to do a deployment planner in charge
of do the ws-deployment?
>-- Original Message --
>Reply-To: geronimo-dev@incubator.apache.org
>Date: Thu, 5 Feb 2004 05:35:26 -0800 (PST)
>From: Davanum Srinivas <di...@yahoo.com>
>Reply-To: dims@yahoo.com
>Subject: Re: [EWS] Geronimo - EWS Deployment Team
>To: geronimo-dev@incubator.apache.org
>
>
>Luis,
>
>Let us step back a bit. There are two stages
>
>Stage #1: Design/Coding Phase
>Stage #2: Runtime
>
>In stage #1, the web services developer will use the tools (the ones in
EWS
>repository NOW) to
>generate JSR 109 compliant artifacts like (All these items are packed into
>the EAR):
>- webservices.xml
>- jaxrpcmapping.xml
>- implementation of handlers
>- implementation of server-side code
>
>Note that the developer may choose to use a tool from a different vendor
>to generate the EAR with
>the exact same stuff. Ias and Srinath are working on tools for generating
>the stuff for stage #1.
>
>In stage #2, This is where you jump in, you will need to extract information
>from the EAR and use
>those information to hook up Geronimo and Axis.
>
>TIP: If you look at org.apache.axis.deployment.wsdd package in Axis, you
>will see how Axis
>currently uses information present in WSDD files to deploy the service.
>TIP: If you look at EJBProvider in Axis, you will see how EJB's are currently
>invoked from Axis
>
>See http://www-106.ibm.com/developerworks/webservices/library/ws-jsrart/
>for additional
>information.
>
>Thanks,
>dims
>
>--- knight@adsl.tie.cl wrote:
>>
>> Hi all,
>>
>> Recently i sent a mail to Srinath bec me and Jeremy were a little confused
>> about our role in the Geronimo - JSR-109 Integration. Srinath told me
that
>> we present a proposal to the list.
>>
>> We were thinking about what we need to do. And our conclusion was that
>we
>> must be involved in the deployment of WS over geronimo.
>>
>> Our proposal consists in two steps and we show them to you:
>>
>> 1.- Get the neccesary files from the ear, war, ejb-jar and give it to
the
>> ews code for generate the files neccesary's to do the ws-deployment (service
>> impl,s, service endpoint Interface impl's, stubs, xml's, etc.)
>>
>> 2.- With the result obtained from ews we will deploy the ws over a web-app
>> who will contain only one servlet who will receive the soap requests.
This
>> implies the bindings too.
>>
>> Our job will concentrate in two sides:
>>
>> 1.- Do a WS-deployment planner who will do the steps 1 and 2 from the
geronimo
>> deployment side and
>>
>> 2.- Add code to the axis-servlet to do the ws deployment.
>>
>> We'd really appreciate our comments please.
>>
>> Cheers.
>>
>> Luis Avila
>>
>>
>>
>>
>>
>
>
>=====
>Davanum Srinivas - http://webservices.apache.org/~dims/
Re: [EWS] Geronimo - EWS Deployment Team
Posted by Davanum Srinivas <di...@yahoo.com>.
Luis,
Let us step back a bit. There are two stages
Stage #1: Design/Coding Phase
Stage #2: Runtime
In stage #1, the web services developer will use the tools (the ones in EWS repository NOW) to
generate JSR 109 compliant artifacts like (All these items are packed into the EAR):
- webservices.xml
- jaxrpcmapping.xml
- implementation of handlers
- implementation of server-side code
Note that the developer may choose to use a tool from a different vendor to generate the EAR with
the exact same stuff. Ias and Srinath are working on tools for generating the stuff for stage #1.
In stage #2, This is where you jump in, you will need to extract information from the EAR and use
those information to hook up Geronimo and Axis.
TIP: If you look at org.apache.axis.deployment.wsdd package in Axis, you will see how Axis
currently uses information present in WSDD files to deploy the service.
TIP: If you look at EJBProvider in Axis, you will see how EJB's are currently invoked from Axis
See http://www-106.ibm.com/developerworks/webservices/library/ws-jsrart/ for additional
information.
Thanks,
dims
--- knight@adsl.tie.cl wrote:
>
> Hi all,
>
> Recently i sent a mail to Srinath bec me and Jeremy were a little confused
> about our role in the Geronimo - JSR-109 Integration. Srinath told me that
> we present a proposal to the list.
>
> We were thinking about what we need to do. And our conclusion was that we
> must be involved in the deployment of WS over geronimo.
>
> Our proposal consists in two steps and we show them to you:
>
> 1.- Get the neccesary files from the ear, war, ejb-jar and give it to the
> ews code for generate the files neccesary's to do the ws-deployment (service
> impl,s, service endpoint Interface impl's, stubs, xml's, etc.)
>
> 2.- With the result obtained from ews we will deploy the ws over a web-app
> who will contain only one servlet who will receive the soap requests. This
> implies the bindings too.
>
> Our job will concentrate in two sides:
>
> 1.- Do a WS-deployment planner who will do the steps 1 and 2 from the geronimo
> deployment side and
>
> 2.- Add code to the axis-servlet to do the ws deployment.
>
> We'd really appreciate our comments please.
>
> Cheers.
>
> Luis Avila
>
>
>
>
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
[EWS] Geronimo - EWS Deployment Team
Posted by kn...@adsl.tie.cl.
Hi all,
Recently i sent a mail to Srinath bec me and Jeremy were a little confused
about our role in the Geronimo - JSR-109 Integration. Srinath told me that
we present a proposal to the list.
We were thinking about what we need to do. And our conclusion was that we
must be involved in the deployment of WS over geronimo.
Our proposal consists in two steps and we show them to you:
1.- Get the neccesary files from the ear, war, ejb-jar and give it to the
ews code for generate the files neccesary's to do the ws-deployment (service
impl,s, service endpoint Interface impl's, stubs, xml's, etc.)
2.- With the result obtained from ews we will deploy the ws over a web-app
who will contain only one servlet who will receive the soap requests. This
implies the bindings too.
Our job will concentrate in two sides:
1.- Do a WS-deployment planner who will do the steps 1 and 2 from the geronimo
deployment side and
2.- Add code to the axis-servlet to do the ws deployment.
We'd really appreciate our comments please.
Cheers.
Luis Avila
Re: [EWS] maven-ized ews module
Posted by Davanum Srinivas <di...@yahoo.com>.
Please go ahead and commit it. If anyone else is working on it, they will have to merge. first
come, first serve :)
thanks,
dims
--- Guillaume Sauthier <Gu...@Objectweb.org> wrote:
> Ias wrote:
>
> > I revised J2eeGeneratorFactory to support full java-xml-type-mappings. Now
> > you can get exactly what you intend with the mapping file. I added your WSDL
> > and JAX-RPC mapping file to ews/src/samples/mapper/google and added a test
> > case to MapperTest. Please check out codes from EWS CVS, run "maven" and see
> > target/generated/samples/mapper/google directory. MyGoogleSearchResult must
> > exist. :-)
> >
> > Thanks very much,
> >
> > Ias
>
> OK Thanks
> It works great :)
> I'll try to complicate this mapping file :)
>
> I'm looking at your code.
> I tried to get GenerateTest working. I made a few changes in
> o.a.g.ews.ws4j2ee.context.webservices.server package (lot of
> Node.toString() changed into Node.getNodeValue())!
> After theses changes, GeneratorTest is working. (no more
> FileNotFOundExceptions)
>
> I also add a JOnASDDWriter which is almost the same as JBossDDWriter ...
>
> Can I commit thses changes or are you working on theses files ???
>
> Regards
> Guillaume
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: [EWS] maven-ized ews module
Posted by Guillaume Sauthier <Gu...@Objectweb.org>.
Ias wrote:
> I revised J2eeGeneratorFactory to support full java-xml-type-mappings. Now
> you can get exactly what you intend with the mapping file. I added your WSDL
> and JAX-RPC mapping file to ews/src/samples/mapper/google and added a test
> case to MapperTest. Please check out codes from EWS CVS, run "maven" and see
> target/generated/samples/mapper/google directory. MyGoogleSearchResult must
> exist. :-)
>
> Thanks very much,
>
> Ias
OK Thanks
It works great :)
I'll try to complicate this mapping file :)
I'm looking at your code.
I tried to get GenerateTest working. I made a few changes in
o.a.g.ews.ws4j2ee.context.webservices.server package (lot of
Node.toString() changed into Node.getNodeValue())!
After theses changes, GeneratorTest is working. (no more
FileNotFOundExceptions)
I also add a JOnASDDWriter which is almost the same as JBossDDWriter ...
Can I commit thses changes or are you working on theses files ???
Regards
Guillaume
RE: [EWS] maven-ized ews module
Posted by Ias <ia...@tmax.co.kr>.
> I 've just changed a java-xml-type-mapping
> (GoogleSearchResult renamed into MyGoogleSearchResult) and I
> can't see any changes in generated classes !?
>
> here is my command line :
> java -cp <all needed classes>
> org.apache.geronimo.ews.jaxrpcmapping.WsdlToJ2ee
> GoogleSearch.wsdl -o ~/tmp -m googleMapping.xml (theses files
> have been sent with my previous post :) )
>
> and here are the classes I get :
> org/objectweb/wssample/gen/google:
> DirectoryCategory.java GoogleSearchService.java
> GoogleSearchBindingStub.java GoogleSearchServiceLocator.java
> GoogleSearchPort.java ResultElement.java
> GoogleSearchResult.java <-- Should be MyGoogleSearchResult !?
>
I revised J2eeGeneratorFactory to support full java-xml-type-mappings. Now
you can get exactly what you intend with the mapping file. I added your WSDL
and JAX-RPC mapping file to ews/src/samples/mapper/google and added a test
case to MapperTest. Please check out codes from EWS CVS, run "maven" and see
target/generated/samples/mapper/google directory. MyGoogleSearchResult must
exist. :-)
Thanks very much,
Ias
Re: [EWS] maven-ized ews module
Posted by Guillaume Sauthier <Gu...@Objectweb.org>.
OK, if I can help, I'll be happy to :)
I'm reading Ias code at this time. And trying to understand Generator's
logic ...
I'm focused on jaxrpc mapper as you can see.
because the jaxrpc mapper is the part that I can use in JOnAS JSR109
impl :)
regards
Guillaume
Davanum Srinivas wrote:
>
> Ias,
> Can you please help with this?
>
> Guillaume,
> Am trying to wrap my hands around existing code written by Ias and Srinath. So please bear with us
> as we cleanup/integrate/refactor the code.
>
> thanks,
> dims
>
> --- Guillaume Sauthier <Gu...@Objectweb.org> wrote:
> >
> > Hi Dims
> > I've checked out latest cvs version.
> > I 've tried ews with my own simple example and do not work as expected.
> >
> > I 've just changed a java-xml-type-mapping
> > (GoogleSearchResult renamed into MyGoogleSearchResult) and I can't see
> > any changes in generated classes !?
> >
> > here is my command line :
> > java -cp <all needed classes>
> > org.apache.geronimo.ews.jaxrpcmapping.WsdlToJ2ee GoogleSearch.wsdl -o
> > ~/tmp -m googleMapping.xml
> > (theses files have been sent with my previous post :) )
> >
> > and here are the classes I get :
> > org/objectweb/wssample/gen/google:
> > DirectoryCategory.java GoogleSearchService.java
> > GoogleSearchBindingStub.java GoogleSearchServiceLocator.java
> > GoogleSearchPort.java ResultElement.java
> > GoogleSearchResult.java <-- Should be MyGoogleSearchResult !?
> >
> > java-xml-type-mapping don't seem to be read...
> > And Your samples doesn't use java-xml-type-mapping. they "only" use
> > other complex tags !
> >
> > Any ideas ???
> > I'as seen a method in J2eeEmitter :
> > public boolean isGeneratingTypes() {
> > // TODO Auto-generated method stub
> > return false;
> > }
> > Is this means that types are mapped to default Axis types and not java
> > types defined by jaxrpc mapping file?
> >
> > Thanks for your answers !
> >
> > Regards
> > Guillaume
> >
> > Davanum Srinivas wrote:
> > >
> > > Guillaume,
> > >
> > > Check out latest cvs (watch out for pserver lags), i works fine. Also the mappings are all
> > defined
> > > as part of JSR 109 (http://www.google.com/search?q=JSR+109)
> > >
> > > thanks,
> > > dims
> > >
> > > --- Guillaume Sauthier <Gu...@Objectweb.org> wrote:
> > > > Hello
> > > >
> > > > When I tryed ews with maven, the ews-1.0.jar created in target doesn't
> > > > contains required jaxb properties!
> > > > You can add theses files with this little XML snippet in your
> > > > project.xml :
> > > > in <ressources> tag add the following :
> > > > <resource>
> > > > <directory>target/src</directory>
> > > > <includes>
> > > >
> > > > <include>org/apache/geronimo/ews/ws4j2ee/parsers/ejbdd/jaxb.properties</include>
> > > >
> > > > <include>org/apache/geronimo/ews/ws4j2ee/parsers/ejbdd/bgm.ser</include>
> > > >
> > > > <include>org/apache/geronimo/ews/jaxrpcmapping/descriptor/jaxb.properties</include>
> > > >
> > > > <include>org/apache/geronimo/ews/jaxrpcmapping/descriptor/bgm.ser</include>
> > > > </includes>
> > > > </resource>
> > > >
> > > > Is there somewhere a document explaining the functionnalities of the
> > > > jaxrpc mapper ?
> > > > what are the supported tags from jaxrpm-mapping-file
> > > > (java-xml-type-mapping, ...) for generation ?
> > > >
> > > > Regards
> > > > Guillaume
> > > >
> > > > Ias wrote:
> > > > >
> > > > > > i fixed the problem. please try again. specifically try
> > > > > > "maven clean" followed by "maven"
> > > > >
> > > > > Thanks for your fix and instructing me how to use Maven (Actually today is
> > > > > the first day of my running Maven :-) . Now building with Maven works well.
> > > > >
> > > > > >
> > > > > > thanks,
> > > > > > dims
> > > > > >
> > > > > > --- Ias <ia...@tmax.co.kr> wrote:
> > > > > > > > > let's stop working on the contrib and jax-rpc-mapper module
> > > > > > > > and switch
> > > > > > > > > over to the ews module that i checked in a few mins ago. It
> > > > > > > > has code
> > > > > > > > > from both contrid/ws4j2ee and jax-rpc-mapper. It generates the
> > > > > > > > > jaxb stuff as well. just run "maven" from the root directory
> > > > > > > > after checking
> > > > > > > > > out the ews modules.
> > > > > > > > >
> > > > > > > > I checked ews in and ran maven, version 1.0 RC1.
> > > > > > >
> > > > > > > Oops! Sorry. not "in" but "out" actually.
> > > > > > >
> > > > > > > > Unfortunately, I failed to compile Java source files. I modified
> > > > > > > >
> > > > > > > > <sourceDirectory>${basedir}/target/src</sourceDirectory>
> > > > > > > > to
> > > > > > > > <sourceDirectory>target/src</sourceDirectory>
> > > > > > > >
> > > > > > > > in project and succeeded in obtaining the right ews.jar. Do you
> > > > > > > > think I should commit this change?
> > > > > > > >
> > > > > > > > Thanks for your organizing EWS :-)
> > > > > > > >
> > > > > > > > Ias
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > =====
> > > > > > Davanum Srinivas - http://webservices.apache.org/~dims/
> > > > > >> <?xml version="1.0"?>
> > > >
> > > > <!-- WSDL description of the Google Web APIs.
> > > > The Google Web APIs are in beta release. All interfaces are subject to
> > > > change as we refine and extend our APIs. Please see the terms of use
> > > > for more information. -->
> > > >
> > > > <!-- Revision 2002-08-16 -->
> > > >
> > > > <definitions name="GoogleSearch"
> > > > targetNamespace="urn:GoogleSearch"
> > > > xmlns:typens="urn:GoogleSearch"
> > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
> > > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> > > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> > > > xmlns="http://schemas.xmlsoap.org/wsdl/">
> > > >
> > > > <!-- Types for search - result elements, directory categories -->
> > > >
> > > > <types>
> > > > <xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
> > > > targetNamespace="urn:GoogleSearch">
> > > >
> > > > <xsd:complexType name="GoogleSearchResult">
> > > > <xsd:all>
> > > > <xsd:element name="documentFiltering" type="xsd:boolean"/>
> > > > <xsd:element name="searchComments" type="xsd:string"/>
> > > > <xsd:element name="estimatedTotalResultsCount" type="xsd:int"/>
> > > > <xsd:element name="estimateIsExact" type="xsd:boolean"/>
> > > > <xsd:element name="resultElements" type="typens:ResultElementArray"/>
> > > > <xsd:element name="searchQuery" type="xsd:string"/>
> > > > <xsd:element name="startIndex" type="xsd:int"/>
> > > > <xsd:element name="endIndex" type="xsd:int"/>
> > > > <xsd:element name="searchTips" type="xsd:string"/>
> > > > <xsd:element name="directoryCategories"
> > type="typens:DirectoryCategoryArray"/>
> > > > <xsd:element name="searchTime" type="xsd:double"/>
> > > > </xsd:all>
> > > > </xsd:complexType>
> > > >
> > > > <xsd:complexType name="ResultElement">
> > > > <xsd:all>
> > > > <xsd:element name="summary" type="xsd:string"/>
> > > > <xsd:element name="URL" type="xsd:string"/>
> > > > <xsd:element name="snippet" type="xsd:string"/>
> > > > <xsd:element name="title" type="xsd:string"/>
> > > > <xsd:element name="cachedSize" type="xsd:string"/>
> > > > <xsd:element name="relatedInformationPresent" type="xsd:boolean"/>
> > > > <xsd:element name="hostName" type="xsd:string"/>
> > > > <xsd:element name="directoryCategory" type="typens:DirectoryCategory"/>
> > > > <xsd:element name="directoryTitle" type="xsd:string"/>
> > > > </xsd:all>
> > > > </xsd:complexType>
> > > >
> > > > <xsd:complexType name="ResultElementArray">
> > > > <xsd:complexContent>
> > > > <xsd:restriction base="soapenc:Array">
> > > > <xsd:attribute ref="soapenc:arrayType"
> > wsdl:arrayType="typens:ResultElement[]"/>
> > > > </xsd:restriction>
> > > > </xsd:complexContent>
> > > > </xsd:complexType>
> > > >
> > > > <xsd:complexType name="DirectoryCategoryArray">
> > > > <xsd:complexContent>
> > > > <xsd:restriction base="soapenc:Array">
> > > > <xsd:attribute ref="soapenc:arrayType"
> > > > wsdl:arrayType="typens:DirectoryCategory[]"/>
> > > > </xsd:restriction>
> > > > </xsd:complexContent>
> > > > </xsd:complexType>
> > > >
> > > > <xsd:complexType name="DirectoryCategory">
> > > > <xsd:all>
> > > > <xsd:element name="fullViewableName" type="xsd:string"/>
> >
> === message truncated ===
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
Re: [EWS] maven-ized ews module
Posted by Davanum Srinivas <di...@yahoo.com>.
Ias,
Can you please help with this?
Guillaume,
Am trying to wrap my hands around existing code written by Ias and Srinath. So please bear with us
as we cleanup/integrate/refactor the code.
thanks,
dims
--- Guillaume Sauthier <Gu...@Objectweb.org> wrote:
>
> Hi Dims
> I've checked out latest cvs version.
> I 've tried ews with my own simple example and do not work as expected.
>
> I 've just changed a java-xml-type-mapping
> (GoogleSearchResult renamed into MyGoogleSearchResult) and I can't see
> any changes in generated classes !?
>
> here is my command line :
> java -cp <all needed classes>
> org.apache.geronimo.ews.jaxrpcmapping.WsdlToJ2ee GoogleSearch.wsdl -o
> ~/tmp -m googleMapping.xml
> (theses files have been sent with my previous post :) )
>
> and here are the classes I get :
> org/objectweb/wssample/gen/google:
> DirectoryCategory.java GoogleSearchService.java
> GoogleSearchBindingStub.java GoogleSearchServiceLocator.java
> GoogleSearchPort.java ResultElement.java
> GoogleSearchResult.java <-- Should be MyGoogleSearchResult !?
>
> java-xml-type-mapping don't seem to be read...
> And Your samples doesn't use java-xml-type-mapping. they "only" use
> other complex tags !
>
> Any ideas ???
> I'as seen a method in J2eeEmitter :
> public boolean isGeneratingTypes() {
> // TODO Auto-generated method stub
> return false;
> }
> Is this means that types are mapped to default Axis types and not java
> types defined by jaxrpc mapping file?
>
> Thanks for your answers !
>
> Regards
> Guillaume
>
> Davanum Srinivas wrote:
> >
> > Guillaume,
> >
> > Check out latest cvs (watch out for pserver lags), i works fine. Also the mappings are all
> defined
> > as part of JSR 109 (http://www.google.com/search?q=JSR+109)
> >
> > thanks,
> > dims
> >
> > --- Guillaume Sauthier <Gu...@Objectweb.org> wrote:
> > > Hello
> > >
> > > When I tryed ews with maven, the ews-1.0.jar created in target doesn't
> > > contains required jaxb properties!
> > > You can add theses files with this little XML snippet in your
> > > project.xml :
> > > in <ressources> tag add the following :
> > > <resource>
> > > <directory>target/src</directory>
> > > <includes>
> > >
> > > <include>org/apache/geronimo/ews/ws4j2ee/parsers/ejbdd/jaxb.properties</include>
> > >
> > > <include>org/apache/geronimo/ews/ws4j2ee/parsers/ejbdd/bgm.ser</include>
> > >
> > > <include>org/apache/geronimo/ews/jaxrpcmapping/descriptor/jaxb.properties</include>
> > >
> > > <include>org/apache/geronimo/ews/jaxrpcmapping/descriptor/bgm.ser</include>
> > > </includes>
> > > </resource>
> > >
> > > Is there somewhere a document explaining the functionnalities of the
> > > jaxrpc mapper ?
> > > what are the supported tags from jaxrpm-mapping-file
> > > (java-xml-type-mapping, ...) for generation ?
> > >
> > > Regards
> > > Guillaume
> > >
> > > Ias wrote:
> > > >
> > > > > i fixed the problem. please try again. specifically try
> > > > > "maven clean" followed by "maven"
> > > >
> > > > Thanks for your fix and instructing me how to use Maven (Actually today is
> > > > the first day of my running Maven :-) . Now building with Maven works well.
> > > >
> > > > >
> > > > > thanks,
> > > > > dims
> > > > >
> > > > > --- Ias <ia...@tmax.co.kr> wrote:
> > > > > > > > let's stop working on the contrib and jax-rpc-mapper module
> > > > > > > and switch
> > > > > > > > over to the ews module that i checked in a few mins ago. It
> > > > > > > has code
> > > > > > > > from both contrid/ws4j2ee and jax-rpc-mapper. It generates the
> > > > > > > > jaxb stuff as well. just run "maven" from the root directory
> > > > > > > after checking
> > > > > > > > out the ews modules.
> > > > > > > >
> > > > > > > I checked ews in and ran maven, version 1.0 RC1.
> > > > > >
> > > > > > Oops! Sorry. not "in" but "out" actually.
> > > > > >
> > > > > > > Unfortunately, I failed to compile Java source files. I modified
> > > > > > >
> > > > > > > <sourceDirectory>${basedir}/target/src</sourceDirectory>
> > > > > > > to
> > > > > > > <sourceDirectory>target/src</sourceDirectory>
> > > > > > >
> > > > > > > in project and succeeded in obtaining the right ews.jar. Do you
> > > > > > > think I should commit this change?
> > > > > > >
> > > > > > > Thanks for your organizing EWS :-)
> > > > > > >
> > > > > > > Ias
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > =====
> > > > > Davanum Srinivas - http://webservices.apache.org/~dims/
> > > > >> <?xml version="1.0"?>
> > >
> > > <!-- WSDL description of the Google Web APIs.
> > > The Google Web APIs are in beta release. All interfaces are subject to
> > > change as we refine and extend our APIs. Please see the terms of use
> > > for more information. -->
> > >
> > > <!-- Revision 2002-08-16 -->
> > >
> > > <definitions name="GoogleSearch"
> > > targetNamespace="urn:GoogleSearch"
> > > xmlns:typens="urn:GoogleSearch"
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
> > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> > > xmlns="http://schemas.xmlsoap.org/wsdl/">
> > >
> > > <!-- Types for search - result elements, directory categories -->
> > >
> > > <types>
> > > <xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
> > > targetNamespace="urn:GoogleSearch">
> > >
> > > <xsd:complexType name="GoogleSearchResult">
> > > <xsd:all>
> > > <xsd:element name="documentFiltering" type="xsd:boolean"/>
> > > <xsd:element name="searchComments" type="xsd:string"/>
> > > <xsd:element name="estimatedTotalResultsCount" type="xsd:int"/>
> > > <xsd:element name="estimateIsExact" type="xsd:boolean"/>
> > > <xsd:element name="resultElements" type="typens:ResultElementArray"/>
> > > <xsd:element name="searchQuery" type="xsd:string"/>
> > > <xsd:element name="startIndex" type="xsd:int"/>
> > > <xsd:element name="endIndex" type="xsd:int"/>
> > > <xsd:element name="searchTips" type="xsd:string"/>
> > > <xsd:element name="directoryCategories"
> type="typens:DirectoryCategoryArray"/>
> > > <xsd:element name="searchTime" type="xsd:double"/>
> > > </xsd:all>
> > > </xsd:complexType>
> > >
> > > <xsd:complexType name="ResultElement">
> > > <xsd:all>
> > > <xsd:element name="summary" type="xsd:string"/>
> > > <xsd:element name="URL" type="xsd:string"/>
> > > <xsd:element name="snippet" type="xsd:string"/>
> > > <xsd:element name="title" type="xsd:string"/>
> > > <xsd:element name="cachedSize" type="xsd:string"/>
> > > <xsd:element name="relatedInformationPresent" type="xsd:boolean"/>
> > > <xsd:element name="hostName" type="xsd:string"/>
> > > <xsd:element name="directoryCategory" type="typens:DirectoryCategory"/>
> > > <xsd:element name="directoryTitle" type="xsd:string"/>
> > > </xsd:all>
> > > </xsd:complexType>
> > >
> > > <xsd:complexType name="ResultElementArray">
> > > <xsd:complexContent>
> > > <xsd:restriction base="soapenc:Array">
> > > <xsd:attribute ref="soapenc:arrayType"
> wsdl:arrayType="typens:ResultElement[]"/>
> > > </xsd:restriction>
> > > </xsd:complexContent>
> > > </xsd:complexType>
> > >
> > > <xsd:complexType name="DirectoryCategoryArray">
> > > <xsd:complexContent>
> > > <xsd:restriction base="soapenc:Array">
> > > <xsd:attribute ref="soapenc:arrayType"
> > > wsdl:arrayType="typens:DirectoryCategory[]"/>
> > > </xsd:restriction>
> > > </xsd:complexContent>
> > > </xsd:complexType>
> > >
> > > <xsd:complexType name="DirectoryCategory">
> > > <xsd:all>
> > > <xsd:element name="fullViewableName" type="xsd:string"/>
>
=== message truncated ===
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: [EWS] maven-ized ews module
Posted by Guillaume Sauthier <Gu...@Objectweb.org>.
Hi Dims
I've checked out latest cvs version.
I 've tried ews with my own simple example and do not work as expected.
I 've just changed a java-xml-type-mapping
(GoogleSearchResult renamed into MyGoogleSearchResult) and I can't see
any changes in generated classes !?
here is my command line :
java -cp <all needed classes>
org.apache.geronimo.ews.jaxrpcmapping.WsdlToJ2ee GoogleSearch.wsdl -o
~/tmp -m googleMapping.xml
(theses files have been sent with my previous post :) )
and here are the classes I get :
org/objectweb/wssample/gen/google:
DirectoryCategory.java GoogleSearchService.java
GoogleSearchBindingStub.java GoogleSearchServiceLocator.java
GoogleSearchPort.java ResultElement.java
GoogleSearchResult.java <-- Should be MyGoogleSearchResult !?
java-xml-type-mapping don't seem to be read...
And Your samples doesn't use java-xml-type-mapping. they "only" use
other complex tags !
Any ideas ???
I'as seen a method in J2eeEmitter :
public boolean isGeneratingTypes() {
// TODO Auto-generated method stub
return false;
}
Is this means that types are mapped to default Axis types and not java
types defined by jaxrpc mapping file?
Thanks for your answers !
Regards
Guillaume
Davanum Srinivas wrote:
>
> Guillaume,
>
> Check out latest cvs (watch out for pserver lags), i works fine. Also the mappings are all defined
> as part of JSR 109 (http://www.google.com/search?q=JSR+109)
>
> thanks,
> dims
>
> --- Guillaume Sauthier <Gu...@Objectweb.org> wrote:
> > Hello
> >
> > When I tryed ews with maven, the ews-1.0.jar created in target doesn't
> > contains required jaxb properties!
> > You can add theses files with this little XML snippet in your
> > project.xml :
> > in <ressources> tag add the following :
> > <resource>
> > <directory>target/src</directory>
> > <includes>
> >
> > <include>org/apache/geronimo/ews/ws4j2ee/parsers/ejbdd/jaxb.properties</include>
> >
> > <include>org/apache/geronimo/ews/ws4j2ee/parsers/ejbdd/bgm.ser</include>
> >
> > <include>org/apache/geronimo/ews/jaxrpcmapping/descriptor/jaxb.properties</include>
> >
> > <include>org/apache/geronimo/ews/jaxrpcmapping/descriptor/bgm.ser</include>
> > </includes>
> > </resource>
> >
> > Is there somewhere a document explaining the functionnalities of the
> > jaxrpc mapper ?
> > what are the supported tags from jaxrpm-mapping-file
> > (java-xml-type-mapping, ...) for generation ?
> >
> > Regards
> > Guillaume
> >
> > Ias wrote:
> > >
> > > > i fixed the problem. please try again. specifically try
> > > > "maven clean" followed by "maven"
> > >
> > > Thanks for your fix and instructing me how to use Maven (Actually today is
> > > the first day of my running Maven :-) . Now building with Maven works well.
> > >
> > > >
> > > > thanks,
> > > > dims
> > > >
> > > > --- Ias <ia...@tmax.co.kr> wrote:
> > > > > > > let's stop working on the contrib and jax-rpc-mapper module
> > > > > > and switch
> > > > > > > over to the ews module that i checked in a few mins ago. It
> > > > > > has code
> > > > > > > from both contrid/ws4j2ee and jax-rpc-mapper. It generates the
> > > > > > > jaxb stuff as well. just run "maven" from the root directory
> > > > > > after checking
> > > > > > > out the ews modules.
> > > > > > >
> > > > > > I checked ews in and ran maven, version 1.0 RC1.
> > > > >
> > > > > Oops! Sorry. not "in" but "out" actually.
> > > > >
> > > > > > Unfortunately, I failed to compile Java source files. I modified
> > > > > >
> > > > > > <sourceDirectory>${basedir}/target/src</sourceDirectory>
> > > > > > to
> > > > > > <sourceDirectory>target/src</sourceDirectory>
> > > > > >
> > > > > > in project and succeeded in obtaining the right ews.jar. Do you
> > > > > > think I should commit this change?
> > > > > >
> > > > > > Thanks for your organizing EWS :-)
> > > > > >
> > > > > > Ias
> > > > > >
> > > > >
> > > >
> > > >
> > > > =====
> > > > Davanum Srinivas - http://webservices.apache.org/~dims/
> > > >> <?xml version="1.0"?>
> >
> > <!-- WSDL description of the Google Web APIs.
> > The Google Web APIs are in beta release. All interfaces are subject to
> > change as we refine and extend our APIs. Please see the terms of use
> > for more information. -->
> >
> > <!-- Revision 2002-08-16 -->
> >
> > <definitions name="GoogleSearch"
> > targetNamespace="urn:GoogleSearch"
> > xmlns:typens="urn:GoogleSearch"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> > xmlns="http://schemas.xmlsoap.org/wsdl/">
> >
> > <!-- Types for search - result elements, directory categories -->
> >
> > <types>
> > <xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
> > targetNamespace="urn:GoogleSearch">
> >
> > <xsd:complexType name="GoogleSearchResult">
> > <xsd:all>
> > <xsd:element name="documentFiltering" type="xsd:boolean"/>
> > <xsd:element name="searchComments" type="xsd:string"/>
> > <xsd:element name="estimatedTotalResultsCount" type="xsd:int"/>
> > <xsd:element name="estimateIsExact" type="xsd:boolean"/>
> > <xsd:element name="resultElements" type="typens:ResultElementArray"/>
> > <xsd:element name="searchQuery" type="xsd:string"/>
> > <xsd:element name="startIndex" type="xsd:int"/>
> > <xsd:element name="endIndex" type="xsd:int"/>
> > <xsd:element name="searchTips" type="xsd:string"/>
> > <xsd:element name="directoryCategories" type="typens:DirectoryCategoryArray"/>
> > <xsd:element name="searchTime" type="xsd:double"/>
> > </xsd:all>
> > </xsd:complexType>
> >
> > <xsd:complexType name="ResultElement">
> > <xsd:all>
> > <xsd:element name="summary" type="xsd:string"/>
> > <xsd:element name="URL" type="xsd:string"/>
> > <xsd:element name="snippet" type="xsd:string"/>
> > <xsd:element name="title" type="xsd:string"/>
> > <xsd:element name="cachedSize" type="xsd:string"/>
> > <xsd:element name="relatedInformationPresent" type="xsd:boolean"/>
> > <xsd:element name="hostName" type="xsd:string"/>
> > <xsd:element name="directoryCategory" type="typens:DirectoryCategory"/>
> > <xsd:element name="directoryTitle" type="xsd:string"/>
> > </xsd:all>
> > </xsd:complexType>
> >
> > <xsd:complexType name="ResultElementArray">
> > <xsd:complexContent>
> > <xsd:restriction base="soapenc:Array">
> > <xsd:attribute ref="soapenc:arrayType" wsdl:arrayType="typens:ResultElement[]"/>
> > </xsd:restriction>
> > </xsd:complexContent>
> > </xsd:complexType>
> >
> > <xsd:complexType name="DirectoryCategoryArray">
> > <xsd:complexContent>
> > <xsd:restriction base="soapenc:Array">
> > <xsd:attribute ref="soapenc:arrayType"
> > wsdl:arrayType="typens:DirectoryCategory[]"/>
> > </xsd:restriction>
> > </xsd:complexContent>
> > </xsd:complexType>
> >
> > <xsd:complexType name="DirectoryCategory">
> > <xsd:all>
> > <xsd:element name="fullViewableName" type="xsd:string"/>
> > <xsd:element name="specialEncoding" type="xsd:string"/>
> > </xsd:all>
> > </xsd:complexType>
> >
> > </xsd:schema>
> > </types>
> >
> > <!-- Messages for Google Web APIs - cached page, search, spelling. -->
> >
> > <message name="doGetCachedPage">
> > <part name="key" type="xsd:string"/>
> > <part name="url" type="xsd:string"/>
> > </message>
> >
> > <message name="doGetCachedPageResponse">
> > <part name="return" type="xsd:base64Binary"/>
> > </message>
> >
> > <message name="doSpellingSuggestion">
> > <part name="key" type="xsd:string"/>
> > <part name="phrase" type="xsd:string"/>
> > </message>
> >
> > <message name="doSpellingSuggestionResponse">
> > <part name="return" type="xsd:string"/>
> > </message>
> >
> > <!-- note, ie and oe are ignored by server; all traffic is UTF-8. -->
> >
> > <message name="doGoogleSearch">
> > <part name="key" type="xsd:string"/>
> > <part name="q" type="xsd:string"/>
> > <part name="start" type="xsd:int"/>
> > <part name="maxResults" type="xsd:int"/>
> > <part name="filter" type="xsd:boolean"/>
> > <part name="restrict" type="xsd:string"/>
> > <part name="safeSearch" type="xsd:boolean"/>
> > <part name="lr" type="xsd:string"/>
> > <part name="ie" type="xsd:string"/>
> > <part name="oe" type="xsd:string"/>
> > </message>
> >
> > <message name="doGoogleSearchResponse">
> > <part name="return" type="typens:GoogleSearchResult"/>
> > </message>
> >
> > <!-- Port for Google Web APIs, "GoogleSearch" -->
> >
> > <portType name="GoogleSearchPort">
> >
> > <operation name="doGetCachedPage">
> > <input message="typens:doGetCachedPage"/>
> > <output message="typens:doGetCachedPageResponse"/>
> > </operation>
> >
> > <operation name="doSpellingSuggestion">
> > <input message="typens:doSpellingSuggestion"/>
> > <output message="typens:doSpellingSuggestionResponse"/>
> > </operation>
> >
> > <operation name="doGoogleSearch">
> > <input message="typens:doGoogleSearch"/>
> > <output message="typens:doGoogleSearchResponse"/>
> > </operation>
> >
> > </portType>
> >
> >
> > <!-- Binding for Google Web APIs - RPC, SOAP over HTTP -->
> >
> > <binding name="GoogleSearchBinding" type="typens:GoogleSearchPort">
> > <soap:binding style="rpc"
> > transport="http://schemas.xmlsoap.org/soap/http"/>
> >
> > <operation name="doGetCachedPage">
> > <soap:operation soapAction="urn:GoogleSearchAction"/>
> > <input>
> > <soap:body use="encoded"
> > namespace="urn:GoogleSearch"
> > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> > </input>
> > <output>
> > <soap:body use="encoded"
> > namespace="urn:GoogleSearch"
> > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> > </output>
> > </operation>
> >
> > <operation name="doSpellingSuggestion">
> > <soap:operation soapAction="urn:GoogleSearchAction"/>
> > <input>
> > <soap:body use="encoded"
> > namespace="urn:GoogleSearch"
> > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> > </input>
> > <output>
> > <soap:body use="encoded"
> > namespace="urn:GoogleSearch"
> > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> > </output>
> > </operation>
> >
> > <operation name="doGoogleSearch">
> > <soap:operation soapAction="urn:GoogleSearchAction"/>
> > <input>
> > <soap:body use="encoded"
> > namespace="urn:GoogleSearch"
> > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> > </input>
> > <output>
> > <soap:body use="encoded"
> > namespace="urn:GoogleSearch"
> > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> > </output>
> > </operation>
> > </binding>
> >
> > <!-- Endpoint for Google Web APIs -->
> > <service name="GoogleSearchService">
> > <port name="GoogleSearchPort" binding="typens:GoogleSearchBinding">
> > <soap:address location="http://api.google.com/search/beta2"/>
> > </port>
> > </service>
> >
> > </definitions>
> > > <?xml version="1.0"?>
> > <java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> > http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd"
> > version="1.1">
> > <package-mapping>
> > <package-type>org.objectweb.wssample.gen.google</package-type>
> > <namespaceURI>urn:GoogleSearch</namespaceURI>
> > </package-mapping>
> > <java-xml-type-mapping>
> > <java-type>org.objectweb.wssample.gen.google.MyGoogleSearchResult</java-type>
> > <root-type-qname xmlns:ns="urn:GoogleSearch">ns:GoogleSearchResult</root-type-qname>
> > <qname-scope>complexType</qname-scope>
> > </java-xml-type-mapping>
> > <java-xml-type-mapping>
> > <java-type>org.objectweb.wssample.gen.google.ResultElement</java-type>
> > <root-type-qname xmlns:ns="urn:GoogleSearch">ns:ResultElement</root-type-qname>
> > <qname-scope>complexType</qname-scope>
> > </java-xml-type-mapping>
> > <java-xml-type-mapping>
> > <java-type>org.objectweb.wssample.gen.google.ResultElement[]</java-type>
> > <root-type-qname xmlns:ns="urn:GoogleSearch">ns:ResultElementArray</root-type-qname>
> > <qname-scope>complexType</qname-scope>
> > </java-xml-type-mapping>
> > <java-xml-type-mapping>
> > <java-type>org.objectweb.wssample.gen.google.DirectoryCategory[]</java-type>
> > <root-type-qname xmlns:ns="urn:GoogleSearch">ns:DirectoryCategoryArray</root-type-qname>
> > <qname-scope>complexType</qname-scope>
> > </java-xml-type-mapping>
> > <java-xml-type-mapping>
> > <java-type>org.objectweb.wssample.gen.google.DirectoryCategory</java-type>
> > <root-type-qname xmlns:ns="urn:GoogleSearch">ns:DirectoryCategory</root-type-qname>
> > <qname-scope>complexType</qname-scope>
> > </java-xml-type-mapping>
> >
> > </java-wsdl-mapping>
> >
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
Re: [EWS] maven-ized ews module
Posted by Davanum Srinivas <di...@yahoo.com>.
Guillaume,
Check out latest cvs (watch out for pserver lags), i works fine. Also the mappings are all defined
as part of JSR 109 (http://www.google.com/search?q=JSR+109)
thanks,
dims
--- Guillaume Sauthier <Gu...@Objectweb.org> wrote:
> Hello
>
> When I tryed ews with maven, the ews-1.0.jar created in target doesn't
> contains required jaxb properties!
> You can add theses files with this little XML snippet in your
> project.xml :
> in <ressources> tag add the following :
> <resource>
> <directory>target/src</directory>
> <includes>
>
> <include>org/apache/geronimo/ews/ws4j2ee/parsers/ejbdd/jaxb.properties</include>
>
> <include>org/apache/geronimo/ews/ws4j2ee/parsers/ejbdd/bgm.ser</include>
>
> <include>org/apache/geronimo/ews/jaxrpcmapping/descriptor/jaxb.properties</include>
>
> <include>org/apache/geronimo/ews/jaxrpcmapping/descriptor/bgm.ser</include>
> </includes>
> </resource>
>
> Is there somewhere a document explaining the functionnalities of the
> jaxrpc mapper ?
> what are the supported tags from jaxrpm-mapping-file
> (java-xml-type-mapping, ...) for generation ?
>
> Regards
> Guillaume
>
> Ias wrote:
> >
> > > i fixed the problem. please try again. specifically try
> > > "maven clean" followed by "maven"
> >
> > Thanks for your fix and instructing me how to use Maven (Actually today is
> > the first day of my running Maven :-) . Now building with Maven works well.
> >
> > >
> > > thanks,
> > > dims
> > >
> > > --- Ias <ia...@tmax.co.kr> wrote:
> > > > > > let's stop working on the contrib and jax-rpc-mapper module
> > > > > and switch
> > > > > > over to the ews module that i checked in a few mins ago. It
> > > > > has code
> > > > > > from both contrid/ws4j2ee and jax-rpc-mapper. It generates the
> > > > > > jaxb stuff as well. just run "maven" from the root directory
> > > > > after checking
> > > > > > out the ews modules.
> > > > > >
> > > > > I checked ews in and ran maven, version 1.0 RC1.
> > > >
> > > > Oops! Sorry. not "in" but "out" actually.
> > > >
> > > > > Unfortunately, I failed to compile Java source files. I modified
> > > > >
> > > > > <sourceDirectory>${basedir}/target/src</sourceDirectory>
> > > > > to
> > > > > <sourceDirectory>target/src</sourceDirectory>
> > > > >
> > > > > in project and succeeded in obtaining the right ews.jar. Do you
> > > > > think I should commit this change?
> > > > >
> > > > > Thanks for your organizing EWS :-)
> > > > >
> > > > > Ias
> > > > >
> > > >
> > >
> > >
> > > =====
> > > Davanum Srinivas - http://webservices.apache.org/~dims/
> > >> <?xml version="1.0"?>
>
> <!-- WSDL description of the Google Web APIs.
> The Google Web APIs are in beta release. All interfaces are subject to
> change as we refine and extend our APIs. Please see the terms of use
> for more information. -->
>
> <!-- Revision 2002-08-16 -->
>
> <definitions name="GoogleSearch"
> targetNamespace="urn:GoogleSearch"
> xmlns:typens="urn:GoogleSearch"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> xmlns="http://schemas.xmlsoap.org/wsdl/">
>
> <!-- Types for search - result elements, directory categories -->
>
> <types>
> <xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
> targetNamespace="urn:GoogleSearch">
>
> <xsd:complexType name="GoogleSearchResult">
> <xsd:all>
> <xsd:element name="documentFiltering" type="xsd:boolean"/>
> <xsd:element name="searchComments" type="xsd:string"/>
> <xsd:element name="estimatedTotalResultsCount" type="xsd:int"/>
> <xsd:element name="estimateIsExact" type="xsd:boolean"/>
> <xsd:element name="resultElements" type="typens:ResultElementArray"/>
> <xsd:element name="searchQuery" type="xsd:string"/>
> <xsd:element name="startIndex" type="xsd:int"/>
> <xsd:element name="endIndex" type="xsd:int"/>
> <xsd:element name="searchTips" type="xsd:string"/>
> <xsd:element name="directoryCategories" type="typens:DirectoryCategoryArray"/>
> <xsd:element name="searchTime" type="xsd:double"/>
> </xsd:all>
> </xsd:complexType>
>
> <xsd:complexType name="ResultElement">
> <xsd:all>
> <xsd:element name="summary" type="xsd:string"/>
> <xsd:element name="URL" type="xsd:string"/>
> <xsd:element name="snippet" type="xsd:string"/>
> <xsd:element name="title" type="xsd:string"/>
> <xsd:element name="cachedSize" type="xsd:string"/>
> <xsd:element name="relatedInformationPresent" type="xsd:boolean"/>
> <xsd:element name="hostName" type="xsd:string"/>
> <xsd:element name="directoryCategory" type="typens:DirectoryCategory"/>
> <xsd:element name="directoryTitle" type="xsd:string"/>
> </xsd:all>
> </xsd:complexType>
>
> <xsd:complexType name="ResultElementArray">
> <xsd:complexContent>
> <xsd:restriction base="soapenc:Array">
> <xsd:attribute ref="soapenc:arrayType" wsdl:arrayType="typens:ResultElement[]"/>
> </xsd:restriction>
> </xsd:complexContent>
> </xsd:complexType>
>
> <xsd:complexType name="DirectoryCategoryArray">
> <xsd:complexContent>
> <xsd:restriction base="soapenc:Array">
> <xsd:attribute ref="soapenc:arrayType"
> wsdl:arrayType="typens:DirectoryCategory[]"/>
> </xsd:restriction>
> </xsd:complexContent>
> </xsd:complexType>
>
> <xsd:complexType name="DirectoryCategory">
> <xsd:all>
> <xsd:element name="fullViewableName" type="xsd:string"/>
> <xsd:element name="specialEncoding" type="xsd:string"/>
> </xsd:all>
> </xsd:complexType>
>
> </xsd:schema>
> </types>
>
> <!-- Messages for Google Web APIs - cached page, search, spelling. -->
>
> <message name="doGetCachedPage">
> <part name="key" type="xsd:string"/>
> <part name="url" type="xsd:string"/>
> </message>
>
> <message name="doGetCachedPageResponse">
> <part name="return" type="xsd:base64Binary"/>
> </message>
>
> <message name="doSpellingSuggestion">
> <part name="key" type="xsd:string"/>
> <part name="phrase" type="xsd:string"/>
> </message>
>
> <message name="doSpellingSuggestionResponse">
> <part name="return" type="xsd:string"/>
> </message>
>
> <!-- note, ie and oe are ignored by server; all traffic is UTF-8. -->
>
> <message name="doGoogleSearch">
> <part name="key" type="xsd:string"/>
> <part name="q" type="xsd:string"/>
> <part name="start" type="xsd:int"/>
> <part name="maxResults" type="xsd:int"/>
> <part name="filter" type="xsd:boolean"/>
> <part name="restrict" type="xsd:string"/>
> <part name="safeSearch" type="xsd:boolean"/>
> <part name="lr" type="xsd:string"/>
> <part name="ie" type="xsd:string"/>
> <part name="oe" type="xsd:string"/>
> </message>
>
> <message name="doGoogleSearchResponse">
> <part name="return" type="typens:GoogleSearchResult"/>
> </message>
>
> <!-- Port for Google Web APIs, "GoogleSearch" -->
>
> <portType name="GoogleSearchPort">
>
> <operation name="doGetCachedPage">
> <input message="typens:doGetCachedPage"/>
> <output message="typens:doGetCachedPageResponse"/>
> </operation>
>
> <operation name="doSpellingSuggestion">
> <input message="typens:doSpellingSuggestion"/>
> <output message="typens:doSpellingSuggestionResponse"/>
> </operation>
>
> <operation name="doGoogleSearch">
> <input message="typens:doGoogleSearch"/>
> <output message="typens:doGoogleSearchResponse"/>
> </operation>
>
> </portType>
>
>
> <!-- Binding for Google Web APIs - RPC, SOAP over HTTP -->
>
> <binding name="GoogleSearchBinding" type="typens:GoogleSearchPort">
> <soap:binding style="rpc"
> transport="http://schemas.xmlsoap.org/soap/http"/>
>
> <operation name="doGetCachedPage">
> <soap:operation soapAction="urn:GoogleSearchAction"/>
> <input>
> <soap:body use="encoded"
> namespace="urn:GoogleSearch"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> </input>
> <output>
> <soap:body use="encoded"
> namespace="urn:GoogleSearch"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> </output>
> </operation>
>
> <operation name="doSpellingSuggestion">
> <soap:operation soapAction="urn:GoogleSearchAction"/>
> <input>
> <soap:body use="encoded"
> namespace="urn:GoogleSearch"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> </input>
> <output>
> <soap:body use="encoded"
> namespace="urn:GoogleSearch"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> </output>
> </operation>
>
> <operation name="doGoogleSearch">
> <soap:operation soapAction="urn:GoogleSearchAction"/>
> <input>
> <soap:body use="encoded"
> namespace="urn:GoogleSearch"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> </input>
> <output>
> <soap:body use="encoded"
> namespace="urn:GoogleSearch"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> </output>
> </operation>
> </binding>
>
> <!-- Endpoint for Google Web APIs -->
> <service name="GoogleSearchService">
> <port name="GoogleSearchPort" binding="typens:GoogleSearchBinding">
> <soap:address location="http://api.google.com/search/beta2"/>
> </port>
> </service>
>
> </definitions>
> > <?xml version="1.0"?>
> <java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd"
> version="1.1">
> <package-mapping>
> <package-type>org.objectweb.wssample.gen.google</package-type>
> <namespaceURI>urn:GoogleSearch</namespaceURI>
> </package-mapping>
> <java-xml-type-mapping>
> <java-type>org.objectweb.wssample.gen.google.MyGoogleSearchResult</java-type>
> <root-type-qname xmlns:ns="urn:GoogleSearch">ns:GoogleSearchResult</root-type-qname>
> <qname-scope>complexType</qname-scope>
> </java-xml-type-mapping>
> <java-xml-type-mapping>
> <java-type>org.objectweb.wssample.gen.google.ResultElement</java-type>
> <root-type-qname xmlns:ns="urn:GoogleSearch">ns:ResultElement</root-type-qname>
> <qname-scope>complexType</qname-scope>
> </java-xml-type-mapping>
> <java-xml-type-mapping>
> <java-type>org.objectweb.wssample.gen.google.ResultElement[]</java-type>
> <root-type-qname xmlns:ns="urn:GoogleSearch">ns:ResultElementArray</root-type-qname>
> <qname-scope>complexType</qname-scope>
> </java-xml-type-mapping>
> <java-xml-type-mapping>
> <java-type>org.objectweb.wssample.gen.google.DirectoryCategory[]</java-type>
> <root-type-qname xmlns:ns="urn:GoogleSearch">ns:DirectoryCategoryArray</root-type-qname>
> <qname-scope>complexType</qname-scope>
> </java-xml-type-mapping>
> <java-xml-type-mapping>
> <java-type>org.objectweb.wssample.gen.google.DirectoryCategory</java-type>
> <root-type-qname xmlns:ns="urn:GoogleSearch">ns:DirectoryCategory</root-type-qname>
> <qname-scope>complexType</qname-scope>
> </java-xml-type-mapping>
>
> </java-wsdl-mapping>
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: [EWS] maven-ized ews module
Posted by Guillaume Sauthier <Gu...@Objectweb.org>.
Hello
When I tryed ews with maven, the ews-1.0.jar created in target doesn't
contains required jaxb properties!
You can add theses files with this little XML snippet in your
project.xml :
in <ressources> tag add the following :
<resource>
<directory>target/src</directory>
<includes>
<include>org/apache/geronimo/ews/ws4j2ee/parsers/ejbdd/jaxb.properties</include>
<include>org/apache/geronimo/ews/ws4j2ee/parsers/ejbdd/bgm.ser</include>
<include>org/apache/geronimo/ews/jaxrpcmapping/descriptor/jaxb.properties</include>
<include>org/apache/geronimo/ews/jaxrpcmapping/descriptor/bgm.ser</include>
</includes>
</resource>
Is there somewhere a document explaining the functionnalities of the
jaxrpc mapper ?
what are the supported tags from jaxrpm-mapping-file
(java-xml-type-mapping, ...) for generation ?
Regards
Guillaume
Ias wrote:
>
> > i fixed the problem. please try again. specifically try
> > "maven clean" followed by "maven"
>
> Thanks for your fix and instructing me how to use Maven (Actually today is
> the first day of my running Maven :-) . Now building with Maven works well.
>
> >
> > thanks,
> > dims
> >
> > --- Ias <ia...@tmax.co.kr> wrote:
> > > > > let's stop working on the contrib and jax-rpc-mapper module
> > > > and switch
> > > > > over to the ews module that i checked in a few mins ago. It
> > > > has code
> > > > > from both contrid/ws4j2ee and jax-rpc-mapper. It generates the
> > > > > jaxb stuff as well. just run "maven" from the root directory
> > > > after checking
> > > > > out the ews modules.
> > > > >
> > > > I checked ews in and ran maven, version 1.0 RC1.
> > >
> > > Oops! Sorry. not "in" but "out" actually.
> > >
> > > > Unfortunately, I failed to compile Java source files. I modified
> > > >
> > > > <sourceDirectory>${basedir}/target/src</sourceDirectory>
> > > > to
> > > > <sourceDirectory>target/src</sourceDirectory>
> > > >
> > > > in project and succeeded in obtaining the right ews.jar. Do you
> > > > think I should commit this change?
> > > >
> > > > Thanks for your organizing EWS :-)
> > > >
> > > > Ias
> > > >
> > >
> >
> >
> > =====
> > Davanum Srinivas - http://webservices.apache.org/~dims/
> >
Re: [EWS] Need to fix GenerateTest (for testing ws4j2ee)
Posted by Srinath Perera <he...@opensource.lk>.
Hi All;
I fix the GenarateTest .. Actually each test case we used for the
test the ws4j2ee should have three parts
1) genarate the Client side with wsdl
2) genarete the serve side with wsdl
3) Genarate the all when wsdl not present using the ejb jar.
(It was my mistake to put the code at test to genarate the client side
code only)
With the recent axis code the wsdl generatin code give a null pointer
exception. When I try it in WSDL2Java gives the same result .. I am not
sure is it something to do with axis or ws4j2ee. I will check.
when that is done the ws4j2ee support the all 1,2,3 senario's. With the
1) it will genarate a build file that would automate the jar creation.
As Guillaume pointed out we(myself aand Chatura) will replace/merge the
code that do the manual parsing of webservice.xml with the JAXB code over
the weekend.
Thanks
Srinath
> Ias, Srinath,
>
> Can you guys please fix the GenerateTest test that i added for ws4j2ee?
> Am not sure where the problem is happening. You need to edit project.xml
> and comment out the excludes section in unitTest block and then run
> "maven" to recreate the problem.
>
> thanks,
> dims
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
------------------------------------
Lanka Sofware Foundation
------------------------------------
RE: [EWS] Need to fix GenerateTest (for testing ws4j2ee)
Posted by Ias <ia...@tmax.co.kr>.
> Fixed :)
>
Thanks a lot! (Actually I didn't understand the whole situation at all. :-)
> Just a Question, Why don't we use a schema
> (j2ee_webservices_1_1.xsd) with JAXB?
> We parse jax rpc mapping file with the help of jaxb generated
> file from jaxrpmc_mapping.xsd but webservices.xml is
> "manually" parsed! That was the cause of the GenerateTest failure ...
>
jax-rpc-mapper's using of JAXB was my (private preferred) decision. Perhaps
Srinath can answer your question. :-)
Ias
> Regards
> Guillaume
>
> Davanum Srinivas wrote:
> >
> > Ias, Srinath,
> >
> > Can you guys please fix the GenerateTest test that i added for
> > ws4j2ee? Am not sure where the problem is happening. You
> need to edit
> > project.xml and comment out the excludes section in
> unitTest block and then run "maven" to recreate the problem.
> >
> > thanks,
> > dims
> >
> > =====
> > Davanum Srinivas - http://webservices.apache.org/~dims/
>
Re: [EWS] Need to fix GenerateTest (for testing ws4j2ee)
Posted by Guillaume Sauthier <Gu...@Objectweb.org>.
Fixed :)
Just a Question, Why don't we use a schema (j2ee_webservices_1_1.xsd)
with JAXB?
We parse jax rpc mapping file with the help of jaxb generated file from
jaxrpmc_mapping.xsd but webservices.xml is "manually" parsed! That was
the cause of the GenerateTest failure ...
Regards
Guillaume
Davanum Srinivas wrote:
>
> Ias, Srinath,
>
> Can you guys please fix the GenerateTest test that i added for ws4j2ee? Am not sure where the
> problem is happening. You need to edit project.xml and comment out the excludes section in
> unitTest block and then run "maven" to recreate the problem.
>
> thanks,
> dims
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
[EWS] Need to fix GenerateTest (for testing ws4j2ee)
Posted by Davanum Srinivas <di...@yahoo.com>.
Ias, Srinath,
Can you guys please fix the GenerateTest test that i added for ws4j2ee? Am not sure where the
problem is happening. You need to edit project.xml and comment out the excludes section in
unitTest block and then run "maven" to recreate the problem.
thanks,
dims
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
RE: [EWS] maven-ized ews module
Posted by Ias <ia...@tmax.co.kr>.
> i fixed the problem. please try again. specifically try
> "maven clean" followed by "maven"
Thanks for your fix and instructing me how to use Maven (Actually today is
the first day of my running Maven :-) . Now building with Maven works well.
>
> thanks,
> dims
>
> --- Ias <ia...@tmax.co.kr> wrote:
> > > > let's stop working on the contrib and jax-rpc-mapper module
> > > and switch
> > > > over to the ews module that i checked in a few mins ago. It
> > > has code
> > > > from both contrid/ws4j2ee and jax-rpc-mapper. It generates the
> > > > jaxb stuff as well. just run "maven" from the root directory
> > > after checking
> > > > out the ews modules.
> > > >
> > > I checked ews in and ran maven, version 1.0 RC1.
> >
> > Oops! Sorry. not "in" but "out" actually.
> >
> > > Unfortunately, I failed to compile Java source files. I modified
> > >
> > > <sourceDirectory>${basedir}/target/src</sourceDirectory>
> > > to
> > > <sourceDirectory>target/src</sourceDirectory>
> > >
> > > in project and succeeded in obtaining the right ews.jar. Do you
> > > think I should commit this change?
> > >
> > > Thanks for your organizing EWS :-)
> > >
> > > Ias
> > >
> >
>
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
RE: [EWS] maven-ized ews module
Posted by Davanum Srinivas <di...@yahoo.com>.
i fixed the problem. please try again. specifically try "maven clean" followed by "maven"
thanks,
dims
--- Ias <ia...@tmax.co.kr> wrote:
> > > let's stop working on the contrib and jax-rpc-mapper module
> > and switch
> > > over to the ews module that i checked in a few mins ago. It
> > has code
> > > from both contrid/ws4j2ee and jax-rpc-mapper. It generates the jaxb
> > > stuff as well. just run "maven" from the root directory
> > after checking
> > > out the ews modules.
> > >
> > I checked ews in and ran maven, version 1.0 RC1.
>
> Oops! Sorry. not "in" but "out" actually.
>
> > Unfortunately, I failed to compile Java source files. I modified
> >
> > <sourceDirectory>${basedir}/target/src</sourceDirectory>
> > to
> > <sourceDirectory>target/src</sourceDirectory>
> >
> > in project and succeeded in obtaining the right ews.jar. Do
> > you think I should commit this change?
> >
> > Thanks for your organizing EWS :-)
> >
> > Ias
> >
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
RE: [EWS] maven-ized ews module
Posted by Ias <ia...@tmax.co.kr>.
> > let's stop working on the contrib and jax-rpc-mapper module
> and switch
> > over to the ews module that i checked in a few mins ago. It
> has code
> > from both contrid/ws4j2ee and jax-rpc-mapper. It generates the jaxb
> > stuff as well. just run "maven" from the root directory
> after checking
> > out the ews modules.
> >
> I checked ews in and ran maven, version 1.0 RC1.
Oops! Sorry. not "in" but "out" actually.
> Unfortunately, I failed to compile Java source files. I modified
>
> <sourceDirectory>${basedir}/target/src</sourceDirectory>
> to
> <sourceDirectory>target/src</sourceDirectory>
>
> in project and succeeded in obtaining the right ews.jar. Do
> you think I should commit this change?
>
> Thanks for your organizing EWS :-)
>
> Ias
>
RE: [EWS] maven-ized ews module
Posted by Ias <ia...@tmax.co.kr>.
> Srinath, Ias,
>
> let's stop working on the contrib and jax-rpc-mapper module
> and switch over to the ews module that i checked in a few
> mins ago. It has code from both contrid/ws4j2ee and
> jax-rpc-mapper. It generates the jaxb stuff as well. just run
> "maven" from the root directory after checking out the ews modules.
>
I checked ews in and ran maven, version 1.0 RC1. Unfortunately, I failed to
compile Java source files. I modified
<sourceDirectory>${basedir}/target/src</sourceDirectory>
to
<sourceDirectory>target/src</sourceDirectory>
in project and succeeded in obtaining the right ews.jar. Do you think I
should commit this change?
Thanks for your organizing EWS :-)
Ias
[EWS] maven-ized ews module
Posted by Davanum Srinivas <di...@yahoo.com>.
Srinath, Ias,
let's stop working on the contrib and jax-rpc-mapper module and switch over to the ews module that
i checked in a few mins ago. It has code from both contrid/ws4j2ee and jax-rpc-mapper. It
generates the jaxb stuff as well. just run "maven" from the root directory after checking out the
ews modules.
thanks,
dims
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Idea
Posted by Srinath Perera <he...@opensource.lk>.
Hi all;
Please let me add something,
1)Practically the EJBProvider and the wrapper WS is the same thing (Reason
I decide on the wrapper WS is the understanding that the genarated code is
mora flexible than handle all in the code at ejb provider. (both use
remote interface)
2) I think the Richard concern (which I myself belive to valied) is
acsessing through the Remote interface and want to acsess the EJB using
geranimo internals to solve it.
Srinath
Note: Please sombody do me a favour if possible (Sorry if this is straight
foward Q ... I am reading abut maven .. want get answers yet)
1) I am having trouble runing the maven build (I can't afford to download
all the jar on time of build ..will take hours :( ... I have all jar's
locally How can I use it)
2)for the sake of people(including me ) who want to run the maven offline
can we have a alternative build file. I will commit it but prob is am
can't figure out how to do it yet. :(
> Richard,
>
> Have you seen the code in Axis' EJBProvider?
> (http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/providers/java/).
> We can use that as a starting point to write our own GeronimoProvider if
> we want more control...
>
> thanks,
> -- dims
>
> --- Richard Monson-Haefel <Ri...@Monson-Haefel.com> wrote:
>> Hi, I actually had an adapter written up but now I can't find it ...
>> Very weird. Anyway, if memory serves I used the ApacheRpcAdapter
>> (something like that) because this delivered the invocation in the
>> form of that could be easily translated into an Invocation object as
>> used in the Geronimo call stack. I think this is the best way to go,
>> as it lets us introduce the functionality we need for handlers in the
>> Geronimo call stack after the transaction and security interceptors
>> have been called, but before the call in delegated to the bean
>> instance.
>>
>> I'm going on vacation and won't be around next week. I hope this helps
>> ... I'm working off of memory and trying to tie loose ends before I
>> leave (read: in a rush!)
>>
>> Richard
>> --
>> Richard Monson-Haefel
>> http://www.Monson-Haefel.com
>>
>
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
------------------------------------
Lanka Sofware Foundation
------------------------------------
Re: Idea
Posted by Davanum Srinivas <di...@yahoo.com>.
Richard,
Have you seen the code in Axis' EJBProvider?
(http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/providers/java/). We can use
that as a starting point to write our own GeronimoProvider if we want more control...
thanks,
-- dims
--- Richard Monson-Haefel <Ri...@Monson-Haefel.com> wrote:
> Hi, I actually had an adapter written up but now I can't find it ... Very
> weird. Anyway, if memory serves I used the ApacheRpcAdapter (something like
> that) because this delivered the invocation in the form of that could be
> easily translated into an Invocation object as used in the Geronimo call
> stack. I think this is the best way to go, as it lets us introduce the
> functionality we need for handlers in the Geronimo call stack after the
> transaction and security interceptors have been called, but before the call
> in delegated to the bean instance.
>
> I'm going on vacation and won't be around next week. I hope this helps ...
> I'm working off of memory and trying to tie loose ends before I leave (read:
> in a rush!)
>
> Richard
> --
> Richard Monson-Haefel
> http://www.Monson-Haefel.com
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Idea
Posted by Richard Monson-Haefel <Ri...@Monson-Haefel.com>.
Hi, I actually had an adapter written up but now I can't find it ... Very
weird. Anyway, if memory serves I used the ApacheRpcAdapter (something like
that) because this delivered the invocation in the form of that could be
easily translated into an Invocation object as used in the Geronimo call
stack. I think this is the best way to go, as it lets us introduce the
functionality we need for handlers in the Geronimo call stack after the
transaction and security interceptors have been called, but before the call
in delegated to the bean instance.
I'm going on vacation and won't be around next week. I hope this helps ...
I'm working off of memory and trying to tie loose ends before I leave (read:
in a rush!)
Richard
--
Richard Monson-Haefel
http://www.Monson-Haefel.com
[EWS] ws4j2ee
Posted by Davanum Srinivas <di...@yahoo.com>.
Srinath,
Just checked in a few mods to the ws4jeee module:
- Checking in dependent libs.
- Fix classpaths in build.xml's
- Fix Clean target
Notes:
- Currently ONLY the JAXB-RI is supported. We need to be able to work with just JaxMe (without
needing JAXB-RI/JWSDP)
- Can we please integrate the ws4j2ee and the jax-rpc-mapper into one single source tree with an
integrated build (BUT generate 2 jars if you so wish)
- Please add a target to run the sample in the main build.xml itself.
- Replace org.apache.x.ws4j2ee with (org.apache.geronimo.ws or org.apache.geronimo.ws4j2ee)
Thanks,
dims
PS: Please use geronimo-dev mailing list for all discussions.
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
RE: [EWS] jax-rpc-mapper
Posted by Ias <ia...@tmax.co.kr>.
> Ias,
>
> Just checked in a few mods to the jax-rpc-mapper module:
> - Checking in dependent libs.
> - Fix classpaths in build.xml's
> - Fix code to work with latest axis.
> - "ant all" builds everything
> - Fix Clean target
Thanks for your nice work on those. I checked out all the changes and found
it worked fine.
> Notes:
> - Currently ONLY the JAXB-RI stuff works. We need to be able
> to work with just JaxMe (without needing JAXB-RI)
I'll response to this item at "Status of code in EWS" message thread.
> - Can we please integrate the ws4j2ee and the jax-rpc-mapper
> into one single source tree with an integrated build (BUT
> generate 2 jars if you so wish)
I think we can and actually we already have it as "ews" module. I agree to
stop jax-rpc-mapper module and work on the integrated ews module. (Yes, +1
:-)
Ias