Great - thanks for getting back to me.
Susantha Kumara [EMAIL PROTECTED]
03/03/2005 06:07
Please respond to
Apache AXIS C Developers List
To
Apache AXIS C Developers
List axis-c-dev@ws.apache.org
cc
Subject
Re: wcg
Hi John,
c/src/wcg contains the C++ code written by
[ http://issues.apache.org/jira/browse/AXISCPP-483?page=history ]
Mark Whitlock closed AXISCPP-483:
-
Resolution: Fixed
Fixed as suggested
Trace this on exit
--
Key: AXISCPP-483
URL:
[ http://issues.apache.org/jira/browse/AXISCPP-493?page=history ]
Mark Whitlock closed AXISCPP-493:
-
Resolution: Fixed
Fixed as suggested
HeaderBlock::attrSerialize is traced as static
--
[
http://issues.apache.org/jira/browse/AXISCPP-497?page=comments#action_60107 ]
Mark Whitlock commented on AXISCPP-497:
---
Hi Samisa,
There are several problems here. Fred put in a fix under AXISCPP-478/490 into
Call::setTransportProperty to
No soapaction means handlers can't be called
Key: AXISCPP-499
URL: http://issues.apache.org/jira/browse/AXISCPP-499
Project: Axis-C++
Type: Bug
Components: Handlers
Reporter: Mark Whitlock
Assigned to: Mark
[
http://issues.apache.org/jira/browse/AXISCPP-497?page=comments#action_60108 ]
Samisa Abeysinghe commented on AXISCPP-497:
---
Hi Mark,
Yes I do realize the problems here.
However, dopping Stub::setTransportProperty( char* ) is not a
[
http://issues.apache.org/jira/browse/AXISCPP-499?page=comments#action_60110 ]
Mark Whitlock commented on AXISCPP-499:
---
I discussed this problem with Adrian and he (kindly) pointed out
- if the soapaction is not set in the wsdl, this fix
[
http://issues.apache.org/jira/browse/AXISCPP-497?page=comments#action_60109 ]
Samisa Abeysinghe commented on AXISCPP-497:
---
As a solution what if we relpace the m_pTransport-setTransportProperty(char*,
char*) calls in Stub class with
try
[
http://issues.apache.org/jira/browse/AXISCPP-499?page=comments#action_60111 ]
Samisa Abeysinghe commented on AXISCPP-499:
---
What if we update the generated code (that is WSDL2Ws tool) so that if SOAP
Action is already set, we do not set
Remove wcg content
--
Key: AXISCPP-500
URL: http://issues.apache.org/jira/browse/AXISCPP-500
Project: Axis-C++
Type: Task
Reporter: Samisa Abeysinghe
Priority: Trivial
Fix For: 1.5 Final
As per the mailing list discussions, wcg are to
Hi Manohar,
This happens because there is a wrong header file inclision in
inquire_v2Client.cpp
I fixed this couple of days back. If you could try with a new CVS
checkout that would work.
Thanks,
Samisa...
On Thu, 3 Mar 2005 10:31:58 +0530, Manohar K Chintala
[EMAIL PROTECTED]
Hi Manohar,
The fault model changed a while ago. These generated exceptions have
disappeared and instead SoapFaultException is thrown. If the server returns
a soap fault that is not in the WSDL an OtherFaultException is thrown. If a
user soap fault defined in the WSDL is returned, then the
[
http://issues.apache.org/jira/browse/AXISCPP-497?page=comments#action_60114 ]
Mark Whitlock commented on AXISCPP-497:
---
Hi Samisa,
Thank you for comments. I understand the need to have a
setTransportProperty(char*, char*) now.
On Call there
[
http://issues.apache.org/jira/browse/AXISCPP-499?page=comments#action_60115 ]
Mark Whitlock commented on AXISCPP-499:
---
Hi Samisa,
Yes, I like your solution because it allows the client to override the
soapaction even if it has been set in
[ http://issues.apache.org/jira/browse/AXISCPP-479?page=history ]
Mark Whitlock closed AXISCPP-479:
-
Resolution: Fixed
This test is now fixed
HandlerTest4 fails on AIX
-
Key: AXISCPP-479
URL:
[
http://issues.apache.org/jira/browse/AXISCPP-497?page=comments#action_60119 ]
Samisa Abeysinghe commented on AXISCPP-497:
---
A look into
HTTPTransport::setTransportProperty( AXIS_TRANSPORT_INFORMATION_TYPE type,
const char *value)
and
[ http://issues.apache.org/jira/browse/AXISCPP-500?page=history ]
Samisa Abeysinghe reassigned AXISCPP-500:
-
Assign To: Samisa Abeysinghe
Remove wcg content
--
Key: AXISCPP-500
URL:
[
http://issues.apache.org/jira/browse/AXISCPP-497?page=comments#action_60118 ]
Samisa Abeysinghe commented on AXISCPP-497:
---
Hi Mark,
Yes I agree - having two APIs here is a maintanance headache.
While I would love to have
[ http://issues.apache.org/jira/browse/AXISCPP-428?page=history ]
Samisa Abeysinghe closed AXISCPP-428:
-
Resolution: Fixed
Added proxy support and tested with inquire_v2 on Linux.
Tests were successful
Proxy support for axis3 transport
IAttributeTest4Request.out change
-
Key: AXISCPP-501
URL: http://issues.apache.org/jira/browse/AXISCPP-501
Project: Axis-C++
Type: Bug
Environment: n/a
Reporter: Fred Preston
Assigned to: Fred Preston
The content of
[ http://issues.apache.org/jira/browse/AXISCPP-501?page=history ]
Fred Preston resolved AXISCPP-501:
--
Resolution: Fixed
IAttributeTest4Request.out change
-
Key: AXISCPP-501
URL:
[ http://issues.apache.org/jira/browse/AXISCPP-501?page=history ]
Fred Preston closed AXISCPP-501:
IAttributeTest4Request.out change
-
Key: AXISCPP-501
URL:
[ http://issues.apache.org/jira/browse/AXISCPP-501?page=history ]
Fred Preston reopened AXISCPP-501:
--
Still problems with the expected request
IAttributeTest4Request.out change
-
Key: AXISCPP-501
[
http://issues.apache.org/jira/browse/AXISCPP-501?page=comments#action_60139 ]
Fred Preston commented on AXISCPP-501:
--
There is still a problem with the uri associated with the nsp prefix. It
changed from its original definition of
[ http://issues.apache.org/jira/browse/AXISCPP-409?page=history ]
Samisa Abeysinghe reassigned AXISCPP-409:
-
Assign To: Samisa Abeysinghe
SimpleAxisServer hangs
--
Key: AXISCPP-409
URL:
[ http://issues.apache.org/jira/browse/AXISCPP-409?page=history ]
Samisa Abeysinghe closed AXISCPP-409:
-
Resolution: Fixed
Fix Version: 1.5 Final
The fixes to axis3 transport to handle HTTP properly has fixed this problem as
well.
It is
Hi,
We are trying to automated the server
side to test case, which will help to test client with the sever side.
But we have problem here several test
will generate same file in auto generated skeleton.
E.g. MathOps.cpp use by FaultMapping.wsdl,
FaultMappingDoc.wsdl,
ect..
IT is
Hi,
This is a redone version of the code I submitted before. It was based
on the Axis1 mail code. A test case is also included now.
Addition to the normal external jars used in axis2 the following jars
are needed to run the code,
jaf
javamail
common-net
Best Regards,
Chamil Thanthrimudalige.
Well Chamil,
Its easy for us if you can send us the patch as a *file* so that I can apply
it easily.
And since we are using Maven, you can add the dependencies to the correct
module project.xml.
BTW : If I apply the match, anyhow, the code may break for others due to
dependencies.
Regards,
I would like to wait bit to apply the patach till the new teansport
module is created as it does not worth doing it twice .. Let us wait
bit till we decide on tranport modules/module
Thanks
Srinath
On Thu, 3 Mar 2005 15:45:50 +0600, Eran Chinthaka
[EMAIL PROTECTED] wrote:
Well Chamil,
Its
[EMAIL PROTECTED] wrote:
Hi,
would it be possible to modify the logging framework, so that the
commons-logging Log class isn't used anymore throughout the entire axis
distribution, but only in -say- the org.apache.axis.compontents.logging.Log
class? So you get a more loosely coupled logging
Hi.
The Aixom doest not seem to serialize soap message which has an unqualified
soap body element.
For example,
soapenv:Body
ns1:getBalance xmlns:ns1=http://localhost:8081/axis/services/BankPort/
accountNo href=#id0/
/ns1:getBalacne
/soapenv:Body
The following exception
Hi Jongjin,
Yes, OM throws errors when SOAP messages violate the SOAP spec. The
reason simply is that OM is meant to be a SOAP specific object model.
So SOAP messages that are not qualified will throw errors :) We are
thinking of extending OM as a generic XML object model but it's still
in the
Hi Axis2 developers,
Even I too am facing same problem. And, this appears like a bug to me.
As per SOAP element names should be qualified, but that doesn't
necessarily mean prefixes should exist. A default namespace element
may just be qualified with a null prefix. This should be fixed at the
Hi list
i need to get the get the client certificate during
http session in web service using axis.
can you help me ?
can you give me references to consult?
my best regards
___
Nuovo Yahoo! Messenger: E' molto più divertente: Audibles, Avatar,
Hi there,
I suppose what you meant by the null prefix is the default namespace
declaration.
have a look at the following XML's and tell me if I have understood
the problem correctly
xml fragment 1
a xmlns=myns
b/
/a
in this case element b belongs to the namespace myns even though its
is not
Hi Dheeraj,
Try to make available all the necessary classes (I'd say every class
that are talked about in the scenario you explained) in the
web-inf/classes directory of Tomcat, and give it a try once again. My
personal thought is that a beanMapping on the entry level object is
sufficient provided
Hi All;
This is regarding the invoke, pausing and resuming the the invocation!
To this point this is implemented with an ExecutionChain kept in the
MessageContext ..calling the invoke on the MessageContext.
But more I look at the code more I convinced the way the Glen has done
it in EngineToy
Ajith,
If we send or receive soap message which is rpc-encoded, the xml fragment 2 can
be possible.
SOAP 1.1's soap encoding uses unqualified accessor element in compound type.
http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383519
I think this is the case for #2.
Also,, I suppose, we can
Dennis, Everyone,
- IF you *KNOW* a problem make sure there is a JIRA bug.
- IF the JIRA bug is CLOSED. Make a comment in the bug report and i
will re-open it.
- IF the JIRA bug DOES NOT have a simple test case to recreate the
bug, please add one.
IF we don't know a bug is there, we cannot fix
Hi axis-developers,
I've just deployed a simple Echo service using Axis1.2RC2 on Tomcat.
I invoked the service using an Axis2 synchronous client and the log of
request and response SOAP messages as seen on tcpmon are as follows.
Request:
-
soapenv:Envelope
[ http://issues.apache.org/jira/browse/AXIS-530?page=history ]
Davanum Srinivas reopened AXIS-530:
---
Reopening as per Dennis' comments.
elements without minOccurs=0 produce isnill=true on the wire
Sanjiva -
Here are some of my additional comments. I apologize if they are not
polished. I'm in the middle of a conference, and could not prepare
myself better ;) :
1. I believe the integration style of messaging is more applicable to
large-scale distributed computing, and hence have been
Eran Chinthaka wrote:
We implemented a SOAP layer on top of OM using the SOAPBuilder. But it
was in accordance with SOAP 1.1. But now I think its time to support
SOAP 1.2 as well. There we have a problem as some of the things are
bit different in 1.2 compared to 1.1. (see here
[ http://issues.apache.org/jira/browse/AXIS-530?page=history ]
Davanum Srinivas resolved AXIS-530:
---
Resolution: Fixed
Checked in a fix just now.
-- dims
elements without minOccurs=0 produce isnill=true on the wire
Hi,
I'm having some trouble compiling code generated by Axis 1.2 RC3 from my
WSDL-file.
It's quite obvious what's causing the compile to fail, two arguments with
the same name (cause1) to the constructor, not really a good idea. ;)
Is this a bug or am I'm doing something really wrong here?
Please open a bug report and then upload the complete wsdl file.
thanks,
dims
On Thu, 3 Mar 2005 22:32:43 +0100 (CET), Niclas Gustafsson
[EMAIL PROTECTED] wrote:
Hi,
I'm having some trouble compiling code generated by Axis 1.2 RC3 from my
WSDL-file.
It's quite obvious what's causing the
Axis is behaving properly. ns1:echoStringResponse, which is the
RPC/encoded wrapper element, and the child element of the SOAP body,
is a qualified element -- as it should be. EchoStringReturn, which
is the return value for an RPC/encoded, and the child element of the
return wrapper element is an
[
http://issues.apache.org/jira/browse/AXIS-1835?page=comments#action_60151 ]
Davanum Srinivas commented on AXIS-1835:
Yes, we'd be interested in this effort (as long as you can do the work :)
-- dims
Create an Eclipse update manager site
[
http://issues.apache.org/jira/browse/AXIS-1739?page=comments#action_60150 ]
Davanum Srinivas commented on AXIS-1739:
not sure about this one. Please try RC3 and report behaviour changes if any.
please do change DOCUMENT to WRAPPED on the
[ http://issues.apache.org/jira/browse/AXIS-1833?page=history ]
Davanum Srinivas resolved AXIS-1833:
Resolution: Fixed
Try Axis 1.2 RC3 and let us know if you still have this specific problem (then
we can reopen the bug).
thanks,
dims
'no
Is anyone familiar with posting JARs up to
http://www.ibiblio.org/maven/axis/jars/. It would be good to get RC3 up there.
Isn't it a bad idea to have a complexType with two elements of the same
name (but NOT representing an array)?
Davanum Srinivas wrote:
Please open a bug report and then upload the complete wsdl file.
thanks,
dims
On Thu, 3 Mar 2005 22:32:43 +0100 (CET), Niclas Gustafsson
[EMAIL
I'd recommend
modules/core
/etc
transports/http
/jms
/smtp
/etc
however, this isn't too hard to reorganize later if you start with one
transport module and decide to split it up later.
david jencks
On Mar 3, 2005, at 6:42 PM,
Just one comments to add, I believe in the implementing all messaging
patterns on top of *One way*, but NOT believe in the implementing SYNC
on top of ASYNC nor ASYNC on top of SYNC. As well all have fed up with
seeing the sync all around us and values Async there is a danger we
might overdo by
Can someone bring up JIRA site?
thanks
venkat
56 matches
Mail list logo
