[newbie] cannot read patch

[Joerg Buchberger]

Hi.

There is a patch that allows us to expose Avalon Components via SOAP:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12903

Unfortunately, whenever I click on one of the patch/attachment links, the patch
isn't shown.
Can someone please send me that patch by mail?
Thanks.

Cheers.
Joerg

Thomas KRIECHBAUM ist außer Haus.

[Thomas KRIECHBAUM]

Ich werde ab  31.03.2003 nicht im Büro sein. Ich kehre zurück am
07.04.2003.


Die Rückmeldung bezieht sich auf ein Mail mit folgendem Thema:
extending i18n message files


Gesendet (c) GRZ/RACON Linz 2001 Agent 'Abwesenheit'



__

Der Austausch von Nachrichten mit o.a.  Absender via e-mail dient
ausschließlich Informationszwecken.
Rechtsgeschäftliche Erklärungen dürfen über dieses Medium nicht
ausgetauscht werden.

Correspondence with a.m. sender via e-mail is only for information
purposes.
This medium is not to be used for the exchange of legally-binding
communications.

Thomas KRIECHBAUM ist außer Haus.

[Thomas KRIECHBAUM]

Ich werde ab  31.03.2003 nicht im Büro sein. Ich kehre zurück am
07.04.2003.


Die Rückmeldung bezieht sich auf ein Mail mit folgendem Thema:
RE: cofiguring SOAPMonitor


Gesendet (c) GRZ/RACON Linz 2001 Agent 'Abwesenheit'



__

Der Austausch von Nachrichten mit o.a.  Absender via e-mail dient
ausschließlich Informationszwecken.
Rechtsgeschäftliche Erklärungen dürfen über dieses Medium nicht
ausgetauscht werden.

Correspondence with a.m. sender via e-mail is only for information
purposes.
This medium is not to be used for the exchange of legally-binding
communications.

Thomas KRIECHBAUM ist außer Haus.

[Thomas KRIECHBAUM]

Ich werde ab  31.03.2003 nicht im Büro sein. Ich kehre zurück am
07.04.2003.


Die Rückmeldung bezieht sich auf ein Mail mit folgendem Thema:
Re: java.util.List and 1.1.RC2


Gesendet (c) GRZ/RACON Linz 2001 Agent 'Abwesenheit'



__

Der Austausch von Nachrichten mit o.a.  Absender via e-mail dient
ausschließlich Informationszwecken.
Rechtsgeschäftliche Erklärungen dürfen über dieses Medium nicht
ausgetauscht werden.

Correspondence with a.m. sender via e-mail is only for information
purposes.
This medium is not to be used for the exchange of legally-binding
communications.

Thomas KRIECHBAUM ist außer Haus.

[Thomas KRIECHBAUM]

Ich werde ab  31.03.2003 nicht im Büro sein. Ich kehre zurück am
07.04.2003.


Die Rückmeldung bezieht sich auf ein Mail mit folgendem Thema:
Re: java.util.List and 1.1.RC2


Gesendet (c) GRZ/RACON Linz 2001 Agent 'Abwesenheit'



__

Der Austausch von Nachrichten mit o.a.  Absender via e-mail dient
ausschließlich Informationszwecken.
Rechtsgeschäftliche Erklärungen dürfen über dieses Medium nicht
ausgetauscht werden.

Correspondence with a.m. sender via e-mail is only for information
purposes.
This medium is not to be used for the exchange of legally-binding
communications.

Thomas KRIECHBAUM ist außer Haus.

[Thomas KRIECHBAUM]

Ich werde ab  31.03.2003 nicht im Büro sein. Ich kehre zurück am
07.04.2003.


Die Rückmeldung bezieht sich auf ein Mail mit folgendem Thema:
cofiguring SOAPMonitor


Gesendet (c) GRZ/RACON Linz 2001 Agent 'Abwesenheit'



__

Der Austausch von Nachrichten mit o.a.  Absender via e-mail dient
ausschließlich Informationszwecken.
Rechtsgeschäftliche Erklärungen dürfen über dieses Medium nicht
ausgetauscht werden.

Correspondence with a.m. sender via e-mail is only for information
purposes.
This medium is not to be used for the exchange of legally-binding
communications.

Thomas KRIECHBAUM ist außer Haus.

[Thomas KRIECHBAUM]

Ich werde ab  31.03.2003 nicht im Büro sein. Ich kehre zurück am
07.04.2003.


Die Rückmeldung bezieht sich auf ein Mail mit folgendem Thema:
Re: [java.util.List and 1.1.RC2]


Gesendet (c) GRZ/RACON Linz 2001 Agent 'Abwesenheit'



__

Der Austausch von Nachrichten mit o.a.  Absender via e-mail dient
ausschließlich Informationszwecken.
Rechtsgeschäftliche Erklärungen dürfen über dieses Medium nicht
ausgetauscht werden.

Correspondence with a.m. sender via e-mail is only for information
purposes.
This medium is not to be used for the exchange of legally-binding
communications.

RE: Invalid WSDD element 'service' (wanted 'deployment')

[Clay Graham]

Just for a followup

This all seems to go away when I remove the server-config.wsdd.

So it seems that I cannot invoke the admistrator remote, so the only way
to get this to deploy through the init method of the servlet I posted
earlier.

Its ok, I consider it to be a superior way anyway, I just wish I knew
why it was barfing.

That is so weird, 

-
Clay Graham
President
newObjectivity, Inc.
making the mobile-world-office
http://www.newobjectivity.com/



