Sending large files to WS
Hi, I’am writing now my thesis and want to use Axis in my project. We want to develop a P2P-Filesharing system for promotional and commercial use where any peer can exchange some files with another peers in a trusted environment. We use in our project JXTA for filesharing. But in addition to JXTA, we need some Services which we use to query, insert and delete data in a database. I have now read the user guide and everything works fine. I write a test service with the following steps. Create a java interface. Use Java2WSDL Use WSDL2Java Deploy Service Invoke Service from a testclient. Our problem now is that our clients sometimes must register a new file for sharing. A peer must upload a file to the service and on the service a method must calculate the Fingerprint. How can I upload a file to a web service? I’ve see in informer postings that axis offers to use attachments? But which size is allowed for attachments? Another idea from me was to create a Bean with a byte[] getFile() and setFile(byte[] file) method where I can read on the client side a file into a byte array and on the server side I extract the byte[]. Today I want to test the variation with the bean but my server has not enough memory and throw java.lang.OutOfMemoryError: Java heap space. Our first goal is to upload only audio files which is normally not bigger than 4 - 10 MB. In future we plan to use upload bigger files(video files). I don’t know if I’am on the right way. Can anybody help me? Are there any simple code examples how to use Attachments in Axis? Thanks for any help in advance. Ferruh Zamangör
RE: Axis and Castor - newbie question - Extending org.apache.axis.encoding.ser.castor.Deserializer
Hi there, first: I have the same problem. I'd need Axis to use Castor serializer with mapping file. But I can tell you, with the given Castor-Serializer it's not possible, as I made my may through the source of it. But it would be easyly extendable. Currently I'm extending it, giving the mapping file within the wsdd of the type mapping. This should work. Now my question: The DEserializer interface is completly different. Instead of having one easy method serialize(...) that is doing all (and where just the castor marshaller is called), there are a lot of methods that seem to be called element by element. The org.apache.axis.encoding.ser.castor.Deserializer does not seem to do much different then the normal Axis Deserializer and I didn't find any place where to provide the castor mapping. And another drawback: I didn't find an easy way to provide the mapping-file parameter. The Serializer directly get's the parameters from the wsdd file, but I couldn't find something like that in the deserializer interface. Did anyone work already with this things, or was overriding a deserializer? Any ideas? Cheers, Frank -Original Message- From: David Easley [mailto:[EMAIL PROTECTED] Sent: 1. mai 2005 19:00 To: axis-user@ws.apache.org Subject: Axis and Castor - newbie question I've been experimenting using Axis and Castor along the lines described in the IBM article: http://www-106.ibm.com/developerworks/webservices/library/ws-castor/ Everything's working fine, but I have a few questions: 1. I want to test that the WS messages are being validated against my schema (after all, this is one of the main reasons I'm using Castor rather than plain old WSDL2Java). My test set-up involves using the Castor generated code on the client and server side, so it's impossible to generate invalid XML! What's the simplest way to test this? 2. On the server side, I already have a set of DTOs that I must use internal to the app. So I'm currently having to translate between the Castor generated objects and my own DTOs, which is a pain. Ideally, I'd like Castor to unmarshall/marshall directly to/from my DTOs. I've read the provided Castor XML Mapping documentation but I can't see how to integrate my Castor XML mapping file into my Axis+Castor solution. Can this be done? 3. If the answer to 2. is yes, can the incoming WS request messages and the outgoing WS response messages still be validated against my schema? If the answer to 2 & 3 is yes, yipp! Thanks for any help, David
wsdl2java
Hello, how can I make wsdl2java to emit (I need SOAP 1.2 for fault sub codes): _call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP12_CONSTANTS); instead of _call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP11_CONSTANTS); This happens in the binding stubs that wsdl2java generates. I can of course change SOAP11_CONSTANTS to SOAP12_CONSTANTS manually, but those changes will get overwritten when my Ant build script invokes wsdl2java. Jyrki
newbie question: CommonsHTTPSender examples
Hi all, Can someone send me examples of how to use org.apache.axis.transport.http.CommonsHTTPSender class to send SOAP message? The only example that I can find is to specify it in wsdd. Currently, I send SOAP message like this: Service service = new Service(); Call call = (Call) service.createCall(); SOAPEnvelope elemenv = call.invoke(env); (env is a SOAPEnvelope.) I want to use CommonsHTTPSender so that I can use POST HTTP/1.1. Thanks in advance! Regards, Ada
How to get SOAP body parameter
Hi all, I have the SOAPMessage as this -- http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://schemas.xmlsoap.org/ws/2002/07/utility";> http://schemas.xmlsoap.org/soap/encoding/"; xmlns:ns1="http://dataaccess.service.eTranscript.interfacemgmt.net";>--- I want to get the content of ... How to do that in Java? Thanks, Yixing Ma
RE: running out of sockets???
When the application close a socket, the system may delay the actual release for a defined time that you can configure. During this time, the socket is in "close wait" state until the communication resources are fully released. I don't remember which registry key defines this for windows, but the value default may be minutes. In fact, 8 invocations don't seem to be enough to consume all the numbers. I have experienced this kind of problem with some performance testing clients that can quickly use all the port numbers... In your case, more probably, the problem cause will be in your http server or client... and for that i have no idea... Sorry. >>> -Original Message- >>> From: John Windberg [mailto:[EMAIL PROTECTED] >>> Sent: Wednesday, May 18, 2005 8:05 PM >>> To: axis-user@ws.apache.org >>> Subject: RE: running out of sockets??? >>> >>> >>> If my client app calls web services one at a time, >>> shouldn't the previous socket be closed before the >>> next socket is open? >>> And in this case, I'm only managing to get around 8 >>> web service calls before it starts failing. >>> >>> 8 is not very many. >>> >>> -j >>> >>> >>> >>> --- Ephemeris Lappis <[EMAIL PROTECTED]> >>> wrote: >>> > Are you sure the problem is the http connections ? >>> > I remember, long time ago, a problem with sockets on >>> > windows workstation >>> > systems (NT and 2000) which source was the limited >>> > socket numbers. If i >>> > remember well, unlike server versions, workstation >>> > configurations limit >>> > socket number up to 5000. In a typical case when >>> > both your server and your >>> > client run on the same system, you can quickly >>> > consume all your accepted >>> > numbers. If you want more, you have to change some >>> > key in the registry >>> > (sorry, i don't remember which one). The problem >>> > comes when many connections >>> > are open in a short time. You must also adjust the >>> > time the stack keeps the >>> > socket in close-wait state before the number can be >>> > used again... You can >>> > check it with a netstat or a similar tools. >>> > I hope this can help you. >>> > >>> > >>> > >>> -Original Message- >>> > >>> From: John Windberg [mailto:[EMAIL PROTECTED] >>> > >>> Sent: Wednesday, May 18, 2005 3:44 AM >>> > >>> To: axis-user@ws.apache.org >>> > >>> Subject: running out of sockets??? >>> > >>> >>> > >>> >>> > >>> I'm writing client code against Autodesk Vault >>> > web >>> > >>> services which are .Net code within an IIS >>> > instance. >>> > >>> After a series of calls I start getting "out of >>> > >>> sockets" or "access denied" errors, which seem >>> > to be >>> > >>> caused because IIS on this XP instance has a >>> > limited >>> > >>> number of available connections. >>> > >>> >>> > >>> I'm only calling one at a time. Why would my >>> > >>> connections not be getting closed? >>> > >>> >
RE: running out of sockets???
If my client app calls web services one at a time, shouldn't the previous socket be closed before the next socket is open? And in this case, I'm only managing to get around 8 web service calls before it starts failing. 8 is not very many. -j --- Ephemeris Lappis <[EMAIL PROTECTED]> wrote: > Are you sure the problem is the http connections ? > I remember, long time ago, a problem with sockets on > windows workstation > systems (NT and 2000) which source was the limited > socket numbers. If i > remember well, unlike server versions, workstation > configurations limit > socket number up to 5000. In a typical case when > both your server and your > client run on the same system, you can quickly > consume all your accepted > numbers. If you want more, you have to change some > key in the registry > (sorry, i don't remember which one). The problem > comes when many connections > are open in a short time. You must also adjust the > time the stack keeps the > socket in close-wait state before the number can be > used again... You can > check it with a netstat or a similar tools. > I hope this can help you. > > > >>> -Original Message- > >>> From: John Windberg [mailto:[EMAIL PROTECTED] > >>> Sent: Wednesday, May 18, 2005 3:44 AM > >>> To: axis-user@ws.apache.org > >>> Subject: running out of sockets??? > >>> > >>> > >>> I'm writing client code against Autodesk Vault > web > >>> services which are .Net code within an IIS > instance. > >>> After a series of calls I start getting "out of > >>> sockets" or "access denied" errors, which seem > to be > >>> caused because IIS on this XP instance has a > limited > >>> number of available connections. > >>> > >>> I'm only calling one at a time. Why would my > >>> connections not be getting closed? > >
RE: running out of sockets???
Are you sure the problem is the http connections ? I remember, long time ago, a problem with sockets on windows workstation systems (NT and 2000) which source was the limited socket numbers. If i remember well, unlike server versions, workstation configurations limit socket number up to 5000. In a typical case when both your server and your client run on the same system, you can quickly consume all your accepted numbers. If you want more, you have to change some key in the registry (sorry, i don't remember which one). The problem comes when many connections are open in a short time. You must also adjust the time the stack keeps the socket in close-wait state before the number can be used again... You can check it with a netstat or a similar tools. I hope this can help you. >>> -Original Message- >>> From: John Windberg [mailto:[EMAIL PROTECTED] >>> Sent: Wednesday, May 18, 2005 3:44 AM >>> To: axis-user@ws.apache.org >>> Subject: running out of sockets??? >>> >>> >>> I'm writing client code against Autodesk Vault web >>> services which are .Net code within an IIS instance. >>> After a series of calls I start getting "out of >>> sockets" or "access denied" errors, which seem to be >>> caused because IIS on this XP instance has a limited >>> number of available connections. >>> >>> I'm only calling one at a time. Why would my >>> connections not be getting closed?
Re: running out of sockets...
Uh, I'm just using the code created by WSDL2Java with org.apache.axis.transport.http.CommonsHTTPSender in my client-config.wsdd. I needed that so I could do ntlm with another web service. The creators of this service are all .net weenies and with the .net tools this problem doesn't happen. Is there a config somewhere to force closure of a connection no longer needed? I create the locator, get the stub, and use it, over and over again calling methods on it created by WSDL2Java. This would have to be changes to the client only. The server is not under my control and does not cause problems when used with vs .net based clients. Only with axis clients. -j --- Marko Sormunen <[EMAIL PROTECTED]> wrote: > John Windberg wrote the following on 18.5.2005 3:28: > > I'm writing client code against Autodesk Vault web > > services which are .Net code within an IIS > instance. > > After a series of calls I start getting "out of > > sockets" or "access denied" errors, which seem to > be > > caused because IIS on this XP instance has a > limited > > number of available connections. > > I'm only calling one at a time. Why would my > > connections not be getting closed? > > This is just an idea, but could it be because HTTP > 1.1 connections have a time > out of 300 seconds by default? The socket level > connection is not terminated as > the response is read from the socket, but left open > in case the same socket is > used again sortly. This is a HTTP 1.1 way of not > creating a new socket with each > HTTP call. Are you using the same socket instance or > creating a new one with > each call? If you wait for approximately 300 > seconds, can your client again make > the calls succesfully? > > -- > Marko Sormunen, M.Sc. > Messenger: [EMAIL PROTECTED] > HIS-research unit, Centek, Computing Centre > University of Kuopio >
Reset keystore, trustore settings during runtime
Title: Reset keystore, trustore settings during runtime Hi all, I'm trying to reset, modify (many times !) keystore, trustore and http proxy settings during runtime. For the http proxy, I use the solution described in http://wiki.apache.org/ws/FrontPage/Axis/AxisProxy http://marc.theaimsgroup.com/?l=axis-user&m=111023524509845&w=2 But I found any solution concerning the keystore and trustore settings. Did you have any idea ? Thanks & Regards, Rémy
Deployment wsdd and Copying files
I have been going through the Axis user's guide and working through the
examples and my own simple test. I cannot get the admin client to copy
the class to the server directory though. (I'm using axis 1.2 RC3 on
Tomcat 5.5, default port 8080). Here's what I have done:
1. Created a simple java class: TestService.java
package com.abc.service;
public class TestService {
public String echoMethod(String arg)
{
return arg;
}
}
2. Created a simple wsdd:
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
3. Ran the AdminClient (from ant)
The response was:
[java] Done processing
4. Looked in the server-config.wsdd. It included the service
TestService
5. Tried to list the service using the axis web page. I got:
Fault - Could not find class for the service named:
com.abc.service.TestService
Hint: you may need to copy your class files/tree into
the right location (which depends on the servlet system you are using).;
nested exception is:
java.lang.ClassNotFoundException:
com.ncc.wrap.weatherservice.TestService
6. My trivial client for this service failed as well.
Why does this fail? Does the admin client create the correct directory
structure under classes and copy the class file?
--> Do I have to explicitly copy the service to the server? If so, is
there an ant task that I should use?
If I create the directory structure .../WEB-INF/classes/com/abc/service
and then copy the TestService.class into there, it works. Do I have to
do that step manually (or within ant)?
Thanks,
Clark
org.apache.axis.ConfigurationException: No service named is available
Hey all,
i'm trying to connect to a self-developed web service from a jsp page.
The web service is deployed in the same tomcat and is working.
I can successfully use Axis: http://../../ServiceName?method=getVersion
I can use a java console application to call getVersion() on my service.
However, trying to use the webservice from within a JSP page, it results
in the following exception.
I think it has something to do with the client-config.wsdd.
Since the service is defined there.
It is found in standalone mode, but I think that he might have problems
getting it in Tomcat. The classpath where client-config.wsdd resides, is
added to the Tomcat classpath (in the Sysdeo Tomcat Eclipse Plugin).
If anyone has a tipp, a comment or anything. Please let me know :-)
regards
Mike
-CLIENT-CODE IN JSP:--
<% Retriever retriever = new Retriever(); %>
<%=retriever.getVersion();%>
-RETRIEVER:--
Service service = new Service();
// I gave him the service name here for testing,
// but didn't help.
// new QName("","ServiceName");
call = (Call) service.createCall();
call.setOperationStyle(Style.WRAPPED);
call.setOperationUse(Use.LITERAL);
call.setUsername(username);
call.setPassword(password);
call.setTargetEndpointAddress(endpoint); // endpoint is correct
call.setOperation("GetVersion");
Object obj = call.invoke(new Object[] { someParameters });
VERSIONS---
Java 1.4.2_06, running on Windows 2000
Tomcat 5.0.30, running in Eclipse 3.1M7
Axis 1.2 final, running in same Tomcat
Struts 1.2, running in same Tomcat
-EXCEPTION:--
15:57:16,984 DEBUG [org.apache.axis.i18n.ProjectResourceBundle]
org.apache.axis.i18n.resource::handleGetObject(engineFactory)
15:57:16,984 DEBUG
[org.apache.axis.configuration.EngineConfigurationFactoryFinder] Got
EngineFactory:
org.apache.axis.configuration.EngineConfigurationFactoryDefault
15:57:16,984 DEBUG [org.apache.axis.AxisEngine] Enter: AxisEngine::init
15:57:17,000 DEBUG [org.apache.axis.AxisEngine] Exit: AxisEngine::init
15:57:17,000 DEBUG [org.apache.axis.i18n.ProjectResourceBundle]
org.apache.axis.i18n.resource::handleGetObject(transport00)
15:57:17,000 DEBUG [org.apache.axis.client.Call] Transport is
[EMAIL PROTECTED]
15:57:17,000 DEBUG [org.apache.axis.description.OperationDesc]
@b3951dsetReturnType(null)
15:57:17,000 DEBUG [org.apache.axis.client.Call] Enter: Call::invoke(ns,
meth, args)
15:57:17,000 DEBUG [org.apache.axis.client.Call] operation=name:null
returnQName: null
returnType: null
returnClass: null
elementQName:null
soapAction: null
style: rpc
use: encoded
numInParams: 0
method:null
15:57:17,000 DEBUG [org.apache.axis.client.Call] operation.getNumParams()=0
15:57:17,000 DEBUG [org.apache.axis.client.Call] Enter:
Call::invoke(RPCElement)
15:57:17,000 DEBUG [org.apache.axis.SOAPPart] Enter: SOAPPart
ctor(FORM_SOAPENVELOPE)
15:57:17,000 DEBUG [org.apache.axis.i18n.ProjectResourceBundle]
org.apache.axis.i18n.resource::handleGetObject(setMsgForm)
15:57:17,000 DEBUG [org.apache.axis.SOAPPart] Setting current message
form to: FORM_SOAPENVELOPE (currentMessage is now
org.apache.axis.message.SOAPEnvelope)
15:57:17,000 DEBUG [org.apache.axis.SOAPPart] Exit: SOAPPart ctor()
15:57:17,000 DEBUG [org.apache.axis.i18n.ProjectResourceBundle]
org.apache.axis.i18n.resource::handleGetObject(addBody00)
15:57:17,000 DEBUG [org.apache.axis.message.SOAPBody] Adding body
element to message...
15:57:17,000 DEBUG [org.apache.axis.client.Call] Enter: Call::invoke()
15:57:17,000 DEBUG [org.apache.axis.SOAPPart] Enter:
SOAPPart::getAsSOAPEnvelope()
15:57:17,015 DEBUG [org.apache.axis.i18n.ProjectResourceBundle]
org.apache.axis.i18n.resource::handleGetObject(currForm)
15:57:17,015 DEBUG [org.apache.axis.SOAPPart] current form is
FORM_SOAPENVELOPE
15:57:17,015 DEBUG [org.apache.axis.MessageContext] MessageContext:
setTargetService()
15:57:17,015 DEBUG [org.apache.axis.i18n.ProjectResourceBundle]
org.apache.axis.i18n.resource::handleGetObject(noService10)
15:57:17,015 DEBUG [org.apache.axis.ConfigurationException] Exception:
org.apache.axis.ConfigurationException: No service named is available
org.apache.axis.ConfigurationException: No service named is available
at
org.apache.axis.configuration.FileProvider.getService(FileProvider.java:233)
at org.apache.axis.AxisEngine.getService(AxisEngine.java:311)
at org.apache.axis.MessageContext.setTargetService(MessageContext.java:755)
at org.apache.axis.client.Call.invoke(Call.java:2689)
at org.apache.axis.client.Call.invoke(Call.java:2424)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
at
de.innovations.licenseserver.axis.Retriever.getServerStatus(Retriever.java:168)
at
org.apache.jsp.serverstatus_jsp._jspService(org.apache.jsp.serverstatus_jsp:77)
RE: AdminClient + log4j
Thanks Tony, I think my problem was not including the "file:" part in front of the path to the properties file. The log still seems pretty sparse though. ie, if an axisfault occurs during deployment, it is only printed, and not actually logged through log4j. I will take a look at the src to see if that really is the case. (Can anyone else confirm if it is or isn't?) thanks again, --Chris -Original Message-From: Tony Fernandes [mailto:[EMAIL PROTECTED]Sent: Tuesday, May 17, 2005 4:18 AMTo: axis-user@ws.apache.orgSubject: Re: AdminClient + log4j This configuration file works with both méthods ( see attachments) under windows and solaris. -Dlog4j.configuration=file:/home//log4j.properties or CLASSPATH + restart your application server On 5/16/05, Hewitt, Christopher <[EMAIL PROTECTED]> wrote: Hi,Does anyone know how to get the AdminClient to use log4j?I just can't seem to get it to work. I've added a log4j.properties to the classpath, as well as passing in the configuration file via -Dlog4j.configuration=xxx.Neither seem to work, and AdminClient's output only appears to be print statements to stdout. Any help would be appreciated.Thanks.Chris HewittEmail: [EMAIL PROTECTED]
Re: jws compile problem
Sorry, I didn't mean to ask that question. Was talking to someone else at the time! Sorry
DanOn 5/18/05, Dan O'Neill <[EMAIL PROTECTED]> wrote:
No problem...
Thanks,
Dan
Actually, what are your imports? On 5/18/05, Frank <
[EMAIL PROTECTED]> wrote:
Dan O'Neill wrote:
Actually that
should have been my first reply.. don't know why I was focusin on
tomcat
The reason i mentioned the placement of the jws is that in your first
email you were just placing the class file into the jwsClasses folder.
Why not put the original TLS.jws into the tomcathome\webapps\axis
folder?
actually that's what I did initially. but when axis tried to compile
it when I went to that url it failed.
As a work around I tired to place the manually generated class file in
the classes directory, that too failed. I'm Sorry guess I did not make
that clear.
But if you've got it working, well done, and sorry for this curiousity!
Dan
On 5/18/05, Frank <[EMAIL PROTECTED]> wrote:
found the problem classpath seems to not make a
difference, why I don't
know. Put the classes files in axis/WEB-INF/classes and it find them.
And this is where in the Axis documentation? LOL
The reason I think its tomcats classpath is that you can (I think)
compile the java without a problem normally?
Also If that doesn't solve it try just putting the jws file straight
into the webapps/axis folder and let axis itself look after the
compiling
That was the problem letting axis compile then. Just doing
a javac on
them worked directly worked, that was the frustrating problem and was
using the same classpath
Thanks for the help
Dan
On 5/17/05, Frank <[EMAIL PROTECTED]
>
wrote:
Well
I looked at the catalina.bat file. Seems it does not use the
CLASSPATH environment variable that is set for the system. I changed
it to do that and restarted Tomcat but no good. Same problem.
Is there a separate variable used for tomcat for it's classpath beyond
that? like TOMCAT_CLASSPATH or something?
Thanks,
Frank
Dan O'Neill wrote:
This
is probably a stupid thing to say but have you checked tomcats
classpath
Dan
On 5/17/05, Frank <[EMAIL PROTECTED]
>
wrote:
I
have a problem that I believe to be a classpath problem (see below),
but I have included the path to the localhost directory, even created a
jar of the class files and still get the error. I can compile the
file directory just fine. But if I put the class file from a normal
javac in the jwsClasses directory the call to produce the WSDL
(http://kw14:8080/axis/TLS.jws?wsdl)
from the browser say's file not
found.
Line in java code (the directory structure exists and the java code is
compiled):
import localhost.axis.OMS_jws.*;
Running on XP
Using tomcat distributed with JWSDP 1.4
Axis 1.2
AXIS error
Sorry, something seems to have gone wrong... here are
the
details:
Fault - Error while compiling: C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.javaAxisFault faultCode: {
http://xml.apache.org/axis/}Server.compileError faultSubcode: faultString: Error while compiling: C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java faultActor: faultNode:
faultDetail: {}Errors:Error compiling C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java:Line 0, column 0: could not parse error message: Note: sun.tools.javac.Main has been deprecated.
SoC:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java:39: Package localhost.axis.OMS_jws not found in import.import localhost.axis.OMS_jws.*;
--
http://www.spreadfirefox.com/?q=affiliates&id=0&t=82"
>http://sfx-images.mozilla.org/affiliates/Buttons/80x15/white_1.gif"/
>
--
"I swear, the next bastard that kisses the ground in front of me is
gonna get
kicked in the antique chicken coops." - Cohen the Barbarian
--
"I swear, the next bastard that kisses the ground in front of me is
gonna get
kicked in the antique chicken coops." - Cohen the Barbarian
-- "I swear, the next bastard that kisses the ground in front of me is gonna getkicked in the antique chicken coops." - Cohen the Barbarian
-- "I swear, the next bastard that kisses the ground in front of me is gonna getkicked in the antique chicken coops." - Cohen the Barbarian
Re: jws compile problem
No problem...
Thanks,
Dan
Actually, what are your imports? On 5/18/05, Frank <[EMAIL PROTECTED]> wrote:
Dan O'Neill wrote:
Actually that
should have been my first reply.. don't know why I was focusin on
tomcat
The reason i mentioned the placement of the jws is that in your first
email you were just placing the class file into the jwsClasses folder.
Why not put the original TLS.jws into the tomcathome\webapps\axis
folder?
actually that's what I did initially. but when axis tried to compile
it when I went to that url it failed.
As a work around I tired to place the manually generated class file in
the classes directory, that too failed. I'm Sorry guess I did not make
that clear.
But if you've got it working, well done, and sorry for this curiousity!
Dan
On 5/18/05, Frank <[EMAIL PROTECTED]> wrote:
found the problem classpath seems to not make a
difference, why I don't
know. Put the classes files in axis/WEB-INF/classes and it find them.
And this is where in the Axis documentation? LOL
The reason I think its tomcats classpath is that you can (I think)
compile the java without a problem normally?
Also If that doesn't solve it try just putting the jws file straight
into the webapps/axis folder and let axis itself look after the
compiling
That was the problem letting axis compile then. Just doing
a javac on
them worked directly worked, that was the frustrating problem and was
using the same classpath
Thanks for the help
Dan
On 5/17/05, Frank <[EMAIL PROTECTED]
>
wrote:
Well
I looked at the catalina.bat file. Seems it does not use the
CLASSPATH environment variable that is set for the system. I changed
it to do that and restarted Tomcat but no good. Same problem.
Is there a separate variable used for tomcat for it's classpath beyond
that? like TOMCAT_CLASSPATH or something?
Thanks,
Frank
Dan O'Neill wrote:
This
is probably a stupid thing to say but have you checked tomcats
classpath
Dan
On 5/17/05, Frank <[EMAIL PROTECTED]
>
wrote:
I
have a problem that I believe to be a classpath problem (see below),
but I have included the path to the localhost directory, even created a
jar of the class files and still get the error. I can compile the
file directory just fine. But if I put the class file from a normal
javac in the jwsClasses directory the call to produce the WSDL
(http://kw14:8080/axis/TLS.jws?wsdl)
from the browser say's file not
found.
Line in java code (the directory structure exists and the java code is
compiled):
import localhost.axis.OMS_jws.*;
Running on XP
Using tomcat distributed with JWSDP 1.4
Axis 1.2
AXIS error
Sorry, something seems to have gone wrong... here are
the
details:
Fault - Error while compiling: C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.javaAxisFault faultCode: {
http://xml.apache.org/axis/}Server.compileError faultSubcode: faultString: Error while compiling: C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java faultActor: faultNode:
faultDetail: {}Errors:Error compiling C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java:Line 0, column 0: could not parse error message: Note: sun.tools.javac.Main has been deprecated.
C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java:39: Package localhost.axis.OMS_jws not found in import.import localhost.axis.OMS_jws.*;
--
http://www.spreadfirefox.com/?q=affiliates&id=0&t=82"
>http://sfx-images.mozilla.org/affiliates/Buttons/80x15/white_1.gif"/
>
--
"I swear, the next bastard that kisses the ground in front of me is
gonna get
kicked in the antique chicken coops." - Cohen the Barbarian
--
"I swear, the next bastard that kisses the ground in front of me is
gonna get
kicked in the antique chicken coops." - Cohen the Barbarian
-- "I swear, the next bastard that kisses the ground in front of me is gonna getkicked in the antique chicken coops." - Cohen the Barbarian
Re: jws compile problem
Dan O'Neill wrote:
Actually that
should have been my first reply.. don't know why I was focusin on
tomcat
The reason i mentioned the placement of the jws is that in your first
email you were just placing the class file into the jwsClasses folder.
Why not put the original TLS.jws into the tomcathome\webapps\axis
folder?
actually that's what I did initially. but when axis tried to compile
it when I went to that url it failed.
As a work around I tired to place the manually generated class file in
the classes directory, that too failed. I'm Sorry guess I did not make
that clear.
But if you've got it working, well done, and sorry for this curiousity!
Dan
On 5/18/05, Frank <[EMAIL PROTECTED]> wrote:
found the problem classpath seems to not make a
difference, why I don't
know. Put the classes files in axis/WEB-INF/classes and it find them.
And this is where in the Axis documentation? LOL
The reason I think its tomcats classpath is that you can (I think)
compile the java without a problem normally?
Also If that doesn't solve it try just putting the jws file straight
into the webapps/axis folder and let axis itself look after the
compiling
That was the problem letting axis compile then. Just doing
a javac on
them worked directly worked, that was the frustrating problem and was
using the same classpath
Thanks for the help
Dan
On 5/17/05, Frank <[EMAIL PROTECTED]>
wrote:
Well
I looked at the catalina.bat file. Seems it does not use the
CLASSPATH environment variable that is set for the system. I changed
it to do that and restarted Tomcat but no good. Same problem.
Is there a separate variable used for tomcat for it's classpath beyond
that? like TOMCAT_CLASSPATH or something?
Thanks,
Frank
Dan O'Neill wrote:
This
is probably a stupid thing to say but have you checked tomcats
classpath
Dan
On 5/17/05, Frank <[EMAIL PROTECTED]
>
wrote:
I
have a problem that I believe to be a classpath problem (see below),
but I have included the path to the localhost directory, even created a
jar of the class files and still get the error. I can compile the
file directory just fine. But if I put the class file from a normal
javac in the jwsClasses directory the call to produce the WSDL
(http://kw14:8080/axis/TLS.jws?wsdl)
from the browser say's file not
found.
Line in java code (the directory structure exists and the java code is
compiled):
import localhost.axis.OMS_jws.*;
Running on XP
Using tomcat distributed with JWSDP 1.4
Axis 1.2
AXIS error
Sorry, something seems to have gone wrong... here are
the
details:
Fault - Error while compiling: C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java
AxisFault
faultCode: {
http://xml.apache.org/axis/}Server.compileError
faultSubcode:
faultString: Error while compiling: C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java
faultActor:
faultNode:
faultDetail:
{}Errors:Error compiling C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java:
Line 0, column 0: could not parse error message: Note: sun.tools.javac.Main has been deprecated.
C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java:39:
Package localhost.axis.OMS_jws not found in import.
import localhost.axis.OMS_jws.*;
--
http://www.spreadfirefox.com/?q=affiliates&id=0&t=82"
>http://sfx-images.mozilla.org/affiliates/Buttons/80x15/white_1.gif"/
>
--
"I swear, the next bastard that kisses the ground in front of me is
gonna get
kicked in the antique chicken coops." - Cohen the Barbarian
--
"I swear, the next bastard that kisses the ground in front of me is
gonna get
kicked in the antique chicken coops." - Cohen the Barbarian
Re: jws compile problem
Actually that should have been my first reply.. don't know why I was focusin on tomcat
The reason i mentioned the placement of the jws is that in your first
email you were just placing the class file into the jwsClasses folder.
Why not put the original TLS.jws into the tomcathome\webapps\axis
folder?
But if you've got it working, well done, and sorry for this curiousity!
Dan
On 5/18/05, Frank <[EMAIL PROTECTED]> wrote:
found the problem classpath seems to not make a difference, why I don't
know. Put the classes files in axis/WEB-INF/classes and it find them.
And this is where in the Axis documentation? LOL
The reason I think its tomcats classpath is that you can (I think)
compile the java without a problem normally?
Also If that doesn't solve it try just putting the jws file straight
into the webapps/axis folder and let axis itself look after the
compiling
That was the problem letting axis compile then. Just doing a javac on
them worked directly worked, that was the frustrating problem and was
using the same classpath
Thanks for the help
Dan
On 5/17/05, Frank <[EMAIL PROTECTED]> wrote:
Well I looked at the catalina.bat file. Seems it does not use the
CLASSPATH environment variable that is set for the system. I changed
it to do that and restarted Tomcat but no good. Same problem.
Is there a separate variable used for tomcat for it's classpath beyond
that? like TOMCAT_CLASSPATH or something?
Thanks,
Frank
Dan O'Neill wrote:
This
is probably a stupid thing to say but have you checked tomcats
classpath
Dan
On 5/17/05, Frank <[EMAIL PROTECTED]
>
wrote:
I
have a problem that I believe to be a classpath problem (see below),
but I have included the path to the localhost directory, even created a
jar of the class files and still get the error. I can compile the
file directory just fine. But if I put the class file from a normal
javac in the jwsClasses directory the call to produce the WSDL
(http://kw14:8080/axis/TLS.jws?wsdl)
from the browser say's file not
found.
Line in java code (the directory structure exists and the java code is
compiled):
import localhost.axis.OMS_jws.*;
Running on XP
Using tomcat distributed with JWSDP 1.4
Axis 1.2
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - Error while compiling: C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.javaAxisFault faultCode: {
http://xml.apache.org/axis/}Server.compileError faultSubcode: faultString: Error while compiling: C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java faultActor: faultNode: faultDetail:
{}Errors:Error compiling C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java:Line 0, column 0: could not parse error message: Note: sun.tools.javac.Main has been deprecated.C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java:39:
Package localhost.axis.OMS_jws not found in import.import localhost.axis.OMS_jws.*;
--
http://www.spreadfirefox.com/?q=affiliates&id=0&t=82"
>http://sfx-images.mozilla.org/affiliates/Buttons/80x15/white_1.gif"/
>
--
"I swear, the next bastard that kisses the ground in front of me is
gonna get
kicked in the antique chicken coops." - Cohen the Barbarian
-- "I swear, the next bastard that kisses the ground in front of me is gonna getkicked in the antique chicken coops." - Cohen the Barbarian
Re: jws compile problem
Dan O'Neill wrote:
I know this is kind
of cheating but and again I don't know if it will
solve your problem but try putting all the axis jar files into a
\webapps\ROOT\WEB-INF\lib folder, where is tomcats home
folder. These automatically get dynamically added to the classpath when
tomcat is started.
found the problem classpath seems to not make a difference, why I don't
know. Put the classes files in axis/WEB-INF/classes and it find them.
And this is where in the Axis documentation? LOL
The reason I think its tomcats classpath is that you can (I think)
compile the java without a problem normally?
Also If that doesn't solve it try just putting the jws file straight
into the webapps/axis folder and let axis itself look after the
compiling
That was the problem letting axis compile then. Just doing a javac on
them worked directly worked, that was the frustrating problem and was
using the same classpath
Thanks for the help
Dan
On 5/17/05, Frank <[EMAIL PROTECTED]> wrote:
Well I looked at the catalina.bat file. Seems it does not use the
CLASSPATH environment variable that is set for the system. I changed
it to do that and restarted Tomcat but no good. Same problem.
Is there a separate variable used for tomcat for it's classpath beyond
that? like TOMCAT_CLASSPATH or something?
Thanks,
Frank
Dan O'Neill wrote:
This
is probably a stupid thing to say but have you checked tomcats
classpath
Dan
On 5/17/05, Frank <[EMAIL PROTECTED]>
wrote:
I
have a problem that I believe to be a classpath problem (see below),
but I have included the path to the localhost directory, even created a
jar of the class files and still get the error. I can compile the
file directory just fine. But if I put the class file from a normal
javac in the jwsClasses directory the call to produce the WSDL
(http://kw14:8080/axis/TLS.jws?wsdl)
from the browser say's file not
found.
Line in java code (the directory structure exists and the java code is
compiled):
import localhost.axis.OMS_jws.*;
Running on XP
Using tomcat distributed with JWSDP 1.4
Axis 1.2
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - Error while compiling: C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java
AxisFault
faultCode: {
http://xml.apache.org/axis/}Server.compileError
faultSubcode:
faultString: Error while compiling: C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java
faultActor:
faultNode:
faultDetail:
{}Errors:Error compiling C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java:
Line 0, column 0: could not parse error message: Note: sun.tools.javac.Main has been deprecated.
C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java:39:
Package localhost.axis.OMS_jws not found in import.
import localhost.axis.OMS_jws.*;
--
http://www.spreadfirefox.com/?q=affiliates&id=0&t=82"
>http://sfx-images.mozilla.org/affiliates/Buttons/80x15/white_1.gif"/
>
--
"I swear, the next bastard that kisses the ground in front of me is
gonna get
kicked in the antique chicken coops." - Cohen the Barbarian
Re: Session not set in generated code
Paul, Tom,
Thanks for your tips, now i've got it to work.
I've only changed someStub._getCall().setMaintainSession(true); to
someStub.setMaintainSession(true); to set the maintainsession in the
parent stub.
Thanks for the helping hand.
Peter
Flores, Raul schreef:
The deployscope attribute listed in your build.xml file is used for the
server side build. It causes the scope attribute to be generated in the
deploy.xml file as defined (application, session, request).
Once the client stubs have been generated, code the client as previously
suggested:
KodoLocator locator = new KodoLocator();
KodoServicePortType kodoDs = locator.getKodoServicePort(url);
( (Stub) kodoDs).setMaintainSession(true);
Raul Flores
-Original Message-
From: Peter Bosmans [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 17, 2005 4:45 AM
To: axis-user@ws.apache.org
Subject: Re: Session not set in generated code
Tom,
Thanks for the reply.
If tested your suggestion, but i get a null pointer exception in
someStub._getCall().setMaintainSession(true); // enable sessions
At that point the _call variable is not instantiated, this variable will
be instantiated when i call one of my service method's. (so, that to
late)
But when i look into the generated code 'SomeSoapBindingStub', i found
in the method 'createCall()' the next entry :
if (super.maintainSessionSet) {
_call.setMaintainSession(super.maintainSession);
}
Is there a way to set the maintainSessionSet in the super method (maybe
via a config-file or an other way)
Kind regards,
Peter
Tom Ziemer schreef:
Hi Peter,
you could try the following in your client:
SomeServiceLocator someLocator = new SomeServiceLocator(); // ant
generated SomeSoapBindingStub someStub = null; // ant generated try {
someStub = SomeSoapBindingStub someLocator.getSomeService(); //
get the service
someStub._getCall().setMaintainSession(true); // enable sessions
someStub.someMethod(); // call one of your service's methods ...
}
...
Hope this helps,
Regards,
Tom
Peter Bosmans wrote:
Hi,
In my build.xml file, to generate client-side java code, i specify
that the client must work in a session scope.
When i run the client, it will not work in session scope.
Therefore i must add the following line in the generated Service
source.
_call.setMaintainSession(true);
But i don't want to add or change stuff in generated code.
Is there an other way to set the maintainsession ?
Peter
Re: jws compile problem
I know this is kind of cheating but and again I don't know if it will
solve your problem but try putting all the axis jar files into a
\webapps\ROOT\WEB-INF\lib folder, where is tomcats home
folder. These automatically get dynamically added to the classpath when
tomcat is started.
The reason I think its tomcats classpath is that you can (I think) compile the java without a problem normally?
Also If that doesn't solve it try just putting the jws file straight
into the webapps/axis folder and let axis itself look after the
compiling
DanOn 5/17/05, Frank <[EMAIL PROTECTED]> wrote:
Well I looked at the catalina.bat file. Seems it does not use the
CLASSPATH environment variable that is set for the system. I changed
it to do that and restarted Tomcat but no good. Same problem.
Is there a separate variable used for tomcat for it's classpath beyond
that? like TOMCAT_CLASSPATH or something?
Thanks,
Frank
Dan O'Neill wrote:
This
is probably a stupid thing to say but have you checked tomcats
classpath
Dan
On 5/17/05, Frank <[EMAIL PROTECTED]> wrote:
I have a problem that I believe to be a classpath problem (see below),
but I have included the path to the localhost directory, even created a
jar of the class files and still get the error. I can compile the
file directory just fine. But if I put the class file from a normal
javac in the jwsClasses directory the call to produce the WSDL
(http://kw14:8080/axis/TLS.jws?wsdl)
from the browser say's file not
found.
Line in java code (the directory structure exists and the java code is
compiled):
import localhost.axis.OMS_jws.*;
Running on XP
Using tomcat distributed with JWSDP 1.4
Axis 1.2
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - Error while compiling: C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.javaAxisFault faultCode: {
http://xml.apache.org/axis/}Server.compileError faultSubcode: faultString: Error while compiling: C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java faultActor: faultNode: faultDetail:
{}Errors:Error compiling C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java:Line 0, column 0: could not parse error message: Note: sun.tools.javac.Main has been deprecated.C:\tomcat-jwsdp-1.4\webapps\axis\WEB-INF\jwsClasses\TLS.java:39:
Package localhost.axis.OMS_jws not found in import.import localhost.axis.OMS_jws.*;
--
http://www.spreadfirefox.com/?q=affiliates&id=0&t=82"
>http://sfx-images.mozilla.org/affiliates/Buttons/80x15/white_1.gif"/
>
-- "I swear, the next bastard that kisses the ground in front of me is gonna getkicked in the antique chicken coops." - Cohen the Barbarian
