Russell,
Thanks for fixing those tests. What's the use of WSDL2Java generating those
constructors if their signatures can't be relied upon not to change?
Glyn
Ah, well so much for that idea then. :)
> -Original Message-
> From: Melissa Turner [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 21, 2002 5:22 PM
> To: [EMAIL PROTECTED]
> Subject: Re: complexType extending a simpleType
>
>
> On Thursday, February 21, 2002, at 01:43 , R J Sch
This issue only arises when you write code to a given binding, and then
pass the WSDL for that binding AND YOUR CODE somewhere else. If that
somewhere-else were going to write their own code based on their own
bindings, there'd be no problem (I think).
I suspect we see this problem when we cross
Although as was pointed out, it's not possible to extend the primitive wrapper types
or String, I think InternationalPrice indeed IS-A String - extension in schema is just
like inheritance in programming languages. It just so happens InternationalPrice has
another attribute field as well as b
glyn02/02/22 05:55:39
Modified:java/src/javax/xml/rpc Call.java
Log:
Superficial comment changes.
Revision ChangesPath
1.8 +83 -63xml-axis/java/src/javax/xml/rpc/Call.java
Index: Call.java
=
Title: Default type mapping (another attempt)
I'm trying it again.
The WSDL2Java and Java2WSDL take care of properly mapping http://my.app.corp.etc namespaces back to and from etc.corp.app.my packages (see code fragments below). SOAP processing pipeline does not. It always assumes the typema
rsitze 02/02/22 06:49:15
Modified:java/docs developers-guide.html integration-guide.html
Log:
Updated log/trace section
Revision ChangesPath
1.8 +222 -1xml-axis/java/docs/developers-guide.html
Index: developers-guide.html
===
Title: Default type mapping (another attempt)
-1
I
don't think this is the right solution to this.
IMO,
we shouldn't map java types to individual namespaces per package, but if we want
a "deployment-free" typemapping (i.e. one where the QName of the type gives us
enough info to figure ou
rsitze 02/02/22 07:07:33
Modified:java/src log4j.properties
Log:
Allow INFO messages: many calls to System.out.println have
been replaced with calls to log.info. Also prep'd for file
logging.
Revision ChangesPath
1.4 +3 -3 xml-axis/java/src/log4j.propert
How will JAXM & Axis play together?
Will Axis adopt the JAXM API for send & recv messsages/responses?
Thanks
__
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games
http://sports.yahoo.com
rsitze 02/02/22 07:16:52
xml-axis/java/test/lib - New directory
rsitze 02/02/22 07:19:43
Added: java/test/lib jakarta-oro-2.0.5.jar
Log:
Jakarta ORO is a Regular Expression engine/compiler.
Revision ChangesPath
1.1 xml-axis/java/test/lib/jakarta-oro-2.0.5.jar
<>
rsitze 02/02/22 07:21:18
Modified:java/test/utils TestMessages.java
Log:
Replaced '\n' with attribute initialized from system property.
Revision ChangesPath
1.6 +6 -3 xml-axis/java/test/utils/TestMessages.java
Index: TestMessages.java
=
Title: Message
Glen,
so then if we change it to , then do you agree it's
good to have the "deployment-free" typemapping in
Axis?
I'm
not sure it's going to interop well with .NET... With the current http://my.app.corp.etc mapping it interops just
fine...
Also I
thought XML Schema sugge
rsitze 02/02/22 07:37:48
Modified:java/src/org/apache/axis AxisEngine.java Message.java
Part.java SOAPPart.java
java/src/org/apache/axis/attachments
BoundaryDelimitedStream.java
ManagedMemoryDataSour
rsitze 02/02/22 07:39:04
Modified:java build.xml
java/test/utils TestSrcContent.java
Log:
Updated tests to check for inappropriate use of System.{out|err}.println
Revision ChangesPath
1.113 +9 -0 xml-axis/java/build.xml
Index: build.xml
Title: Message
Glen,
Moreover, will
contradict JAXRPC 0.7 PRD2 Appendix 18.
The
same spec also says
The JAX-RPC specification requires the namespace definitions in
the WSDL document
to be mapped in an application specific manner. A Java to WSDL
mapping tool is
required to support the c
+1 to leaving the constructor in with a comment.
--
Tom Jordahl
Macromedia
-Original Message-
From: Russell Butek [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 22, 2002 8:38 AM
To: [EMAIL PROTECTED]
Subject: Re: cvs commit: xml-axis/java/test/wsdl/interop3/groupE/client
InteropTestD
I completely agree Simon.
But until the Axis runtime is "xml-aware" the only place to put this meta
information is on the skeleton/bean classes.
So I agree with the solution for the current version of Axis. If/when the
Axis runtime is made "xml-aware", this meta information
should be removed.
rsitze 02/02/22 10:12:39
Modified:java/docs developers-guide.html
Log:
Rearranged text and added details on overriding logging properties under section on
debugging.
Revision ChangesPath
1.9 +120 -49 xml-axis/java/docs/developers-guide.html
Index: develope
+1 to getting rid of the full constructor in the generated bean classes.
Now that Tom and Glen have added attribute support, the attribute
parameters also appear in the full constructor list.
This is a bad idea since attributes are supposed to be order independent.
Since it is not a dependable
In the future, we may add support for facets.
This may be implemented as assertion checks within the setter methods.
If an assertion fails, the setter would be expected to throw an exception
indicating an illegal argument.
So it is reasonable to insist that a bean be constructed with a default
co
+1 to getting rid of the full constructor.
Now that attributes are involved, you've convinced me that we should not
have that constructor. Also, if we start dealing with default values the
constructor becomes even worse: a constructor parameter MUST have a value,
even if it's null; what does nu
butek 02/02/22 10:51:50
Modified:java/test/wsdl Wsdl2javaTestSuite.xml
java/test/wsdl/interop3 Import2TestCase.java
Log:
Added interop round 3 absolute import2 test.
Revision ChangesPath
1.78 +40 -0 xml-axis/java/test/wsdl/Wsdl2javaTestSuite.xml
I modified the comprehensive test in my sandbox to exploit the attribute
support.
The test works, but I the properties that I marked as attributes are still
sent over the
wire as elements.
Could you explain why you turned off the serialization of attributes for
soap encoding?
I looked in the SOAP
Attribute encoding is turned of because I was lead to believe
attributes are not allowed in SOAP encoding.
--
Tom Jordahl
Macromedia
-Original Message-
From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 22, 2002 1:57 PM
To: [EMAIL PROTECTED]
Subject: Question abou
I am hesitant about removing the full constructor.
It would be easy to remove the attribute elements from the argument list.
In fact, I might argue that it is a bug that I let them be generated that way.
The argument about enforcing restriction in set methods is a good one however.
My vote: +
It is possible for an element to have a default= attribute. We just don't
support it yet.
So elements have the same problems as attributes.
Unless I get a disagreement, I am going to remove the full constructor
emission and
fix the testcases.
Rich Scheuerle
XML & Web Services Development
512-
rsitze 02/02/22 11:48:26
Modified:java/docs developers-guide.html
Log:
Clarification on logging and i18n
Revision ChangesPath
1.10 +12 -6 xml-axis/java/docs/developers-guide.html
Index: developers-guide.html
==
tomj02/02/22 12:03:03
Modified:java/src/org/apache/axis/message MessageElement.java
Log:
Fix logic to prevent emitting an encoding style of ""
unless we are overriding a parent scope.
Revision ChangesPath
1.78 +8 -2 xml-axis/java/src/org/apache/axis/messa
tomj02/02/22 12:04:43
Modified:java/src/org/apache/axis/encoding/ser BeanSerializer.java
Log:
Add defensive code to prevent initializing an attributes object
in getObjectAttributes() with a null.
Revision ChangesPath
1.8 +6 -2
xml-axis/java/src/org/apac
rsitze 02/02/22 12:32:11
Modified:java/src/org/apache/axis/client Call.java
java/src/org/apache/axis/handlers JWSProcessor.java
SimpleAuthorizationHandler.java
java/src/org/apache/axis/server AxisServer.java
java/src/
gdaniels02/02/22 14:35:41
Added: java/test/wsdl/interop3 RPCEncD.xml
Log:
Ant file for RPCEncoding test (round 3D)
Revision ChangesPath
1.1 xml-axis/java/test/wsdl/interop3/RPCEncD.xml
Index: RPCEncD.xml
=
scheu 02/02/22 15:11:35
Modified:java/src/org/apache/axis/encoding/ser BeanDeserializer.java
BeanSerializer.java
java/src/org/apache/axis/wsdl/fromJava Types.java
java/src/org/apache/axis/wsdl/toJava
JavaCom
I've reworked AdminClient to use the logging API. Therefore I've removed
the parameterized constructors for streams of various sorts.
Any problems?
***
Richard A. Sitze[EMAIL PROTECTED]
CORBA Interoperability & WebServices
IBM WebSphere Deve
Hmm. I have no problem with it using the logging API, but now if you want to do a
simple "load up an AdminClient, run it, and capture the output" you need to muck with
logging configuration? That seems a little suboptimal to me. If you set it up so
that the APIs still work the old way, and t
scheu 02/02/22 16:48:28
Modified:java/samples/addr Main.java
java/src/org/apache/axis/wsdl/toJava
JavaComplexTypeWriter.java
java/test/wsdl/arrays PersonalInfoBookServiceTestCase.java
java/test/wsdl/inout DetailedIno
Russell Butek wrote:
> This is why I said Richard ALMOST convinced me. Sure, log.debug is shorter
> to type than System.out.println. But in order to use it I have to turn
> debugging on, and grep for my stuff in a potentially huge pile of output.
> And then when I'm done I have to remember to t
38 matches
Mail list logo
