[
https://issues.apache.org/jira/browse/AXIS2C-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dushshantha Chandradasa reassigned AXIS2C-541:
--
Assignee: Dushshantha Chandradasa
[Axis2] WSDL2C boolean not handled
[
https://issues.apache.org/jira/browse/AXIS2C-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dushshantha Chandradasa resolved AXIS2C-541.
Resolution: Fixed
fixed. Please try with the latest svn.
[Axis2] WSDL2C
Hi,
As we observed, ops structures lead to a considerable performance
hit and It may lead to binary compatibility issues that may
difficult to resolve. Therefor We are in a process of dropping those
ops structures from the Axis2/C code base.
Without ops structures , I could see that
[
https://issues.apache.org/jira/browse/AXIS2-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved AXIS2-1657.
-
Resolution: Fixed
add the method header comments
Problems in
[
https://issues.apache.org/jira/browse/AXIS2-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved AXIS2-983.
Resolution: Fixed
I have already added the list and union support
Antoine Levy-Lambert wrote:
Hello Stefan,
it looks like the intention of the developers of commons-jelly-tags-soap
was to use two distinct saaj jars and two distinct jaxrpc jars,
one from axis, and one from geronimo.
The project.xml [1] of commons-jelly-tags-soap suggest that the gump
build
[
https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved AXIS2-2246.
-
Resolution: Fixed
make part name unqualifed. so nonamespace
[
https://issues.apache.org/jira/browse/AXIS2-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved AXIS2-2238.
-
Resolution: Fixed
now adb supports inner choice elements
I believe it's there to support async processing of one-way messages
and of async 2-way (via ws-addressing).
So... I don't think it's needed for PUT but I'm not entirely sure. The
javadoc for RequestResponseTransport is pretty giid and might help.
David
On 28/02/07, keith chapman [EMAIL
Hi Keith,
The relevant commits are:
Revision 489259 - (view) (download) (annotate) - [select for diffs]
Modified Thu Dec 21 03:39:21 2006 UTC (2 months, 1 week ago) by
chamikara
File length: 13755 byte(s)
Diff to previous 487227 (colored)
Added a mechanism to give the current state of the
[
https://issues.apache.org/jira/browse/AXIS2-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476594
]
John Turner commented on AXIS2-2030:
In addition, the JMSConnectionfactory contains a mapping between the
Update to metadata URIResolverImpl to handle https protocol based schema imports
Key: AXIS2-2272
URL: https://issues.apache.org/jira/browse/AXIS2-2272
Project: Axis 2.0
hi,
I still working on HttpBinding support and multiservice support for
WSDL 1.1and hope I could finish on end of next week (at least good
enough to have a
RC1).
I did a lot of bug fixing and improvements for adb, WSDL processing and
codegen. In the user list I saw some people testing with
[
https://issues.apache.org/jira/browse/AXIS2-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dustin Amrhein updated AXIS2-2272:
--
Attachment: patch.txt
Update to metadata URIResolverImpl to handle https protocol based
H. Interesting issue! Should we be doing the same in Axis2?
Sanjiva.
--
Sanjiva Weerawarana, Ph.D.
Founder Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
I think the addition of annotations itself justifies 1.2 .. that's a major
userbility improvement.
Isn't that independent of JAX-WS?
Sanjiva.
Deepal Jayasinghe wrote:
Hi Deve;
As I mentioned in the initial mail on Axis2 1.2 release , we need to
have JAX-WS support in this release. So cloud
[
https://issues.apache.org/jira/browse/AXIS2-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476657
]
Shawn J. Dyck commented on AXIS2-2254:
--
Does this does the axis2-SNAPSHOT-02-28-07 have the windows path fix
[
https://issues.apache.org/jira/browse/AXIS2-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476658
]
Shawn J. Dyck commented on AXIS2-2254:
--
Please see error listed below:
Problem parsing referenced XML
Howdy All,
I've just commited a new metadata DescriptionFactory method that takes a
single annotated web service implementation class and returns a single
ServiceDescription. Commited revision 512819.
The returned ServiceDescription will have an AxisService hierachy created
and attached.
[
https://issues.apache.org/jira/browse/AXIS2-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476668
]
Shawn J. Dyck commented on AXIS2-1993:
--
would you please include this patch in the NIGHTLY-SPANSHOT ?
[
https://issues.apache.org/jira/browse/AXIS2-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476673
]
Shawn J. Dyck commented on AXIS2-2254:
--
Please include http://issues.apache.org/jira/browse/AXIS2-1993 patch in
Hi Brian,
I think it's important that if this (message being swallowed) is
happening, that we make it very obvous. What do you think about
logging at a higher level than debug?
David
On 28/02/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: pradine
Date: Wed Feb 28 09:43:07 2007
New
[
https://issues.apache.org/jira/browse/AXIS2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476715
]
Manoj Khangaonkar commented on AXIS2-2116:
--
Hi Deepal,
To integrate 1749 with 2116, I ran into a small
[
https://issues.apache.org/jira/browse/AXIS2-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roy A. Wood Jr. updated AXIS2-2216:
---
Attachment: DBC_0228_patch.txt
Ignore the first attachment to this issue. This 2nd
[
https://issues.apache.org/jira/browse/AXIS2-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2272.
-
Resolution: Fixed
Patch applied. Committed revision 513095.
Thanks, Dustin!
Update to
+1 but I'm confused why we'd remove this exception .. if someone sends a
response message again we should be saying nope been there done that
already back to the sender. If you eat the exception and log it they have
no info. What is broken about the old code?
Sanjiva.
David Illsley wrote:
The toString() methods in the metadata description package should not cause
fatal errors
Key: AXIS2-2273
URL: https://issues.apache.org/jira/browse/AXIS2-2273
[
https://issues.apache.org/jira/browse/AXIS2-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dustin Amrhein updated AXIS2-2273:
--
Attachment: patch2.txt
The toString() methods in the metadata description package should not
[
https://issues.apache.org/jira/browse/AXIS2-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476826
]
Amila Chinthaka Suriarachchi commented on AXIS2-1993:
-
What you get as the systemID is the
[
https://issues.apache.org/jira/browse/AXIS2-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476828
]
Amila Chinthaka Suriarachchi commented on AXIS2-1993:
-
Please ignore my earlier comment. I have
[
https://issues.apache.org/jira/browse/AXIS2-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476830
]
Deepal Jayasinghe commented on AXIS2-2212:
--
At the initial development time we thought not to terminate
[
https://issues.apache.org/jira/browse/AXIS2-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2257.
--
Resolution: Duplicate
2258
Documentation and Sample for EJB Provider
[
https://issues.apache.org/jira/browse/AXIS2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Khangaonkar updated AXIS2-2116:
-
Attachment: axis2-1749and2116.txt
Attached a patch that include both 1749 and 2116
[
https://issues.apache.org/jira/browse/AXIS2-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Khangaonkar updated AXIS2-1749:
-
Attachment: axis2-1749and2116.txt
Attached a patch that includes 1749 and 2116.
Manoj
Hi Jeff ;
Great , I will have a look at than will use that for POJO annotation.
One small question , do you have any idea on generating Schemas for the
annotated service ?
Thanks
Deepal
Howdy All,
I've just commited a new metadata DescriptionFactory method that takes a
single annotated web
Axis 2 as a client, access https:// doesn't work
Key: AXIS2-2274
URL: https://issues.apache.org/jira/browse/AXIS2-2274
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/AXIS2-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476843
]
Manoj Khangaonkar commented on AXIS2-2239:
--
Hi,
Working on this. Will provide a patch shortly.
Anything
I think the addition of annotations itself justifies 1.2 .. that's a
major userbility improvement.
Isn't that independent of JAX-WS?
hmm ,it is YES and No answer . The issue is pojo annotation uses JAX-WS
API as well as metedat module , in the meantime there is a dependency to
JAX-WS as well
[
https://issues.apache.org/jira/browse/AXIS2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476846
]
Deepal Jayasinghe commented on AXIS2-2116:
--
Hi Manoj;
I tried to apply your patch , but I got a number of
[
https://issues.apache.org/jira/browse/AXIS2-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476853
]
Angel Todorov commented on AXIS2-2212:
--
Hi Deepal,
What do you mean by terminate Axis2? Axis2 is not
40 matches
Mail list logo
