[
http://issues.apache.org/jira/browse/AXIS-1827?page=comments#action_61474 ]
Konstantin Kasatkin commented on AXIS-1827:
---
Of cource Jongjin, I can remove it, but I think it is not right way to fix the
problem. It smells slightly of shamanism
The chat today was majorly about the upcoming summit and a bit about
the mail transport
[09:02] *** Apache Axis -- WSDL SOAP XML-RPC
[09:04] Hello
[09:04] at last someone wake up ;)
[09:05] GM/GE ;-)
[09:05] hi Alek .. how are the things?
[09:06] we are preparing for the f2f ..these days
[09:06]
Hi all,
Some draft material for the upcoming Axis2 summit are hosted at
http://cvs.apache.org/~ajith/summit/
Wiki has also being updated at http://wiki.apache.org/ws/FrontPage/Axis2/f2f-2
All are welcome to have a look and send any comments to the mailing list
--
Ajith Ranabahu
[
http://issues.apache.org/jira/browse/AXIS-1827?page=comments#action_61456 ]
Jongjin Choi commented on AXIS-1827:
Hi Konstantin,
Why not just comment out or remove the from your axisclient.xml.
It will give you the right result.
I think the axi
WSDL2JAva fails on SQL Reporting Services
-
Key: AXIS-1900
URL: http://issues.apache.org/jira/browse/AXIS-1900
Project: Axis
Type: Bug
Components: WSDL processing
Versions: current (nightly)
Reporter: Tom Jordah
[ http://issues.apache.org/jira/browse/AXIS-1900?page=history ]
Tom Jordahl updated AXIS-1900:
--
Attachment: reportservice.wsdl
This WSDL demonstrates the problem.
> WSDL2JAva fails on SQL Reporting Services
> -
>
>
Dasarath Weeratunge wrote:
--- Aleksander Slominski <[EMAIL PROTECTED]> wrote:
At first all entities in OM were nodes—using a burned
in linked list. Later Attributes and Namespaces were
stored using hash-maps and people were in doubt as to
whether we need this burned in linked structure at
all.
The
[
http://issues.apache.org/jira/browse/AXIS-1754?page=comments#action_61429 ]
Tim Kagle commented on AXIS-1754:
-
As far as I recall the service is not thread safe. Previous call should
probably mean the last call made by the service, that would be more
[
http://issues.apache.org/jira/browse/AXIS-1754?page=comments#action_61428 ]
Steven Schwell commented on AXIS-1754:
--
What do you mean by "previous call"? last one created by the current thread or
the last one created by the current Service instan
[
http://issues.apache.org/jira/browse/AXIS-1754?page=comments#action_61427 ]
Tim Kagle commented on AXIS-1754:
-
The previous call is useful in order to get the cookies out of it and set them
on another stub to share them for example (see
http://issue
[
http://issues.apache.org/jira/browse/AXIS-1754?page=comments#action_61424 ]
Steven Schwell commented on AXIS-1754:
--
What is Service.getCall() supposed to return anyway? It is not documented. Is
it the last Call created by the current Thread? or
SOAP fault sent by Axis in rpc/encoded mode not compatible with .NET
Key: AXIS-1899
URL: http://issues.apache.org/jira/browse/AXIS-1899
Project: Axis
Type: Bug
Reporter: Tim Kagle
I'm filing a
I'm connecting to a webservice deployed on Websphere server (who knows what
stack/version).
Our client code generated with axis1_1 works fine without issues but when we
attempted to move to Axis1_2RC3 we ran into an issue where server would not
accept soap generated by new client code. Some deb
Hello all, I have a slight problem with my client when trying to use a
web service that uses a more complex return type (wrapped primitives
work fine, String and HashMap also work fine, but anything beyond is
giving me problems). This is the exception I am getting:
- Exception:
org.xml.sax.SAXExce
--- Aleksander Slominski <[EMAIL PROTECTED]> wrote:
At first all entities in OM were nodesusing a burned
in linked list. Later Attributes and Namespaces were
stored using hash-maps and people were in doubt as to
whether we need this burned in linked structure at
all.
The use of collection classe
Forwarding with correct subject.
BTW the page is at http://wiki.apache.org/ws/Axis2/MTOM :)
-- Forwarded message --
From: Thilina Gunarathne <[EMAIL PROTECTED]>
Date: Wed, 23 Mar 2005 04:49:11 -0800
Subject: MTOM implementation wiki created
To: axis-dev@ws.apache.org
Hi,
I creat
Hi All;
Based on the Shawn proposal I have checked in, a toy for the Axis2 core.
https://svn.apache.org/repos/asf/webservices/axis/trunk/archive/java/scratch/srinath_jaliya/
more improvements coming soon
Thanks
Srinath
Hi All,
I have document/literal WSDL generated by AXIS 1.2 RC2, JDK 1.4,
Windows 2000 on the server side and I want to test this WSDL by
feeding it to a .NET 1.1 SOAP Toolkit on the client side.
As I dont have .NET 1.1 SOAP Toolkit Environment I cannot test my
WSDL's and so can anyone working on
Hi,
I created a wiki page with details of the MTOM implementation for
AXIOM. Anybody who is interested in going in to details of the
(simple:) ) architecture can have a look at that page.
regards,
-Thilina
[ http://issues.apache.org/jira/browse/AXIS-1827?page=history ]
Konstantin Kasatkin updated AXIS-1827:
--
Attachment: example.zip
> Unnecessary empty-valued attribute "xmlns" in Envelope parameter values
> -
Hi there,
there is no client side DD or such. We haven't really thought of a way
of doing that either but the bias is to do it without such a
configuration file. When we use the code generation tool, all the
necessary details can be generated into the stubs! So no worries about
client side DD's tha
[
http://issues.apache.org/jira/browse/AXIS-1827?page=comments#action_61410 ]
Konstantin Kasatkin commented on AXIS-1827:
---
Problem still have been appearing even on AXIS 1.2RC3
I attached example.zip with test application.
Firstly you should
Extremely sorry guys!
Resending with proper subject line
-- Forwarded message --
From: jayachandra <[EMAIL PROTECTED]>
Date: Wed, 23 Mar 2005 16:14:00 +0530
Subject: Doubts regarding client side DD and test case for HTTPTransportSender.
To: axis-dev@ws.apache.org
With the idea o
With the idea of each transport being a new module, the way any
TransportSender handler gets picked up got totally changed.
Everything seems to be through DD. On the client side how should the
deployment info be mentioned to use a specific transport handler for
communication, is it through some cl
resending with proper subject -
---
hi folks,
Ashutosh and Jayachandra have put together a quick implementation for
SAAJ over OM as an exercise to see if the current OM API can cater the
needs of a SAAJ layer. We find that the basic needs are met to a build
a saaj SOAP
hi folks,
Ashutosh and Jayachandra have put together a quick implementation for
SAAJ over OM as an exercise to see if the current OM API can cater the
needs of a SAAJ layer. We find that the basic needs are met to a build
a saaj SOAPEnvelope object, but still there are some stuff that waits
for co
Hi Jayachandra,
Yup.. It was noticed and fixed.
Pls get an update and check.
Thanks
Chathura
> -Original Message-
> From: jayachandra [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 23, 2005 11:37 AM
> To: axis-dev@ws.apache.org
> Cc: Chathura Herath
> Subject: Re: [Axis2]Maven Build
Dasarath Weeratunge wrote:
Hi Alek,
have a look at
https://svn.apache.org/repos/asf/webservices/axis/trunk/archive/java/scratch/dasarath/om/$1/summary.html
Sorry for the messup with the tabs!
i think you need to modify how you do calculations - having 0 ms timings
means you have either insane
Just now checked out from svn and ran a maven build
org.apache.axis.engine.EchoRawXMLTest in samples module is failing and
build is breaking. Plz look into this ASAP
Jayachandra
On Tue, 22 Mar 2005 17:58:31 +0530, Ashutosh Shahi <[EMAIL PROTECTED]> wrote:
> Chathura,
> Sending the input
Hi,
Im interested in finding out what people are
expecting from axis2 when it comes to data binding.
Until yesterday I was thinking (this may sound naive)
that we would select a particular data-binding tool at
the time we generate code and then thats it
the
generated code would be tightly coupl
30 matches
Mail list logo
