Dear WS Folks,
It's time for our quarterly report to the board. It's our duty as
committers and pmc members to provide an accurate and detailed
description of our activities to the board. So please take a few
minutes and add information on projects that you are involved in.
[ http://issues.apache.org/jira/browse/AXIS2C-173?page=all ]
Sanjaya Ratnaweera closed AXIS2C-173:
-
Add content to README and NEWS files of xml_schema sub-build system
---
[ http://issues.apache.org/jira/browse/AXIS2C-173?page=all ]
Sanjaya Ratnaweera resolved AXIS2C-173:
---
Resolution: Fixed
Updated empty files.
Add content to README and NEWS files of xml_schema sub-build system
[ http://issues.apache.org/jira/browse/AXIS2C-176?page=all ]
Sanjaya Ratnaweera resolved AXIS2C-176:
---
Resolution: Fixed
Updated empty files.
Files without content in util sub-build system
--
[ http://issues.apache.org/jira/browse/AXIS2C-176?page=all ]
Sanjaya Ratnaweera closed AXIS2C-176:
-
Files without content in util sub-build system
--
Key: AXIS2C-176
URL:
[ http://issues.apache.org/jira/browse/AXIS2C-172?page=all ]
Sanjaya Ratnaweera resolved AXIS2C-172:
---
Resolution: Fixed
Updated empty files.
Add content to README and NEWS files of woden sub-build system
[ http://issues.apache.org/jira/browse/AXIS2C-172?page=all ]
Sanjaya Ratnaweera closed AXIS2C-172:
-
Add content to README and NEWS files of woden sub-build system
--
Key:
MSVCP70.DLL and MSVCR70.DLL required in windows binary build for
axis_client.dll and not bundled
Key: AXISCPP-974
URL: http://issues.apache.org/jira/browse/AXISCPP-974
Project:
[ http://issues.apache.org/jira/browse/AXIS2C-185?page=all ]
Damitha Kumarage resolved AXIS2C-185:
-
Fix Version: 1.0.0
Resolution: Fixed
Assign To: Damitha Kumarage
Done
Having a new function called contains_key in axis2_hash table
[ http://issues.apache.org/jira/browse/AXIS2C-186?page=all ]
Damitha Kumarage resolved AXIS2C-186:
-
Resolution: Fixed
Created a new class called axis2_uri and it contain the above solution.
The method is
/**
* Return a URI created from a
[
http://issues.apache.org/jira/browse/AXIS2-759?page=comments#action_12414917 ]
Rob Vincent commented on AXIS2-759:
---
I'm receiving a nearly identical stack trace in my log file when I just change
a very basic service based on the Version sample. If I
[ http://issues.apache.org/jira/browse/AXIS2-786?page=all ]
Eran Chinthaka resolved AXIS2-786:
--
Resolution: Fixed
Assign To: Eran Chinthaka (was: Deepal Jayasinghe)
Fixed the code to not to throw NPE. Thanks Kent for pointing this out.
Hello,
Does anyone know why the core/conf/axis2.xml
file includes the RequestURIBasedDispatcher and the SOAPActionBasedDispatcher
in the Transport phase of the Inflow? This seems to contradict the phase
descriptions in the section Processing an Incoming SOAP Message
of the Apache Axis2
WSDL2Java generate incorrect code for Open Oasis UBL schemas
Key: AXIS-2492
URL: http://issues.apache.org/jira/browse/AXIS-2492
Project: Apache Axis
Type: Bug
Components: WSDL processing
Versions:
[ http://issues.apache.org/jira/browse/AXIS-2492?page=all ]
Rémi Flament updated AXIS-2492:
---
Attachment: Order.wsdl
WSDL2Java generate incorrect code for Open Oasis UBL schemas
Key:
Samuel,
Could u please post a quick patch?
thanks,
dims
On 6/5/06, Samuel Isokpunwu [EMAIL PROTECTED] wrote:
Compilation errors in Axis2 tools package.
1. The org.apache.axis2.tool.codegen.WSDL2JavaGenerator is
referencing
org.apache.axis2.description.WSDL2AxisServiceBuilder
builder class
Should have added [Axis2] to the subject
originally.
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal
246319
If you can't find the time to do it right the first time, where will you
find the time to do it again?
- Forwarded by Brian
De
Dear WS Folks,
It's time for our quarterly report to the board. It's our duty as
committers and pmc members to provide an accurate and detailed
description of our activities to the board. So please take a few
minutes and add information on projects that you are involved in.
Method overloading should not be exposed through your WSDL interface. You should define a unique operation name and a unique input message for each operation. If your service implementation uses method overloading, that's fine -- but you need to provide an abstraction layer between your WSDL
Sanjiva Weerawarana wrote:
Folks, there's going to be a big group of Axis2 and Synapse guys from
WSO2 at ApacheCon Europe in June. Would others be interested in getting
together for some f2f/hacking work at the hackathon?
I think it'd be mighty useful.
Maybe, I'm flying in to dublin on
Jongjin Choi wrote:
My point is that the JAX-RPC and JAX-WS impl in a Java EE 5 container
should use same SAAJ impl. If not, two implementation of one interface
co-exists and that may cause some problem.
I agree with you. SAAJ is SAAJ but SAAJ impl of Axis 2 is based on
Axiom. Isn't it?
I think
Hi folks,
Just wondering where we are in terms of development on the axis2 / woden
integration for the interop event, and what is there left to do?
I know that one or two contributors are already actively working on this.
I think that a good minimal demonstration for the interop event would be
[ http://issues.apache.org/jira/browse/AXIS2-803?page=all ]
Travis Hein updated AXIS2-803:
--
Attachment: WarBasedAxisConfigurator.java.diff
Ok, here is the patch version.
(WarBasedAxisConfigurator.java.diff)
fix small issue causing null pointer exception,
[ http://issues.apache.org/jira/browse/AXIS2-803?page=all ]
Davanum Srinivas resolved AXIS2-803:
Resolution: Fixed
Applied (r412144)
thanks.,
dims
fix small issue causing null pointer exception, fix typos, add javadoc
comments.
[ http://issues.apache.org/jira/browse/AXIS2-264?page=all ]
Davanum Srinivas resolved AXIS2-264:
Resolution: Fixed
I think we have nailed this now. Please reopen with a test if you still see it.
thanks,
dims
improve memory usage when parsing
Hi folks!
This is an automatic reminder that the weekly Axis2 developer chat
will be occurring tomorrow, June 07, at:
5AM SF, 8AM Boston, 1PM London, 5:30PM Colombo, 10PM Melbourne
The chat takes place on the freenode IRC network, (use server
irc.freenode.net), on channel #apache-axis, and is
Chathura,
can you tell us how your Axis2/Woden integration is going?
At the W3C WSDL 2.0 Interop event on July 5th we'd like to show Woden
working with Axis2, that is, show Axis2 parsing WSDL 2.0 documents and
successfully doing stuff ... WSDL2java generation and/or runtime
SOAP messages. Do you
[ http://issues.apache.org/jira/browse/AXIS-1411?page=all ]
Marc Foley updated AXIS-1411:
-
Attachment: wsdl_xsd.zip
I am having the same issue in that the wsdl that gets autogenerated is not
correct and when the service is called the user gets a type
[
http://issues.apache.org/jira/browse/AXIS-2491?page=comments#action_12415001 ]
Bjorn Townsend commented on AXIS-2491:
--
It's difficult to determine whether you're compliant with the SOAP/1.1 spec
without seeing your SOAP transaction. Can you use
Compilation errors in Axis2 tools package.
--
Key: AXIS2-806
URL: http://issues.apache.org/jira/browse/AXIS2-806
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: Tools
Versions: 1.0
Environment: Win XP
[ http://issues.apache.org/jira/browse/AXIS2-806?page=all ]
Samuel Isokpunwu updated AXIS2-806:
---
Attachment: WSDL2JavaGenerator-patch.txt
This quick fix assume that the wsdlURI parameter points to a wsdl 1.1 verssion.
A better fix should be to
[
http://issues.apache.org/jira/browse/AXIS2-801?page=comments#action_12415036 ]
Bille commented on AXIS2-801:
-
Thanks Eran,
I tried again including your changes and it really looks better now.
Issues 2) and 3) are still remaining!!
The SOAP-response now looks
[
http://issues.apache.org/jira/browse/AXIS2-801?page=comments#action_12415038 ]
Bille commented on AXIS2-801:
-
you mentioned BTW, set all the fault properties to the in message context when
you are throwing the fault.
I set those properties, that are
For an interface with a complex type parameter for the method, incorrect WSDL
is generated
--
Key: AXIS2-807
URL: http://issues.apache.org/jira/browse/AXIS2-807
Project: Apache Axis 2.0
Anne: Thanks for your interest.
I had solved it. I modified my input.xsd, i defined my input (that has a
choice) as a complextype and then different elements of that type, each one
for each operation.
Greetings.
Julio César.
From: Anne Thomas Manes [EMAIL PROTECTED]
Reply-To:
Hi,With the help of the core Axis2 dev team, I'm also in the process of implementing the Axis2/Woden integration. At the moment, my efforts are on populating the AxisService once a WSDL2.0 is bundled in a service archive file and deployed on Axis2.
There's a class called WSDL20ToAxisServiceBuilder
Oshani,
can you please open a JIRA issue and keep uploading diff's as you progress?
thanks,
dims
On 6/6/06, Oshani Seneviratne [EMAIL PROTECTED] wrote:
Hi,
With the help of the core Axis2 dev team, I'm also in the process of
implementing the Axis2/Woden integration. At the moment, my efforts
can you please open a JIRA issue and keep uploading diff's as you progress?
Sure
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
So here is where we stand. Basic skeleton of the integration is
there.I called it skeleton because it need to handle the rpc case and
not so urgent but eventually need to handle the policy stuff. you can
run WSDL2Jave with -wv 2 which will engage the woden. It will not
codegen successfully,
Well we had to move dispatchers here and there to solve security
(ws-sec) problem. I mean they wanted to dispatch using request uri. I
will update the documents to cope with the changes. I am very sorry for
our problem.
Brian De Pradine wrote:
Should have added [Axis2] to the subject
40 matches
Mail list logo
