Hi all:
The RC2 release of Axis 1.2 (probably the last before 1.2 (finally) goes
final) is now available at:
http://www.apache.org/dist/ws/axis/1_2RC2/
This version includes:
* Performance enhancements over RC1
* Better doc/lit type mapping support
* JAX-RPC compatibility switch for WSDL2Java
Greetings!
If you point a browser at:
http://www.apache.org/dyn/closer.cgi/ws/axis/1_2RC1/
you will find the binary and source distributions of Axis 1.2 Release
Candidate 1. There are still a few issues (in particular documentation)
that need cleaning up before the final release, but they shou
Hi Toshi.
>It seems that you set not '1.2beta2' but '1.2beta' as the
> axisVersion when you built the released package. IMHO, it
> might have a confusion on checking the active version of Axis
> with 'java org.apache.axis.Version'.
>
> Should we release an updated version very soon ?
W
Hi Riken:
I'm sorry, just to be clear, your problem is that you want to completely
turn off the query string handling, not customize it, right?
--Glen
- Original Message -
From: "Riken Shah" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 13, 2004 9:00 AM
Subject: RE: ho
Hi y'all:
The Axis team would like to announce that Axis 1.2 beta 2 has been released.
This version has passed both the JAX-RPC 1.1 and the SAAJ 1.2 TCKs, and is
just about ready to ship. There are a few other bugs we're considering
fixing, and we do expect some further doc updates in the next w
Hi Tony:
> I am calling it during an active invocation on the server side (not sure
> how you would call it outside of an active invocation there?). I
> basically have a method in my service like this:
>
> public String getFile( String ) {
> // NullPointerException thrown here because
> AxisE
Hi Tony:
> So, I am back to my original question. Why does
> AxisEngine.getCurrentMessageContext() return null?
It returns null if there isn't a current MessageContext.
When are you calling it? If you're calling it outside the context of an
active invocation, you won't get anything because the
+1, this override works too. Of course, "client-config.wsdd" is the default
value for that property, and will just look in the current directory - if
you want it to look somewhere in particular, use the full pathname.
--Glen
> Try something like that on your command line
>
> java -Daxis.ClientCo
Hi Richard!
> I'm having trouble getting AXIS to notice that I have a
> client-config.wsdd on the classpath that specifies a number of client
> side handlers. The file's location is alleady declared on the classpath
> and it doesn't work - is there anything else that I need to do? Is there
> a bet
Greetings, Axis community:
After a bunch more bug fixing, the Axis 1.2 beta release is finally ready to
go.
You'll find it at http://www.apache.org/dist/ws/axis/1_2beta/ - the versions
on the mirrors are incomplete ones from yesterday, so until they update
(dates on the files should be 31-Mar-200
Hi all!
There is an alpha release of Axis 1.2 at
http://www.apache.org/dist/ws/axis/1_2alpha/
Please grab it if you get a chance and test away. We'll be fixing more bugs
over the next couple of weeks, and the docs are in serious need of editing
as well. Expect a beta release sometime in mid-lat
+1! :)
A reminder - as dims noted a while ago, we should be using the #apache-axis
channel on irc.freenode.net for realtime conversation. I'm heading into my
office in a little while and once I'm there I'll be logged on to IRC the
rest of the day. If you're working on something and have question
Hi Susantha!
One of the important parts of WSDL generation on-the-fly is that the
deployed Handlers for a particular service can participate in generating the
WSDL document. So for instance, if you have WS-Security handlers present on
your global chain, they can add appropriate policy statements
I've modified the Wiki pages to account for a) the need for a general
extensibility architecture before we start having too many extensions, and
b) the fact that there are currently two WS-RM prototypes over Axis
(probably three, counting Dug's! But we won't see that one :)).
--Glen
- Origin
Hi Dimuthu, all:
> > Does anybody know if Axis performs 'Remote DTD/Schema referencing' ?
> > Does it fetch all the XML schemas/DTD posted in a
> particular HTTP soap
> > request message?
> >
> No axis doesn't support romote XML schemas/DTD referecing
> yet. But if you
> want reference a schema
Hi Davor, Gary:
Older versions of Axis supported the interim SOAP 1.2 namespace, but we've since moved
to supporting just the Rec version. There are two ways I can see to solve your
problem, Davor - 1) go back to an earlier version of Axis (you can track the changes
to org.apache.axis.Constant
Hi Cory:
WSDL please? :)
--G
> -Original Message-
> From: Cory Wilkerson [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 13, 2003 4:28 PM
> To: [EMAIL PROTECTED]
> Subject: nightly drops generating bad responses?
>
>
> I've noticed that in the latest nightly drops -- the response
Hi all:
The Apache Axis team is pleased to announce that version 1.1 of the Axis SOAP toolkit
is now available for download at:
http://ws.apache.org/axis/dist/1_1
The 1.1 release includes many improvements from 1.0, including:
* Better support for doc/literal WSDLs, more schema types,
Hi Chris:
> I am attempting to process my first WSDL w/ Axis.
> Unfortunately one of my
> types is defined as TypeDesc, and thus becomes getTypeDesc(),
> etc in the
> generated Bean. This directly conflicts with the
> getTypeDesc(), etc that
> Axis places into the files on it's own. (BTW: perh
Hi Celia!
I'd try reposting, since this mail got through OK.
--Glen
> -Original Message-
> From: Celia Berry [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 05, 2003 10:55 AM
> To: [EMAIL PROTECTED]
> Subject: repost?
>
>
> Greetings,
> I am new to axis-user. Yesterday I posted two s
(note to self - read all the mail before responding. :) Thanks Sameer!)
> -Original Message-
> From: Sameer Bombatkar [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 04, 2003 3:16 AM
> To: [EMAIL PROTECTED]
> Subject: Re: returning an array of javabeans
>
>
> Standard beanmapping en
SOAP-encoded arrays are automatically mapped, so you should be fine with just the bean
class.
--Glen
> -Original Message-
> From: Joel Realubit [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 04, 2003 3:10 AM
> To: [EMAIL PROTECTED]
> Subject: returning an array of javabeans
>
>
>
Hi folks:
> I dont think there is any 'built-in' way to call the web
> service from a
> browser as there is in the GLUE product.
We do have a simple way to call RPC services via an HTTP GET, which works like this:
http://host:8080/axis/services/MyService?method=getTemp&zip=02474
i.e. use the m
Hi Reto:
I just added a test in test.utils.TestXMLUtils which confirms that xml:lang is getting
parsed correctly by our deserialization system, so I think we shouldn't be throwing
this error. This test (and I believe your example) works fine under Xerces, but I'll
bet it fails for you with cr
Hi folks!
You can now pick up Axis 1.1 (release candidate 2) at
http://ws.apache.org/axis/dist/1_1rc2/
This release is primarily for bug fixes, of which there were quite a few. Please take
a look, run tests, let us know what you think, etc.
We hope to release 1.1 final in a few weeks.
Enjoy
Hi Harry!
Could you explain what you mean in a little more detail? I'm not sure what you're
asking here.
--Glen
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 20, 2003 11:52 AM
> To: [EMAIL PROTECTED]
> Subject: Files Generated fro
Hi all:
The Axis team would like to announce that the 1.1 release candidate 1 version of Axis
has been posted to http://ws.apache.org/axis/dist/1_1RC1/
This release is primarily for bug fixes. Some highlights:
- java.sql.Date works now
- 404 errors correctly returned on bad *.jws URLs
- doubl
I don't think WSDL prohibits it. You'd get something
like:
...
...
Most WSDLs use a single part for doc/lit services, and indeed Axis
doesn't deal with multiple parts like this very well.
--Glen
-Original Message-From: Wei Chen
[mailto:[EMAIL PROTECTED]]Sent: Tuesday
What do your types/parts look like? You can't have multiple definitions for the same
element in schema, so I'm not quite sure how you'd express what you're talking about
(i.e. one method which takes the "old" version and another which takes the "new").
--Glen
> -Original Message-
> Fr
(BIt appears there are hard coded values for this speckled in various places throughout
(Bthe source, and the default seems to be 16K
(B(ManagedMemoryDataSource.MAX_MEMORY_DISK_CACHED). This definitely seems like
(Bsomething that should be configurable.
(B
(BIt would be quick and easy to
Hi Markus:
That's not strictly true. SOAP 1.1 does not prohibit GET requests from returning
SOAP, it simply says if you want to use the standard HTTP binding to *send* SOAP, you
must use POST. Several packages (most notably .NET) support GET-style invocation with
SOAP 1.1 returns.
SOAP 1.2
ed wanted to replace or wrap
> BeanSerializer with one that had it's own logic for
> determining whether
> something was a Bean or another well-known (to the platform) type)?
>
>
> -Original Message-
> From: Glen Daniels [mailto:[EMAIL PROTECTED]]
> Sen
03, 2003 11:13 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Make beanMapping default
>
>
> Hi
>
> Would this work with Java2WSDL as well?
>
> Thanks
>
> Mark
>
> -Original Message-
> From: Glen Daniels [mailto:[EMAIL PROTECTED]]
Hi Joel!
There is some unfinished support in Axis for "autoTyping", which sounds like what you
want. AutoTyping, when switched on, will take any class which it doesn't find a
mapping for and use the Bean serializer/deserializer with an XML type QName of
"java:package.subpackage.classname".
T
Web site updated, release posted.
Have at.
Note that this is really just a beta - we do expect to do some more work in between
now and the official 1.1 release, which we expect sometime around the end of the year.
It's being released now to give people who want the fixes in the current source
Hi Sandeep, Ricky:
The stubs end up caching the HTTP information (i.e. the HTTPTransport object)
per-Service (i.e. org.apache.axis.client.Service). This means that if you use
the same Locator object to get stubs, they'll all end up sharing the same
session. If you instead new up a fresh Locator
Hi Rajal:
I'm not sure what you mean by your question, but here's a little info about handlers:
1) In general, you don't want to keep state in the Handler itself.
However, you can control things by selecting one of three "scopes"
for the handler in the WSDD - "per-request", "per-access", and
"s
You wouldn't, because that class has been removed from the package, as have all
references to it. Are you perhaps using old classes/code?
--Glen
> -Original Message-
> From: James Black [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 30, 2002 4:03 PM
> To: [EMAIL PROTECTED]
> Sub
Actually, Axis includes standalone HTTP
(org.apache.axis.transport.http.SimpleAxisServer) and TCP
(samples.transport.tcp.TCPListener) implementations, but they aren't advertised as
"enterprise-ready". They are, however, pretty easy to run or embed inside your
application.
After 1.0, I suspe
'm off here, but I'm just jumping into all this,
> and you sounded
> urgent in your ALL CAPS RFC. The current MessageContext-containing
> signature is the one I am planning on using (for
> flexibility), so I'd hate
> to see it go.
>
> --
> Dan Kam
Hi Mark!
tt-bytecode is no longer needed for Axis. We should update the docs, sorry for any
inconvenience.
--Glen
> -Original Message-
> From: Mark Hansen [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 23, 2002 4:09 PM
> To: [EMAIL PROTECTED]
> Subject: tt-bytecode.jar ???
>
>
OK, I have dispatch to multiple methods in message-style services working in my
sandbox. This has the added bonus of speeding up message-based services because we
now avoid introspection on every call - the initial introspection in ServiceDesc now
understands what type of message method (Vect
Just FYI, Axis has some SOAP 1.2 support already, and we're planning to be complete by
1.0.
--Glen
> -Original Message-
> From: doug [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 23, 2002 1:13 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Axis vs. Systinet WASP?
>
>
> yep - but if tha
Hi Richard!
Take a look at org.apache.axis.encoding.SerializationContextImpl. Sounds like exactly
what you're talking about.
I'm not sure I get your question, though - are you asking how to turn an XML String
into a DOM? It's called parsing. :)
--Glen
> -Original Message-
> From:
This is now fixed in current CVS.
The problem was that options which are "normalized" (i.e. turned from Strings a la
deploy.wsdd values into Objects, Booleans in particular) were being defaulted to
"true", and the code that does the normalization was formerly only run for the engine.
Now ser
Hi all you SOAP fans out there!
Apache Axis (http://xml.apache.org/axis) has just released our third beta, on our way
to a 1.0 release this summer.
Axis:
* Is a flexible, extensible Web Services framework for Java developers.
* Has an almost complete implementation of Sun's JAX-RPC and SAAJ s
JAX-RPC Handlers and Axis Handlers are different beasties, which is a bit of a shame,
but makes some sense too. There is no mechanism in JAX-RPC by which you actually
connect Handlers to your system on the server side, for one thing - the only thing it
specifies is how to programatically regi
Hi Christian!
Vectors (just like any other Collection class) should be serialized as SOAP arrays,
which .NET should have no trouble consuming Could you send your generated WSDL to
the list?
Thanks,
--Glen
> -Original Message-
> From: Christian Schmitz [mailto:[EMAIL PROTECTED]]
Hi Ed,
Caching resources like db connections is certainly possible in Axis, but we try
where possible to avoid transport level dependencies on things like
HTTP/servlets. There are several ways you can go about this:
1) Set your service to be "scope='application'", which will share a single
inst
Hi
Brenton!
So
you're saying that you observe the fault you posted below coming back across the
wire, and when that gets turned into an AxisFault you can't get at the
details? That sounds like a bug to me if that's the
case.
Regardless of whether or not Axis uses the details to constru
Hi
Scott:
Here's
my guess - try going into the server-config.wsdd in your axis WEB-INF directory
and taking a look at that. The problem is that your beanmapping is
apparently using a bad (or nonexistent) prefix for the type='' attribute.
For instance, this won't work:
but
this w
Could
you send along the WSDL?
-Original Message-From: Dennis Reil
[mailto:[EMAIL PROTECTED]]Sent: Friday, May 10, 2002 5:57
AMTo: AXIS-User-ListSubject: can't find deserializer
problem
I wrote a wsdl-document describing a service,
which uses schemas to describe
custo
Hi Vadim!
You can certainly include the AxisServlet in your own web application - we do this all
the time at Macromedia to "web-service enable" our webapps. The servlet context
(assuming that's how you share state) is available to your back-end service objects or
custom Handlers via the Mess
Hi Andrew!
When you set "scope=session" on a service, the JavaProvider will actually use the
Session object that is associated with the MessageContext to store the service object
(under the service's name - so you should actually be careful not to overwrite it if
you use the Session in your o
Hi Andrew!
Sorry I wasn't more precise. Yes, it's a transport-specific property that gets set by
the AxisServlet. In particular, it can be retrieved with:
((HttpServlet)msgContext.getProperty(HTTPConstants.MC_HTTP_SERVLET)).getServletContext();
In answer to your second question, you just hav
You bet.
> -Original Message-
> From: Andrew Vardeman [mailto:[EMAIL PROTECTED]]
> Sent: Monday, May 06, 2002 3:46 PM
> To: [EMAIL PROTECTED]
> Subject: RE: can you register a service to be notified when
> container is
> s hut down?
>
>
> Glen,
>
> thanks for the answer (and the func
JAX-RPC specs a ServiceLifecycle interface which contains init(Object context) and
destroy(). So you just have your service object implement ServiceLifecycle, and
init()/destroy() will be called appropriately.
I've just implemented this functionality in Axis for request, session, and applicat
This was recently fixed - try tonight's nightly, or grab the current CVS.
--Glen
> -Original Message-
> From: Bob Cotton [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 03, 2002 12:39 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Java2WSDL breaks for me beta1 -> beta2
>
>
>
> The change i
Hi Steve:
The provider question has already been answered, but I wanted to note that you don't
need to use your own Handler as a provider in order to access the MessageContext. You
can simply deploy a standard RPC or Message service and call
"MessageContext.getCurrentContext()" from your ser
array or Collection class on the client side
(in this case an ArrayList).
Just FYI.
--Glen
> -Original Message-
> From: Glen Daniels [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 25, 2002 8:52 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Using the A
Hi Jonathan!
Chris makes some good points, although I'm not sure I'd classify the docs as
"excellent" yet. :)
To address the particular scenario you mention (returning an ArrayList), you really
don't have to do anything complicated...
On the server, just deploy a service which returns an Arr
Performance is an area we've been neglecting for the past few releases, and one which
we plan to address after beta-2. Right now we're doing way too much work during
deserialization (recording SAX events, etc) in situations where we don't need to be,
so I don't doubt that the RI is much faste
We can add an option to the local transport to switch off
serialization/deserialization if you want to use it for high-speed non-testing
purposes after beta-2.
--Glen
> -Original Message-
> From: Mukund Balasubramanian [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 23, 2002 4:01 PM
ding you the code so that
> you can point
> out anything that u see I am doing wrong. Hope this helps you solve my
> problem.
>
> This is great help and I surely appreciate it.
> Thanks
>
> Vaishakhi
>
> - Original Message -
> From: "Glen Daniels" <[EM
Is anyone currently using the method signatures with the MessageContext argument on
document-style services with the MsgProvider? e.g.:
public void myMethod(MessageContext context, Document doc)
I am planning to remove this functionality over the weekend. Please switch to using
MessageConte
Hi Andrew!
Sessions are easy if you're using Axis on both sides - if not you have to make sure
that your non-Axis client can send the right cookies/SOAP headers to use them. Then
you set your service to be session-enabled:
...
The other issue, asynchronous callbacks, is more interest
Actually, the call.setReturnClass() method removes the need for the convert() (that's
the whole point of that method).
Vaishakhi, are you sure your service is actually returning a SOAP array? Also, you
need to specify both the return type and the return class, I believe.
--Glen
> -Origi
http://marc.theaimsgroup.com/?l=axis-user&m=101917211723166&w=2
:)
-Original Message-From: Vaishakhi Ajmera
[mailto:[EMAIL PROTECTED]]Sent: Friday, April 19, 2002
2:01 PMTo: ^BoyInterrupted^;
[EMAIL PROTECTED]Subject: Re: How do I invoke a method that
takes no parameters
The default for this is to search your classpath for
org/apache/axis/client/client-config.wsdd. Hence, if you just put the file there in
your jar, and your jar is on the classpath before axis.jar, yours will be picked up
without needing to set the system property. Either way works fine.
--G
Yup. :) I'll be making some improvements to this doc over the next few days, this is
on the list. Thanks!
--Glen
> -Original Message-
> From: CM [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 18, 2002 4:13 PM
> To: [EMAIL PROTECTED]
> Subject: Minor correction in Axis User's Guid
Or even call.invoke(null)
--Glen
> -Original Message-
> From: Vidyanand Murunikkara [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 18, 2002 6:48 PM
> To: [EMAIL PROTECTED]
> Subject: RE: How do I invoke a method that takes no parameters ?
>
>
> I guess all u have to do is
>
Hi Torsten!
Here's the quick answer to your question. The JavaProvider class does the
instantiation of the service object, in the getServiceObject() method, which calls
getNewServiceObject() if necessary. The provider is the Handler at the very "back
end" of the chain of invocation, and its
Hi Vidula!
You'd get this error if your server side crashed, for instance. It just means that
the connection was dropped and the client doesn't know why. Can't really tell you
much more than that - were you running against an Axis server?
--Glen
> -Original Message-
> From: Vidula
Hi
Deepthi!
Yes,
that's the right syntax. If this doesn't work for you, please let us
know and we'll resolve it.
--Glen
-Original Message-From: DEEPTHI PRABHAKAR
[mailto:[EMAIL PROTECTED]]Sent: Thursday, April 18, 2002 5:40
AMTo: [EMAIL PROTECTED]Subject: Glen, I think
thing like
public Collection
echoList(Collection c) { return c; }
and then run WSDL2Java on the resulting wsdl file, I assume
that I will get
public Object[]
echoList(Object[] c) { return c; }
Is this assumption valid?
Naresh
-Original Message----- From: Glen
Danie
(hey Russell, could you add this to the FAQ while you're working on it? Is this too
long?)
Q: How do I use Java Collection classes and Arrays with Axis?
A: Axis automatically understands how to serialize and deserialize arrays and Java
Collections "out of the box". All of these things wil
Hi
Jonathan:
You
can use the AdminClient as a class, rather than running its
main():
AdminClient client = new AdminClient();
String
results = client.process(new String [] { "list" });
Does
that work for you?
--Glen
-Original Message-From: Jonathan
[mailto:[EMAIL PROTEC
Hi
Mark, Jonathan:
Mark
is mostly right, except that you do not have to restart the server to get access
to the new service. It is both added to the current in-memory engine
configuration and the persistent server-config.wsdd file.
You
can see a list by running "java org.apache.axis.cl
Axis has an XML<->Java databinding framework which is still evolving and
doesn't really support all that much yet. Essentially we have metadata
associated with your Java class which tells the runtime how to map fields to
and from XML elements and attributes. Eventually I'd like to see us get to
Hi Paul!
In cases like this, a tcpmon trace almost always
pinpoints the cause of the trouble. It looks like you're not sending valid
XML for some reason. If you can't figure it out yourself from looking at a
trace, please forward it along to the list.
--Glen
- Original Message --
Hi June!
1. All of our validation is currently in the
deserializers. The schema information (i.e. what XML to expect when)
exists in the form of a TypeDesc (org.apache.axis.description.TypeDesc) for
JavaBeans, which is the common case. This will match up
elements/attributes to the approp
Hi Hozefa:
I wouldn't rely on the MessageContext being set in the constructor for your
object, although it is interesting that we apparently make two service
objects - I'll look into that to see what's up there.
The MessageContext represents information about a PARTICULAR
request/invocation, and
Go Ramon!
Just a note from the Axis team here - we really REALLY appreciate it when all
of you who are using the toolkit take the time to help each other out on this
list.
We realize that the Axis docs need improving, and we have a desperate need for
a FAQ, both of which we'll try to deal with,
Hi Bryan!
Axis has a "local" transport which basically does what you
want (i.e. calls an in-proc server) but it currently enforces
serialization/deserialization both ways across the connection. This is
because the transport is primarily used for testing. It would be very easy
to turn th
Literal encoding means "no encodingStyle", so
setting this to either null or "" will get you literal
serialization.
Note that you need to make sure to use the ""
namespace on any custom TypeMappings you deploy for your particular application
as well!
--G
- Original Message -
+1
We're definitely going to put some time into this in the not-too-distant
future.
--Glen
- Original Message -
From: "Adam Greene" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 05, 2002 1:42 PM
Subject: Re: C++ and Axis
> I'm not sure. Because like every Web Servic
Hi Jamie!
You shouldn't need to write custom serializers for
this, the ArraySerializer will do this for you. I think we have an example
of this in our tests somewhere, but I'm not sure just where.
--Glen
- Original Message -
From:
Jamie Powell
To: '[EMAIL PROTECTED]
Title: RE: deployment descriptor
Both
of which are, alas, way out of date. Sigh. This is on my list, but
keeps getting bumped due to higher-priority stuff.
--G
-Original Message-From: Volkmann, Mark
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, April 02, 2002
10:36 AMTo: '[EMAI
Hola, Stan!
Comments inline:
> The good news is that it's very easy to develop stateful web services
> (hooray!). But...
> 1. If you write your client 'by hand' you must include this
> statement in
> Client.java:
> call.setMaintainSession(true);
> 2. If you generate a wsdl file and
Title: repost of WSDL2Java question
Reposting this here too.
-Original Message-From: Glen Daniels Sent:
Monday, April 01, 2002 1:54 PMTo:
'[EMAIL PROTECTED]'Subject: RE: repost of WSDL2Java
question
Hi
Mark, sorry for the delay in getting back to you!
The
Service.jav
Yup. service.getOption("paramName")
You
can get the current Service from the MessageContext with
msgContext.getService(), either in a Handler or in your backend service
method. If you want the MessageContext from your service method, call
MessageContext.getCurrentContext().
--Glen
- that worked. Is having MessageContext as
> > the first
> > argument of a service method a thing of the past?
> >
> > -Ken
> >
> > - Original Message -
> > From: "Glen Daniels" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]&g
Hi Richard!
Doing it the way we do it now makes for fast and easy serialization. We simply
serialize on the fly, and each time we come to a non-primitive we lay down an HREF,
knowing that we'll write out the actual value at the end.
Doing it the way you want to do it is much more complicated
Hi Ken:
Try MessageContext.getCurrentContext().
--Glen
> -Original Message-
> From: Ken Weiner [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 25, 2002 4:49 PM
> To: [EMAIL PROTECTED]
> Subject: MessageContext argument in service method
>
>
> Should I be able to include org.apache.a
Hi Lene:
Axis knows natively how to serialize Lists, so Vectors, ArrayLists, etc. will all
serialize to SOAP arrays right out of the box. In looking at the Collection class, I
see no reason we couldn't serialize an arbitrary Collection. I had been under the
impression that Collection was al
Hi Vaidya!
Well, the MapSerializer is responsible for writing out the declaration,
and it expects to be writing the "xml-soap:Map" type, since that's the interoperable
name for the Map encoding which a bunch of SOAP toolkits support. This type is
automatically mapped in Axis.
So if you jus
Hey Tom, Till - I just implemented this in my sandbox. Will check it in as soon as
I'm at a good stopping place with the rest of the changes I'm making. It looks like
this in the WSDD:
c:/echo.wsdl
...
If not specified, we build one dynamically. If it is, we return the contents of th
Hi Martina!
Here's the deal (maybe we can save Rich some time :)). Axis takes all Java "linear
collection" classes (i.e. anything that implements List) and serializes them as SOAP
Arrays, to maximize interoperability with other toolkits. When we receive a SOAP
Array and want to deserialize
I'm glad this has been resolved for you, but can the Axis team make a note to look
into this and try to do better than a NullPointerException? It would be nice if we
could be a little more informative as to the actual problem.
--Glen
> -Original Message-
> From: Stan Jordan [mailto:[
This will be fixed Real Soon Now. Probably for beta-2.
--G
> -Original Message-
> From: Russell Butek [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 20, 2002 1:51 PM
> To: [EMAIL PROTECTED]
> Subject: Re: real AXIS beta 1 problem (samples/message)
>
>
> You may be the first one
1 - 100 of 130 matches
Mail list logo
