Re: project.xml for clnt-axis

Nils is at your (web)service!

i had a look at clnt-axis and think there are dependencies missing.

if you download axis from apache, it has the following jars in /lib:
axis-ant
axis
commons-discovery (x)
commons-logging
jaxrpc
log4j-1.2.8 (x)
saaj (x)
wsdl4j (x)

those marked with (x) i couldn't find in project.xml

on the configuration side, everything seems to be in place

here the current error:

18.03.2005 11:30:11 org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Allocate exception for servlet AxisServlet
javax.servlet.ServletException: Error instantiating servlet class 
org.apache.axis.transport.http.AxisServlet
    at 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1034)
    at 
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:725)
    at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:131)
    at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
    at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
    at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
    at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
    at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
    at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)
    at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738)
    at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)
    at 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
    at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
    at java.lang.Thread.run(Unknown Source)



Max wrote:

> 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
>

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