-Original Message-
From: Clay Graham [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 02, 2003 9:45 AM
To: [EMAIL PROTECTED]
Subject: Invalid WSDD element 'service' (wanted 'deployment')


Hello Axis Users!

I have run into a bit of a wall here and desperately need to some advice
on how to fix it. I have been looking through the archives quite a bit
and haven't found anything "quite" like this problem. I have done the
basic axis install to the tomcat webapp directories, I am using the
latest version of xerces (2.4) with tomcat 4.1.3. My "happy" page comes
up just fine:

##BEGIN HAPPY.JSP

Found SAAJ API (javax.xml.soap.SOAPMessage) at
/home/tomcat/jakarta-tomcat-4.1.3/common/lib/saaj.jar
Found JAX-RPC API (javax.xml.rpc.Service) at
/home/tomcat/jakarta-tomcat-4.1.3/common/lib/jaxrpc-api.jar
Found Apache-Axis (org.apache.axis.transport.http.AxisServlet) at
/home/tomcat/jakarta-tomcat-4.1.3/webapps/axis/WEB-INF/lib/axis.jar
Found Jakarta-Commons Discovery (org.apache.commons.discovery.Resource)
at
/home/tomcat/jakarta-tomcat-4.1.3/webapps/axis/WEB-INF/lib/commons-disco
very.jar
Found Jakarta-Commons Logging (org.apache.commons.logging.Log) at
/home/tomcat/jakarta-tomcat-4.1.3/webapps/axis/WEB-INF/lib/commons-loggi
ng.jar
Found Log4j (org.apache.log4j.Layout) at
/home/tomcat/jakarta-tomcat-4.1.3/webapps/axis/WEB-INF/lib/log4j-1.2.4.j
ar
Found IBM's WSDL4Java (com.ibm.wsdl.factory.WSDLFactoryImpl) at
/home/tomcat/jakarta-tomcat-4.1.3/webapps/axis/WEB-INF/lib/wsdl4j.jar
Found JAXP implementation (javax.xml.parsers.SAXParserFactory)
Found Activation API (javax.activation.DataHandler) at
/home/tomcat/jakarta-tomcat-4.1.3/common/lib/activation.jar

END HAPPY.JSP

And I have uncommented the administration servlet lines from web.xml
because I want to be able to deploy using wsdd.

So this all sounds like goodness right? 

The problem is when I attempt to click on the Administer Axis link on
the main axis page (axis webapp) the following exeption is printed. This
seems like the most basic functionality, the link is on the main page
for goodness sake!

org.apache.axis.deployment.wsdd.WSDDException: Invalid WSDD element
'service' (wanted 'deployment')

I have attempted to use the basic deployment.wsdd that is in the user
guide and I get the exact same error. 

BEGIN DEPLOYMENT.WSDD

http://xml.apache.org/axis/wsdd/"; 
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"; 
xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance";> 


http://meis/mailservlet/ 






END DEPLOYMENT.WSDD

So when this didn't work I went to a programattic approach thinking, hey
I have heard rumblings about people who don't like the administrator, so
why not use the servlet init approach:

BEGIN ServicesDeploymentServlet.java

/*
 * ServicesDeploymentServlet.java
 *
 * Created on April 1, 2003, 5:39 PM
 */

package com.noi.web.servlet;

import java.io.*;
import java.net.*;

import javax.servlet.*;
import javax.servlet.http.*;
import org.apache.axis.transport.http.*;
import org.apache.axis.*;
import org.apache.axis.deployment.wsdd.*;
import javax.xml.parsers.*;
import org.w3c.dom.*;
import org.xml.sax.*;

import com.noi.utility.data.*;


/**
 *
 * @author  clay
 * @version
 */
public class ServicesDeploymentServlet extends HttpServlet {

/** Initializes the servlet.
 */
public void init(ServletConfig sconfig) throws ServletException {
super.init(sconfig);
   AxisServlet axisServlet = new AxisServlet(); 
   ServletConfig sC = getServletConfig(); 
   ServletContext context = this.getServletContext();
   try { 
   axisServlet.init(sC); 
   } catch (ServletException e) { 
   e.printStackTrace(); 
   } 
   try { 
   AxisEngine engine = axisServlet.getEngine(); 
   DocumentBuilderFactory fact =
DocumentBuilderFactory.newInstance(); 
   Document doc = null; 
   //this should be a resource
   DocumentBuilder builder = fact.newDocumentBuilder(); 
   fact.setNamespaceAware(true);
   URL deployURL = context.getResource("/wsdd/deploy.wsdd"); 
   XMLDocumentReader reader = new XMLDocumentReader();
   reader.parse(deployURL);  
   doc = reader.getDocument();
   
   Element element = doc.getDocumentEleme

Re: Turning off ?wsdl feature

[Steve Loughran]

- Original Message -
From: "Mike Burati" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 02, 2003 13:44
Subject: RE: Turning off ?wsdl feature


> You lost me - not sure why you'd want it to be /axis*?wsdl...
>
> The article describes how in the WSDD deployment descriptor, you would go
> about changing the URL used for that service, for retrieving WSDL.  That
URL
> can be a resource in your WAR - it does not have to be under /axis/* - you
> could have it be /myservice or similar (I believe, I haven't tried it,
just
> read the article).  Then you in your web.xml could say that /myservice
> requests should go to a servlet that you wrote yourself or to a JSP page,
> and then in that servlet or JSP, you could dispatch to the right WSDL file
> for the client (eg, if you wanted each client to have a different set of
>  elements in the WSDL)...

I dont think that would work. Because I think it loads a class resource, not
a servlet resource.

Re: Turning off ?wsdl feature

[Steve Loughran]

I've thought of (in the axis 1.2 timeframe) letting you specify a
WsdlGenerator, a class that generates wsdl for an endpoint. The base impls.
would be 'return a resource' and 'make one from introspection', but I'd
envisage smarter things like running the resource through velocity to expand
templates.

for now, jsut turn ?wsdl off (point to an empty resource) and serve up wsdl
in some other manner, off a different url


- Original Message -
From: "Gurkan, Ozzie (MAN-Corporate)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 02, 2003 13:39
Subject: RE: Turning off ?wsdl feature


> Short of writing a filter to intercept the ?wsdl querystring, I am not
sure
> how I trap that request in the web.xml file. Currently, the web.xml has an
> entry for /axis/* for all services to be handled by the AxisServlet. How
> would I intercept something like "/axis/*?wsdl"?
>
> -Original Message-
> From: Mike Burati [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 02, 2003 4:37 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Turning off ?wsdl feature
>
>
>
> Use that feature to point it to a resource in your WAR (defined by
web.xml)
> which is a servlet or JSP controller that dispatches to the
client-specific
> actual WSDL based on which client is making the request?
>
> -Original Message-
> From: Gurkan, Ozzie (MAN-Corporate) [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 02, 2003 4:28 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Turning off ?wsdl feature
>
>
> That works great for only one, but I want to be able to select different
> WSDL files, not just one. I guess you could conceivably have different
> service urls for each client, but that gets ugly fast.
>
> -Original Message-
> From: Kellogg, Richard [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 02, 2003 4:23 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Turning off ?wsdl feature
>
>
> Try the following article:
>
http://www.fawcette.com/javapro/2003_02/online/WSDL_kjones_02_27_03/default_
> pf.asp
>
 _pf.asp>
>
>
> -Original Message-
> From: Gurkan, Ozzie (MAN-Corporate) [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 02, 2003 4:18 PM
> To: '[EMAIL PROTECTED]'
> Subject: Turning off ?wsdl feature
>
>
> Is there a way to limit access to the ?wsdl feature or turn it off
> completely? I need to be able customize the WSDL file based on the client,
> so I don't want it readily available to all clients.
>
> Thanks,
> Ozzie
>
>

Aha! (Was:RE: cofiguring SOAPMonitor)

[Allen, Michael E.]

Title: RE: cofiguring SOAPMonitor









I just
found that I had not read enough of the documentation.  There is link under “Reading Guide” to page
that describes how to deploy SOAPMonitor. 
Now… why that deploy-monitor.wsdd file is not part of the distribution
and why none of this is mentioned under the “using SOAPMonitor” link (I
actually found the link by running a google query!) remains a bit of a mystery
to me.

 

-Original
Message-
From: Allen, Michael E. 
Sent: Wednesday, April 02, 2003
3:53 PM
To: [EMAIL PROTECTED]
Subject: RE: cofiguring
SOAPMonitor

 

Ok; so I would like to see every
soap  message received and sent by axis.  How do I do that?  Do
I need to modify the deploy.wsdd file generated by WSDL2Java, or is do I add
the services I want to monitor to web.xml, or ...?

-Original Message- 
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, April 02, 2003 1:15 PM 
To: [EMAIL PROTECTED] 
Subject: RE: cofiguring SOAPMonitor 

SOAPMonitor needs to forward the messages
to 5001. The SOAPMonitor itself will be taking messages from a different port
on behalf of the server you have listening on 5001. You specify that port and
make sure the client is sending to that port you chose SOAPMonitor to listen
on.

 
Harry J. Kobetitsch 
UBS Warburg 
One North Wacker Drive 
Chicago, Illinois 60606-2809 
312-525-5866 
[EMAIL PROTECTED] 
-Original Message- 
From: Allen, Michael E. [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, April 02, 2003 12:02 PM 
To: [EMAIL PROTECTED] 
Subject: cofiguring SOAPMonitor 

 

I am trying to use SOAPMonitor, but am
seeing no messages.  I looked at the axis/WEB-INF/web.xml file and it is
configured to listen on port 5001.  Why?

Thanks, 
Michael 

 

Visit our website at http://www.ubswarburg.com 

This message contains confidential
information and is intended only 
for the individual named.  If you are not the named addressee
you 
should not disseminate, distribute or copy this e-mail. 
Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system. 

E-mail transmission cannot be guaranteed
to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender
therefore 
does not accept liability for any errors or omissions in the
contents 
of this message which arise as a result of e-mail
transmission.  If

verification is required please request a hard-copy version. 
This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities
or 
related financial instruments. 

RE: cofiguring SOAPMonitor

[Allen, Michael E.]

Title: RE: cofiguring SOAPMonitor





Ok; so I would like to see every soap  message received and sent by axis.  How do I do that?  Do I need to modify the deploy.wsdd file generated by WSDL2Java, or is do I add the services I want to monitor to web.xml, or ...?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 02, 2003 1:15 PM
To: [EMAIL PROTECTED]
Subject: RE: cofiguring SOAPMonitor


SOAPMonitor needs to forward the messages to 5001. The SOAPMonitor itself will be taking messages from a different port on behalf of the server you have listening on 5001. You specify that port and make sure the client is sending to that port you chose SOAPMonitor to listen on.


Harry J. Kobetitsch
UBS Warburg
One North Wacker Drive
Chicago, Illinois 60606-2809
312-525-5866
[EMAIL PROTECTED]
-Original Message-
From: Allen, Michael E. [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 02, 2003 12:02 PM
To: [EMAIL PROTECTED]
Subject: cofiguring SOAPMonitor



I am trying to use SOAPMonitor, but am seeing no messages.  I looked at the axis/WEB-INF/web.xml file and it is configured to listen on port 5001.  Why?

Thanks,
Michael



Visit our website at http://www.ubswarburg.com


This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.


E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.

RE: Turning off ?wsdl feature

[Gurkan, Ozzie (MAN-Corporate)]

Title: Message



Mike, 
I believe I understand what you mean now. The  entry can be 
replace with a URL, so it doesn't necessarily have to be a physical resource 
such as a file. I will have to give that a shot to see if it works. I probably 
have to give it an absolute URL for it work, though. Is this what you 
meant?

  
  -Original Message-From: Mike Burati 
  [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 2003 4:44 
  PMTo: '[EMAIL PROTECTED]'Subject: RE: Turning off 
  ?wsdl feature
  You 
  lost me - not sure why you'd want it to be /axis*?wsdl...
   
  The 
  article describes how in the WSDD deployment descriptor, you would go about 
  changing the URL used for that service, for retrieving WSDL.  That URL 
  can be a resource in your WAR - it does not have to be under /axis/* - you 
  could have it be /myservice or similar (I believe, I haven't tried it, just 
  read the article).  Then you in your web.xml could say that /myservice 
  requests should go to a servlet that you wrote yourself or to a JSP page, and 
  then in that servlet or JSP, you could dispatch to the right WSDL file for the 
  client (eg, if you wanted each client to have a different set of 
   elements in the WSDL)... 
   
  Without knowing what you're trying to do different 
  for each client, that's about the best suggestion I have at the 
  moment...
  
-Original Message-From: Gurkan, Ozzie 
(MAN-Corporate) [mailto:[EMAIL PROTECTED]Sent: Wednesday, 
April 02, 2003 4:39 PMTo: 
'[EMAIL PROTECTED]'Subject: RE: Turning off ?wsdl 
feature
Short of writing a filter to intercept the ?wsdl querystring, I am 
not sure how I trap that request in the web.xml file. Currently, the web.xml 
has an entry for /axis/* for all services to be handled by the AxisServlet. 
How would I intercept something like "/axis/*?wsdl"?

  
  -Original Message-From: Mike Burati 
  [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 2003 
  4:37 PMTo: '[EMAIL PROTECTED]'Subject: RE: 
  Turning off ?wsdl feature
   
  Use that feature to point it to a resource in 
  your WAR (defined by web.xml) which is a servlet or JSP controller that 
  dispatches to the client-specific actual WSDL based on which client is 
  making the request?
  
-Original Message-From: Gurkan, Ozzie 
(MAN-Corporate) [mailto:[EMAIL PROTECTED]Sent: Wednesday, 
April 02, 2003 4:28 PMTo: 
'[EMAIL PROTECTED]'Subject: RE: Turning off ?wsdl 
feature
That works great for only one, but I want to be able to select 
different WSDL files, not just one. I guess you could conceivably have 
different service urls for each client, but that gets ugly 
fast.

  
  -Original Message-From: Kellogg, 
  Richard [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 
  02, 2003 4:23 PMTo: 
  [EMAIL PROTECTED]Subject: RE: Turning off ?wsdl 
  feature
  Try the following article:
  http://www.fawcette.com/javapro/2003_02/online/WSDL_kjones_02_27_03/default_pf.asp
   
  
-Original Message-From: Gurkan, Ozzie 
(MAN-Corporate) [mailto:[EMAIL PROTECTED]Sent: 
Wednesday, April 02, 2003 4:18 PMTo: 
'[EMAIL PROTECTED]'Subject: Turning off ?wsdl 
feature
Is there 
a way to limit access to the ?wsdl feature or turn it off 
completely? I need to be able customize the WSDL file based on the 
client, so I don't want it readily available to all 
clients.
 
Thanks,
Ozzie

RE: Capitalization issue with Java2WSDL

[Steve Stallion]

ala the wsdd reference in axis docs:

  
 
A simplified type mapping, which uses pre-defined
serializers/deserializers to encode/decode JavaBeans. The class named by
"classname" must follow the JavaBean standard pattern of get/set
accessors.






-Original Message-
From: Steve Pannier [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 02, 2003 3:12 PM
To: [EMAIL PROTECTED]
Subject: RE: Capitalization issue with Java2WSDL



I'm aware of the coding standards, etc.  I probably should have
explained that the service code I'm working with is generated within a
GUI which allows the user to design/create service methods; they can
define variables, parameters, data types, and programmatic flow.  If the
name of a variable or type element they have defined starts with an
upper case letter (or ,for that matter, is all uppercase or any other
valid Java identifier), then the code that gets generated for the
service reflects that.

What we're seeing is clients that are generated using our wsdl are
expecting something called "str1" (using the example below), when what
they actually receive on the wire is "Str1".

If indeed what your reply states is the reason for Java2WSDL's behavior,
that's OK - I'm willing to accept that.  I just wanted to get some
insight as to why it behaves this way, and get a better feel for what
I'm up against here.

Thanks for your reply.  Any other comments on this?


Steve Pannier
Jacada, Inc.
(763) 201-0002 Ext. 219
[EMAIL PROTECTED]
http://www.jacada.com



> take a look at the sun coding standards.
>
> also, i am assuming you are using beanMappings -- these follow 
> javabean introspection rules, so you need follow that standard to get 
> reliable results.
>
>
>
> -Original Message-
> From: Steve Pannier [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 02, 2003 2:24 PM
> To: [EMAIL PROTECTED]
> Subject: Capitalization issue with Java2WSDL
>
>
> Hello all.
>
> Axis-1_1RC2:  I'm using Java2WSDL to generate WSDL for my service. I 
> have class properties that start with an upper case letter.  The 
> generated WSDL, however, contains the property name with the first 
> letter lower case.
>
> Why does Java2WSDL do this?  Is there a way to force it to generate 
> WSDL maintaining the capitalization of each class member?
>
>
> Here's an example:
>
> package test;
> public class Foo {
> public Bar getData (  ) {
> return null;
> }
> }
>
>
> package test;
> public class Bar {
> private String Str1 = null;
> private String Str2 = null;
>
> public String getStr1() {
> return this.Str1;
> }
> public void setStr1( String str ) {
> this.Str1 = str;
> }
> public String getStr2() {
> return this.Str2;
> }
> public void setStr2( String str ) {
> this.Str2 = str;
> }
> }
>
> I run the command "
> java -classpath c:\wsdl\TestToWsdl\RPC-Style\Test-Java2WSDL;%AXIS_DIR%
> \axis.jar;%AXIS_DIR%\jaxrpc.jar;%AXIS_DIR%\saaj.jar;%AXIS_DIR%
> \wsdl4j.jar;%AXIS_DIR%\commons-logging.jar;%AXIS_DIR%
> \commons-discovery.jar;c:\xerces.jar org.apache.axis.wsdl.Java2WSDL -l

> http://10.150.5.147:8091/axis/services/Foo -s FooPort -S Foo -o 
> Foo.wsdl test.Foo".
>
> The types section of the generated WSDL follows (note that "str1" and 
> "str2" are not capitalized.):
>
>  
>   http://test"; xmlns 
> ="http://www.w3.org/2001/XMLSchema";>
>http://schemas.xmlsoap.org/soap/encoding/"/>
>
> 
>  
>  
> 
>
>   
>  
>
>
> Regards.
>
>
> Steve Pannier
> Jacada, Inc.
> (763) 201-0002 Ext. 219
> [EMAIL PROTECTED]
> http://www.jacada.com
>
>
>

RE: Turning off ?wsdl feature

[Mike Burati]

Title: Message



You 
lost me - not sure why you'd want it to be /axis*?wsdl...
 
The 
article describes how in the WSDD deployment descriptor, you would go about 
changing the URL used for that service, for retrieving WSDL.  That URL can 
be a resource in your WAR - it does not have to be under /axis/* - you could 
have it be /myservice or similar (I believe, I haven't tried it, just read the 
article).  Then you in your web.xml could say that /myservice requests 
should go to a servlet that you wrote yourself or to a JSP page, and then in 
that servlet or JSP, you could dispatch to the right WSDL file for the client 
(eg, if you wanted each client to have a different set of  
elements in the WSDL)... 
 
Without knowing what you're trying to do different for 
each client, that's about the best suggestion I have at the 
moment...

  -Original Message-From: Gurkan, Ozzie 
  (MAN-Corporate) [mailto:[EMAIL PROTECTED]Sent: Wednesday, April 
  02, 2003 4:39 PMTo: '[EMAIL PROTECTED]'Subject: 
  RE: Turning off ?wsdl feature
  Short of writing a filter to intercept the ?wsdl querystring, I am not 
  sure how I trap that request in the web.xml file. Currently, the web.xml has 
  an entry for /axis/* for all services to be handled by the AxisServlet. How 
  would I intercept something like "/axis/*?wsdl"?
  

-Original Message-From: Mike Burati 
[mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 2003 
4:37 PMTo: '[EMAIL PROTECTED]'Subject: RE: 
Turning off ?wsdl feature
 
Use that feature to point it to a resource in your 
WAR (defined by web.xml) which is a servlet or JSP controller that 
dispatches to the client-specific actual WSDL based on which client is 
making the request?

  -Original Message-From: Gurkan, Ozzie 
  (MAN-Corporate) [mailto:[EMAIL PROTECTED]Sent: Wednesday, 
  April 02, 2003 4:28 PMTo: 
  '[EMAIL PROTECTED]'Subject: RE: Turning off ?wsdl 
  feature
  That works great for only one, but I want to be able to select 
  different WSDL files, not just one. I guess you could conceivably have 
  different service urls for each client, but that gets ugly 
  fast.
  

-Original Message-From: Kellogg, 
Richard [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 
02, 2003 4:23 PMTo: 
[EMAIL PROTECTED]Subject: RE: Turning off ?wsdl 
feature
Try the following article:
http://www.fawcette.com/javapro/2003_02/online/WSDL_kjones_02_27_03/default_pf.asp
 

  -Original Message-From: Gurkan, Ozzie 
  (MAN-Corporate) [mailto:[EMAIL PROTECTED]Sent: 
  Wednesday, April 02, 2003 4:18 PMTo: 
  '[EMAIL PROTECTED]'Subject: Turning off ?wsdl 
  feature
  Is there a 
  way to limit access to the ?wsdl feature or turn it off completely? I 
  need to be able customize the WSDL file based on the client, so I 
  don't want it readily available to all clients.
   
  Thanks,
  Ozzie

RE: Turning off ?wsdl feature

[Gurkan, Ozzie (MAN-Corporate)]

Title: Message



Short 
of writing a filter to intercept the ?wsdl querystring, I am not sure how I trap 
that request in the web.xml file. Currently, the web.xml has an entry for 
/axis/* for all services to be handled by the AxisServlet. How would I intercept 
something like "/axis/*?wsdl"?

  
  -Original Message-From: Mike Burati 
  [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 2003 4:37 
  PMTo: '[EMAIL PROTECTED]'Subject: RE: Turning off 
  ?wsdl feature
   
  Use 
  that feature to point it to a resource in your WAR (defined by web.xml) which 
  is a servlet or JSP controller that dispatches to the client-specific actual 
  WSDL based on which client is making the request?
  
-Original Message-From: Gurkan, Ozzie 
(MAN-Corporate) [mailto:[EMAIL PROTECTED]Sent: Wednesday, 
April 02, 2003 4:28 PMTo: 
'[EMAIL PROTECTED]'Subject: RE: Turning off ?wsdl 
feature
That works great for only one, but I want to be able to select 
different WSDL files, not just one. I guess you could conceivably have 
different service urls for each client, but that gets ugly 
fast.

  
  -Original Message-From: Kellogg, 
  Richard [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 
  2003 4:23 PMTo: [EMAIL PROTECTED]Subject: RE: 
  Turning off ?wsdl feature
  Try the following article:
  http://www.fawcette.com/javapro/2003_02/online/WSDL_kjones_02_27_03/default_pf.asp
   
  
-Original Message-From: Gurkan, Ozzie 
(MAN-Corporate) [mailto:[EMAIL PROTECTED]Sent: Wednesday, 
April 02, 2003 4:18 PMTo: 
'[EMAIL PROTECTED]'Subject: Turning off ?wsdl 
feature
Is there a 
way to limit access to the ?wsdl feature or turn it off completely? I 
need to be able customize the WSDL file based on the client, so I don't 
want it readily available to all clients.
 
Thanks,
Ozzie

RE: Turning off ?wsdl feature

[Mike Burati]

Title: Message



 
Use 
that feature to point it to a resource in your WAR (defined by web.xml) which is 
a servlet or JSP controller that dispatches to the client-specific actual WSDL 
based on which client is making the request?

  -Original Message-From: Gurkan, Ozzie 
  (MAN-Corporate) [mailto:[EMAIL PROTECTED]Sent: Wednesday, April 
  02, 2003 4:28 PMTo: '[EMAIL PROTECTED]'Subject: 
  RE: Turning off ?wsdl feature
  That 
  works great for only one, but I want to be able to select different WSDL 
  files, not just one. I guess you could conceivably have different service urls 
  for each client, but that gets ugly fast.
  

-Original Message-From: Kellogg, 
Richard [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 
2003 4:23 PMTo: [EMAIL PROTECTED]Subject: RE: 
Turning off ?wsdl feature
Try the following article:
http://www.fawcette.com/javapro/2003_02/online/WSDL_kjones_02_27_03/default_pf.asp
 

  -Original Message-From: Gurkan, Ozzie 
  (MAN-Corporate) [mailto:[EMAIL PROTECTED]Sent: Wednesday, 
  April 02, 2003 4:18 PMTo: 
  '[EMAIL PROTECTED]'Subject: Turning off ?wsdl 
  feature
  Is there a way 
  to limit access to the ?wsdl feature or turn it off completely? I need to 
  be able customize the WSDL file based on the client, so I don't want it 
  readily available to all clients.
   
  Thanks,
  Ozzie

RE: Turning off ?wsdl feature

[Gurkan, Ozzie (MAN-Corporate)]

Title: Message



That 
works great for only one, but I want to be able to select different WSDL files, 
not just one. I guess you could conceivably have different service urls for each 
client, but that gets ugly fast.

  
  -Original Message-From: Kellogg, Richard 
  [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 2003 4:23 
  PMTo: [EMAIL PROTECTED]Subject: RE: Turning off 
  ?wsdl feature
  Try 
  the following article:
  http://www.fawcette.com/javapro/2003_02/online/WSDL_kjones_02_27_03/default_pf.asp
   
  
-Original Message-From: Gurkan, Ozzie 
(MAN-Corporate) [mailto:[EMAIL PROTECTED]Sent: Wednesday, 
April 02, 2003 4:18 PMTo: 
'[EMAIL PROTECTED]'Subject: Turning off ?wsdl 
feature
Is there a way 
to limit access to the ?wsdl feature or turn it off completely? I need to be 
able customize the WSDL file based on the client, so I don't want it readily 
available to all clients.
 
Thanks,
Ozzie

RE: Turning off ?wsdl feature

[Kellogg, Richard]

Title: Message



Try 
the following article:
http://www.fawcette.com/javapro/2003_02/online/WSDL_kjones_02_27_03/default_pf.asp
 

  -Original Message-From: Gurkan, Ozzie 
  (MAN-Corporate) [mailto:[EMAIL PROTECTED]Sent: Wednesday, April 
  02, 2003 4:18 PMTo: '[EMAIL PROTECTED]'Subject: 
  Turning off ?wsdl feature
  Is there a way to 
  limit access to the ?wsdl feature or turn it off completely? I need to be able 
  customize the WSDL file based on the client, so I don't want it readily
  available to all clients.
   
  Thanks,
  Ozzie

Turning off ?wsdl feature

[Gurkan, Ozzie (MAN-Corporate)]

Title: Message



Is there a way to 
limit access to the ?wsdl feature or turn it off completely? I need to be able 
customize the WSDL file based on the client, so I don't want it readily 
available to all clients.
 
Thanks,
Ozzie

RE: happyaxis.jsp Error

[Willis, Keith]

Title: happyaxis.jsp Error



I 
found out what this was already...  A permissions issue on the 
server.
 
Thanks,
 
Keith

  -Original Message-From: Willis, Keith 
  [mailto:[EMAIL PROTECTED]Sent: Wednesday, April 02, 2003 
  2:50 PMTo: '[EMAIL PROTECTED]'Subject: 
  happyaxis.jsp Error
  Hi All, 
  I am trying to set axis up on a server and I am getting a 500 
  server error on happyaxis.jsp. 
  Here is the error I am gettting... 
  any help would be appreciated. 
  Thanks, 
  Keith 
  type Exception report 
  message 
  description The server encountered an internal error () that 
  prevented it from fulfilling this request. 
  exception 
  org.apache.jasper.JasperException: Unable to compile class for 
  JSP 
  An error occurred at line: -1 in the jsp file: null 

  Generated servlet error:     [javac] Since fork is true, ignoring compiler 
  setting.     [javac] Compiling 1 source 
  file     [javac] Since fork is true, 
  ignoring compiler setting. 
      at 
  org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130) 
      at 
  org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:293) 
      at 
  org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:353) 
      at 
  org.apache.jasper.compiler.Compiler.compile(Compiler.java:370) 
      at 
  org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:473) 
      at 
  org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190) 
      at 
  org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) 
      at 
  org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) 
      at 
  javax.servlet.http.HttpServlet.service(HttpServlet.java:853) 
      at 
  org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) 
      at 
  org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) 
      at 
  org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) 
      at 
  org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 
      at 
  org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 
      at 
  org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) 
      at 
  org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 
      at 
  org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 
      at 
  org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 
      at 
  org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) 
      at 
  org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) 
      at 
  org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) 
      at 
  org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 
      at 
  org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) 
      at 
  org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) 
      at 
  org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) 
      at 
  org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) 
      at 
  org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 
      at 
  org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) 
      at 
  org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) 
      at 
  org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 
      at 
  org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 
      at 
  org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) 
      at 
  org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) 
      at 
  org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) 
      at 
  org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) 
      at 
  org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) 
      at 
  org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) 
      at 
  java.lang.Thread.run(Thread.java:536) 

RE: Capitalization issue with Java2WSDL

[Steve Pannier]

I'm aware of the coding standards, etc.  I probably should have
explained that the service code I'm working with is generated within
a GUI which allows the user to design/create service methods; they
can define variables, parameters, data types, and programmatic
flow.  If the name of a variable or type element they have defined
starts with an upper case letter (or ,for that matter, is all uppercase
or any other valid Java identifier), then the code that gets generated
for the service reflects that.

What we're seeing is clients that are generated using our wsdl are
expecting something called "str1" (using the example below), when
what they actually receive on the wire is "Str1".

If indeed what your reply states is the reason for Java2WSDL's
behavior, that's OK - I'm willing to accept that.  I just wanted to get
some insight as to why it behaves this way, and get a better feel
for what I'm up against here.

Thanks for your reply.  Any other comments on this?


Steve Pannier
Jacada, Inc.
(763) 201-0002 Ext. 219
[EMAIL PROTECTED]
http://www.jacada.com



> take a look at the sun coding standards.
>
> also, i am assuming you are using beanMappings -- these follow javabean
> introspection rules, so you need follow that standard to get reliable
> results.
>
>
>
> -Original Message-
> From: Steve Pannier [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 02, 2003 2:24 PM
> To: [EMAIL PROTECTED]
> Subject: Capitalization issue with Java2WSDL
>
>
> Hello all.
>
> Axis-1_1RC2:  I'm using Java2WSDL to generate WSDL for my service. I
> have class properties that start with an upper case letter.  The
> generated WSDL, however, contains the property name with the first
> letter lower case.
>
> Why does Java2WSDL do this?  Is there a way to force it to generate WSDL
> maintaining the capitalization of each class member?
>
>
> Here's an example:
>
> package test;
> public class Foo {
> public Bar getData (  ) {
> return null;
> }
> }
>
>
> package test;
> public class Bar {
> private String Str1 = null;
> private String Str2 = null;
>
> public String getStr1() {
> return this.Str1;
> }
> public void setStr1( String str ) {
> this.Str1 = str;
> }
> public String getStr2() {
> return this.Str2;
> }
> public void setStr2( String str ) {
> this.Str2 = str;
> }
> }
>
> I run the command "
> java -classpath c:\wsdl\TestToWsdl\RPC-Style\Test-Java2WSDL;%AXIS_DIR%
> \axis.jar;%AXIS_DIR%\jaxrpc.jar;%AXIS_DIR%\saaj.jar;%AXIS_DIR%
> \wsdl4j.jar;%AXIS_DIR%\commons-logging.jar;%AXIS_DIR%
> \commons-discovery.jar;c:\xerces.jar org.apache.axis.wsdl.Java2WSDL -l
> http://10.150.5.147:8091/axis/services/Foo -s FooPort -S Foo -o Foo.wsdl
> test.Foo".
>
> The types section of the generated WSDL follows (note that "str1" and
> "str2" are not capitalized.):
>
>  
>   http://test"; xmlns
> ="http://www.w3.org/2001/XMLSchema";>
>http://schemas.xmlsoap.org/soap/encoding/"/>
>
> 
>  
>  
> 
>
>   
>  
>
>
> Regards.
>
>
> Steve Pannier
> Jacada, Inc.
> (763) 201-0002 Ext. 219
> [EMAIL PROTECTED]
> http://www.jacada.com
>
>
>

RE: java.util.List and 1.1.RC2

[Brain, Jim]

Well, I don't mean to toot my own horn, but I am rather impressed with my
tool.  It supports the following features:

* Automatically takes classes with mixed data (getters/setters) and action
methods and splits them into Beans and Impl Action classes
* Converts all methods to throw RemoteException
* "flattens" inheritance model so that classes in the same package are
inherited.  All inherited methods out of package are rolled into the lowest
base class that is in package. (I know, this sounds like it should not work,
but it does, and if I find a case where it does not work, it can be turned
off, but it works well to simplify the data beans)
* Spits out either one Wsdd or one wsdd per class in package
* Can convert an entire package at once
* Supports outputting classes with overloaded methods or without. (adds
2,3,4 to overloaded versions)
* Optionally excludes entire classes -x jim.MyClass or specific methods -x
jim.MyClass.method1 or the more global *.method1
* Optionally Simplifies Vectors and Lists into array of Object.
* Creates JAX-RPC interfaces for Action classes
* User defined extensions for Bean, Interface, and Action classes (defaults
to "","IF", and "Impl")
* Automatically walks the extension tree to add beanMappings to WSDD file
for all classes used in a service

1200 line program, and pretty messy (it was not designed for long term use,
just to get this set of vendor classes ready for Web service consumption).
But, if there is interest in a TIE (I think that is the name) gen tool that
cleans up arbitrary classes for consumption, let me know.

As to your suggestion below, I can if I go through the actual class code,
but that is a vendor product, and I'm not sure it's going to be easy to find
9they are very heavy inheritance users)

Jim


Jim Brain, [EMAIL PROTECTED]
"Researching tomorrow's decisions today."
(319) 369-2070 (work)
SYSTEMS ARCHITECT, ITS, AEGON FINANCIAL PARTNERS

 -Original Message-
From:   Steve Loughran [mailto:[EMAIL PROTECTED] 
Sent:   Wednesday, April 02, 2003 1:44 PM
To: [EMAIL PROTECTED]
Subject:Re: java.util.List and 1.1.RC2

Brain, Jim wrote:
> I know, and I thought of that.
> 
> Unfortunately, I need to expose 296 service classes, containing 5000
> references to List, and I have a program that is creating web service
> wrappers for all the classes (the original classes combined data and
access
> logic, which had to split in half to work in the web service world.  The
> program I wrote can be applied to any arbitrary class, though, uses
> reflection, and I am planning on cleaning it up and offering it).
> Programmatically, I can't determine the data type of a List, so I have to
> replace with Object[], which isn't much better (although AXIS WSDL code
> seems to like that)

You cant add xdoclet metadata to state the type of lists? I really miss 
typed datastructures, its the main bit of C++ that I still miss, even if 
its templating was awful compared to that of the polymorphic type 
inference features of Standard ML.

I guess porting to the generics compiler is out too, huh :) That's OK, 
axis cant handle that iether.

It seems to me that if Axis handles Object[] then it should be able to 
serialize List, at the very least by going List.toArray() & returning 
the object array. typing would be a nice extra, with a configurable in 
the WSDD declarations that stated the java class in the list.

You sound like you are doing a major undertaking there. I wish you well 
-you could probably derive an interesting paper or two from the experience.

I'll point you at my making web-services-that-work paper 
http://www.iseran.com/Steve/papers/wstw/
which may be of interest

-steve

Re: [Re: java.util.List and 1.1.RC2]

[Mitch Gitman]

I've used toArray() numerous times in my service code and had no problem with
that. Obviously, Jim (the fellow who started this thread) doesn't have the
luxury of coding that manually.

My point, to be more precise, is that JAX-RPC 1.0 says nothing about java.util
collections classes/interfaces. Of course, Axis doesn't compromise its
compliance with the JAX-RPC spec by providing functionality that extends the
spec, but as a developer I am reluctant to use that extended functionality.
Personally, I would prefer to see collections explicitly disallowed (Java2WSDL
would throw an exception), so developers don't step in something they didn't
see. But if collections are allowed, I would like to see that clearly
documented.

Naturally, if I would like to see something, I am free to produce it myself.
But that goes back to my question: how does Axis 1.1 RC2 support java.util
collections besides Java2WSDL's just blindly producing a generic Array complex
type? The most I've read on this subject is a cryptic mention of the
"--extraClasses" argument to Java2WSDL.

Concerning "there is meant to be something in soap where you do say you are
returning an Object and the type is passed in the envelope at run time." I
don't understand how passing a type name in the SOAP envelope helps since the
SOAP engine can dynamically build the SOAP message at request time anyway, and
the SOAP engine still must fill in the XML Schema type's elements
corresponding to the dynamically identified class' fields.

Steve Loughran <[EMAIL PROTECTED]> wrote:
Mitch Gitman wrote:
> I'm still wondering about the apparent existing support for java.util.List
and
> the like. It seems to me that Java2WSDL should generate an exception when
it
> comes across a collection class that stores java.lang.Object instances.

That is one thing wrong with collections; you cannot state in advance 
their type, and the thing at the far end cannot deal with arbitrary java 
objects.

If you go
  return (Foo)list.toArray(new Foo[0]);
You can turn a list to an array in a snap. A fromArray() would be nice 
to match it.

However, there is meant to be something in soap where you do say you are 
returning an Object and the type is passed in the envelope at run time. 
I dont know the exact details...

RE: Capitalization issue with Java2WSDL

[Steve Stallion]

take a look at the sun coding standards.

also, i am assuming you are using beanMappings -- these follow javabean
introspection rules, so you need follow that standard to get reliable
results.



-Original Message-
From: Steve Pannier [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 02, 2003 2:24 PM
To: [EMAIL PROTECTED]
Subject: Capitalization issue with Java2WSDL


Hello all.

Axis-1_1RC2:  I'm using Java2WSDL to generate WSDL for my service. I
have class properties that start with an upper case letter.  The
generated WSDL, however, contains the property name with the first
letter lower case.

Why does Java2WSDL do this?  Is there a way to force it to generate WSDL
maintaining the capitalization of each class member?


Here's an example:

package test;
public class Foo {
public Bar getData (  ) {
return null;
}
}


package test;
public class Bar {
private String Str1 = null;
private String Str2 = null;

public String getStr1() {
return this.Str1;
}
public void setStr1( String str ) {
this.Str1 = str;
}
public String getStr2() {
return this.Str2;
}
public void setStr2( String str ) {
this.Str2 = str;
}
}

I run the command "
java -classpath c:\wsdl\TestToWsdl\RPC-Style\Test-Java2WSDL;%AXIS_DIR%
\axis.jar;%AXIS_DIR%\jaxrpc.jar;%AXIS_DIR%\saaj.jar;%AXIS_DIR%
\wsdl4j.jar;%AXIS_DIR%\commons-logging.jar;%AXIS_DIR%
\commons-discovery.jar;c:\xerces.jar org.apache.axis.wsdl.Java2WSDL -l
http://10.150.5.147:8091/axis/services/Foo -s FooPort -S Foo -o Foo.wsdl
test.Foo".

The types section of the generated WSDL follows (note that "str1" and
"str2" are not capitalized.):

 
  http://test"; xmlns
="http://www.w3.org/2001/XMLSchema";>
   http://schemas.xmlsoap.org/soap/encoding/"/>
   

 
 

   
  
 


Regards.


Steve Pannier
Jacada, Inc.
(763) 201-0002 Ext. 219
[EMAIL PROTECTED]
http://www.jacada.com

Capitalization issue with Java2WSDL

[Steve Pannier]

Hello all.

Axis-1_1RC2:  I'm using Java2WSDL to generate WSDL for my service.
I have class properties that start with an upper case letter.  The
generated
WSDL, however, contains the property name with the first letter lower case.

Why does Java2WSDL do this?  Is there a way to force it to generate
WSDL maintaining the capitalization of each class member?


Here's an example:

package test;
public class Foo {
public Bar getData (  ) {
return null;
}
}


package test;
public class Bar {
private String Str1 = null;
private String Str2 = null;

public String getStr1() {
return this.Str1;
}
public void setStr1( String str ) {
this.Str1 = str;
}
public String getStr2() {
return this.Str2;
}
public void setStr2( String str ) {
this.Str2 = str;
}
}

I run the command "
java -classpath c:\wsdl\TestToWsdl\RPC-Style\Test-Java2WSDL;%AXIS_DIR%
\axis.jar;%AXIS_DIR%\jaxrpc.jar;%AXIS_DIR%\saaj.jar;%AXIS_DIR%
\wsdl4j.jar;%AXIS_DIR%\commons-logging.jar;%AXIS_DIR%
\commons-discovery.jar;c:\xerces.jar org.apache.axis.wsdl.Java2WSDL -l
http://10.150.5.147:8091/axis/services/Foo -s FooPort -S Foo -o Foo.wsdl
test.Foo".

The types section of the generated WSDL follows (note that "str1" and
"str2" are not capitalized.):

 
  http://test"; xmlns
="http://www.w3.org/2001/XMLSchema";>
   http://schemas.xmlsoap.org/soap/encoding/"/>
   

 
 

   
  
 


Regards.


Steve Pannier
Jacada, Inc.
(763) 201-0002 Ext. 219
[EMAIL PROTECTED]
http://www.jacada.com

happyaxis.jsp Error

[Willis, Keith]

Title: happyaxis.jsp Error





Hi All,


I am trying to set axis up on a server and I am getting a 500 server error on happyaxis.jsp.


Here is the error I am gettting...


any help would be appreciated.


Thanks,


Keith




type Exception report


message 


description The server encountered an internal error () that prevented it from fulfilling this request.


exception 


org.apache.jasper.JasperException: Unable to compile class for JSP


An error occurred at line: -1 in the jsp file: null


Generated servlet error:
    [javac] Since fork is true, ignoring compiler setting.
    [javac] Compiling 1 source file
    [javac] Since fork is true, ignoring compiler setting.




    at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130)
    at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:293)
    at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:353)
    at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370)
    at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:473)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
    at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
    at java.lang.Thread.run(Thread.java:536)

extending i18n message files

[Herrick, Mike]

Hi,

I am following the directions at in the Integration Guide for Extending Message Files, 
but am having trouble.

I keep getting Cannot find resource.

I copied all of the files from java/src/org/apache/axis/i18n into my package structure:
I updated the copy the MessageConstants class like this:
public class MessagesConstants {
//public static final String projectName = "org.apache.axis".intern();
//  Change 
public static final String projectName = "com.mentor.pubsubservice".intern();
public static final String resourceName = "resource".intern();
public static final Locale locale = null;

//public static final String rootPackageName = "org.apache.axis.i18n".intern();
//  Change 
public static final String rootPackageName = 
"com.mentor.pubsubservice.util.i18n".intern();

public static final ResourceBundle rootBundle =
ProjectResourceBundle.getBundle(projectName,
rootPackageName,
resourceName,
locale,
MessagesConstants.class.getClassLoader(),
null);
}

Here is what I get from the log:
2003-04-02 11:30:30,593 [main] DEBUG 
com.mentor.pubsubservice.util.i18n.ProjectResourceBundle - 
getBundle(com.mentor.pubsubservice,com.mentor.pubsubservice.util.i18n,resource,null,...)
2003-04-02 11:30:30,609 [main] DEBUG 
com.mentor.pubsubservice.util.i18n.ProjectResourceBundle - loadBundle: Ignoring 
MissingResourceException: Can't find bundle for base name 
com.mentor.pubsubservice.util.i18n.resource, locale en_US
2003-04-02 11:30:30,609 [main] DEBUG 
com.mentor.pubsubservice.util.i18n.ProjectResourceBundle - loadBundle: Ignoring 
MissingResourceException: Can't find bundle for base name 
com.mentor.pubsubservice.util.resource, locale en_US
2003-04-02 11:30:30,625 [main] DEBUG 
com.mentor.pubsubservice.util.i18n.ProjectResourceBundle - loadBundle: Ignoring 
MissingResourceException: Can't find bundle for base name 
com.mentor.pubsubservice.resource, locale en_US
java.lang.ExceptionInInitializerError: java.util.MissingResourceException: Cannot find 
resource 'com.mentor.pubsubservice.util.i18n.resource'
at 
com.mentor.pubsubservice.util.i18n.ProjectResourceBundle.getBundle(ProjectResourceBundle.java:327)
at 
com.mentor.pubsubservice.util.i18n.MessagesConstants.(MessagesConstants.java:73)
at com.mentor.pubsubservice.util.i18n.Messages.(Messages.java:83)
at com.mentor.pubsubservice.util.i18n.MessagesMain.main(MessagesMain.java:15)
Exception in thread "main" Process terminated with exit code 1

I do have the resource.properties in the com.mentor.pubsubservice.util.i18n directory. 
 I also tried adding resources_en_US.properties, but get the same error.  I have been 
cursed with ResourceBundles my entire Java programming life ... the saga continues.

Any ideas? 

Best regards,

Mike

Re: java.util.List and 1.1.RC2

[Steve Loughran]

Brain, Jim wrote:
I know, and I thought of that.

Unfortunately, I need to expose 296 service classes, containing 5000
references to List, and I have a program that is creating web service
wrappers for all the classes (the original classes combined data and access
logic, which had to split in half to work in the web service world.  The
program I wrote can be applied to any arbitrary class, though, uses
reflection, and I am planning on cleaning it up and offering it).
Programmatically, I can't determine the data type of a List, so I have to
replace with Object[], which isn't much better (although AXIS WSDL code
seems to like that)
You cant add xdoclet metadata to state the type of lists? I really miss 
typed datastructures, its the main bit of C++ that I still miss, even if 
its templating was awful compared to that of the polymorphic type 
inference features of Standard ML.

I guess porting to the generics compiler is out too, huh :) That's OK, 
axis cant handle that iether.

It seems to me that if Axis handles Object[] then it should be able to 
serialize List, at the very least by going List.toArray() & returning 
the object array. typing would be a nice extra, with a configurable in 
the WSDD declarations that stated the java class in the list.

You sound like you are doing a major undertaking there. I wish you well 
-you could probably derive an interesting paper or two from the experience.

I'll point you at my making web-services-that-work paper 
http://www.iseran.com/Steve/papers/wstw/
which may be of interest

-steve

RE: cofiguring SOAPMonitor

[Harry . Kobetitsch]

SOAPMonitor needs to forward the messages to 5001. The SOAPMonitor itself 
will be taking messages from a different port on behalf of the server you have 
listening on 5001. You specify that port and make sure the client is sending to 
that port you chose SOAPMonitor to listen on.
Harry J. KobetitschUBS 
WarburgOne North Wacker DriveChicago, Illinois 
60606-2809312-525-5866[EMAIL PROTECTED] 

  -Original Message-From: Allen, Michael E. 
  [mailto:[EMAIL PROTECTED]Sent: Wednesday, April 02, 2003 
  12:02 PMTo: [EMAIL PROTECTED]Subject: cofiguring 
  SOAPMonitor
  
  I am trying to 
  use SOAPMonitor, but am seeing no messages.  I looked at the axis/WEB-INF/web.xml 
  file and it is configured to listen on port 5001.  Why?
   
  Thanks,
  Michael

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.

Re: java.util.List and 1.1.RC2

[Steve Loughran]

Mitch Gitman wrote:
Right, refer to the "Forgive me..." message which I sent out five minutes
later when I realized this. 
yeah, I caught that

I'm still wondering about the apparent existing support for java.util.List and
the like. It seems to me that Java2WSDL should generate an exception when it
comes across a collection class that stores java.lang.Object instances.
That is one thing wrong with collections; you cannot state in advance 
their type, and the thing at the far end cannot deal with arbitrary java 
objects.

If you go
 return (Foo)list.toArray(new Foo[0]);
You can turn a list to an array in a snap. A fromArray() would be nice 
to match it.

However, there is meant to be something in soap where you do say you are 
returning an Object and the type is passed in the envelope at run time. 
I dont know the exact details...

RE: java.util.List and 1.1.RC2

[Brain, Jim]

I know, and I thought of that.

Unfortunately, I need to expose 296 service classes, containing 5000
references to List, and I have a program that is creating web service
wrappers for all the classes (the original classes combined data and access
logic, which had to split in half to work in the web service world.  The
program I wrote can be applied to any arbitrary class, though, uses
reflection, and I am planning on cleaning it up and offering it).
Programmatically, I can't determine the data type of a List, so I have to
replace with Object[], which isn't much better (although AXIS WSDL code
seems to like that)

Jim


Jim Brain, [EMAIL PROTECTED]
"Researching tomorrow's decisions today."
(319) 369-2070 (work)
SYSTEMS ARCHITECT, ITS, AEGON FINANCIAL PARTNERS

 -Original Message-
From:   James Black [mailto:[EMAIL PROTECTED] 
Sent:   Wednesday, April 02, 2003 12:27 PM
To: [EMAIL PROTECTED]
Subject:Re: java.util.List and 1.1.RC2

Brain, Jim wrote:

>All I know at present is that when I expose a method that returns List, the
>Java2WSDL piece in AXIS complains bitterly when I do ?WSDL.
>
>As for customizing AXIS, I'm willing to try, but my knowledge of the inner
>workings of AXIS is extremely limited.
>
  What I did is to just turn the list into an array of beans, and pass 
that around. The only advantage of a list is that it can change in size, 
but once I send it to the client it will not change in size.
  It is also trivial to turn that back into a list on the .NET side.

>  
>

Re: java.util.List and 1.1.RC2

[Mitch Gitman]

Right, refer to the "Forgive me..." message which I sent out five minutes
later when I realized this. 

I'm still wondering about the apparent existing support for java.util.List and
the like. It seems to me that Java2WSDL should generate an exception when it
comes across a collection class that stores java.lang.Object instances.

Steve Loughran <[EMAIL PROTECTED]> wrote:
Mitch Gitman wrote:
> Jim,
> There seem to be two separate issues here. 
> 
> The one (which bug 8435 addresses) is how to emulate an enumeration type,
> which of course is not natively supported in Java. I could have sworn
recently
> I saw (maybe on this list) a roundabout example how to code a Java class
that
> Axis would recognize as an enumeration. The class made use of public
constants
> together with getters/setters. It would be helpful if bug 8435’s text was
> amended with this example.

no, this is a special case of bitfield enums that axis doesnt handle yet.

Re: java.util.List and 1.1.RC2

[James Black]

Brain, Jim wrote:

All I know at present is that when I expose a method that returns List, the
Java2WSDL piece in AXIS complains bitterly when I do ?WSDL.
As for customizing AXIS, I'm willing to try, but my knowledge of the inner
workings of AXIS is extremely limited.
 What I did is to just turn the list into an array of beans, and pass 
that around. The only advantage of a list is that it can change in size, 
but once I send it to the client it will not change in size.
 It is also trivial to turn that back into a list on the .NET side.

 

RE: java.util.List and 1.1.RC2

[Brain, Jim]

All I know at present is that when I expose a method that returns List, the
Java2WSDL piece in AXIS complains bitterly when I do ?WSDL.

As for customizing AXIS, I'm willing to try, but my knowledge of the inner
workings of AXIS is extremely limited.

Jim


Jim Brain, [EMAIL PROTECTED]
"Researching tomorrow's decisions today."
(319) 369-2070 (work)
SYSTEMS ARCHITECT, ITS, AEGON FINANCIAL PARTNERS

 -Original Message-
From:   Steve Loughran [mailto:[EMAIL PROTECTED] 
Sent:   Wednesday, April 02, 2003 12:08 PM
To: [EMAIL PROTECTED]
Subject:Re: java.util.List and 1.1.RC2

Brain, Jim wrote:
> Does anyone know if:
> 
> Bugzilla Bug 8435 
>   [xsd:list] WSDL2Java doesn't handle schema  enumerations 

if its open, its probably open; you can always write a test to make sure.

Note that is the special case of a list enum, not a simple list. The way 
.NET serialises a bitfield enum with things like
  foo=1
  bar=2
and a value of foo | bar is to pump out
< >foo bar

which axis doesnt handle. These are not java lists, which you seem to be 
talking about


> has been fixed.  I don't know how current Bugzilla is, though I concerned
it
> is, as this seems to preclude the use of AXIS for our project (makes heavy
> use of Lists)
> 

On the contrary, you have an opportunity to customise axis to meet your 
needs, and contribute something back to the community.

Re: [java.util.List and 1.1.RC2]

[Steve Loughran]

Mitch Gitman wrote:
Jim,
There seem to be two separate issues here. 

The one (which bug 8435 addresses) is how to emulate an enumeration type,
which of course is not natively supported in Java. I could have sworn recently
I saw (maybe on this list) a roundabout example how to code a Java class that
Axis would recognize as an enumeration. The class made use of public constants
together with getters/setters. It would be helpful if bug 8435’s text was
amended with this example.
no, this is a special case of bitfield enums that axis doesnt handle yet.

Re: java.util.List and 1.1.RC2

[Steve Loughran]

Brain, Jim wrote:
Does anyone know if:

Bugzilla Bug 8435 	
  [xsd:list] WSDL2Java doesn't handle schema  enumerations 
if its open, its probably open; you can always write a test to make sure.

Note that is the special case of a list enum, not a simple list. The way 
.NET serialises a bitfield enum with things like
 foo=1
 bar=2
and a value of foo | bar is to pump out
< >foo bar

which axis doesnt handle. These are not java lists, which you seem to be 
talking about


has been fixed.  I don't know how current Bugzilla is, though I concerned it
is, as this seems to preclude the use of AXIS for our project (makes heavy
use of Lists)
On the contrary, you have an opportunity to customise axis to meet your 
needs, and contribute something back to the community.

cofiguring SOAPMonitor

[Allen, Michael E.]

I am trying to use
SOAPMonitor, but am seeing no messages.  I looked at the axis/WEB-INF/web.xml file and it is
configured to listen on port 5001. 
Why?

 

Thanks,

Michael

Invalid WSDD element 'service' (wanted 'deployment')

[Clay Graham]

Hello Axis Users!

I have run into a bit of a wall here and desperately need to some advice
on how to fix it. I have been looking through the archives quite a bit
and haven't found anything "quite" like this problem. I have done the
basic axis install to the tomcat webapp directories, I am using the
latest version of xerces (2.4) with tomcat 4.1.3. My "happy" page comes
up just fine:

##BEGIN HAPPY.JSP

Found SAAJ API (javax.xml.soap.SOAPMessage) at
/home/tomcat/jakarta-tomcat-4.1.3/common/lib/saaj.jar
Found JAX-RPC API (javax.xml.rpc.Service) at
/home/tomcat/jakarta-tomcat-4.1.3/common/lib/jaxrpc-api.jar
Found Apache-Axis (org.apache.axis.transport.http.AxisServlet) at
/home/tomcat/jakarta-tomcat-4.1.3/webapps/axis/WEB-INF/lib/axis.jar
Found Jakarta-Commons Discovery (org.apache.commons.discovery.Resource)
at
/home/tomcat/jakarta-tomcat-4.1.3/webapps/axis/WEB-INF/lib/commons-disco
very.jar
Found Jakarta-Commons Logging (org.apache.commons.logging.Log) at
/home/tomcat/jakarta-tomcat-4.1.3/webapps/axis/WEB-INF/lib/commons-loggi
ng.jar
Found Log4j (org.apache.log4j.Layout) at
/home/tomcat/jakarta-tomcat-4.1.3/webapps/axis/WEB-INF/lib/log4j-1.2.4.j
ar
Found IBM's WSDL4Java (com.ibm.wsdl.factory.WSDLFactoryImpl) at
/home/tomcat/jakarta-tomcat-4.1.3/webapps/axis/WEB-INF/lib/wsdl4j.jar
Found JAXP implementation (javax.xml.parsers.SAXParserFactory)
Found Activation API (javax.activation.DataHandler) at
/home/tomcat/jakarta-tomcat-4.1.3/common/lib/activation.jar

END HAPPY.JSP

And I have uncommented the administration servlet lines from web.xml
because I want to be able to deploy using wsdd.

So this all sounds like goodness right? 

The problem is when I attempt to click on the Administer Axis link on
the main axis page (axis webapp) the following exeption is printed. This
seems like the most basic functionality, the link is on the main page
for goodness sake!

org.apache.axis.deployment.wsdd.WSDDException: Invalid WSDD element
'service' (wanted 'deployment')

I have attempted to use the basic deployment.wsdd that is in the user
guide and I get the exact same error. 

BEGIN DEPLOYMENT.WSDD

http://xml.apache.org/axis/wsdd/"; 
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"; 
xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance";> 


http://meis/mailservlet/ 






END DEPLOYMENT.WSDD

So when this didn't work I went to a programattic approach thinking, hey
I have heard rumblings about people who don't like the administrator, so
why not use the servlet init approach:

BEGIN ServicesDeploymentServlet.java

/*
 * ServicesDeploymentServlet.java
 *
 * Created on April 1, 2003, 5:39 PM
 */

package com.noi.web.servlet;

import java.io.*;
import java.net.*;

import javax.servlet.*;
import javax.servlet.http.*;
import org.apache.axis.transport.http.*;
import org.apache.axis.*;
import org.apache.axis.deployment.wsdd.*;
import javax.xml.parsers.*;
import org.w3c.dom.*;
import org.xml.sax.*;

import com.noi.utility.data.*;


/**
 *
 * @author  clay
 * @version
 */
public class ServicesDeploymentServlet extends HttpServlet {

/** Initializes the servlet.
 */
public void init(ServletConfig sconfig) throws ServletException {
super.init(sconfig);
   AxisServlet axisServlet = new AxisServlet(); 
   ServletConfig sC = getServletConfig(); 
   ServletContext context = this.getServletContext();
   try { 
   axisServlet.init(sC); 
   } catch (ServletException e) { 
   e.printStackTrace(); 
   } 
   try { 
   AxisEngine engine = axisServlet.getEngine(); 
   DocumentBuilderFactory fact =
DocumentBuilderFactory.newInstance(); 
   Document doc = null; 
   //this should be a resource
   DocumentBuilder builder = fact.newDocumentBuilder(); 
   fact.setNamespaceAware(true);
   URL deployURL = context.getResource("/wsdd/deploy.wsdd"); 
   XMLDocumentReader reader = new XMLDocumentReader();
   reader.parse(deployURL);  
   doc = reader.getDocument();
   
   Element element = doc.getDocumentElement(); 
   System.out.println ( "Element: " + element.getNodeName() ); 
//-- prints out 'deployment' 
   WSDDDocument wsddDoc = new WSDDDocument(element);
   //--  EXCEPTION BEING THROWN HERE 
   EngineConfiguration config =
(EngineConfiguration)engine.getConfig(); 
   
   if ( config instanceof WSDDEngineConfiguration) { 
   WSDDDeployment deployment =
((WSDDEngineConfiguration)config).getDeployment(); 
   wsddDoc.deploy(deployment); 
   } 
   engine.refreshGlobalOptions(); 
   engine.saveConfiguration();
   }
catch (IOException e) { 
   e.printStackTrace(); 

Re: WSDL error after deploying a service using AdminClient

[Debbie Vasaturo]

I'm replying to my own post here.  I was not 
able to solve this problem but I found a post by Gene Chuang on 12-30-02 
explaining a workaround.  I used Java2WSDL to create the wsdll and then 
used WSDL2Java -s to create deploy.wsdd.  The xml namespaces were created 
and my app deployed just fine.   Gene, if you're still out there 
thanks a bunch!!
 
debbie.

  - Original Message - 
  From: 
  Debbie 
  Vasaturo 
  To: [EMAIL PROTECTED] 
  Sent: Wednesday, April 02, 2003 10:20 
  AM
  Subject: Re: WSDL error after deploying a 
  service using AdminClient
  
  Olivier,
  Thanks for your suggestion.  I added the 
  namespace tags but I am still getting the same error.  I can see the new 
  namespace tags in the server-config.wsdd.  I can also see the new 
  beanMapping tags defined in my deploy.wsdd.  Oddly though, 
  qName="".   I have also read earlier posts reporting the same error 
  message. Others have suggested that this error may occur if the class is not a 
  properly formated JavaBean.  I have verified I am using proper 
  JavaBeans.  I also have the same problem when trying to deploy the 
  OrderProcessing BeanService in the example5 of the axis installation.  
  
   
  thanks.
  debbie.
  
- Original Message - 
From: 
Olivier 
Gauwin 
To: [EMAIL PROTECTED] 
Sent: Wednesday, April 02, 2003 2:04 
AM
Subject: Re: WSDL error after deploying 
a service using AdminClient
Hello Debbie,You could try to add something like 
urn:BookSwapbetween 
 and .I've never seen your error before, 
but it sometimes resolves namespace related 
problems.HTH,OlivierDebbie Vasaturo wrote:

  
  

  Hello,
  I have just deployed my service 
  using:
  java org.apache.axis.client.AdminClient 
  -lhttp://localhost:8080/axis/services/AdminService 
deploy.wsdd
   
  Here is my deploy.wsdd:
   
  http://xml.apache.org/axis/wsdd/" 
  xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">"java:RPC">         "java:bookswap.books.Book"/>   
  "java:bookswap.owner.Owner"/>
   
  The service is deployed OK (I'm told) and I 
  can see the methods displayed for my service when I view the services at 
  http://localhost:8080/axis/servlet/AxisServlet.
   
  However, when I select the wsdl link to view 
  the wsdl, the following exception is thrown:
   
  Has anyone seen this error?  I do not 
  understand the error message.
  Thanks in advance.
   
  debbie.
   
  
  AXIS error
  Sorry, something seems to have gone wrong... here are the details:Fault - WSDLException: faultCode=PARSER_ERROR: Problem parsing '- WSDL Document -'.: The value of the attribute "xmlns:tns1" is invalid. Prefixed namespace bindings may not be empty.: org.xml.sax.SAXParseException: The value of the attribute "xmlns:tns1" is invalid. Prefixed namespace bindings may not be empty.
	at org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:267)
	at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:201)
	at com.ibm.wsdl.xml.WSDLWriterImpl.getDocument(Unknown Source)
	at com.ibm.wsdl.xml.WSDLWriterImpl.getDocument(Unknown Source)
	at org.apache.axis.wsdl.fromJava.Emitter.emit(Emitter.java:269)
	at org.apache.axis.providers.java.JavaProvider.generateWSDL(JavaProvider.java:478)
	at org.apache.axis.strategies.WSDLGenStrategy.visit(WSDLGenStrategy.java:72)
	at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:156)
	at org.apache.axis.SimpleChain.generateWSDL(SimpleChain.java:143)
	at org.apache.axis.handlers.soap.SOAPService.generateWSDL(SOAPService.java:368)
	at org.apache.axis.server.AxisServer.generateWSDL(AxisServer.java:491)
	at org.apache.axis.transport.http.AxisServlet.processWsdlRequest(AxisServlet.java:434)
	at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:286)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
	at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:339)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
	at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	at org.apache.catalin

BUG: Axis + Java Web Start + Authenticating Proxies

[Bruno.Melloni]

Using Java Web Start and Axis together is a great idea.  But there is a design flaw 
that prevents using the combination in professional-quality internet-aware 
applications.  Any solutions or workarounds would be greatly welcome.

Description:

1) Problem occurs only when working with a proxy, and when the proxy requires 
username/password authentication.  Things work fine in all other situations.

2) I am aware that Axis obtains proxy host and port information from the system 
properties http.proxyHost and http.proxyPort.  Not a problem, since Java Web Start 
uses proxyHost and proxyPort and it is a simple matter to copy the values.

3) Java Web Start brings up a proxy login dialog box before the application starts up 
(since it needs to check/retrieve the latest version of the code).  It assumes that 
the application will rely on HttpURLConnection and therefore inherit the 
DefaultAuthenticator (from Java Web Start).

