You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by "Jeremy Hughes (JIRA)" <ji...@apache.org> on 2006/09/08 17:21:23 UTC

[jira] Created: (WODEN-56) Extensions' impl classes shouldn't have to use other *internal* classes in their implementation

Extensions' impl classes shouldn't have to use other *internal* classes in their implementation
-----------------------------------------------------------------------------------------------

                 Key: WODEN-56
                 URL: http://issues.apache.org/jira/browse/WODEN-56
             Project: Woden
          Issue Type: Improvement
            Reporter: Jeremy Hughes


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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


[jira] Commented: (WODEN-56) Extensions' impl classes shouldn't have to use *internal* classes in their implementation

Posted by "John Kaputin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WODEN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568238#action_12568238 ] 

John Kaputin commented on WODEN-56:
-----------------------------------

This issue has been partially resolved by WODEN-47:
* the 'interna' base class ComponentExtensionsImpl has been replaced by the API-public class BaseComponentExtensionContext
* the extension Constants files have been moved from 'internal' packages to the corresponding API packages

> 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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


[jira] Updated: (WODEN-56) Extensions' impl classes shouldn't have to use *internal* classes in their implementation

Posted by "John Kaputin (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/WODEN-56?page=all ]

John Kaputin updated WODEN-56:
------------------------------

    Component/s: Parser

Allocated this issue to the Parser category as it concerns the programming model for using the parser.

> Extensions' impl classes shouldn't have to use *internal* classes in their implementation
> -----------------------------------------------------------------------------------------
>
>                 Key: WODEN-56
>                 URL: http://issues.apache.org/jira/browse/WODEN-56
>             Project: Woden
>          Issue Type: Improvement
>          Components: Parser
>            Reporter: Jeremy Hughes
>         Assigned To: John Kaputin
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


[jira] Assigned: (WODEN-56) Extensions' impl classes shouldn't have to use *internal* classes in their implementation

Posted by "John Kaputin (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/WODEN-56?page=all ]

John Kaputin reassigned WODEN-56:
---------------------------------

    Assignee: John Kaputin

> Extensions' impl classes shouldn't have to use *internal* classes in their implementation
> -----------------------------------------------------------------------------------------
>
>                 Key: WODEN-56
>                 URL: http://issues.apache.org/jira/browse/WODEN-56
>             Project: Woden
>          Issue Type: Improvement
>            Reporter: Jeremy Hughes
>         Assigned To: John Kaputin
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


[jira] Updated: (WODEN-56) Extensions' impl classes shouldn't have to use *internal* classes in their implementation

Posted by "Lawrence Mandel (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WODEN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lawrence Mandel updated WODEN-56:
---------------------------------

    Fix Version/s:     (was: M7)
                   M8

> 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
>         Assigned To: 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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


[jira] Updated: (WODEN-56) Extensions' impl classes shouldn't have to use *internal* classes in their implementation

Posted by "John Kaputin (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/WODEN-56?page=all ]

John Kaputin updated WODEN-56:
------------------------------

    Affects Version/s: M7

> Extensions' impl classes shouldn't have to use *internal* classes in their implementation
> -----------------------------------------------------------------------------------------
>
>                 Key: WODEN-56
>                 URL: http://issues.apache.org/jira/browse/WODEN-56
>             Project: Woden
>          Issue Type: Improvement
>          Components: Parser
>    Affects Versions: M7
>            Reporter: Jeremy Hughes
>         Assigned To: John Kaputin
>             Fix For: M7
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


[jira] Updated: (WODEN-56) Extensions' impl classes shouldn't have to use *internal* classes in their implementation

Posted by "Lawrence Mandel (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/WODEN-56?page=all ]

Lawrence Mandel updated WODEN-56:
---------------------------------

    Fix Version/s: M7

> Extensions' impl classes shouldn't have to use *internal* classes in their implementation
> -----------------------------------------------------------------------------------------
>
>                 Key: WODEN-56
>                 URL: http://issues.apache.org/jira/browse/WODEN-56
>             Project: Woden
>          Issue Type: Improvement
>          Components: Parser
>    Affects Versions: M7
>            Reporter: Jeremy Hughes
>         Assigned To: John Kaputin
>             Fix For: M7
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


