You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2010/11/14 11:39:13 UTC
[jira] Created: (AXIOM-350) Clean up the
org.apache.axiom.attachments.Part interface
Clean up the org.apache.axiom.attachments.Part interface
--------------------------------------------------------
Key: AXIOM-350
URL: https://issues.apache.org/jira/browse/AXIOM-350
Project: Axiom
Issue Type: Task
Components: API
Reporter: Andreas Veithen
Assignee: Andreas Veithen
Fix For: 1.2.11
Currently, the Part interface is only used internally by Axiom. This can be seen from the current Javadoc [1] (note that Part is used by PartFactory, which is also only used internally [2]). Therefore the Part interface is not really part of the public API and modifying it would only impact code that uses Part and PartFactory independently from the rest of the Axiom API, which is a highly unlikely case.
In order to solve AXIOM-31 and AXIOM-280, it is proposed to expose the Part instances via the Attachments object. This is also necessary to make the SAAJ implementation in Axis2 complete, because SAAJ defines methods to access the headers of a MIME part, and this is not possible with the current Axiom API.
Exposing the Part instances via the Attachments object will make the Part interface part of the public API. Before doing this, we should clean up this interface a bit. In particular, we should eliminate its dependency on the JavaMail API (usage of javax.mail.MessagingException by all methods and usage of javax.mail.Header as a return value of getAllHeaders).
[1] http://ws.apache.org/axiom/apidocs/org/apache/axiom/attachments/class-use/Part.html
[2] http://ws.apache.org/axiom/apidocs/org/apache/axiom/attachments/impl/class-use/PartFactory.html
--
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: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
[jira] [Updated] (AXIOM-350) Clean up the
org.apache.axiom.attachments.Part interface
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIOM-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIOM-350:
----------------------------------
Fix Version/s: (was: 1.2.12)
1.2.13
> Clean up the org.apache.axiom.attachments.Part interface
> --------------------------------------------------------
>
> Key: AXIOM-350
> URL: https://issues.apache.org/jira/browse/AXIOM-350
> Project: Axiom
> Issue Type: Task
> Components: API
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
> Fix For: 1.2.13
>
>
> Currently, the Part interface is only used internally by Axiom. This can be seen from the current Javadoc [1] (note that Part is used by PartFactory, which is also only used internally [2]). Therefore the Part interface is not really part of the public API and modifying it would only impact code that uses Part and PartFactory independently from the rest of the Axiom API, which is a highly unlikely case.
> In order to solve AXIOM-31 and AXIOM-280, it is proposed to expose the Part instances via the Attachments object. This is also necessary to make the SAAJ implementation in Axis2 complete, because SAAJ defines methods to access the headers of a MIME part, and this is not possible with the current Axiom API.
> Exposing the Part instances via the Attachments object will make the Part interface part of the public API. Before doing this, we should clean up this interface a bit. In particular, we should eliminate its dependency on the JavaMail API (usage of javax.mail.MessagingException by all methods and usage of javax.mail.Header as a return value of getAllHeaders).
> [1] http://ws.apache.org/axiom/apidocs/org/apache/axiom/attachments/class-use/Part.html
> [2] http://ws.apache.org/axiom/apidocs/org/apache/axiom/attachments/impl/class-use/PartFactory.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
[jira] [Updated] (AXIOM-350) Clean up the
org.apache.axiom.attachments.Part interface
Posted by "Andreas Veithen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIOM-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIOM-350:
----------------------------------
Fix Version/s: (was: 1.2.13)
1.2.14
> Clean up the org.apache.axiom.attachments.Part interface
> --------------------------------------------------------
>
> Key: AXIOM-350
> URL: https://issues.apache.org/jira/browse/AXIOM-350
> Project: Axiom
> Issue Type: Task
> Components: API
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
> Fix For: 1.2.14
>
>
> Currently, the Part interface is only used internally by Axiom. This can be seen from the current Javadoc [1] (note that Part is used by PartFactory, which is also only used internally [2]). Therefore the Part interface is not really part of the public API and modifying it would only impact code that uses Part and PartFactory independently from the rest of the Axiom API, which is a highly unlikely case.
> In order to solve AXIOM-31 and AXIOM-280, it is proposed to expose the Part instances via the Attachments object. This is also necessary to make the SAAJ implementation in Axis2 complete, because SAAJ defines methods to access the headers of a MIME part, and this is not possible with the current Axiom API.
> Exposing the Part instances via the Attachments object will make the Part interface part of the public API. Before doing this, we should clean up this interface a bit. In particular, we should eliminate its dependency on the JavaMail API (usage of javax.mail.MessagingException by all methods and usage of javax.mail.Header as a return value of getAllHeaders).
> [1] http://ws.apache.org/axiom/apidocs/org/apache/axiom/attachments/class-use/Part.html
> [2] http://ws.apache.org/axiom/apidocs/org/apache/axiom/attachments/impl/class-use/PartFactory.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
[jira] [Commented] (AXIOM-350) Clean up the
org.apache.axiom.attachments.Part interface
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIOM-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161987#comment-13161987 ]
Hudson commented on AXIOM-350:
------------------------------
Integrated in ws-axiom-trunk #731 (See [https://builds.apache.org/job/ws-axiom-trunk/731/])
AXIOM-350: Avoid usage of JavaMail exceptions.
veithen :
Files :
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/attachments/Part.java
> Clean up the org.apache.axiom.attachments.Part interface
> --------------------------------------------------------
>
> Key: AXIOM-350
> URL: https://issues.apache.org/jira/browse/AXIOM-350
> Project: Axiom
> Issue Type: Task
> Components: API
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
> Fix For: 1.2.14
>
>
> Currently, the Part interface is only used internally by Axiom. This can be seen from the current Javadoc [1] (note that Part is used by PartFactory, which is also only used internally [2]). Therefore the Part interface is not really part of the public API and modifying it would only impact code that uses Part and PartFactory independently from the rest of the Axiom API, which is a highly unlikely case.
> In order to solve AXIOM-31 and AXIOM-280, it is proposed to expose the Part instances via the Attachments object. This is also necessary to make the SAAJ implementation in Axis2 complete, because SAAJ defines methods to access the headers of a MIME part, and this is not possible with the current Axiom API.
> Exposing the Part instances via the Attachments object will make the Part interface part of the public API. Before doing this, we should clean up this interface a bit. In particular, we should eliminate its dependency on the JavaMail API (usage of javax.mail.MessagingException by all methods and usage of javax.mail.Header as a return value of getAllHeaders).
> [1] http://ws.apache.org/axiom/apidocs/org/apache/axiom/attachments/class-use/Part.html
> [2] http://ws.apache.org/axiom/apidocs/org/apache/axiom/attachments/impl/class-use/PartFactory.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
[jira] [Commented] (AXIOM-350) Clean up the
org.apache.axiom.attachments.Part interface
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIOM-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078931#comment-13078931 ]
Hudson commented on AXIOM-350:
------------------------------
Integrated in ws-axiom-trunk #480 (See [https://builds.apache.org/job/ws-axiom-trunk/480/])
AXIOM-350: Stripped a couple of methods from the Part interface that are currently not used.
veithen :
Files :
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/attachments/impl/PartOnFile.java
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/attachments/Part.java
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/attachments/impl/PartOnMemoryEnhanced.java
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/attachments/impl/AbstractPart.java
> Clean up the org.apache.axiom.attachments.Part interface
> --------------------------------------------------------
>
> Key: AXIOM-350
> URL: https://issues.apache.org/jira/browse/AXIOM-350
> Project: Axiom
> Issue Type: Task
> Components: API
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
> Fix For: 1.2.13
>
>
> Currently, the Part interface is only used internally by Axiom. This can be seen from the current Javadoc [1] (note that Part is used by PartFactory, which is also only used internally [2]). Therefore the Part interface is not really part of the public API and modifying it would only impact code that uses Part and PartFactory independently from the rest of the Axiom API, which is a highly unlikely case.
> In order to solve AXIOM-31 and AXIOM-280, it is proposed to expose the Part instances via the Attachments object. This is also necessary to make the SAAJ implementation in Axis2 complete, because SAAJ defines methods to access the headers of a MIME part, and this is not possible with the current Axiom API.
> Exposing the Part instances via the Attachments object will make the Part interface part of the public API. Before doing this, we should clean up this interface a bit. In particular, we should eliminate its dependency on the JavaMail API (usage of javax.mail.MessagingException by all methods and usage of javax.mail.Header as a return value of getAllHeaders).
> [1] http://ws.apache.org/axiom/apidocs/org/apache/axiom/attachments/class-use/Part.html
> [2] http://ws.apache.org/axiom/apidocs/org/apache/axiom/attachments/impl/class-use/PartFactory.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
[jira] [Commented] (AXIOM-350) Clean up the
org.apache.axiom.attachments.Part interface
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIOM-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078463#comment-13078463 ]
Hudson commented on AXIOM-350:
------------------------------
Integrated in ws-axiom-trunk #479 (See [https://builds.apache.org/job/ws-axiom-trunk/479/])
Removed PartOnMemory. As noted in AXIOM-350, the PartOn* classes are not considered part of the public API, and PartOnMemory is no longer used (only PartOnMemoryEnhanced is).
veithen :
Files :
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/attachments/impl/PartOnMemory.java
> Clean up the org.apache.axiom.attachments.Part interface
> --------------------------------------------------------
>
> Key: AXIOM-350
> URL: https://issues.apache.org/jira/browse/AXIOM-350
> Project: Axiom
> Issue Type: Task
> Components: API
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
> Fix For: 1.2.13
>
>
> Currently, the Part interface is only used internally by Axiom. This can be seen from the current Javadoc [1] (note that Part is used by PartFactory, which is also only used internally [2]). Therefore the Part interface is not really part of the public API and modifying it would only impact code that uses Part and PartFactory independently from the rest of the Axiom API, which is a highly unlikely case.
> In order to solve AXIOM-31 and AXIOM-280, it is proposed to expose the Part instances via the Attachments object. This is also necessary to make the SAAJ implementation in Axis2 complete, because SAAJ defines methods to access the headers of a MIME part, and this is not possible with the current Axiom API.
> Exposing the Part instances via the Attachments object will make the Part interface part of the public API. Before doing this, we should clean up this interface a bit. In particular, we should eliminate its dependency on the JavaMail API (usage of javax.mail.MessagingException by all methods and usage of javax.mail.Header as a return value of getAllHeaders).
> [1] http://ws.apache.org/axiom/apidocs/org/apache/axiom/attachments/class-use/Part.html
> [2] http://ws.apache.org/axiom/apidocs/org/apache/axiom/attachments/impl/class-use/PartFactory.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
[jira] Updated: (AXIOM-350) Clean up the
org.apache.axiom.attachments.Part interface
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIOM-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIOM-350:
----------------------------------
Fix Version/s: (was: 1.2.11)
1.2.12
> Clean up the org.apache.axiom.attachments.Part interface
> --------------------------------------------------------
>
> Key: AXIOM-350
> URL: https://issues.apache.org/jira/browse/AXIOM-350
> Project: Axiom
> Issue Type: Task
> Components: API
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
> Fix For: 1.2.12
>
>
> Currently, the Part interface is only used internally by Axiom. This can be seen from the current Javadoc [1] (note that Part is used by PartFactory, which is also only used internally [2]). Therefore the Part interface is not really part of the public API and modifying it would only impact code that uses Part and PartFactory independently from the rest of the Axiom API, which is a highly unlikely case.
> In order to solve AXIOM-31 and AXIOM-280, it is proposed to expose the Part instances via the Attachments object. This is also necessary to make the SAAJ implementation in Axis2 complete, because SAAJ defines methods to access the headers of a MIME part, and this is not possible with the current Axiom API.
> Exposing the Part instances via the Attachments object will make the Part interface part of the public API. Before doing this, we should clean up this interface a bit. In particular, we should eliminate its dependency on the JavaMail API (usage of javax.mail.MessagingException by all methods and usage of javax.mail.Header as a return value of getAllHeaders).
> [1] http://ws.apache.org/axiom/apidocs/org/apache/axiom/attachments/class-use/Part.html
> [2] http://ws.apache.org/axiom/apidocs/org/apache/axiom/attachments/impl/class-use/PartFactory.html
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org