Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Message-ID: <24349109.1189042534960.JavaMail.jira@brutus>
Date: Wed, 5 Sep 2007 18:35:34 -0700 (PDT)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: cxf-issues@incubator.apache.org
Subject: [jira] Commented: (CXF-972) Define a tns prefix
In-Reply-To: <33395031.1189011816268.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CXF-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525273 ] 

Daniel Kulp commented on CXF-972:
---------------------------------

2 questions/comments:

1) I think the AegisBinding needs a similar tns namespace setup.

2) Did you run all the tests?   I'd be VERY surprised if the tooling tests passed with these changes.   Most likely, some of the java2wsdl tests will fail.   (if you did, great.   I haven't tried applying the patch and running them yet.)


> Define a tns prefix
> -------------------
>
>                 Key: CXF-972
>                 URL: https://issues.apache.org/jira/browse/CXF-972
>             Project: CXF
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.0.1
>            Reporter: benson margulies
>             Fix For: 2.1
>
>         Attachments: patches.tns
>
>
> Currently, the CXF wsdl generator never creates a tns prefix. Types in the schema (or even wsdl) target namespace get automatically generated prefixes, like 'ns1'. The wsdl's would be more readable with the explicit namespace.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.