4) Java Web Start provides no mechanism to extract the username and password from the 
initial proxy login.  Sun appears to want things to remain this way.  Therefore using 
Call.setUsername() and Call.setPassword does not really help.

5) It is possible to call Authenticator.requestPasswordAuthentication() to bring up a 
popup login for the proxy username and password.

The problem is that we can justify to the user the application login as a business 
necessity, and the initial proxy login as Sun's unfriendly and lame implementation of 
Java Web Start, but it is impossible to justify a second proxy login.

We have found a temporary workaround by (a) Using a raw socket (not an 
HttpURLConnection in order to bypass Java Web Start) to query the proxy for its proxy 
prompt, and (b) Supplying the host, port and prompt to 
requestPasswordAuthentication().  If the values match the ones used by the initial 
proxy login, a second login screen is not displayed but the PasswordAuthentication 
object is returned with the username and password.  Unfortunately, Sun considers this 
behavior a security bug and plans to block it in the upcoming JRE 1.4.2.

Note, this problem also happens when using the older Apache SOAP.

Can someone suggest a solution to this problem?

Bruno

Re: java.util.List and 1.1.RC2

[Mitch Gitman]

Forgive me. Bug 8435 concerns how to go from an enum type in a WSDL to Java.
Not how to emulate an enum type in Java and then produce a WSDL from it. 

