[
https://issues.apache.org/jira/browse/WODEN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566988#action_12566988
]
John Kaputin commented on WODEN-56:
-----------------------------------
Analysis of 'internal' classes classes used within the Woden-defined extensions:
HTTPBindingFaultExtensionImpl
* QNameTokenAnyAttrImpl
HTTPHeaderDeserializer
* ErrorLocatorImpl
HTTPHeaderImpl
* ExtensionElementImpl
* AttributeExtensibleImpl
* ElementExtensibleImpl
* TypesImpl
* BindingImpl
SOAPBindingFaultExtensionsImpl
* QNameListOrTokenAnyAttrImpl
* QNameOrTokenAnyAttrImpl
SOAPHeaderBlockDeserializer
* ErrorReporterImpl
* SOAPHeaderBlockImpl
SOAPHeaderBlockImpl
* AttributeExtensibleImpl
* ElementExtensibleImpl
* TypesImpl
* BindingImpl
SOAPModuleDeserializer
* ErrorLocatorImpl
SOAPModuleImpl
* ErrorLocatorImpl
* AttributeExtensibleImpl
* ElementExtensibleImpl
> Extensions' impl classes shouldn't have to use *internal* classes in their
> implementation
> -----------------------------------------------------------------------------------------
>
> Key: WODEN-56
> URL: https://issues.apache.org/jira/browse/WODEN-56
> Project: Woden
> Issue Type: Improvement
> Components: Parser
> Reporter: Jeremy Hughes
> Assignee: John Kaputin
> Fix For: M8
>
>
> An extension writer shouldn't be expected to use any classes internal to
> Woden (ie ones that have 'internal' in their package name). Everthing an
> extension implementation (as well as interface) needs to get to should be on
> an external package.
> We should eat our own food by changing the SOAP and HTTP extensions to do
> this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
