Robert,
I think your second option is the best route. I have used MessageContext
to get a hold of my servlet's context and it works dandy.
-Original Message-
From: Robert Bateman [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 15, 2005 3:01 PM
To: axis-user
Subject: Re:
The problem is that the Applet is trying to read (not write) the log level.
We have to find a way to give it that knowledge. Doing a quick google. I
found this page.
http://www.geocities.com/dcblaha/articles/Soap/SoapSetup.htm
It gives a recommendation on how to get Axis working in an applet. In
Did you make sure to declare your class in the samples.userguide.example4
package?
Sorry if I offend but sometimes we tend to look over the obvious.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 13, 2005 9:03 AM
To: [EMAIL PROTECTED]
What version of the jdk are you using? What precisely is the exception you
are getting?
-Original Message-
From: Beytullah Yildiz [mailto:[EMAIL PROTECTED]
Sent: Monday, February 14, 2005 2:32 PM
To: [EMAIL PROTECTED]
Subject: Libraries to build source ?
Hi,
Can anybody help me to find
the user is logged in for example.
Thanks,
Abdullah
--- Brown, Mike [EMAIL PROTECTED] wrote:
Abdullah,
What precisely is your business layer? You have a few options...One
you can use a delegate between your impl class and the business layer
that knows how to access the business layer and make
This isn't an axis problem. The servlet spec does not support threads being
spawned by code running in the container. It also does not support opening
ports or several other no-nos.
-Original Message-
From: Ian Wootten [mailto:[EMAIL PROTECTED]
Sent: Friday, February 11, 2005 8:28 AM
Title: Message
Christian,
Because your SOAP requests are
coming over HTTP, they support everything that a normal HTTP request supports,
including Basic-Auth. You can get to the basic-auth headers through the request
(which you can get at using the MessageContext). On the client side, both
Title: Message
Jai,
The problem is one thatpops up
a LOT with Websphere and should find it's way into axis' documentation.
Websphere includes a (very outdated in version 4.0) copy of saaj.jar. By default
it is this copy that gets loaded by your webapp classloader. There is an option
when
Abdullah,
What precisely is your business layer? You have a few options...One you
can use a delegate between your impl class and the business layer that knows
how to access the business layer and make the appropriate calls. Two, you
can have the impl access the business layer directly (I prefer
Currently Axis does not support vectors (that may change when they support
JDK 1.5 which has generic-based vectors).
They do accept arrays of objects but the array has to be of a specific type.
Now you can in theory make a generic type (let's call it WSParam). Your
WSParam would have a
]
Sent: Tuesday, February 01, 2005 3:47 AM
To: Brown, Mike
Cc: [EMAIL PROTECTED]
Subject: Re: Axis Gurus - Please help .. Urgent Issue with Document c
lass ???
Mike- I tried your appraoch in my WSAD but it does not work.
Only combination that successfully run AXIS WEB MODULE is EAR CLASSLOADER
You don't have to declare exceptions in your WSDD. Just make sure that your
custom exception extends RemoteException (java.rmi.RemoteException) then
when you throw it it gets translated into a soap fault.
-Original Message-
From: Jay Glanville [mailto:[EMAIL PROTECTED]
Sent: Tuesday,
Okay, I've been here several times before. Essentially Websphere Server
provides its own SOAP implementation based on SAAJ 1.1
Axis 1.2RC2 uses SAAJ 1.2. One of the jars that the Websphere container
loads is SAAJ1.1.jar
When your axis.war gets loaded by default SAAJ1.1.jar is the first place WS
Your problem is simple. You defined the return type as an array of bytes and
that is what it looks like as SOAP. Using attachments would be best in this
case. Another option would be to return a String that is the file Base64
encoded (that's what I did on a project using SOAP before attachments
I think people are missing his point. He's trying to build Axis from the
source and it won't build under JDK 1.5 because of the differences. Isn't
there some commandline parameter to compile using 1.4 compatibility. But
that would lose any benefits that 1.5 gives.
I guess there should be a branch
I think I understand you but here's the question. Why would you want your
setter called for a null value? If you check the value of
myPropertyHasBeenSet, after it was set with a null value, you'll get true.
Of course this would suck because it was set to null. Is there a reason
you'd want it to be
Luke, use the MessageContext
From within your handler call
HttpServlet
serv=(HttpServlet)MessageContext.getCurrentContext()getProperty(HTTPConstant
s.MC_HTTP_SERVLET);
URL myURL = serv.getServletContext().getResource(/);
This will give you the context root of your application.
-Original
The entire point of WSDL is to allow automatic code generation. The
automatically generated code allows a developer to make calls to a
webservice as if it were a local call. Many generators (including wsdl2java)
embed the endpoint into the client stubs (the same endpoint that is
specified in the
You can get a handle on the request object from the MessageContext. Anywhere
within your service method you can call
MessageContext mc = MessageContext.getCurrentContext();
ServletRequest req =
(ServletRequest)mc.getProperty(HTTPConstants.MC_HTTP_SERVLETREQUEST);
19 matches
Mail list logo