Still wondering about java.util.List and the like.

Mitch Gitman <[EMAIL PROTECTED]> wrote:
Jim,
There seem to be two separate issues here. 

The one (which bug 8435 addresses) is how to emulate an enumeration type,
which of course is not natively supported in Java. I could have sworn recently
I saw (maybe on this list) a roundabout example how to code a Java class that
Axis would recognize as an enumeration. The class made use of public constants
together with getters/setters. It would be helpful if bug 8435’s text was
amended with this example.

The other issue (which you appear to be interested in) concerns support for
the collections classes/interfaces in the java.util package. It seems to me
that collections should NOT be supported because such support is not
prescribed by JAX-RPC 1.0. Literal arrays with [] only.

However, I have experimented with Axis 1.1 RC2 and noticed that Java2WSDL does
try to deal with a java.util.ArrayList and the like. My generated WSDL winds
up with the following:

___
__
_ 
__
___


This type seems meaningless and potentially dangerous because it’s an array
of what? The wsdl:arrayType=“”. I’m curious what else needs to be done
to get this to work. Not that it necessarily should work, though.

"Brain, Jim" <[EMAIL PROTECTED]> wrote:
Does anyone know if:

Bugzilla Bug 8435   
  [xsd:list] WSDL2Java doesn't handle schema  enumerations 

