Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [Wtp-wst-dev] comments about new API design in psychopath engine

All of this explanation from Dave and Jesper is fair enough.

Many thanks.


From:        David Carver <d_a_carver@xxxxxxxxx>
To:        "Web Standard Tools developer discussions." <wtp-wst-dev@xxxxxxxxxxx>
Date:        19/04/2011 05:44 PM
Subject:        Re: [Wtp-wst-dev] comments about new API design in psychopath engine
Sent by:        wtp-wst-dev-bounces@xxxxxxxxxxx

Mukul, in regards to the package naming, it isn't unheard of for projects to have a package the specifically has the work API in the name.   For one thing it clearly communicates that this is API.  Just because a class is publicly accessibile doesn't necessarily mean we want it as API.

There are other ways to handle this as well, many eclipse projects will use the word, "internal", to indicate that these classes aren't API.    As of right now, the API change date for Eclipse projects on the release train has passed, and this is a minor issue in regards to package naming, so we'll probably just leave it as is.

Also for the Type interfaces, at one time IBM had submitted the Xerces's type information to the W3C to try and get it standardized, but the proposal never made it beyond the proposal stage.   Since we didn't want to have to depend and bring in the Xerces api classes and interface files directly, it was best to just create our own.  Plus this allows as Jesper said, for other type systems to be added by other implementations.   So one could take the eclipse EMF XSD implementation and use it for the the type system if one wanted, or the WTP ContentModel as well.


Back to the top