Anyone out there who uses Axis on a production system and has disabled
these features?
Thanks.
Tim
Tim K. (Gmane) wrote:
Hello,
How can I turn off these features for an Axis production deployment:
1) Disable the generation of WSDL when one goes to
http://server:port/app/ws/ServiceName?wsdl
2
similar to that by using custom Axis
handlers and web app filters.
Mike
Tim K. (Gmane) wrote:
Anyone out there who uses Axis on a production system and has disabled
these features?
Thanks.
Tim
Tim K. (Gmane) wrote:
Hello,
How can I turn off these features for an Axis production deployment:
1
I mapped the Axis servlet to a custom URL (e.g. /app/ws) rather than the
default /axis/services/ or whatever it is.
Now if I simply go to: http://server:port/app/ws I see a bunch of links
to the (wsdl) files for each service, but the link is wrong, it is of
the form /app/services/Foo?wsdl
Hello,
How can I turn off these features for an Axis production deployment:
1) Disable the generation of WSDL when one goes to
http://server:port/app/ws/ServiceName?wsdl
2) Turn off listing the available services and their methods by going to
http://server:port/app/ws/
3) Turn off all Admin
The scope (session, application, request) on the server side tells Axis
how many instance of the server implementation classes to create, it
doesn't have much to do with the session on the client side. The client
is not aware of the session scope on the server side. So you can for
example use
On the generated FooServiceLocator call setMaintainSession(true)
Or you can cast the generated Stub to javax.xml.rpc.Stub and then call
stub._setProperty(Stub.SESSION_MAINTAIN_PROPERTY, Boolean.TRUE) which is
the JAX-RPC way.
Both work in Axis, but the first one is Axis specific while the
= ats.getAxisTest(URL);
// This is the JAX-RPC way of setting it at the Stub level,
// no need to do it if you called ats.setMaintainSession(true)
// above
((javax.xml.rpc.Stub) stub)._setProperty(Stub.SESSION_MAINTAIN_PROPERTY,
Boolean.TRUE).
Tim
Tim K
- Original Message - From: Tim K. (Gmane) [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 20, 2005 1:13 PM
Subject: Re: Maintain session when using stubs generated by WSDL2Java
On the generated FooServiceLocator call setMaintainSession(true)
Or you can cast the generated Stub
Axis has a built-in minimal HTTP server from what I read, but I never
used it so I don't know the details. Look into it a little bit and see
if it will work for you.
Tim
Douglas Kunzman wrote:
Hi,
I am looking for a java based web services server that does not need
tomcat or an http server to
Can you please file a bug for this at:
http://issues.apache.org/jira/
for project Axis
Thanks.
Tim
Vy Ho wrote:
That does it. The memory no longer go up. The way I do it is inside
the generated stub, I wrap the call with a try/catch/finally, and in
that, I put your code below. I am not sure
I may not understand exactly what you are trying to do, but did you
notice the -c option to wsdl2java where you can specify a class to use
instead of the BindingImpl?
Sorry if I am off topic with my answer.
Tim
Brian Davis wrote:
I wrote an ant task to do this, you can use it if you like. It
Be aware that getRemoteAddr() may not be the address of the client
sending the request but rather a proxy/caching server in between, load
balancer, etc. As long as you are OK with it you can get the request
like this:
MessageContext context = MessageContext.getCurrentContext();
http://issues.apache.org/jira/
I'm not sure though what the difference between Axis and Axis2 projects
is. I think Axis is where you want to enter your bug.
Tim
Michael Oliver wrote:
How do I go about entering a bugzilla bug for Axis
Michael Oliver
CTO
Alarius Systems LLC
3325 N. Nellis Blvd,
Hello Axis Developers Users,
I think I've discovered an Axis 1.2RC2 bug.
Some servers use cookies to do load balancing, so in addition to the
JSESSIONID session tracking cookie the load balancer may insert its own
cookie in the HTTP response.
There are 2 cases here:
1) The HTTP response will
) still looks like a bug though.
Tim
Tim K. (Gmane) wrote:
Hello Axis Developers Users,
I think I've discovered an Axis 1.2RC2 bug.
Some servers use cookies to do load balancing, so in addition to the
JSESSIONID session tracking cookie the load balancer may insert its own
cookie in the HTTP
(if they are session
cookies, not persistent cookies then they are expired when the client
process exits -- in memory cookies).
Where are the cookies stored between requests? In the Service, Stub,
Call or HTTPTransport?
Tim
Tim K. (Gmane) wrote:
Correction: case 2) below is not valid, apparently one cannot set
Could someone who has more experience with the Axis client side clarify
how it works in a multi-threaded environment?
E.g. if I create a Service instane on the client and from that get a
Stub instance, is it safe for mutliple threads to make calls on the Stub
at the same time?
If not, where
Hello,
I do NOT have log4j in the CLASSPATH because of some conflicts and I do
not want to use log4j or any other logging frameworks.
I just want to:
1) Make Axis write to the servlet engine's log file which gets rotated
and it also captures the messages from my web service server side
I like to read this list as a newsgroup (NNTP) via gmane.org (or you can
read it via a browser thru gmane's web site)
It works quite well, I don't get bombarded with emails all day long, I
read the newsgroup only when I feel like it (sort of like a digest if
you read the newsgroup once a day):
Yeah, it would be nice to keep them separate, I've posted a while ago on
the same topic. My concern is that I am not controlling what WS toolkit
clients will use on the client side and these modules have the concept
of a common session for all of them to work together, so I am not sure
whether
Hi,
Let's assume that I already have a few interfaces and their
implementation that follow all the web services rules and they are
suitable of being exposed via Axis the way they are.
Is it possible for Axis to combine all these interfaces/classes into one
web service automatically or do I
Which in effect does the same thing, it creates an interface for you
with only those methods, right?
Personally I prefer defining the interface myself rather than doing it
via command line options, you get more compile time checking and catch
mistakes early than deal with sometimes obscure
John Walker wrote:
Is it possible to get and set cookies on the HTTP transport from the
*client* side of Axis?
I tried using the MessageContext to get the HttpRequest object, and
then set cookies there, but it seemed that when doing this from the
AXIS client side, when the HTTP message got to
, if
maintainSession is set to true. Provided the same host is called each
time, this should work. Simple Axis handlers can be written to do this.
Tony
*Tim K. (Gmane)* wrote on 01/12/2004 16:45:06:
John Walker wrote:
Is it possible to get and set cookies on the HTTP transport from the
*client* side of Axis
Vy Ho wrote:
I wonder if you declare an interface for this service, then use it to
generate wsdl.
This shields you from how you implement your service.
Right, that's the way to do it, just create an interface for only the
methods you want exposed. The class can have a lot more stuff in it that
Sheptunov, Bogdan wrote:
Could you please elaborate a little more on that? In what way exactly? Have my class implement BeanInfo interface and describe the properties I'd like to see returned in getPropertyDescriptors() method?
Read the Java Beans specification, in particular the sections that
I still see this next error, but the example runs now,
and it's no longer complaining about not being able to
find classes in the wsdl4.jar packages.
- Unable to find required classes
(javax.activation.DataHandler and
javax.mail.internet.MimeMultipart). Attachment support
is disabled.
You need
If anyone else has an example on how to get the Long stuff to
work end-to-end and to interoperate with .NET I would love to
see it (it has to be RPC not doc/lit) as it would be nice to
make use of the nillable property ...
Thanks.
Tim
The long type in .NET is not nullable, so trying to send
I am assuming that you could pass session tracking info in the SOAP Header..
Using SOAP headers may not be an option for me as I may have to share
the same session between the Axis servlet and another plain HTTP servlet
I have running for various reasons.
Is there a way in Axis to get to the
Is it possible to get and set cookies on the HTTP transport from the
*client* side of Axis?
If so, how? Are there any examples, please?
Thank you.
Tim
David Song wrote:
Hi all,
I am getting the following error from Java2WSDL. It was working before,
I just changed some method signatures. Many thanks for the help!
-David
- The class org.apache.axis.MessageContext does not contain a default
constructor, which is a requirement for a bean class.
Hi,
Here's the dilemma that I am facing and I am looking for your
experiences and recommendation.
I need to expose a lot of methods (over 200 with over 20 custom types).
The business logic on the server is implemented, very modular, such as
SessionModule, FileModule, UserModule, etc.
There
[EMAIL PROTECTED] wrote:
Tim,
I've just come across the fact that the BeanSerializer does make use of
a BeanInfo class. Have you tried using a BeanInfo class with your bean?
I don't know if Java2WSDL makes use of it, but the bean serializer seems
to, at run time. Give it a go and let us know.
I have a simple test method:
Long foo(Long bar)
Java2WSDL maps the Long to xsd:long and the client stub contains the
method as:
long foo(long bar)
How does the WSDL look like ? The parameter and return value should
have a nillable='true' attribute, otherwise I guess it's a bug in
the
Viktor Vojnovski wrote:
Tim Gmane se proiznese na 25.11.2004 17:42:
Please post the Java class you are trying to expose. I realize it may
contain proprietary information, so you should try writing a simple
example that reproduces the problem or posting snippets from the bean
that has the CPF
35 matches
Mail list logo