has been fixed.  I don't know how current Bugzilla is, though I concerned it
is, as this seems to preclude the use of AXIS for our project (makes heavy
use of Lists)

Jim
 

Jim Brain, [EMAIL PROTECTED]  
"Researching tomorrow's decisions today."
(319) 369-2070 (work)
Systems Architect, ITS, AEGON Financial Partners

Re: [java.util.List and 1.1.RC2]

[Mitch Gitman]

Jim,
There seem to be two separate issues here. 

The one (which bug 8435 addresses) is how to emulate an enumeration type,
which of course is not natively supported in Java. I could have sworn recently
I saw (maybe on this list) a roundabout example how to code a Java class that
Axis would recognize as an enumeration. The class made use of public constants
together with getters/setters. It would be helpful if bug 8435’s text was
amended with this example.

The other issue (which you appear to be interested in) concerns support for
the collections classes/interfaces in the java.util package. It seems to me
that collections should NOT be supported because such support is not
prescribed by JAX-RPC 1.0. Literal arrays with [] only.

However, I have experimented with Axis 1.1 RC2 and noticed that Java2WSDL does
try to deal with a java.util.ArrayList and the like. My generated WSDL winds
up with the following:

___
__
_ 
__
___


This type seems meaningless and potentially dangerous because it’s an array
of what? The wsdl:arrayType=“”. I’m curious what else needs to be done
to get this to work. Not that it necessarily should work, though.

