Title: Message
It looks like the
port name should be LimaIFPort in namespace urn:Foo, rather than LimaIF in no
namespace.
HTH,
Gary
-Original Message-From: Brian Shields
[mailto:[EMAIL PROTECTED] Sent: Monday, January 26, 2004 8:07
AMTo: [EMAIL PROTECTED]Subject: missing
ion which would do
> just that. Anyway...
>
> Thanks again,
> Stuart
>
>
> -Original Message-
> From: Gary L Peskin [mailto:[EMAIL PROTECTED]
> Sent: Thursday 18 December 2003 21:29
> To: [EMAIL PROTECTED]
> Subject: RE: SecureSocketFactory pluggability?
>
Title: Message
This is thrown when
you try to include a .jar file with a java.* package in it on the regular
classpath. You might want to check with Rommel Sharma since his earlier
email indicated that he did exactly that. I would expect his action to
cause exactly this problem, and it did
java.security file.
Also, be careful of some of the URLs that I provided. They may break into
multiple lines so you'll have to cut and paste.
Gary
> -Original Message-
> From: Gary L Peskin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 18, 2003 12:29 PM
> To: [EMAIL PRO
some customization, though
> I have no idea if I can use it, nor how to instantiate it
> with the 'attributes' Hashtable it takes which can hold
> 'keyStore', 'keyStorePass', etc. Is this coming from
> AxisClientEngine??
>
> In summary, I nee
I'd like to understand better what's happening here and I think I can help.
Can you please explain the first few paragraphs in baby steps so that I can
understand the exact problem?
Is the problem that you can't specify the socket factory that Axis will use?
Have you looked at the properties axis
Rick --
At a glance, it sounds like, in the second application, that the parser is
being loaded by a different classloader than axis. Are you able to bring up
WSAD-IE and just run the second application right after you bring up
WSAD-IE, without first running the first application? Does it still
It looks to me like the default URL built into the HelloWorldLocator comes
from the WSDL which is http://localhost:8080/axis/Hello. This is not
correct. It should match your UrlString. It looks like the WSDL file
soap:address element is just wrong.
As a workaround, you could code service.getHel
Title: Message
It looks like your
actual service is returning a
{ServiceController}Bioentity
rather than
a
{urn:ServiceController}Bioentity
HTH,
Gary
-Original Message-From:
Tania Durán [mailto:[EMAIL PROTECTED] Sent: Wednesday, October
01, 2003 8:09 AMTo: [EMAI
Anne -
I'm working on changes to accomplish this.
Gary
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Saturday, September 27, 2003 11:45 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Soap Fault question
>
>
> I think it makes sense to use Axis Fault to th
Please see my answers below.
Gary
> -Original Message-
> From: Chris Williamson [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 26, 2003 9:35 AM
> To: [EMAIL PROTECTED]
> Subject: RE: namespace question
>
>
> I have a few followup questions about this.
>
> 1) What is the preferred
Ann, Steve --
I am working on a patch for Axis to implement just this functionality.
There is one small clarification, however. The Axis engine is invoked on
the client side via a call to javax.xml.rpc.Call.invoke(...). In Axis, this
is actually implemented in org.apache.axis.client.Call.
Howev
The "text" element is a locally defined element in your schema because it is
declared as a child of the "sequence" element and not as a child of the
"schema" element. The schema element has an attribute elementFormDefault
whose default value is "unqualified". In your example, that attribute of
th
If you're using AxisServlet on the server side, it should strip the
stackTrace except for development Axis servers. Do you have the
axis.development.system property set? What version of Axis are you running
on the server?
Gary
> -Original Message-
> From: Josh Emmons [mailto:[EMAIL PROT
I would like to help answer this question but I don't really understand what
you're asking. Are you saying that the client is requesting a certain URL
but you want them to request a different URL? Perhaps you can handle this
with a request handler.
If you clarify what you're trying to do, I can
If Dims' answer does not get you far enough, can you please describe your
zOS setup a little more. Is it just the client side that's running on zOS?
How are you invoking it? It is running as a servlet or what?
Thanks,
Gary
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL
ry Wilkerson [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 27, 2003 9:52 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Soap Fault Explanation
>
>
> Gary -- what version of Axis are you running?
>
> -Original Message-
> From: Gary L Peskin [mailto:[EMAIL PRO
That URL is for the SOAP 1.2 specification Working Draft of 17 December
2001. Axis can definitely be used by SOAP 1.1 and SOAP 1.2 but I'm not sure
how to use this interim version. Perhaps someone else will now.
HTH,
Gary
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Be
>
> Gary -- what version of Axis are you running?
>
> -----Original Message-
> From: Gary L Peskin [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 27, 2003 11:44 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Soap Fault Explanation
>
>
> The client is java.
xisFault has a
> writeDetails() method that serializes your service specific fields.
>
> > -Original Message-
> > From: Gary L Peskin [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, August 27, 2003 11:22 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Soap
Cory et al --
I'm looking into this code very carefully at the moment. I'm trying to
generate Service Specific Exceptions but having problems on the client side
where an AxisFault is thrown rather than my actual exception. My Service
Specific Exceptions extend Exception but not AxisFault.
Do yo
Have you tried setting the system properties http.proxyHost and
http.proxyPort (and http.nonProxyHosts, if necessary)?
HTH,
Gary
> -Original Message-
> From: Sree K Puvvala [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 26, 2003 10:56 AM
> To: [EMAIL PROTECTED]
> Subject: 403 Firewall
22 matches
Mail list logo
