jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • XFire
  • XFIRE-421

JAXWS generation has a couple of issues

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.1.1
  • Component/s: Generator, JAX-WS
  • Labels:
    None

Description

Changes:

  • Exception are not generated in right package (they should be generated on the package for the wsdl, not the xsd)
  • Add explicitAnnotation option to support running jaxb2 / jaxws on jdk 1.4 with retrotranslator
  • Method names should have the first letter in lower case
  • Web annotation on service interface should have a namespace corresponding to the PortType, not the Service
  • Constructor on fault exceptions has parameters in a wrong order

Note that the explicitAnnotation option requires jaxb2 RI 2.0 (not present in 2.0-EA3)
I have raised a JIRA on maven to upload them

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Text File
    XFIRE-jaxws.patch
    25/May/06 7:13 AM
    9 kB
    Guillaume Nodet

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Dan Diephouse added a comment - 26/May/06 12:08 PM

I noticed that you took the "_Exception" off the exception classes that are generated. Is there a reason? That is how the JAXWS-RI generates exception classes as well.

Show
Dan Diephouse added a comment - 26/May/06 12:08 PM I noticed that you took the "_Exception" off the exception classes that are generated. Is there a reason? That is how the JAXWS-RI generates exception classes as well.
Hide
Permalink
Guillaume Nodet added a comment - 27/May/06 5:52 AM

The jaxws spec says in section 2.5 that
" Conformance (Exception naming): In the absence of customizations, the
name of a mapped exception 1
MUST be the value of the name attribute of the wsdl:message referred to
by the wsdl:fault element 2
mapped according to the rules in sections 2.8 and 2.8.1."

Sections 2.8 and 2.8.1 is for conflict resolution. If there is a
conflict, "_Exception" should be appended to the name
of the exception.

And of course, this is how the RI works.

Show
Guillaume Nodet added a comment - 27/May/06 5:52 AM The jaxws spec says in section 2.5 that " Conformance (Exception naming): In the absence of customizations, the name of a mapped exception 1 MUST be the value of the name attribute of the wsdl:message referred to by the wsdl:fault element 2 mapped according to the rules in sections 2.8 and 2.8.1." Sections 2.8 and 2.8.1 is for conflict resolution. If there is a conflict, "_Exception" should be appended to the name of the exception. And of course, this is how the RI works.
Hide
Permalink
Dan Diephouse added a comment - 12/Jun/06 11:01 AM

Thanks a lot Guillaume! This is now in SVN.

Show
Dan Diephouse added a comment - 12/Jun/06 11:01 AM Thanks a lot Guillaume! This is now in SVN.

People

  • Assignee:
    Guillaume Nodet
    Reporter:
    Guillaume Nodet
Vote (0)
Watch (0)

Dates

  • Created:
    25/May/06 7:13 AM
    Updated:
    12/Jun/06 11:01 AM
    Resolved:
    12/Jun/06 11:01 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.