"Brain, Jim" <[EMAIL PROTECTED]> wrote:
Does anyone know if:

Bugzilla Bug 8435   
  [xsd:list] WSDL2Java doesn't handle schema  enumerations 

has been fixed.  I don't know how current Bugzilla is, though I concerned it
is, as this seems to preclude the use of AXIS for our project (makes heavy
use of Lists)

Jim
 

Jim Brain, [EMAIL PROTECTED]  
"Researching tomorrow's decisions today."
(319) 369-2070 (work)
Systems Architect, ITS, AEGON Financial Partners

Re: WSDL error after deploying a service using AdminClient

[Debbie Vasaturo]

Olivier,
Thanks for your suggestion.  I added the 
namespace tags but I am still getting the same error.  I can see the new 
namespace tags in the server-config.wsdd.  I can also see the new 
beanMapping tags defined in my deploy.wsdd.  Oddly though, 
qName="".   I have also read earlier posts reporting the same error 
message. Others have suggested that this error may occur if the class is not a 
properly formated JavaBean.  I have verified I am using proper 
JavaBeans.  I also have the same problem when trying to deploy the 
OrderProcessing BeanService in the example5 of the axis installation.  

 
thanks.
debbie.

  - Original Message - 
  From: 
  Olivier 
  Gauwin 
  To: [EMAIL PROTECTED] 
  Sent: Wednesday, April 02, 2003 2:04 
  AM
  Subject: Re: WSDL error after deploying a 
  service using AdminClient
  Hello Debbie,You could try to add something like 
  urn:BookSwapbetween  
  and .I've never seen your error before, but it sometimes 
  resolves namespace related problems.HTH,OlivierDebbie 
  Vasaturo wrote:
  



