this is a good improvement.
This performance gain happens only if you are using the same stub for multiple invocations, doesn't it? It is good to improve performance of possible scenarios and I guess this will be quite a common one.
sanjaya
Samisa Abeysinghe [EMAIL PROTECTED] wrote:
There is
SOAP Header tests has been failing due to a bug in the transport. I
fixed that and those are also passing.
We now only have to verify that SSL works with these changes.
Thanks,
Samisa...
On Wed, 2005-06-01 at 11:40, Samisa Abeysinghe wrote:
I have commited my initial changes to the CVS.
The
[
http://issues.apache.org/jira/browse/AXISCPP-622?page=comments#action_66722 ]
Samisa Abeysinghe commented on AXISCPP-622:
---
Based on Adrian's comment, I guess we can consider this issue to be closed.
We also get the any tests working hence
[
http://issues.apache.org/jira/browse/AXISCPP-333?page=comments#action_66729 ]
Dushshantha Chandradasa commented on AXISCPP-333:
-
It seems that we don't handle wsdl:arrayType in Axis C++. In privious cases
where we handle arrays, we
[ http://issues.apache.org/jira/browse/AXISCPP-588?page=all ]
Chinthana Danapala reassigned AXISCPP-588:
--
Assign To: Chinthana Danapala
Cannot compile InteropTestRound1Doc test client
---
[ http://issues.apache.org/jira/browse/AXISCPP-588?page=all ]
Chinthana Danapala resolved AXISCPP-588:
Resolution: Fixed
I have made the corrections to the TestRound1Doc.WSDL and
TestRound1DocClient.cpp files to solve the problem. Now
[ http://issues.apache.org/jira/browse/AXISCPP-588?page=all ]
Chinthana Danapala closed AXISCPP-588:
--
Fixed
Cannot compile InteropTestRound1Doc test client
---
Key: AXISCPP-588
[
http://issues.apache.org/jira/browse/AXISCPP-416?page=comments#action_66735 ]
Adrian Dick commented on AXISCPP-416:
-
I have now updated the axis engine to support all XSD type for deserialization,
meaning the Axis engine can now serialize and
[ http://issues.apache.org/jira/browse/AXISCPP-664?page=all ]
Samisa Abeysinghe updated AXISCPP-664:
--
Attachment: callSeq_openDropped.JPG
I removed the openConnection method from Call class and moved the login that
was inside this method to Call
Guys!
Can someone respond on this, plz.
Thanks
Jaya
On 5/31/05, jayachandra [EMAIL PROTECTED] wrote:
Hi devs,
I have two suggestions regarding OMDocument
First - a trivial one:
---
It lacks an interface definition in the package org.apache.axis.om and
a direct
jayachandra wrote:
Can someone respond on this, plz.
why not model it exactly as it is in XML Infoset - so have children API
but do not extend OMElement just duplicate it (AFAICT Document is not
Element ...)
http://www.w3.org/TR/xml-infoset/#infoitem.document
alek
Thanks
Jaya
On
Yeah! that's a wise way rather than extending OMElement. Apart being
more clear on the readability front it also reduces unnecessary
placeholders from creeping into OMDocument.
Jaya
On 6/1/05, Aleksander Slominski [EMAIL PROTECTED] wrote:
jayachandra wrote:
Can someone respond on this, plz.
Hi,
I'm interested in doing a student project with Axis2 for Google's
Summer of Code program, an initiative aimed at introducing students to
Open Source Software Development
(http://code.google.com/summerofcode.html). I've wanted to become
involved with an open source project for a while now,
Hi Mark;
I feel http://wiki.apache.org/ws/FrontPage/Axis2/Tasks/BinarySerialization
is quite a good bet. Nobody works on it right now. Mat be it a good
summer project proposal
1) It is quite isolated .. so less trouble
2) it is important for Axis2
If you have any trouble in the work we will do
Srinath, should we add this and any other tasks to the wiki page at
http://wiki.apache.org/general/SummerOfCode2005 ?
- venkat
On 6/1/05, Srinath Perera [EMAIL PROTECTED] wrote:
Hi Mark;
I feel http://wiki.apache.org/ws/FrontPage/Axis2/Tasks/BinarySerialization
is quite a good bet. Nobody
Srinath/ Mark
Nice idea. This is a hot area as the W3C are putting some effort into
binary XML right now. In addition to the links listed, I suggest you
look at Dennis Sosnoski's XBIS (http://xbis.sourceforge.net/) and the
cbXML proposal from IBM.
Paul I add your links to the WIKI :)
Venkat .. not sure ..about the how the thing goes foward .. maybody
somebody in the dev list know
Thanks
Srinath
On 6/1/05, Venkat Reddy [EMAIL PROTECTED] wrote:
Srinath, should we add this and any other tasks to the wiki page at
Hi all,
I was also looking in to this BinarySerialization as a proposal for
this google projects. Since somebody has come up with it now I'm
thinking of doing HTTP chunking for Axis2, which will improve the
efficiency of message delivary. What do u all think about it.
Thanks Regards,
~Thilina
[
http://issues.apache.org/jira/browse/AXIS-2026?page=comments#action_66728 ]
Hans commented on AXIS-2026:
Tom, thanx for the test case. The test runs successfully.
I will submit the change in TypeTestCase.java with the fix.
wsdl2java does not generate
Thilina create a Wiki and link it for the Task wiki page
put information/resources there ..
Thanks
Srinath
On 6/1/05, Thilina Gunarathne [EMAIL PROTECTED] wrote:
Hi all,
I was also looking in to this BinarySerialization as a proposal for this
google projects. Since somebody has come up with
Folks
What is the object lifecycle of components used by Axis2 as server
code implementations?
i.e. is there an init() style call? do they get re-used or does the
engine new them up for each invocation? Is there a way of setting
properties on them?
Paul
Paul are you refering to the the class that implements the businuss logic?
Thanks
Srinath
On 6/1/05, Paul Fremantle [EMAIL PROTECTED] wrote:
Folks
What is the object lifecycle of components used by Axis2 as server
code implementations?
i.e. is there an init() style call? do they get
Yes exactly. I'm looking at the sample EchoXML.
Paul
On 6/1/05, Srinath Perera [EMAIL PROTECTED] wrote:
Paul are you refering to the the class that implements the businuss logic?
Thanks
Srinath
On 6/1/05, Paul Fremantle [EMAIL PROTECTED] wrote:
Folks
What is the object lifecycle of
Need for Child API in OMDocument
Key: AXIS2-22
URL: http://issues.apache.org/jira/browse/AXIS2-22
Project: Axis2
Type: Improvement
Components: om
Reporter: Jayachandra Sekhara Rao Sunkara
Assigned to: Davanum Srinivas
[ http://issues.apache.org/jira/browse/AXIS-2002?page=all ]
Venkat Reddy resolved AXIS-2002:
Resolution: Fixed
Problem using OUT-parameters
Key: AXIS-2002
URL:
The ideal thing would be to have OMNode support child API, but was not
considered because OMText should not have children. I still favor
shifting of child API to OMNode.
- venkat
On 6/1/05, jayachandra [EMAIL PROTECTED] wrote:
Yeah! that's a wise way rather than extending OMElement. Apart being
While duplicating the child API into OMDocument I got stuck at something.
The addChild() method of in turn tries to setParent(), and the
datamember parent is rigidly typed to be an OMElement only.
/**
* Field parent
*/
protected OMElementImpl parent;
Now that OMDocument can
Singleton getInstance returns new instances each time ?
---
Key: AXIS-2030
URL: http://issues.apache.org/jira/browse/AXIS-2030
Project: Axis
Type: Bug
Components: Basic Architecture
Versions: 1.2
[ http://issues.apache.org/jira/browse/AXIS-1975?page=all ]
Venkat Reddy resolved AXIS-1975:
Resolution: Fixed
problem with operations with out parameters
---
Key: AXIS-1975
URL:
[ http://issues.apache.org/jira/browse/AXIS-2021?page=all ]
Dan Armbrust updated AXIS-2021:
---
Attachment: VocabBrowser.wsdl
WSDL (as generated by Axis)
String Array Regression causes SAXException: Found character data ...
If my opinion counts... this one is a critical blocker...
http://issues.apache.org/jira/browse/AXIS-2021
Dan
Davanum Srinivas wrote:
Hi all,
Let's get the ball rolling again...Anyone see blockers for a minor
release? Please make sure the problem exists in latest CVS,
write/upload a test
[
http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_66743 ]
Davanum Srinivas commented on AXIS-2021:
Just to confirm, Is this the WSDL generated by java2wsdl tool, using the -y
WRAPPED option in your build process?
thanks,
[
http://issues.apache.org/jira/browse/AXIS-1525?page=comments#action_66750 ]
Michael Thome commented on AXIS-1525:
-
I've been looking at the code - serialization looks pretty straightforward, but
deserialization is going to be tough - off hand, I
[
http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_66755 ]
Dan Armbrust commented on AXIS-2021:
Correct, this WSDL was generated using the -y WRAPPED option.
Here is the ant debug output of the actual command (ignore the [java]
[
http://issues.apache.org/jira/browse/AXIS-2024?page=comments#action_66766 ]
anonymous commented on AXIS-2024:
-
i'm not really recompiling, but just using the jars in a normal java project.
my build.xml doesn't work any more due to that enum package
[ http://issues.apache.org/jira/browse/AXIS-2026?page=all ]
Hans updated AXIS-2026:
---
Attachment: diff.zip
wsdl2java does not generate array of wrappers for soapenc array nillable
elements
[ http://issues.apache.org/jira/browse/AXIS-2026?page=all ]
Hans updated AXIS-2026:
---
Attachment: testcase_diff.zip
Shouldn't forget about the testcase...
wsdl2java does not generate array of wrappers for soapenc array nillable
elements
[ http://issues.apache.org/jira/browse/AXIS-2026?page=all ]
Davanum Srinivas reassigned AXIS-2026:
--
Assign To: Davanum Srinivas
wsdl2java does not generate array of wrappers for soapenc array nillable
elements
wsdl2java failed with an imported XSD with BOM character in front
-
Key: AXIS-2031
URL: http://issues.apache.org/jira/browse/AXIS-2031
Project: Axis
Type: Bug
Components: WSDL processing
[
http://issues.apache.org/jira/browse/AXIS-2026?page=comments#action_66770 ]
Hans commented on AXIS-2026:
attached patch
wsdl2java does not generate array of wrappers for soapenc array nillable
elements
[
http://issues.apache.org/jira/browse/AXIS-1996?page=comments#action_66785 ]
Dennis Sosnoski commented on AXIS-1996:
---
Yes, I mean that the SOAP Body element may be empty. This doesn't really have a
WSDL equivalent as far as I know, since in
On Wed, 2005-06-01 at 12:24 -0400, Mark Pimentel wrote:
Hi everyone,
Thanks for all your help so far. Binary serialization seems
interesting. I'll read up on the topic further, but I think it'd be a
good project.
One question: there are a few different standards for this... Are we
simpleType of string enum derived from simpleType string restrict
-
Key: AXIS-2032
URL: http://issues.apache.org/jira/browse/AXIS-2032
Project: Axis
Type: Bug
Components: WSDL processing
I dug around in the code a bit to get my answer. In case others need
help, here's the deal: org.apache.axis.soap.SOAPConnectionImpl creates a
new Call object every time SOAPConnection.call() is invoked. Thus, it
is impossible to reuse a socket connection and make use of http/1.1
keepalives.
I
[ http://issues.apache.org/jira/browse/AXIS-1752?page=all ]
Steve Green updated AXIS-1752:
--
Attachment: 1752-and-1762-simpler.patch
Attached is a much simpler version of the attribute list {de}serialization bug
patch.
xs:list attributes do not serialize
[ http://issues.apache.org/jira/browse/AXIS-1752?page=all ]
Steve Green updated AXIS-1752:
--
Attachment: testcase.tar
Attached is a test case.
xs:list attributes do not serialize
---
Key: AXIS-1752
Paul sorry had I give a fails hope , What I mean was that we can
implemented that (but not implemented yet).
I belive it is straight foward thing to implement, I will get back if
I able to tacke that
Thanks
Srinath
On 6/1/05, Paul Fremantle [EMAIL PROTECTED] wrote:
Srinath
Thats exactly the
jayachandra wrote:
While duplicating the child API into OMDocument I got stuck at something.
The addChild() method of in turn tries to setParent(), and the
datamember parent is rigidly typed to be an OMElement only.
/**
* Field parent
*/
protected OMElementImpl parent;
Now that
Hi Mark,
Yes it's very straight forward to implement as Sanjiva mentioned. We can
provide you some help in that. And as u also might know, there is no *ONE*
standard on binary stuff up to now. So we prefer to support multiple of
them.
During the last Axis2 summit, Geoffrey Fox was talking about
Not another class, but OMElementImpl need to implement the new
interface and all the child API be moved from OMElement to OMParent.
Also note that OMNode.setParent() now receives OMPraent, instead of
OMElement.
So the result is - OMDocument now implements only child navigation API
and avoids
Didn't I gave my +1 for this. Ok here goes, +1 ;).
-- Chinthaka
-Original Message-
From: Venkat Reddy [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 02, 2005 10:55 AM
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Need for children API for OMDocument
Not another class, but
51 matches
Mail list logo
