Currently SOAPBody.getBytes() just calls getBytes() on the string object.
This will use VM's default character set. That happens to be "Cp1252" on
most systems, so any non LATIN characters in will get corrupt.
Likewise, when creating a String from the raw bytes default encoding is
used.
I think
Which version of axis are you running? I just tried it this morning with a
build from a couple days ago and it worked just fine.
Russell Butek
[EMAIL PROTECTED]
David Altenburg <[EMAIL PROTECTED]> on 02/04/2002 06:31:08 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subje
>I have been playing with Attachment code trying to improve it a little,
and
>fill in the missing parts/TODOs.
>Doing that I am not understanding 2 basic things in the design.
>1) Why would you want to compile Axis without attachment support? Doing so
>creates, in my opinion, unneeded code complex
>Attachment data stored in ManagedMemoryDataSource is deleted (or at least
>marked deleted), as soon as message has been serialized.
>While in most cases you will not want to access the data after you have
sent
>out the message, why force a delete possibly too early?
>In case where a service is tr
Well, he didn't sway me as much. :-)
How about the rule: "the service implementation name ends with the string
'ServiceImpl'".
I also am not a fan of having 2 "Impl" files. But I don't have any really good
replacement names off the top of my head. Can we change one of the other file names
I still stand by my argument, but I don't feel as strongly about it today.
Two reasons:
1. I just went through 15 tests and changed names from XXX to
XXXServiceImpl and all but 2 have the string "ServiceServiceImpl". Yuck.
2. I can't come up with a decent replacement for "Impl".
Your suggestio
The only simpleTypes that are currently supported are enumerations.
We will add your request to our todo list.
Thanks,
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
Just thought I'd inform y'all. We (Tom and Rich and Richard and I) decided
to call this new service implementation a "Locator". It may seem a bit
obscure at first, but the service stanza contains location information; and
it makes a lot of sense when you look at the client code:
AddressBook ab
Igor,
You wrote:
>Another important element is to allow config providers to implement or not
to implement versioning.
Then the engine would have to be able to cope correctly with both kinds of
providers and so it would be worse off than today. I think it would be much
better if all providers
Igor,
You wrote:
>Will EngineConfigurationFactory be a parameter to AxisEngine constructor?
I had to think hard about this, but my intuition is that it would be better
to pass an EngineConfiguration. Perhaps we should revisit this after I've
made my changes as I think the trade-offs will be mo
butek 02/02/05 08:22:41
Modified:java/docs user-guide.html
java/samples/addr Main.java
java/samples/userguide/example6 Main.java
WidgetPriceServiceTestCase.java
java/src/javax/xml/rpc JAXRPCException.java Service.jav
glyn02/02/05 08:25:39
Modified:java/samples/transport/tcp AdminClient.java
java/src/org/apache/axis/client AxisClient.java
java/src/org/apache/axis/configuration
XMLStringProvider.java
java/src/org/apache/axis/serv
Glyn,
The interfaces will be defined in such a way that versioning is always assumed, it is
just that our default implementation of a config provider will basically ignore
versioning. In other words the config provider does not want to implement versioning
the default implementation (which sho
I was wondering how difficult it would be to provide either a "syntax check
only" option to WSDL2Java utility or yet another utility that would reuse
99% of the functionality that is in WSDL2Java to just syntax check WSDL.
Ideally validating any referenced schema too. I'm "assuming" that this
ut
Glyn,
That's right we can discuss it after you make changes. Basically if we want to support
dynamic reconfig with versioning, passing factory as a parameter to the Engine
constructor may be a good architectural simplification. Yes, we'll have one config
factory instance per engine instance, b
Here's my 2 cents.
There are very few syntax checks within WSDL2Java.
The WSDL2Java emitter walks the model provided by WSDL4J to generate the
code.
Therefore any syntax checking should be done in WSDL4J not within the
WSDL2Java emitter.
In addition, WSDL4J should provide a better way of modelin
There is an xmlvalidate task in Ant that might do what you need. It's great for
validating whole directories of various XML files -- it takes a list of local dtd
references and automatically matches them up with the DOCTYPEs in the XML files. Not
specific for WSDL, but might be handy, might a
| Is this a known issue, and if so, what is the planned fix? Would it be
to
| replace all references to the simple
| type with references to the base type (or the first base type reached
that
| maps to a java type when traversing the
| base types?) or to generate the class that is referenced (e.g
> There may be some reasons for this to follow
> the JAXM model. But to make really sure I would need to
> do some more thorough investigation. In doing so what have you fixed?
Not having to depend on Message, you can share Attachments between messages.
In catalog type services you might want to
Like Rich says, WSDL2Java does very little syntax checking. It DOES do
some, however. And you can actually run something to 'validate' your WSDL:
java org.apache.axis.wsdl.toJava.Emitter
This is an undocumented feature and it will stay undocumented. But I
frequently find it useful when writi
It appears with the latest Tomcat 4 that classes that start with javax
won't be found if they only exist in the WEB-INF/lib directories. This is
a problem as axis.jar contains jaxrpc classes. Let me tell you ,this was
no fun to debug, but knowing the Tomcat guys, this is done for a reason and
th
Hi,
I have some problems with optional arrays and WSDL2Java.
This is in my WSDL def:
...
...
Now the stub code will give me the following error:
CreationType.java:115: ']' expected
java.lang.String[][] a = new java.lang.Stri
I can not access to the http://xml.apache.org/axis/wsdd directory
or any of the subdirectory
that are used in SOAP xml. Is there any
alternative site to go?
Thanks.
Charlie
tomj02/02/05 11:36:32
Modified:java/test/wsdl Wsdl2javaTestSuite.xml Java2WsdlAntTask.java
java/test/wsdl/inheritance InheritanceTestCase.java
Added: java/test/wsdl/inheritance README.txt Parent_bean.java
Parent.java Child_bean.java Chi
butek 02/02/05 11:37:48
Modified:java/src/javax/xml/rpc Call.java ServiceFactory.java
java/src/org/apache/axis/client Call.java
ServiceFactory.java
java/src/org/apache/axis/wsdl/toJava JavaStubWriter.java
Log:
JAXRPCException n
There's a bug in Apache SOAP where it doesn't deserialize "1" as
"true". I wrote a test for Axis for the same bug and am including it
here. It's a patch against the latest nightly build.
I was surprised to find this bug doesn't exist in Axis. I thought
Axis, like Apache SOAP, relied on Boolean(St
I guess I need more info. I tried a couple variations of the use of
optionalStringArrayTest and they compiled. Could I see the full WSDL?
What version are you running?
Russell Butek
[EMAIL PROTECTED]
Thomas Sandholm <[EMAIL PROTECTED]> on 02/05/2002 01:11:58 PM
Please respond to [EMAIL PROTE
Thanks for the input Nelson.
You are right. The code in Axis does not have this bug, but I noticed that
the deserializer code
is extremely lame. Here is a snippet from
org.apache.axis.encoding.ser.SimpleDeserializer.java:
public Object makeValue(String source) throws Exception
{
Any word on these bugs, Matt? Particularly #2, overloaded operations; I've
gotten a couple pings from AXIS users about it.
Russell Butek
[EMAIL PROTECTED]
MATTHEW DUFTLER
01/25/2002 12:58 PM
To: Russell Butek/Austin/IBM@IBMUS
cc: [EMAIL PROTECTED]
From: Matthew Duftler/Watson/IBM@IBMUS
S
(with some earlier conversation as well)
#ApacheAxis.DALnet.20020205.log
Description: Binary data
I checked out Axis from CVS a couple of days ago, her's the full WSDL:
http://test.globus.org/optionalarray";
xmlns:tns="http://test.globus.org/optionalarray";
xmlns:types="http://test.globus.org/types";
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:soap="http://schemas.xmlsoap.org
On org.apache.axis.client.Call and Stub we have setMaintainSession methods.
These are AXIS addons to the JAX-RPC interfaces. But now JAX-RPC defines a
standard property called "javax.xml.rpc.http.session.maintain" that can be
passed to Call.setProperty or Stub._setProperty.
I will make our code
Here are some changes I made to Attachments implementation. (diffs attached)
*
AttachmentsImpl.java:
removed reference to Message object.
When Message gets SOAPPart it sets itself as a parent.
added orderedAttachments list that keep
> Incidentally, Tom and I are both going to be at the interop
event
> And we should definitely make a serious push in that
direction beforehand
> So... what's holding you guys back? ;-)
> Lack of Sam-commentary, mostly. We need it to inspire us.
:)
So... which of you are going to implement
You found a bug.
I would assume that if you replace
new java.lang.String[][i+1]
with
new java.lang.String[i+1][]
then everything works?
I'll fix this today or tomorrow.
Russell Butek
[EMAIL PROTECTED]
Thomas Sandholm <[EMAIL PROTECTED]> on 02/05/2002 02:32:45 PM
Please respond to [EMAIL
I guess that would be me.
What does it mean to "implement the test"? Just write a client app against the WSDL
file? Or implement both client and server?
My guess is its the latter.
--
Tom Jordahl
-Original Message-
From: Sam Ruby [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 0
butek 02/02/05 13:53:49
Modified:java/src/org/apache/axis/wsdl/toJava
JavaComplexTypeWriter.java
Log:
Fixed a bug found by Thomas Sandholm. "new String[][i+1]" was being generated.
This should be "new String[i+1][]".
Revision ChangesPath
1.6
I'll look into this. I have seen similar problems.
Thanks
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
Th
>You are right. The code in Axis does not have this bug, but I noticed that
>the deserializer code is extremely lame. switch (source.charAt(0)) {
Hah, no wonder I didn't understand how it worked! Well, at least the
Axis implementation is efficient :-)
>Any suggestions? I would hate to make t
scheu 02/02/05 14:42:36
Modified:java/src/org/apache/axis/wsdl/toJava SchemaUtils.java
SymbolTable.java TypeEntry.java
java/test/wsdl/types ComprehensiveTypes.wsdl
Log:
Added support for simple simpleTypes.
The emitter uses the base name as
I just committed the support for simpleTypes as described below.
Try it out!
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
Well I tried to re-create the problem, but I see that Russell already fixed
it !
Thanks
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
scheu 02/02/05 15:11:13
Modified:java/test/wsdl/types ComprehensiveTypes.wsdl
VerifyTestCase.java
Log:
Small change to comprehensive tests to verify "optional array"
work that Russell added. (See optArray in the wsdl file)
Revision ChangesPath
R J Scheuerle Jr wrote:
>
> You indicated yesterday that a change was made to Apache SOAP to
> register array types. I am concerned that they will run across this same
> problem...and from last night's test it appears that they did.
> See SOAP echoStructArray for SOAP RMI. Also, the SOAP echoStr
+1 for instantiating classes for all subtypes of referenced types. I think the simple
+thing to do might really be to just generate *all* the types, but I guess the worry
+here is that there will be huge commonly imported type library schemas of which only
+a few types are referenced for a gi
As I am reading the JAX-RPC specifications, on page 43 (5.4.1 XML Mapping),
all the values in an XSD construct should be mapped to a serializable
field, therefore generating the methods getXX() and setXX().
When using SOAP Apache, I created a Castor (from exolab) Serializer/Deserializer.
I wil
46 matches
Mail list logo