Hello,
I have just deployed my service 
using:
java org.apache.axis.client.AdminClient 
-lhttp://localhost:8080/axis/services/AdminService deploy.wsdd
 
Here is my deploy.wsdd:
 
http://xml.apache.org/axis/wsdd/" 
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">"java:RPC">      
   
"java:bookswap.books.Book"/>   
"java:bookswap.owner.Owner"/>
 
The service is deployed OK (I'm told) and I can 
see the methods displayed for my service when I view the services at http://localhost:8080/axis/servlet/AxisServlet.
 
However, when I select the wsdl link to view 
the wsdl, the following exception is thrown:
 
Has anyone seen this error?  I do not 
understand the error message.
Thanks in advance.
 
debbie.
 

AXIS error
Sorry, something seems to have gone wrong... here are the details:Fault - WSDLException: faultCode=PARSER_ERROR: Problem parsing '- WSDL Document -'.: The value of the attribute "xmlns:tns1" is invalid. Prefixed namespace bindings may not be empty.: org.xml.sax.SAXParseException: The value of the attribute "xmlns:tns1" is invalid. Prefixed namespace bindings may not be empty.
	at org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:267)
	at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:201)
	at com.ibm.wsdl.xml.WSDLWriterImpl.getDocument(Unknown Source)
	at com.ibm.wsdl.xml.WSDLWriterImpl.getDocument(Unknown Source)
	at org.apache.axis.wsdl.fromJava.Emitter.emit(Emitter.java:269)
	at org.apache.axis.providers.java.JavaProvider.generateWSDL(JavaProvider.java:478)
	at org.apache.axis.strategies.WSDLGenStrategy.visit(WSDLGenStrategy.java:72)
	at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:156)
	at org.apache.axis.SimpleChain.generateWSDL(SimpleChain.java:143)
	at org.apache.axis.handlers.soap.SOAPService.generateWSDL(SOAPService.java:368)
	at org.apache.axis.server.AxisServer.generateWSDL(AxisServer.java:491)
	at org.apache.axis.transport.http.AxisServlet.processWsdlRequest(AxisServlet.java:434)
	at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:286)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
	at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:339)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
	at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
	at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2397)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
	at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
	at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
	at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:171)
	at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invoke

