castor

Introduce an interface XMLNaming instead of todays abstract class which will be named AbstractXMLNaming

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1.2.1
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    all
  • Number of attachments :
    0

Description

Today the class to create valid XML names is XMLNaming which is abstract and its implementation DefaultNaming. The naming class is created either via:
*) configuration or
*) XMLNaming.getInstance (which internally redirects to configuration...)

I would like to introduce an interface XMLNaming, which reflects the methods to implement for XML naming creation.
And rename current XMLNaming to AbstractXMLNaming.

I will do this change in two steps because otherwise SVN will be confused:
1) rename XMLNaming to AbstractXMLNaming
2) introduce XMLNaming interface and use it in every place AbstractXMLNaming is used.

Activity

Hide
Werner Guttmann added a comment -

Absolutely fine by me. Anything that moves away from this use of abstract classes rather than interfaces is .. wonderful.

Show
Werner Guttmann added a comment - Absolutely fine by me. Anything that moves away from this use of abstract classes rather than interfaces is .. wonderful.
Hide
Joachim Grüneis added a comment -

Renamed XMLNaming to AbstractXMLNaming (commit 7357)
Introduced interface XMLNaming for AbstractXMLNaming (commit 7358)
Moved XMLNaming to org.castor.xml (commit 7359)
Adapted castor-jaxb-2.0 to new interface (commit 7360)

Show
Joachim Grüneis added a comment - Renamed XMLNaming to AbstractXMLNaming (commit 7357) Introduced interface XMLNaming for AbstractXMLNaming (commit 7358) Moved XMLNaming to org.castor.xml (commit 7359) Adapted castor-jaxb-2.0 to new interface (commit 7360)

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: