axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russell Butek" <>
Subject Re: Internationalization question
Date Mon, 12 Nov 2001 14:15:33 GMT
Being new to apache, I haven't a clue how to move Wsdl2java to its own
project.  I wouldn't have a problem with it, I just don't know what it

If we DID move it, though, we'd still have part of it - probably the
biggest part - in AXIS.  We're moving the design of Wsdl2java in a
direction where the AXIS-specific stuff is separable from the WSDL stuff
(ie, WSDL4J and DOM structures + a few of our own) so that someone could
write their own back-end code generators.  So if this WERE in it's own
project, it wouldn't be a very big project since most of the design is

Russell Butek

"Sanjiva Weerawarana" <> on 11/11/2001 08:42:52 AM

Please respond to

To:   <>
Subject:  Re: Internationalization question

I'd like to encourage you again to move WSDL2Java to its own project..
its useful for more than Axis-Java!


----- Original Message -----
From: "Russell Butek" <>
To: <>
Sent: Friday, November 09, 2001 4:16 AM
Subject: Internationalization question

> We have 2 'tools' in AXIS (at least that's all I know about):  tcpmon and
> Wsdl2java.
> tcpmon was designed to be it's own beast independent of AXIS and because
> this I'm going to create a separate properties file for it's translatable
> messages.
> But what about Wsdl2java?  It doesn't depend on AXIS, but it's certainly
> more in cahoots with AXIS than tcpmon.  If I put Wsdl2java strings into
> org/apache/axis/utils/, then it will now have a
> dependency on AXIS (the properties file and JavaUtils).  But is that bad?
> Will Wsdl2java ever exist outside of AXIS?
> I am inclined to simply treat Wsdl2java like all other axis code wrt
> internationalization.  If we decide to tear it away in the future we can
> revisit the issue then.
> Russell Butek

View raw message