java.util.List and 1.1.RC2

[Brain, Jim]

Does anyone know if:

Bugzilla Bug 8435   
  [xsd:list] WSDL2Java doesn't handle schema  enumerations 

has been fixed.  I don't know how current Bugzilla is, though I concerned it
is, as this seems to preclude the use of AXIS for our project (makes heavy
use of Lists)

Jim
 

Jim Brain, [EMAIL PROTECTED]  
"Researching tomorrow's decisions today."
(319) 369-2070 (work)
Systems Architect, ITS, AEGON Financial Partners

RE: help required for attachment using ejb as webservice provider

[subhendukumar mohanty]

Hi Toshiyuki
(B
(BMy Answers are as below
(B
(BAxis 1.0 (But we may go for Apache Soap latest version comes with websphere 4.0)
(BType of Image (Jpeg). We get the image as byte array from other source. We do not get 
(Bfile reference.
(B
(BProblem. If i expose my ejb method as webservice interface and i have to use soap with 
(Battachment then the return type of EJB method will be of Datahandler Type. But 
(BDataHandler can  not be return type of an ejb method as it does not implement 
(Bjava.io.serializable and all ejb retutn parameters needs to be serializable.
(B
(BSo to avoid this i was thinking that let my ejb return byte array and i have to write 
(Ba wrapper java class which will convert the byte array to datahandler (still no clear 
(Bhow to convert that). The wrapper java class will be exposed as web service rather 
(Bthan exposing the ejb as webservice.
(B
(BLet me know whethere i am procceding in a correct direction.
(B
(BThanks,
(BSubhendu
(B
(B-Original Message-
(BFrom: Toshiyuki Kimura [mailto:[EMAIL PROTECTED]
(BSent: Tuesday, March 25, 2003 6:27 AM
(BTo: [EMAIL PROTECTED]
(BSubject: Re: help required for attachment using ejb as webservice provider
(B
(B
(BHi Subhendu,
(B
(B  In order to clear questions from you, we'll need more details of
(Byour situation;
(B
(B  - Version of AXIS: 1.0, 1.1Beta, RC1, RC2, or the current ver ?
(B  - Type of Image  : 'JPEG', 'GIF', or the other specific types ?
(B  - Real problem   : 'Exceptions', or 'Functionally defectives' ?
(B
(B  If you're using AXIS 1.1 Beta (or the later) and 'image/jpeg
(Bor image/gif' as the content type (i.e. your image archive only
(Bhas JPEG files and/or GIF files), you might make it with the 
(Bfollowing snapshot;
(B
(Bpublic DataHandler downladFile(java.lang.String filename){
(B  try{
(BFileDataSource dataSource = new FileDataSource(filename);
(BDataHandler dataHandler = new DataHandler(dataSource);
(Breturn dataHandler;
(B  }catch(Exception e){
(B  :
(B  }
(B}
(B
(B  Please note DataHandler hasn't been implemented as serializable,
(Bhowever, some standardized types of content (MIME type) will be
(Bautomatically serialized and deserialized by the runtime, AXIS
(Bwith your right configuration.
(B
(BBest Regards,
(B
(B  Toshi (Toshiyuki Kimura) <[EMAIL PROTECTED]>
(B  R&D Headquarters
(B  NTT DATA Corporation
(B
(B-Original Message-
(BFrom: subhendukumar mohanty [mailto:[EMAIL PROTECTED]
(BSent: Friday, March 21, 2003 10:05 AM
(BTo: [EMAIL PROTECTED]
(BSubject: help required for attachment using ejb as
(B webservice provider
(B
(BWe are creating a ejb which will be exposed as webservice.
(BOne of the method of ejb will return the image from image
(Barchive. So we need to use soap with attachment for this.
(BI learned that if any data is returned using DataHandler
(Bit will be automatically passed as soap with attachment.
(BAs DataHandler is not implemented java.io.serializable,
(BI can not use this as the return type of the ejb. I am new
(Bto webservice and axis. So any body can guide me what to do
(Bin this case..
(B
(BYour help will be appreciated.
(B
(BThanks,
(BSubhendu

stubs and custom serializers

[Volkmann, Mark]

Title: stubs and custom serializers





When a client is invoking an Axis web service using a stub generated by wsdl2java, is there any way it can register custom serializers/deserializers to be used when calls are made on the stub?  It seems to me that the best solution would be to specify the serializers/deserializers to be used in the call to wsdl2java so that it generates a stub that already knows which ones to use, but I don't see any options for doing that.



***
WARNING:  All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.

Vector serializer ...

[Carl Cabou]

Hi all !!

I've deployed successfully 2 services on Axis.
I use two home made classes A and B. Each one has a beanserializer 
declared in the WSDD file.
The 1st service returns a vector of A objects, it works just fine 
without declaring any serializer for java.util.Vector.

The 2nd service returns a vector of vectors of B objects, then I get the 
following exception :

==
java.io.IOException: No serializer found for class java.util.Vector$1 in 
registry [EMAIL PROTECTED]
java.io.IOException: No serializer found for class java.util.Vector$1 in 
registry [EMAIL PROTECTED]
at 
org.apache.axis.encoding.SerializationContextImpl.serializeActual(SerializationContextImpl.java:1235)
at 
org.apache.axis.encoding.SerializationContextImpl.serialize(SerializationContextImpl.java:756)
at 
org.apache.axis.encoding.SerializationContextImpl.outputMultiRefs(SerializationContextImpl.java:853)
at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:147)
at 
org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:401)
at 
org.apache.axis.message.MessageElement.output(MessageElement.java:746)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:273)
at org.apache.axis.SOAPPart.getAsString(SOAPPart.java:488)
at org.apache.axis.SOAPPart.getAsBytes(SOAPPart.java:379)
at org.apache.axis.Message.getContentType(Message.java:400)
at 
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:721)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at 
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:335)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at 
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
at java.lang.Thread.run(Thread.java:479)

==

It seems that I need a serializer for Java.util.Vector, but only on the 
2nd service.

Why that ?!

Any idea or feedback on serializing Vectors with Axis.

Best Regards.

Carl.

initialization of webservice

[Davinder Singh]

Title: initialization of webservice  





Hi,
I have a webservice and the service end point class implements javax.xml.rpc.server.ServiceLifecycle interface. 
Is there a way i can have init() method called without submitting a request to the webservice?
I am using weblogic 7.0 SP 1 / Axis 1.1RC1. Webservice has "application" scope.


thanx for any pointers,
davin

Unable to update a string element within a message with 1.1 rc2.

[Neil Blue]

Hello,

We are now using axis 1.1 rc2, and we have built a request hander, in which
we are trying to alter the request message before it arrives at the soap
binding class. In the handler we perform the following steps:

first we get the request message from the message context with:
Message message = msgContext.getRequestMessage();

next we get the soap body with
MessageElement body = message.getSOAPEnvelope().getBody();

having for the body, we navigate through the object with getChidElements(),
untill we find the elemnt the we want to update.
As we want to update the text within the element, and there is no way do do
this we can find in the API, we create a new MessageElement
MessageElement newElement = new MessageElement(element.getQName(), "new
string value");

Then we remove the original element
MessageElement parent = element.getParentElement();
parent.removeChildElement(element);

Then we add our new element
parent.addChildElement(element);

Also, when we print out the parent with:
System.err.println(parent);
the ouput still contains the original element text

however when we list the child elements parent, it has the new element with
the new text value.

Please can anyone shed some light on this

Thanks
Neil Blue

Re: WSL2Java Question -- Document/Literal

[Paul Jackson]

On a related message-style topic, if I deploy the messaging sample (in
samples\message), the wsdl from "MessagesService?wsdl" contains style="rpc".
Can anyone explain why the message sample's generated wsdl has style="rpc"
and not style="document"?

- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 02, 2003 12:04 AM
Subject: WSL2Java Question -- Document/Literal


>
> Hi, all:
>
> I am gettting started in AXIS 1.1 RC2.
> In my WSDL, I specify "Document/Literal". But, after using WSDL2Java, the
> generated "deploy.wsdd" always has
> the provider="java:RPC". Is this correct? Shouldn't this be
> "provider=java:MSG"?
>
> Thanks a lot
>
>
>
>
>

Re: java.net.ConnectException: Connection refused: connect (RESOLVED)

[Hans Russo resowe]

USING SLASH INSTAD OF BACKSLASH RESOLVED THE PROBLEM:

But the line for the variable Zeitansage_Service_address  was created from
tool WSDL2Java. So somebody should have a look if this a bug of WSDL2Java
for windows.

Thank you very much
Hans

- Original Message -
From: "Steve Loughran" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 01, 2003 9:29 PM
Subject: Re: java.net.ConnectException: Connection refused: connect


> you should be using forward / in urls and things; the backslash is a
> windows only hack.
>
> Hans Russo resowe wrote:
> > Maybe you are right but the file Zeitansageservislocator was generated
by
> > WSDL2Java.
> > Indeed there was a problem: WSDL2Java was not able to write the string
> > Zeitansage_Service_address
> > , see the listing bellow, correctly. I had to edtit the string
> > Zeitansage_Service_address. It was necessary
> > to write two slashes for a slash to be able to compile
> > Zeitansageservislocator with eclipse or javac without error.
> > Maybe there anything wrong now.
> >
> > Thanks in advance
> > Hans
> >
> > /**
> > * ZeitansageServiceLocator.java
> > *
> > * This file was auto-generated from WSDL
> > * by the Apache Axis WSDL2Java emitter.
> > */
> > package kapitel8.zeitansage_wsdl;
> > public class ZeitansageServiceLocator extends
org.apache.axis.client.Service
> > implements kapitel8.zeitansage_wsdl.ZeitansageService {
> > // Use to get a proxy class for Zeitansage_Service
> > private final java.lang.String Zeitansage_Service_address =
> > "http:localhost:8080\\axis\\services\\Zeitansage_Service";
> > public java.lang.String getZeitansage_ServiceAddress() {
> > return Zeitansage_Service_address;
> > }
>
>
>
>