[jira] Commented: (WODEN-56) Extensions' impl classes shouldn't have to use *internal* classes in their implementation

Posted by "John Kaputin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WODEN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561366#action_12561366 ] 

John Kaputin commented on WODEN-56:
-----------------------------------

Jeremy,
what does this issue relate to specifically? Is it the use of the Attr impl classes in org.apache.woden.internal.xml when registering extension attributes in the ExtensionRegistry?  These were created to as part of the woden implementation, for use by Woden's implementation of its SOAP and HTTP extension APIs. Is the issue that users will benefit from reusing these classes too, in which case they should be API public? If so, it's worth noting that they are not exhaustive - they just cover the attribute types defined in the Part 2 adjuncts spec. User may require other types of attributes, but I guess they can define those as part of their own extensions.

Or was it to do with the SOAP and HTTP ExtensionsImpl classes extending ComponentExtensionsImpl? Again, ComponentExtensionsImpl was created to refactor reusable code for use within the Woden implementation  (e.g. in the implementation of the SOAP and HTTP extensions). However, we could perhaps make this an API public abstract super class, instead of an Interface, so that user-defined extensions can inherit from it. Is this what you had in mind?

> 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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


[jira] Commented: (WODEN-56) Extensions' impl classes shouldn't have to use *internal* classes in their implementation

Posted by "John Kaputin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WODEN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467792 ] 

John Kaputin commented on WODEN-56:
-----------------------------------

Woden weekly call 23 Jan 07 delayed M7 release date by 1 week and re-scoped M7 content. This JIRA is now not part of the release defining criteria for M7.   It will remain high priority for the release following M7.

> 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
>         Assigned To: John Kaputin
>             Fix For: M7
>
>
> 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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


[jira] Updated: (WODEN-56) Extensions' impl classes shouldn't have to use *internal* classes in their implementation

Posted by "Jeremy Hughes (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/WODEN-56?page=all ]

Jeremy Hughes updated WODEN-56:
-------------------------------

    Summary: Extensions' impl classes shouldn't have to use *internal* classes in their implementation  (was: Extensions' impl classes shouldn't have to use other *internal* classes in their implementation)

> Extensions' impl classes shouldn't have to use *internal* classes in their implementation
> -----------------------------------------------------------------------------------------
>
>                 Key: WODEN-56
>                 URL: http://issues.apache.org/jira/browse/WODEN-56
>             Project: Woden
>          Issue Type: Improvement
>            Reporter: Jeremy Hughes
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


[jira] Updated: (WODEN-56) Extensions' impl classes shouldn't have to use *internal* classes in their implementation

Posted by "Sagara Gunathunga (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WODEN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sagara Gunathunga  updated WODEN-56:
------------------------------------

    Fix Version/s:     (was: M9)

> 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
>
> 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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


[jira] Updated: (WODEN-56) Extensions' impl classes shouldn't have to use *internal* classes in their implementation

Posted by "John Kaputin (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/WODEN-56?page=all ]

John Kaputin updated WODEN-56:
------------------------------

    Affects Version/s:     (was: M7)

> Extensions' impl classes shouldn't have to use *internal* classes in their implementation
> -----------------------------------------------------------------------------------------
>
>                 Key: WODEN-56
>                 URL: http://issues.apache.org/jira/browse/WODEN-56
>             Project: Woden
>          Issue Type: Improvement
>          Components: Parser
>            Reporter: Jeremy Hughes
>         Assigned To: John Kaputin
>             Fix For: M7
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


[jira] Updated: (WODEN-56) Extensions' impl classes shouldn't have to use *internal* classes in their implementation

Posted by "Lawrence Mandel (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WODEN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lawrence Mandel updated WODEN-56:
---------------------------------

    Fix Version/s:     (was: M8)
                   M9

> 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: M9
>
>
> 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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


[jira] Commented: (WODEN-56) Extensions' impl classes shouldn't have to use *internal* classes in their implementation

Posted by "John Kaputin (JIRA)" <ji...@apache.org>.
    [ 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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org