You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Russell Butek <bu...@us.ibm.com> on 2001/10/09 20:31:29 UTC
AXIS chat log for 9 October, 2001
In essence, today's chat degenerated to Berin and I talking about
namespace->package mappings. In short, we decided we have to do 2 things
for namespace to package name mappings:
1. Get the mappings from the user
2. If the user didn't provide one for a given namespace, make one up
following some set of rules.
For 1 there are a couple new options we could add to Wsdl2java:
--NStoPkg <ns0>=<pkg0>,<ns1>=<pkg1>,...,<nsN>=<pkgN>
--NStoPkgFile <propertyFile>
Do we provide both? One or the other? What about the existing --package
option? Do we toss it? I think we want to avoid a proliferation of
arguments to Wsdl2java.
(See attached file: log)
Russell Butek
butek@us.ibm.com
Re: AXIS chat log for 9 October, 2001
Posted by Berin Loritsch <bl...@apache.org>.
Russell Butek wrote:
>
> In essence, today's chat degenerated to Berin and I talking about
> namespace->package mappings. In short, we decided we have to do 2 things
> for namespace to package name mappings:
>
> 1. Get the mappings from the user
> 2. If the user didn't provide one for a given namespace, make one up
> following some set of rules.
>
> For 1 there are a couple new options we could add to Wsdl2java:
> --NStoPkg <ns0>=<pkg0>,<ns1>=<pkg1>,...,<nsN>=<pkgN>
> --NStoPkgFile <propertyFile>
>
> Do we provide both? One or the other? What about the existing --package
> option? Do we toss it? I think we want to avoid a proliferation of
> arguments to Wsdl2java.
At the end of the meeting--about the time it looked like everyone got
kicked off, I proposed that we drop the support for declaring the multiple
namespace mappings on the command line and just do it in the file.
PS
If you don't want to handcode the parsing for multiple namespace mappings,
the CLIUtil will allow you to do the following:
-N<ns0>=<pkg0> -N<ns1>=<pkg1> ... -N<nsN>=<pkgN>
This allows the CLI utility to give you multiple parameters that it parses.
For 1 or 2 mappings, doing it on the command line is fine. For more than
that, I would probably opt for the file approach.
As to the --package parameter that would be for everything in the target
namespace (<wsdl:definitions targetnamespace="..." .../>). Or, we drop
it completely and use the mapping approach above exclusively.