[
http://issues.apache.org/jira/browse/AXIS-1916?page=comments#action_63249 ]
Tom Jordahl commented on AXIS-1916:
---
Fair enough. This wont make 1.2. But we would welcome any patches you might
want to contribute to add this functionality.
> anyAttr
[ http://issues.apache.org/jira/browse/AXIS-986?page=comments#action_63252
]
Tim K commented on AXIS-986:
Any solutions for this problem in the recent Axis 1.2RC3 builds? Thanks.
> Can't share sessions between different services ??
> --
Venkat Reddy wrote:
Oh, boy! this is not to suggest huge changes, as jaya said :-) You
guys already did enourmous work in designing this stuff. I'm just
trying to see if some api changes would make more sense.
Currently OMElement is doing most of tree manipulation and element
information management
Hi folks!
This is an automatic reminder that the weekly Axis2 developer chat
will be occurring tomorrow, April 20, at:
7PM PST, 10PM EST, 3AM GMT, 9AM (next day) SLT, 2PM (next day) AEST
The chat takes place on the freenode IRC network, (use server
irc.freenode.net), on channel #apache-axis, and
Hi all,
I have a question regarding beanMapping and whether what I have found is
a bug or expected behaviour.
I have two classes, both with get/set methods.
They are called A and B. B is a subclass of A.
I have two services, S1 and S2.
S1 contains: "public A getA();"
S2 contains: "public A[] get
Hm. Look at HTTP sessions: they are typically related to a server, not a
particular URL. I can log in to a site, and it can remember my name, my
shopping cart, etc, across a whole slew of different URLs. I think it's the
same with Web Services.
Of course, one can design this any way one want
[
http://issues.apache.org/jira/browse/AXIS-1930?page=comments#action_63150 ]
Mike Moran commented on AXIS-1930:
--
FYI: I tried the typemapping=1.3 switch with the example code I submitted, and
it fixes the bug.
Should this bug be turned into another
Hi there!
I'm writing a small TestClient to do jaxrpc style invocation of a webservice.
I'm interested in setting a property
(SOAPMessage.CHARACTER_SET_ENCODING) to a different value than the
default. But call.setProperty() did not allow me to set this property
(it's of type javax.xml.soap.charact
Hi All,
+1 for coupling the storage mechanism with
engine. So this is inline with the storage
mechanism proposed by us (Chamikara, Saminda and Me). That is
getEngineContext().getStorage() will return an
object of type Storage as mentioned in the server.xml.
There can be many imple
Oh, boy! this is not to suggest huge changes, as jaya said :-) You
guys already did enourmous work in designing this stuff. I'm just
trying to see if some api changes would make more sense.
Currently OMElement is doing most of tree manipulation and element
information management (attributes, names
10 matches
Mail list logo