Hello.
Is it possible to review and perhaps apply Michaels patches?
Greetings
Franz
Original-Nachricht
Betreff:
[jira] Updated: (AXISCPP-977) axiscpp engine wsdl2ws:
In server response, basic array element no namespace prefix added
Michael Xiong says, he has a fix for this:
citation
This problem is completely the same with AXISCPP-972
AXISCPP-973(for 1.6beta) which I've already reported on JIRA.
http://issues.apache.org/jira/browse/AXISCPP-972
http://issues.apache.org/jira/browse/AXISCPP-973
And it was indeed an old
A glimpse at AXISCPP-716 would be most welcome.
Greetings
Franz
Nadir Amra schrieb:
I will be looking into thisjust trying to clean up some other things
first. I will also be looking at other jira issues and seeing what I can
fix. But all this takes time so please be patient.
Hello,
My posting is admittedly nor very readable, but would it be possible to
comment at least at the three points at the end?
The problem pertains to AXISCPP-716 (info by Adrian) btw.
Thanks and best regards
Franz
Franz Fehringer schrieb:
Hello Adrian,
I looked into the relevant
parsing schemas read from url need to be supported. Currently it only reads
imported schemas from doc base uri
--
Key: AXIS2C-201
URL:
array of Strings changed to element name=varArray type=xsd:string/ in
java2wsdl
-
Key: AXIS-2519
URL: http://issues.apache.org/jira/browse/AXIS-2519
Project: Apache Axis
Type: Bug
orga.apache.axis.client.Call clears the operation's return type information in
addition to clearing the operation's parameter information in
removeAllParameters
Please check now..
-- dims
On 7/7/06, Ajith Ranabahu [EMAIL PROTECTED] wrote:
Hi,
I think I know the problem here.
I modified the XMLSchema project to add a few new methods and fix some
bugs. However the XMLSchema had two builds for maven 1 and maven 2 and
these build scripts were putting the
New JMS Implementation - ConnectionFactory cache for client
---
Key: AXIS2-869
URL: http://issues.apache.org/jira/browse/AXIS2-869
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Components: transports
Hello,
I can now build the adb-codegen module,
but I now get a build error in the integration module. Looking at the code
it seems that the class modules\integration\target\rpc-test2\src\com\example\www\ServiceNameStub.java
is making the following method call:
Attachment deserialization doesnt work with multiref's
--
Key: AXIS-2521
URL: http://issues.apache.org/jira/browse/AXIS-2521
Project: Apache Axis
Type: Bug
Components: Serialization/Deserialization
Hi all,
I'm trying to call a web service with the Non-Blocking API
My code is :
OMElement payload = doc;
Options options = new Options();
options.setTo(targetEPR);
options.setAction(printHello);
hi,
For the async calls to work WS-Addressing needs to be there. Basically
you have to have the addressing module in your modules directory (or
in your class path if you don't have a repo) to be engaged.
Ajith
On 7/7/06, Jean-Michel PATER [EMAIL PROTECTED] wrote:
Hi all,
I'm trying to call a
Hi,
In the available modules, there is addressing-1.0, and in the
available services, for my service it seems that addressing-1.0 is
engaged.
INFO: Starting Servlet Engine: Apache Tomcat/5.5.17
Jul 7, 2006 3:42:14 PM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Brian,The build was sucessfull for me. Maybe try again.thanks Ajith and dims for the supportRegards,RajithOn 7/7/06, Brian De Pradine
[EMAIL PROTECTED] wrote:
Hello,
I can now build the adb-codegen module,
but I now get a build error in the integration module. Looking at the code
it seems that
I found how to do it looking in the following message :
[Axis2] How can I engage a module at the client side?
Thanks
Jean-Michel PATER wrote:
Hi,
In the available modules, there is addressing-1.0, and in the
available services, for my service it seems that addressing-1.0 is
engaged.
JavaServiceDesc.getOperationsByQName doesn't correctly handle empty list of
operations
--
Key: AXIS-2522
URL: http://issues.apache.org/jira/browse/AXIS-2522
Project: Apache Axis
Hi,
I tried again with revision 419900,
and I got the same problem with the integration module :-(
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
I am planning to use AXIS2 within J2EE Security environment. Does AXIS2 currently support J2EE security (with Security Manager enabled)? If yes, Could anyone please provide me some detail information of how to make/enable AXIS2 to work within J2EE Security environment?
One of examples of using
JAXWS: MetaDataQuery (MDQ) - Tool for merging and checking annotation
information with other deployment descriptors
---
Key: AXIS2-872
URL:
Wrap and unWrap JAXB Objects using JAXBWrapperTool
---
Key: AXIS2-873
URL: http://issues.apache.org/jira/browse/AXIS2-873
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Components: jaxws
Reporter: Nikhil
JAXWS: handler framework - HandlerResolver implementation, HandlerProcessor
Key: AXIS2-874
URL: http://issues.apache.org/jira/browse/AXIS2-874
Project: Apache Axis 2.0 (Axis2)
Type: New
Proxy Implementation for JAXWS
--
Key: AXIS2-875
URL: http://issues.apache.org/jira/browse/AXIS2-875
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Components: jaxws
Reporter: Nikhil Thaker
This will be a new Feature for
[ http://issues.apache.org/jira/browse/AXIS2-876?page=all ]
Rich Scheuerle updated AXIS2-876:
-
Component: jaxws
JAXWS: Message Subsystem
Key: AXIS2-876
URL: http://issues.apache.org/jira/browse/AXIS2-876
JAXWS: Message Subsystem
Key: AXIS2-876
URL: http://issues.apache.org/jira/browse/AXIS2-876
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Components: jaxws
Reporter: Rich Scheuerle
Assigned to: Rich Scheuerle
I am currently
[ http://issues.apache.org/jira/browse/AXIS2-877?page=all ]
Ruchith Udayanga Fernando moved ADDR-35 to AXIS2-877:
-
Project: Apache Axis 2.0 (Axis2) (was: Addressing)
Key: AXIS2-877 (was: ADDR-35)
Axis2 1.0 generates
[ http://issues.apache.org/jira/browse/AXIS2-877?page=all ]
Ruchith Udayanga Fernando closed AXIS2-877:
---
Resolution: Duplicate
http://issues.apache.org/jira/browse/AXIS2-870
Axis2 1.0 generates incorrect WSDL
27 matches
Mail list logo
