I do not commit the EWS task becouse there was a problem. If I have not remove it from the patch It mean I have mess it up some how.
I download the your check in of the patch(do not look at it yet). basically I will try my best to get the test cases run and get back to you :). Thanks for your help Srinath > Srinath, > > org.apache.geronimo.ews.ws4j2ee.utils.EWSTask is missing as well in > the EWS project > > -- dims > > On Thu, 22 Jul 2004 11:01:46 -0700, Dain Sundstrom > <[EMAIL PROTECTED]> wrote: >> >> >> On Jul 21, 2004, at 7:22 PM, Srinath Perera wrote: >> >> > the patch is posted to JIRA @ >> > http://nagoya.apache.org/jira/secure/ManageAttachments.jspa?id=22172 >> :) >> > >> >> So ews generates java source code and compiles it? Is there any way >> >> to >> >> skip the Java source generation and thus the need for a compiler? >> >> -dain >> > >> > I think code generation is a must as the axis stub/skeltons need to be >> > generated anyway. >> > >> > but there may be a way out. We can provide the ews as a tools and ask >> > user >> > to run it(in here the ews can find the tools.jar in the same way >> > ant/maven >> > find it, via shell script) and then geronimo can deploy the generated >> > code. (If I am right sun RI ask use to run the generater ws* before >> > deploy >> > code). >> > >> > To me it is better if we can say to the user "give us the bundle the >> > J2EE >> > spec talk about and we will do the rest!!!", but if there practical >> > problems I think it is ok to ask user to run EWS themselves and then >> > deploy. >> >> If we need to generate Java source code and compile it, then I would >> rather have the deployment process simply do that. What I was really >> getting at is can we simply generate the byte code directly and skip >> the Java source generation and compile steps? >> >> -dain >> >> > > > -- > Davanum Srinivas - http://webservices.apache.org/~dims/ > > ------------------------------------ Lanka Sofware Foundation ------------------------------------
