Re: project.xml for clnt-axis

A question on the different keel clients: the last clnt-axis client 
included all of the axis jars and jsp's etc. Nils was doing the same 
thing with clnt-flex - by including the whole of the Flex 
infrastructure. Is it perhaps not better just to include the interface 
code with keel and the axis/flex wars should be deployed independently? 
This is what I did with my Flex coding initiatives. I simply used the 
axis-server project and deployed Flex myself. It should not be too hard 
to get a clnt-axis working like that as well, assuming of course that 
axis has separate deployment wars?

Another question: is the idea of the clnt modules to be able to deploy 
several at the same time? For example a Flex client, an axis client and 
a struts client. Is the maven build system designed to do this?

Max

> Max,
>
>>
>>
>> I believe that you were doing some work on the maven clnt-axis 1.01 
>> module. I have just tried this with plugin 13 but it does not work. I 
>> replaced the clnt-struts dependency with clnt-axis, performed a 
>> keel:maven and built the war file. The war file deploys but does not 
>> seem to contain all the required axis bits - happyaxis.jsp fails.
>>
> I was trying to convert clnt-axis to work with the new build system.  
> However, I am not a Axis/SOAP user, and I don't really have the time 
> to invest in learning all that. I will help anyone willing to trudge 
> through it and suggest changes in the integration with the 
> build-system, though.  I guess Nils is our most active user at this 
> point.
>
> Shash
>
> http://keelframework.org/documentation.shtml
> Keelgroup mailing list
> [email protected]
> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
>
>
>

http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com