classes generated by wsdl2java don't compile
Key: AXIS-2164
URL: http://issues.apache.org/jira/browse/AXIS-2164
Project: Apache Axis
Type: Bug
Components: WSDL processing
Versions: current (nightly)
Reporte
[
http://issues.apache.org/jira/browse/AXIS-2155?page=comments#action_12317594 ]
Tom Jordahl commented on AXIS-2155:
---
We can't do this in Java, as xsd:int is represented as Integer, not a class.
Emitting a JavaBean class for minoccurs=0 element wil probabl
[
http://issues.apache.org/jira/browse/AXIS2-118?page=comments#action_12317595 ]
Ruchith Udayanga Fernando commented on AXIS2-118:
-
This is what I planed to do to add XML version and chaset encoding to the
OMDocument
- Create an interface
[ http://issues.apache.org/jira/browse/AXIS2-42?page=all ]
Eran Chinthaka reassigned AXIS2-42:
---
Assign To: Deepal Jayasinghe (was: Jaliya Ekanayake)
> Message Context Serialization Support
> -
>
> Key: AXIS
[
http://issues.apache.org/jira/browse/AXIS2-93?page=comments#action_12317597 ]
Ajith Harshana Ranabahu commented on AXIS2-93:
--
It seems to me that once the Ant task is complete and running we can have a
generate + compile test case. However th
[ http://issues.apache.org/jira/browse/AXIS2-32?page=all ]
Chamil Thanthrimudalige reassigned AXIS2-32:
Assign To: Chamil Thanthrimudalige
> writing a maillet for Mail transport
>
>
> Key: AXIS2-3
[
http://issues.apache.org/jira/browse/AXIS2-42?page=comments#action_12317600 ]
Deepal Jayasinghe commented on AXIS2-42:
Serialization of Message Context includes number of changes to be done.
1. Has to serialize bottom to top (Message Context t
Hi all,As you all know we have been successfully using XMLBeans for
data binding in Axis2. However right now, we seem to have some problems
with XMLBeans.1. Some schemas are not compiled right by XMLBeans.Consider the following schema snippet.
http://www.w3.org/2001/XMLSchema" targetNamespace="http
[
http://issues.apache.org/jira/browse/AXIS2-93?page=comments#action_12317601 ]
Eran Chinthaka commented on AXIS2-93:
-
Shall we set the target of having a generate + compile test case for 0.95, and
the rest to 1.0 ?
> Axis2 build do not have test cases
[ http://issues.apache.org/jira/browse/AXIS2-112?page=all ]
Chathura Herath updated AXIS2-112:
--
Priority: Minor (was: Major)
> Doclitparams Interoperability Test failed
> -
>
> Key: AXIS2-112
>
[ http://issues.apache.org/jira/browse/AXIS2-112?page=all ]
Chathura Herath reopened AXIS2-112:
---
Assign To: (was: Chathura Herath)
The multipart RPC literal issue is fixed. There is some issue with the interop
where the interop does not func
[ http://issues.apache.org/jira/browse/AXIS2-55?page=all ]
Eran Chinthaka resolved AXIS2-55:
-
Resolution: Fixed
Fixed with Srinath's first option.
We have getDefaultEnvelope method which comes with an Envelope with Header and
Body.
> Children orde
To elaborate on the #2, when we try to code gen from the AntTask the
code failed giving an
Initialization exception. It is fixed when we add the ClassLoader that
include the xml beans jar to the TCCL (Thread Context ClassLoader).
This works fine when it is only Ant, but failed when it is maven!
I
[ http://issues.apache.org/jira/browse/AXIS2-51?page=all ]
Eran Chinthaka resolved AXIS2-51:
-
Resolution: Fixed
Fixed.
> blocking access to some OMElement methods within SOAPElements
> -
>
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project ws-axis-xerces-HEAD has an issue affecting its community integration.
This issue
Sorry for the late response.
Glen's idea is pretty slick and is a good idea. I think I slightly
prefer the Stub being a parent class I think.
I know you Axis 2 guys aren't worried about JAX-RPC, but we could at
least provide the few (username/password/property) _get/_set methods
that they requi
Since this is a "wrapped" doc/lit WSDL, it is expected that the request
message will be treated as a sequence of parameters, and a Stub will be
generated with a 1 argument function: echoString(String inputString).
I did this work for Axis 1.0. Fun stuff. I would say that to provide
the minimum
+1 to solving the cleanup problem.
It would also be great to have a size threshold - anything over X
K-bytes will be streamed to disk, otherwise we handle it in memory. A
reasonable default should be used and of course it should be user
configurable.
Tom Jordahl
Macromedia Server Development
I think Ashutosh was talking about the character set encoding in the XML
declaration at the top of the SOAP XML to something other than utf-8.
I was never quite clear why users wanted to turn on/off the XML
declaration in Axis 1.x but they did (so be prepared). Being able to
set the charset of t
Hi,
I am trying to
communicate with a J2EE webservice running on Bea Weblogic webserver 8.1
SP3. The client side has Axis C++. I am getting error while reading the
SOAP response sent by the webservice. The exception occurs on calling
getElementAsString function
(after checkMessage return
I really don't agree that support for wrapped services is Minor
Tom Jordahl
Macromedia Server Development
-Original Message-
From: Srinath Perera (JIRA) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 02, 2005 9:14 PM
To: axis-dev@ws.apache.org
Subject: [jira] Updated: (AXIS2-109)
[
http://issues.apache.org/jira/browse/AXIS2-109?page=comments#action_12317618 ]
Tom Jordahl commented on AXIS2-109:
---
Since this is a "wrapped" doc/lit WSDL, it is expected that the request
message will be treated as a sequence of parameters, and a Stub wi
On Tue, 2005-08-02 at 21:31 -0500, Aleksander Slominski wrote:
> >
> >
> why not to follow XML model and in particular XML infoset? SOAP
> envelope is EII so it can have DII as parent and DII contains all this
> stuff including declaration, encoding etc - see:
> http://www.w3.org/TR/xml-infoset/#
+1 to making WSDL2Java look much more like Axis 1.x.
Use the Axis command line parser - please do not bring in another jar
for this as we went down that road in 1.0 and it was a pain. In fact I
believe the parser in 1.x *is* the commons implementation.
Tom Jordahl
Macromedia Server Development
On Thu, 2005-08-04 at 14:59 +0600, Ajith Ranabahu wrote:
> Hi all,
> As you all know we have been successfully using XMLBeans for data
> binding in Axis2. However right now, we seem to have some problems
> with XMLBeans.
>
> 1. Some schemas are not compiled right by XMLBeans.Consider the
> followi
On Wed, 2005-08-03 at 18:46 +0600, Srinath Perera wrote:
> Nope it is used by SimpleHTTPServer .. do not remove
?? Why can't SimpleHTTPServer get that behavior from Commons HTTP stuff?
Sorry if I'm missing something obvious.
Sanjiva.
Hi Ajith!
1. Some schemas are not compiled right by XMLBeans.Consider the following
schema snippet.
http://www.w3.org/2001/XMLSchema"; targetNamespace="
http://SimpleTest.org/xsd";>
The inputString element should belong to the targetNamespace. However the
generated EchoStringDocument
Commons http is Only client side stuff
Srinath
On 8/4/05, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-08-03 at 18:46 +0600, Srinath Perera wrote:
> > Nope it is used by SimpleHTTPServer .. do not remove
>
> ?? Why can't SimpleHTTPServer get that behavior from Commons HTTP stuff
You can't get anywhere near a 1.0 release (Beta or otherwise) without
Java2WSDL functionality, right?
Is anyone working on this? WSDL 2.0 support would be a *huge* incentive
for non-Axis users to give Axis2 a try. Of course you need Java2WSDL
because nobody knows how to write WSDL 2.0 yet...
M
Hi Tom;
I make it minor due to 2 reasons
1) It is to be handled after the 0.95 (we say we need to fix all that
is major for 0.95 so that the major is relative! )
2) I understood the bug to mean "we need a make the client stub not
have xml beans specific things", have I misunderstood it?
Thanks
S
On Thu, 2005-08-04 at 08:30 -0400, Tom Jordahl wrote:
> You can't get anywhere near a 1.0 release (Beta or otherwise) without
> Java2WSDL functionality, right?
>
> Is anyone working on this? WSDL 2.0 support would be a *huge* incentive
> for non-Axis users to give Axis2 a try. Of course you need
On Thu, 2005-08-04 at 08:30 -0400, Tom Jordahl wrote:
> Maybe WSO2 (Sanjiva's new company) will step up and do the WSDL 2.0
> work?
> :-)
Forgot to reply to this ..
We could but then we'd be overlapping with Woden. Unfortunately Woden is
a bit slow off the block and its not clear they'll do a S
Sanjiva,
Java2WSDL means more that the commandline tool. It is used at runtime
to generate WSDL from a composite of information from typemapping,
deployment descriptors (maybe annotations) etc. Basically if we drop a
POJO, we should be able to generate a wsdl for it at runtime. Yes,
we'd have to l
Irrespective of the major/minor discussion, I'd like to discuss a
principle that Tom has indicated in this thread: the shape of the stub
should be independent of the data binding framework.
IMO we shouldn't do that: if its a standard-compliant databinding
framework (e.g., a JAXB2 one or a JAX-RPC
I feel that a fairly reliable WSDL2Java (or WSDL2Code) is a must for
1.0 release. The current implementation of our WSDL2Code was not
robust enough to handle a wsdl like amazan or paypal, when i checked
last time.
Also we don't seem to generate a JUnit testcase.
- venkat
On 8/4/05, Sanjiva Weera
Tom,
See http://marc.theaimsgroup.com/?l=axis-dev&m=112239417727592&w=2
-- dims
On 8/4/05, Tom Jordahl <[EMAIL PROTECTED]> wrote:
>
> I think Ashutosh was talking about the character set encoding in the XML
> declaration at the top of the SOAP XML to something other than utf-8.
>
> I was never
I'll add my two cents--a few months ago, I had a project where we were sending
SOAP messages to an application using Tibco BusinessWorks' built-in SOAP
support to receive them. We ran into BOM issues when we used UTF-8, and
finally switched to UTF-16 to get it to work. It's probable that there
[
http://issues.apache.org/jira/browse/AXIS2-118?page=comments#action_12317629 ]
Davanum Srinivas commented on AXIS2-118:
+1 from me.
> OMDocument must have XML Version and Char encoding
> --
>
>
Hi Eran,
What is being done for detaching the body from SOAPEnvelope? I think we
are allowing detaching of the body; then should not accessing body after
that return null, so that user can add body again if we want. Currently
an exception comes up.
Or we should not allow detaching the body at all.
Venkat,
all-tests failing with these changes. can you please recheck?
thanks,
dims
On 3 Aug 2005 10:26:28 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> venkat 2005/08/03 03:26:28
>
> Modified:java/src/org/apache/axis/encoding
> DeserializationContext.j
[ http://issues.apache.org/jira/browse/AXIS2-118?page=all ]
Ruchith Udayanga Fernando resolved AXIS2-118:
-
Resolution: Fixed
Introduced OMDocument interface and OMDocumentImpl implements OMDocument.
Introduced methods to serialize an OMD
[
http://issues.apache.org/jira/browse/AXIS-2155?page=comments#action_12317654 ]
Peter Wisnovsky commented on AXIS-2155:
---
I'm not sure what you mean.
.NET doesn't generate a separate class, just an extra indicator attribute in
the owning class. So
[ http://issues.apache.org/jira/browse/AXIS-2139?page=all ]
Davanum Srinivas reopened AXIS-2139:
Venkat,
Please review the fix. i rolled back the change to
src/org/apache/axis/encoding/DeserializationContext.java
thanks,
dims
> SAX recorder is d
On Thu, 2005-08-04 at 09:05 -0400, Davanum Srinivas wrote:
> Sanjiva,
>
> Java2WSDL means more that the commandline tool. It is used at runtime
> to generate WSDL from a composite of information from typemapping,
> deployment descriptors (maybe annotations) etc. Basically if we drop a
> POJO, we s
I agree completely that you need to pass classes compatible with the
data binding framework for any complex objects. But based on my JibxSoap
experiences with adding wrapped support (still in progress), I suspect
the best way of handling this may be to build in "canned"
serializer/deserializers
axis-wsdl2java used with 'extension base' is producing wrong number of
constructor arguments
Key: AXIS-2165
URL: http://issues.apache.org/jira/browse/AXIS-2165
Project: Apache Axis
[
http://issues.apache.org/jira/browse/AXIS-2145?page=comments#action_12317670 ]
Luis Rivera commented on AXIS-2145:
---
Well, I built the latest axis from the CVS and commons-discoery from the svn
repo. The errors regarding the class loading creation are fi
[
http://issues.apache.org/jira/browse/AXIS-2145?page=comments#action_12317672 ]
Davanum Srinivas commented on AXIS-2145:
I tried using just the regular HTTPSender (not CommonsHTTPSender). Could you
try that first? just to see if it has the same pro
[
http://issues.apache.org/jira/browse/AXIS-2145?page=comments#action_12317673 ]
Davanum Srinivas commented on AXIS-2145:
also look for any typos, extra jars, archive tag etc and make sure you are
using only the jars that are signed and nothing else
[
http://issues.apache.org/jira/browse/AXIS-2139?page=comments#action_12317706 ]
Davanum Srinivas commented on AXIS-2139:
I was thinking about thisCould you please attach a test for "breaks digital
signatures becuase the MessageElement DOM is in
On Aug 4, 2005, at 1:59 AM, Ajith Ranabahu wrote:
Hi all,
As you all know we have been successfully using XMLBeans for data
binding in Axis2. However right now, we seem to have some problems
with XMLBeans.
1. Some schemas are not compiled right by XMLBeans.Consider the
following schema sni
Sanjiva Weerawarana wrote:
On Tue, 2005-08-02 at 21:31 -0500, Aleksander Slominski wrote:
why not to follow XML model and in particular XML infoset? SOAP
envelope is EII so it can have DII as parent and DII contains all this
stuff including declaration, enco
Thilina,
Is there a relationship with this to Axis2-95 ? If yes, please
comment/resolve that issue.
-- Chinthaka
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 05, 2005 9:20 AM
> To: axis-cvs@ws.apache.org
> Subject: svn commit: r230387 -
I'm closing it :)On 8/5/05, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
Thilina,Is there a relationship with this to Axis2-95 ? If yes, pleasecomment/resolve that issue.-- Chinthaka> -Original Message-> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]> Sent: Friday, August 05, 2005 9:20 AM
[ http://issues.apache.org/jira/browse/AXIS2-100?page=all ]
Deepal Jayasinghe reassigned AXIS2-100:
---
Assign To: Deepal Jayasinghe (was: Srinath Perera)
> Separating sample and test cases form Sample module
> ---
[ http://issues.apache.org/jira/browse/AXIS2-100?page=all ]
Deepal Jayasinghe resolved AXIS2-100:
-
Resolution: Fixed
Moved intregration test cases into intregration module and keep all the sample
in sample module
> Separating sample and test c
Arggg,I forgot that issue. I fixed the things I've mentioned in the issue
only. Thanks for reminding it. Will fix it now.
-- EC
> -Original Message-
> From: Shahi, Ashutosh [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 04, 2005 8:42 PM
> To: axis-dev@ws.apache.org
> Subject: RE: [jir
[
http://issues.apache.org/jira/browse/AXIS2-32?page=comments#action_12317743 ]
Chamil Thanthrimudalige commented on AXIS2-32:
--
The requirement here is to get the Axis2 mail transport working with Apache
James, using Apache James mailets.
> wr
[ http://issues.apache.org/jira/browse/AXIS2-95?page=all ]
Thilina Gunarathne resolved AXIS2-95:
-
Resolution: Fixed
A testcase was written for this
Axis2 only accepts SwA messages...Axis2 sends MTOM messages only... We assume
SwA endpoints
Hi Axis2 Developers/Users,
I'd like to propose to
release Axis2 0.95 on next Friday (12-08-2005) and to have a code freeze on
next Tuesday (9-8-2005).
Followings are MUST do things
before the release: 116, 112, 103, 100, 95, 82, 55, 51.
Guys please give us a
helping hand to fix th
Sorry, re-sending with Axis2
prefix………
Hi Axis2 Developers/Users,
I'd like to propose to
release Axis2 0.95 on next Friday (12-08-2005) and to have a code freeze on
next Tuesday (9-8-2005).
Followings are MUST do
things before the release: 116, 112, 103, 100, 95, 82, 55, 51.
G
Hi all;
The declaration of parameters in Axis2 to be done as follows
parameter value
I can not see any use case of
locked="xsd:false" attribute there ,
so can I remove that.
Thoughts ...
Thanks, Deepal~Future
is O
My sincere thought is... if the version 1.0 (such a darn powerful
number that it is) is out, people already frame impressions about
Axis2 in general. And if it's out without being solid enough, first
impressions on Axis2 can be not so welcome ones. We will have to face
tough times advertising later
63 matches
Mail list logo
