. Any ideas or is it a AXIS Bug ?
Thanks Regards,
Kumar.
)
[java] at org.apache.axis.client.Call.invoke(Call.java:1758)
[java] at
irsc.bluestar.DCPlanListWSBindingStub.getDCPlanList(DCPlanListWSBindingStub.java:180)
I am not sure what this error means. Any ideas or is it a AXIS Bug ?
Thanks Regards,
Kumar.
I added a proper testcase to the bug. Please take a look. Thanks!
Bill Keese wrote:
I found the bug:
http://issues.apache.org/jira/browse/AXIS-1547
The bug contains a testcase, more or less; do you want something more
than that?
Thanks,
Bill
Davanum Srinivas wrote:
not i
I am looking at bug http://issues.apache.org/jira/browse/AXIS-986.
Someone submitted the patch but looks ike this was not added to CVS. This bug
surely is a huge bug for those who are using Contaienr based session management
on server side. I am really surprised why this patch was not added
Praveen,
Would you be able to port this to latest Axis cvs? i need a diff -u
against latest CVS.
thanks,
dims
On Tue, 25 Jan 2005 14:30:27 -0500, Praveen Peddi
[EMAIL PROTECTED] wrote:
I am looking at bug http://issues.apache.org/jira/browse/AXIS-986. Someone
submitted the patch but looks
I don't mind doing that but I have to get the source, build, change the
code, test etc. We are trying another work around that was suggested at
http://article.gmane.org/gmane.text.xml.axis.user/16296. If this doesn't
work, I will be happy to send you the patch for bug 986.
Thanks
Praveen
/gmane.text.xml.axis.user/16296. If this doesn't
work, I will be happy to send you the patch for bug 986.
Thanks
Praveen
- Original Message -
From: Davanum Srinivas [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 25, 2005 2:50 PM
Subject: Re: Rolling Fix for Bug 986
for the server to return, so there's a bug on the server here
too. It shows that the server does not handle error well with regard to
performance.
How do I go about entering a bugzilla bug for Axis
Michael Oliver
CTO
Alarius Systems LLC
3325 N. Nellis Blvd, #1
Las Vegas, NV 89115
Phone:(702)643-7425
Fax:(520)844-1036
*Note new email changed from [EMAIL PROTECTED]
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
:
Digging deeper into the code and trying to patch it to fix the bug I
discovered another issue that needs to be addressed.
The particular server that I am using doesn't send the load balancing
cookie on all the responses, it refreshes it every few responses (I am
not sure how it decides
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
) 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
Digging deeper into the code and trying to patch it to fix the bug I
discovered another issue that needs to be addressed.
The particular server that I am using doesn't send the load balancing
cookie on all the responses, it refreshes it every few responses (I am
not sure how it decides
Hello!
I'm using wsdl2java to generate source code from a wsdl, and I don't
known why in the source code and in the deploy file, with qname appears
something as ns:SignResponse when I understand that I shoud be
ns:SignRequest. Could you tell me if there is a bug or I'm doing
something wrong
[mailto:[EMAIL PROTECTED]
Sent: Dienstag, 4. Januar 2005 11:30
To: [EMAIL PROTECTED]
Subject: Bug in WSDL2JAVA?
Hello!
I'm using wsdl2java to generate source code from a wsdl,
and I don't
known why in the source code and in the deploy file, with
qname appears
something
PROTECTED]
Subject: Bug in WSDL2JAVA?
Hello!
I'm using wsdl2java to generate source code from a wsdl,
and I don't
known why in the source code and in the deploy file, with
qname appears
something as ns:SignResponse when I understand that I shoud be
ns:SignRequest. Could you tell me
PROTECTED]
Subject: Bug in WSDL2JAVA?
Hello!
I'm using wsdl2java to generate source code from a wsdl,
and I don't
known why in the source code and in the deploy file, with
qname appears
something as ns:SignResponse when I understand that I shoud be
ns:SignRequest. Could you tell me
oid acquireTask(String taskId) throws RemoteException,
and I am using a java2wsdl (with wrapped option) and then a wsdl2java to generate the stubs. I want to avoid creation of artifacts like _acquireTask.java etc.
Thanks for any pointers,
Shantanu Sen
-Original Message-
From: [EMAI
All,
Please see the stacktrace below. Is there something that I am doing
to cause this, or is this a bug that I'm observing?
Thanks in advance,
-John Walker
Hello,
I tested with 100MB error comes from java side. I hope this log helps
Btw, I tried to set timeout to 5 min, but it's
Lines 143 and 144 of org.apache.axis.encoding.ser.ArraySerializer need
to be reversed. When the componentType of the array is an interface
rather than a class, the first call to searchCls.getSuperclass()
returns null (interfaces have no superclass), which causes an NPE in
the bowels of axis.
This
snippet of code from org.apache.axis.providers.java.RPCProvider looks like a bug
to me (line 156):
//
This may have changed, so get it again...
//
FIXME (there should be a cleaner way to do
this)
operation =
msgContext.getOperation();
if
(operation == null)
{ QName
qname
Hello all. I have a schema with the below structure. In Axis 1.2 RC1
no exception was thrown for the below structure. I traced Axis code
to locate the exception being thrown from the
org.apache.axis.encoding.ser.BeanSerializer class. The
resource.properties message used is
I have an interface:
public interface Test{
public String [] getList();
}
when using java2wsdl with document and literal style, the return type of
getList is String, not String[] or ArrayOfString, or anything like that.
This is Axis 1.2 RC2
More on this, when using Java2Wsdl with document and literal style, and
also using it with rpc encoding on a same interface, any method that
returns an array of a bean class will have different signatures (between
doc/lit style and rpc/enc style).
For example:
public interface Test{
public
Thanks to Roy Willy Haug, he sent me the following message which states
that he have had the same problem and found a way around it. I am not
sure the way he described is the end solution to the problem or not, but
it clearly indicates that this is indeed a bug, and should be an easy fix
When fixing this bug, please also note that why the client freezes up
when doing this (please check the first post). This could be a
potential bug if the api is changed to:
DataHandler echo(DataHandler data);
And the client call the server twice in succession. The 2nd time, the
client would
Since this is a very serious problem and I haven't got any reponse,
please someone in the know throw me some bones on what's going on with
this. Is this being addressed? No body care? I need to file a bug
report for it to go anywhere? Already fixed in the nightly?
Thanks,
vh.
V D wrote:
I
, when I call getData() again (after the first call), the client
waits for a long time.
Using a TcpMonitor, I was shocked to find out that the post from client
to the server also include most of the data in the file. Is this a
known bug?
It's seems a definitely a big bug in Axis, not my code
[mailto:[EMAIL PROTECTED]
Sent: Friday, November 19, 2004 1:16 AM
To: [EMAIL PROTECTED]
Subject: Bug about array of beans in 1.2RC2 (wrapped/literal)
Hi,
We have a strange bug in axis 1.2RC2, dealing with array of beans.
There is a method whose signature is :
public ArrayBean echoArrayBean
Hi,
We have a strange bug in axis 1.2RC2, dealing with array of beans.
There is a method whose signature is :
public ArrayBean echoArrayBean(ArrayBean param);
ArrayBean is defined like this :
public class ArrayBean implements Serializable {
private String stringData;
private SimpleBean
: Bug about array of beans in 1.2RC2 (wrapped/literal)
Hi,
We have a strange bug in axis 1.2RC2, dealing with array of beans.
There is a method whose signature is :
public ArrayBean echoArrayBean(ArrayBean param);
ArrayBean is defined like this :
public class ArrayBean implements Serializable
It seems I found a bug in Axis-1_2RC1:
The class org.apache.axis.message.MessageElement does not implement the
interface org.w3c.dom.NodeList.
So, the method getElementsByTagName gives a ClassCastException:
public NodeList getElementsByTagName(String tagName) {
//use
Eduardo Issao Ito wrote:
It seems I found a bug in Axis-1_2RC1:
The class org.apache.axis.message.MessageElement does not implement the
interface org.w3c.dom.NodeList.
So, the method getElementsByTagName gives a ClassCastException:
public NodeList getElementsByTagName(String tagName
Well, you are rigth it implements NodeList, I've missed it...
But still a bug.
The workaround is to use getElementsByTagNameNS()...
--- Dan Ciarniello [EMAIL PROTECTED] escreveu:
Eduardo Issao Ito wrote:
It seems I found a bug in Axis-1_2RC1:
The class
, on the client:
StringArray ret = webservice.ping();
ret.getString() is null
I would rather expect my client to also receive a StringArray bearing a
String[0]
Is this a bug or a feature?
Cheers,
Silvano
STSM, Emerging e-business Industry Architecture
email: [EMAIL PROTECTED]
blog: http://webpages.charter.net/chrisfer/blog.html
phone: +1 508 377 9295
Anne Thomas Manes [EMAIL PROTECTED] wrote on 10/13/2004 05:52:25 AM:
Chris,
There's a bug in one of the Correct samples in WS-I BP 1.1
Yes, I just got that very same problem! I'm using axis-1_2RC1.
Any workarounds? (Well, besides resorting to using just one fault type,
of course 8-)
silvano
[EMAIL PROTECTED] wrote:
Anyone else observed that when you have code that throws multiple possible
faults, the generated stub assumes that
PROTECTED]
Subject: Re: wsdl2java fault bug ?
Yes, I just got that very same problem! I'm using axis-1_2RC1.
Any workarounds? (Well, besides resorting to using just one fault type,
of course 8-)
silvano
[EMAIL PROTECTED] wrote:
Anyone else observed that when you have code that throws multiple
You need to hand modify the wsdl file so that the qname for each fault is
different.
The java2wsdl util creates the same qname for each fault. This name is used to
lookup the fault from a map and hey presto only one id returned, generally the
last fault specified.
If you hand modify the wsdl
thanks for the tip Steve - looks like this isnt just me so ive made it a bug
report.
/tom
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, October 11, 2004 11:28 AM
To: [EMAIL PROTECTED]
Subject: Re: wsdl2java fault bug ?
You need to hand modify
Anyone else observed that when you have code that throws multiple possible
faults, the generated stub assumes that the fault is always the last
defined ?
in this case, if you throw SomeOtherFault and verify that the XML going
over the wire correctly reflects the fault, client side it assumes the
matthew.hawthorne [EMAIL PROTECTED] writes:
I'm not sure if this is it -- but ThreadLocals don't work inside of
app servers that use thread pooling.
that's news to me. care to clarify this?
perhaps you mean that for a series of requests coming as part of a
single session, the several
Joseph Dane wrote:
matthew.hawthorne [EMAIL PROTECTED] writes:
I'm not sure if this is it -- but ThreadLocals don't work inside of
app servers that use thread pooling.
that's news to me. care to clarify this?
perhaps you mean that for a series of requests coming as part of a
single session, the
Hello,
I have seen in apache buglist a bug regarding ThreadLocal
I am using threadLocal in one of the classes used by my webservice...(I
am
Using Hibernate in my webservice)
Can anyone tell me what that bug was about?
As a matter of fact my code that uses ThreadLocal does not work
Marco Mistroni wrote:
Hello, I have seen in apache buglist a bug regarding ThreadLocal
I am using threadLocal in one of the classes used by my webservice...(I
am Using Hibernate in my webservice)
Can anyone tell me what that bug was about?
As a matter of fact my code that uses ThreadLocal does
. September 2004 00:00
To: [EMAIL PROTECTED]
Subject: bug in apache axis 1.2 beta ?
Hi all,
I'm usign axis 1.2 beta with jboss,as webapp no jboss-net, to
access a EJB using java:EJB as provider.
When I restart Jboss and try a client axis works ok, but when
I restart Jboss and after
Hi all,
I'm usign axis 1.2 beta with jboss,as webapp no jboss-net, to access a
EJB using java:EJB as provider.
When I restart Jboss and try a client axis works ok, but when I restart
Jboss and after getting a correct wsdl http:///axis/services/
MyService?wsdl the client fails with a
be a shortcut to typeMapping
= why is there such a difference ? And why isn't the working code not
automatically generated instead of the non-working? Is it a bug ? ;)
(doc : http://ws.apache.org/axis/java/user-guide.html)
Kind regards,
--
Julien Wajsberg
I tried to use client side JAX-RPC handlers and saw
the following problem.
I had 2 handlers handler1 and handler 2. If I use the
happy path everything is fine - handler1.handleRequest
is first called and then handler2.handleRequest and
then the corresponding handleResponse methods in
reverse
Try www.wingfoot.comfor a more lightweight
Java SOAP client.
-Original Message-From: Rui Craveiro
[mailto:[EMAIL PROTECTED]Sent: 10 August 2004
04:43To: [EMAIL PROTECTED]Subject: Axis and
Applets - Missing Feature (bug) Report
Hello,
I am starting a new project
]
Subject: RE: Axis and Applets -
Missing Feature (bug) Report
Try www.wingfoot.comfor
a more lightweight Java SOAP client.
-Original Message-
From: Rui Craveiro
[mailto:[EMAIL PROTECTED]
Sent: 10 August 2004 04:43
To: [EMAIL PROTECTED]
Subject: Axis and Applets -
Missing Feature
Hello,
I am starting a new project and I was trying to keep my
options open when I decided to tryout available Java APIs to work with
webservices. More precisely, my company is considering to work with .NET and
use it to expose web-services. However, I wanted to be safe to know I will
This Schema, as part of WSDL, instead of generating a function with a
return type of String[] as I specify it here, returns a function with a return
type of Void. Any ideas why??? See QueryList in schema...
Any idea how I correctly declare an array that will work!?
xs:complexType
I have
the following problem,
I
send2 parameters in the in the Method "invoke" one is a String and the
other ist aHashmap.
When i
send a key and only one String as a value there is no
problem!
But
when I use a Array as value for the Hashmap i get a
faultstringorg.xml.sax.SAXException:
looks like a bugplease submit a bug report with a small test case
if possible.,
-- dims
- Original Message -
From: sanjay [EMAIL PROTECTED]
Date: Fri, 9 Jul 2004 23:07:12 +0530
Subject: Service.createCall() - Is this a bug ?
To: [EMAIL PROTECTED]
Hi
Thanks,
I filed a bug for this [AXIS-1445]
Regards
Sanjay
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 10, 2004 12:51 AM
To: [EMAIL PROTECTED]
Subject: Re: Service.createCall() - Is this a bug ?
looks like a bugplease submit a bug report
do u have a patch in mind as well?
-- dism
On Sat, 10 Jul 2004 01:23:30 +0530, sanjay [EMAIL PROTECTED] wrote:
Thanks,
I filed a bug for this [AXIS-1445]
Regards
Sanjay
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 10, 2004 12:51
PROTECTED]
Subject: Re: Service.createCall() - Is this a bug ?
do u have a patch in mind as well?
-- dism
On Sat, 10 Jul 2004 01:23:30 +0530, sanjay [EMAIL PROTECTED] wrote:
Thanks,
I filed a bug for this [AXIS-1445]
Regards
Sanjay
-Original Message-
From: Davanum Srinivas
and update
if it works (if the issue is open by then).
Regards
Sanjay
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 10, 2004 1:49 AM
To: [EMAIL PROTECTED]
Subject: Re: Service.createCall() - Is this a bug ?
do u have a patch in mind
/
/wsdl:message
Notice that the WSDL fragment for dl.wsdl sets a type of xsd:string for the
return type. Needless to say, clients I am targetting to these generated
stubs fail to compile for the doc/lit case.
Is this a bug, or am I doing something wrong? If it is, has it been fixed in
the last 3 weeks
Hi,
I'm having a problem with Axis (tomcat/java) which I can neither explain
nor workaround.
As I don't know if it's a bug in my program or in Axis, I send this
message to both mailing list...
As a reserch project, I'm writing a web services which I want to be able
to communicate binary data
Hello, I am wondering what the road map is for integrating a fix for this
multi-cookie support problem into the code base for axis?
I see that there is a patch but unfortunately I work at a company that
tries to avoid one-off patched versions of tools and since we are already
using axis 1.1 in
If i get a patch against latest CVS. am willing to apply the patch.
thanks,
dims
On Thu, 1 Jul 2004 17:57:17 -0700 (PDT), Alex Burmester [EMAIL PROTECTED] wrote:
Hello, I am wondering what the road map is for integrating a fix for this
multi-cookie support problem into the code base for
Folks,
If you are facing a performance problem(s), please try latest CVS /
nightly, if the problem still exists, open up a bug report with a
stripped down sample to recreate the problem. Am planning to get back
to some performance testing next week. If we can't recreate it, we
can't fix
n the stub was generated. From the API, it looks like that
should remove the xsi:type attributes from the SOAP body, but I still see them
in there. Is thisa bug, or am I missing something?
Thanks,
-
Jason
Jason Dobies
Java Application Developer
Gestalt LLC
[EMAIL PROTECTED]
856.614.5433
Thought I would run this by the list before I entered this bug...
Element defined in schema:
element name=numberOfChildren type=xsd:int minOccurs=0/
When using Axis 1.2 Alpha:
wsdl2java generates this...
private int numberOfChildren;
and when not setting any value for this, this is what
protected and I cannot access it from my code.
Is this a bug?
Any help appreciated.
Thank you
Hemanth Setty
**
The information contained in this communication is confidential, private,
proprietary, or otherwise privileged and is intended only for the use of the
addressee. Unauthorized use
Greetings everyone,
I want to get a reality check before entering a JIRA bug report. Thanks go
out to the SOAPtest guys over at Parasoft for helping me realize this
problem - it was quite subtle. In the following WSDL, I do the following:
BankService-DocLiteral.wsdl, target namespace:
http
Yes, please open a bug report.
thanks,
dims
--- Anderson Jonathan [EMAIL PROTECTED] wrote:
Greetings everyone,
I want to get a reality check before entering a JIRA bug report. Thanks go
out to the SOAPtest guys over at Parasoft for helping me realize this
problem - it was quite subtle
by axis)
only contains one element:
java.util.Map _output;
_output = _call.getOutputParams();
Hi Oliver,
It would help if this mail stated exactly what your problem is.
Regards
Steve
Quoting Oliver Wulff [EMAIL PROTECTED]:
Hi all
I'm wondering whether this is already a known bug in Axis
If there's a bug you wish to see fixed in Axis 1.2-Beta or final, read on...
- If there is no bug currently in JIRA (http://issues.apache.org/jira), please create
one.
- If there is a bug existing in JIRA, then Make sure there is enough information to
recreate the
bug
- Make sure you try latest
Hi all
I'm wondering whether this is already a known bug in Axis because I didn't
get a reply so far.
Thank you for your help.
Oliver
*** BITTE BEACHTEN ***
Diese Nachricht (wie auch allfällige Anhänge dazu) beinhaltet
möglicherweise vertrauliche oder
Hi Oliver,
It would help if this mail stated exactly what your problem is.
Regards
Steve
Quoting Oliver Wulff [EMAIL PROTECTED]:
Hi all
I'm wondering whether this is already a known bug in Axis because I didn't
get a reply so far.
Thank you for your help.
Oliver
I may have found a bug with Axis' treatment of doc-literal encoding in Axis
1.2 alpha. My basic steps were:
1) Create a WSDL file with complexTypes defined using XML Schema
2) Run wsdl2java to generate my WSDD, skeletons, etc.
The classes generated by WSDL2Java that correspond to my complexTypes
This does not seem to be a bug. Your schema definition needs to have the
elementFormDefault attribute with a value of qualified. The default value
(if unspecified) is unqualified which results in your locally declared
elements to be in no namespace.
Modify your schema like:
schema
Thank you for your help Junaid, but I still think that we have found a bug.
You're right, specifying elementFormDefault=qualified gives me the output
I want. However, I think the SOAP generated when
elementFormDefault=unqualified (or is unspecified) is wrong. I think that
specifying xmlns
It is still not a bug. Let em clarify this a bit further:
xmlns= means that the element is in no namespace. Also
elementFormDefault=unqualified only affects locally declared elements - -
It means local elements like controlNum, etc will be in no namespace
(hence the xmlns=). It does
a bug in axis. here is
the
interface portion of my wsdl:
message name=RetrieveRequest
part name=Provider type=xsd:string/
part name=Event type=xsd:string/
part name=foo type=xsd:string/
/message
message name=RetrieveResponse
part name=foo type=xsd:string
howdy all-
i'm working with axis, and am trying to convert a wsdl into java client stubs
and server side skeletons. i'm having much success in most of my wsdls, but
one is giving me problems. i believe i've located a bug in axis. here is the
interface portion of my wsdl:
message name
Hi Steve-
thanks for the prompt response! that clears it up.
false alarm - no bug. :)
-c
On Thu, Mar 11, 2004 at 06:35:51PM +0100, [EMAIL PROTECTED] wrote:
Hi
If you use the same name in both the Request and Response message then it is
translated as an IN/OUT parameter
Title: bug in latest nightly build ?
Hi,
Because of the fact that we experienced timeouts on attachments(DIME) trough the managedmemorydatasource
we tried yesterday to have our aplication use an axis.jar constructed from the latest nightly build. The timeouts
are now gone however now we
dicembre 2003 21.21
A: '[EMAIL PROTECTED]'
Oggetto: RE: Axis Bug?
Remove the restriction bit, since there is no validation anyways...
-Original Message-
From: Tevoi Andrea [mailto:[EMAIL PROTECTED]
Sent: Monday, December 15, 2003 3:22 AM
To: [EMAIL PROTECTED]
Subject: Axis Bug
stringRestriction)
is this an Axis bug?
thanks in advance,
Andrea Tevoi
Remove the restriction bit, since there is no validation anyways...
-Original Message-
From: Tevoi Andrea [mailto:[EMAIL PROTECTED]
Sent: Monday, December 15, 2003 3:22 AM
To: [EMAIL PROTECTED]
Subject: Axis Bug?
Hi all,
I've seen that for a simple type derived from another simple type
Hi
I've had a strange error when i've decided to upgrade my java sdk client side.
I've installed Axis under Tomcat 4.1.27, which runs with sdk 1.4.1. My client sofware,
that i'm developping run
well with sdk 1.4.1... I've decided to upgrade the sdk, server side and client side.
- With sdk
specific Response Chain
7) JAX-RPC Handlers
8) Global Response Chain
9) Transport Specific Response Chain
Is the behaviour on the client a bug?
Thanks,
Thilo
) Service specific Response Chain
7) JAX-RPC Handlers
8) Global Response Chain
9) Transport Specific Response Chain
Is the behaviour on the client a bug?
Thanks,
Thilo
Harald Pollak wrote:
A jax-rpc handler chain can only handle jax-rpc handlers but axis can
deal with both
That's true.
and jax-rpc handler are allways global and not service spezific.
That's not true. JAX-RPC handlers are service specific in Axis.
Thus, I am wondering why they are invoked
ok!
I agree with you in all points.
1. Its realy confusing that client and server chain are different.
2. If jax-rpx handlers are service spezific ( I have missunderstood somthing )- the client should
allso act like the server.
So I allso think its a bug.
Harry
Am Do, den 11.12.2003
Axis developers: was the decribed behaviour intentionally coded like this
or is it a bug?
Harald Pollak wrote:
ok!
I agree with you in all points.
1. Its realy confusing that client and server chain are different.
2. If jax-rpx handlers are service spezific ( I have missunderstood
somthing
Request Chain
5) invoke web service
6) Service specific Response Chain
7) JAX-RPC Handlers
8) Global Response Chain
9) Transport Specific Response Chain
Is the behaviour on the client a bug?
Thanks,
Thilo
) Transport Specific Response Chain
Is the behaviour on the client a bug?
Thanks,
Thilo
Hi Pedro,
Pedro Salazar wrote:
On Thu, 2003-12-04 at 16:59, Rodrigo Ruiz wrote:
Here it is my little proposal (I'm not saying it is easy or fast to
implement ;-) )
For each stateful EJB, create two services:
[snip]
My two cents ;-)
Rodrigo Ruiz
Very interesting, indeed.
Since
Hi
How can I workaround the following problem?
The WSDL of my Java servicedefines anentryDate as follows:element name="entryDate" nillable="true" type="xsd:dateTime" /The entryDatesJava representation isjava.util.Date.Axis sends aSOAP response containing the entryDate as follows: entryDate
To: [EMAIL PROTECTED]
Subject: Bug? Axis returns date
instead of dateTime
Hi
How can I workaround the following problem?
The WSDL of my Java servicedefines
anentryDate as follows:
element name=entryDate nillable=true
type=xsd:dateTime
Has Axis started supporting Stateful session beans? I thought for the EJB
provider, you can only work with Stateless session beans.
-Original Message-
From: Keith Hatton [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2003 10:21 AM
To: Axis-User (E-mail)
Subject: Bug? Stateful
To: '[EMAIL PROTECTED]'
Subject: RE: Bug? Stateful Session EJB support
Has Axis started supporting Stateful session beans? I thought for the EJB
provider, you can only work with Stateless session beans.
[mailto:[EMAIL PROTECTED]
Sent: 04 December 2003 15:25
To: '[EMAIL PROTECTED]'
Subject: RE: Bug? Stateful Session EJB support
Has Axis started supporting Stateful session beans? I thought for the EJB
provider, you can only work with Stateless session beans.
]'
Subject: RE: Bug? Stateful Session EJB support
Has Axis started supporting Stateful session beans? I thought for the EJB
provider, you can only work with Stateless session beans.
/
1 - 100 of 287 matches
Mail list logo
