You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2010/09/22 18:29:36 UTC

[jira] Created: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
----------------------------------------------------------------------------------

                 Key: AXIS2-4828
                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
             Project: Axis2
          Issue Type: Bug
          Components: kernel
            Reporter: Rich Scheuerle
            Assignee: Rich Scheuerle


Background:

The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
Writing to an OutputStream is faster and allows the other components to access the OutputStream.

Proposal:
I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


Re: [jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Rich, IMO this approach of opening an issue just to record a commit is
really not appropriate ... that's not what we use JIRA for!

Sanjiva.

On Mon, Sep 27, 2010 at 9:08 PM, Andreas Veithen (JIRA) <ji...@apache.org>wrote:

>
>    [
> https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915335#action_12915335]
>
> Andreas Veithen commented on AXIS2-4828:
> ----------------------------------------
>
> Rich, it would be nice if before marking an issue as resolved, you could
> read (and react to!) the comments left by others...
>
> > SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when
> doing SWA
> >
> ----------------------------------------------------------------------------------
> >
> >                 Key: AXIS2-4828
> >                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
> >             Project: Axis2
> >          Issue Type: Bug
> >          Components: kernel
> >            Reporter: Rich Scheuerle
> >            Assignee: Rich Scheuerle
> >   Original Estimate: 24h
> >  Remaining Estimate: 24h
> >
> > Background:
> > The SOAPMessageFormatter writes the message to an OutputStream in all
> cases except SWA.
> > Writing to an OutputStream is faster and allows the other components to
> access the OutputStream.
> > Proposal:
> > I am making a small change to the SOAPMessageFormatter SWA flow to use a
> ByteArrayOutputStream as the buffer.
>
> --
> 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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
Sanjiva Weerawarana, Ph.D.
Founder, Director & Chief Scientist; Lanka Software Foundation;
http://www.opensource.lk/
Founder, Chairman & CEO; WSO2; http://wso2.com/
Founder & Director; Thinkcube Systems; http://www.thinkcube.com/
Member; Apache Software Foundation; http://www.apache.org/
Member; Sahana Software Foundation; http://www.sahanafoundation.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

Blog: http://sanjiva.weerawarana.org/

Re: [jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Rich, IMO this approach of opening an issue just to record a commit is
really not appropriate ... that's not what we use JIRA for!

Sanjiva.

On Mon, Sep 27, 2010 at 9:08 PM, Andreas Veithen (JIRA) <ji...@apache.org>wrote:

>
>    [
> https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915335#action_12915335]
>
> Andreas Veithen commented on AXIS2-4828:
> ----------------------------------------
>
> Rich, it would be nice if before marking an issue as resolved, you could
> read (and react to!) the comments left by others...
>
> > SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when
> doing SWA
> >
> ----------------------------------------------------------------------------------
> >
> >                 Key: AXIS2-4828
> >                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
> >             Project: Axis2
> >          Issue Type: Bug
> >          Components: kernel
> >            Reporter: Rich Scheuerle
> >            Assignee: Rich Scheuerle
> >   Original Estimate: 24h
> >  Remaining Estimate: 24h
> >
> > Background:
> > The SOAPMessageFormatter writes the message to an OutputStream in all
> cases except SWA.
> > Writing to an OutputStream is faster and allows the other components to
> access the OutputStream.
> > Proposal:
> > I am making a small change to the SOAPMessageFormatter SWA flow to use a
> ByteArrayOutputStream as the buffer.
>
> --
> 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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
Sanjiva Weerawarana, Ph.D.
Founder, Director & Chief Scientist; Lanka Software Foundation;
http://www.opensource.lk/
Founder, Chairman & CEO; WSO2; http://wso2.com/
Founder & Director; Thinkcube Systems; http://www.thinkcube.com/
Member; Apache Software Foundation; http://www.apache.org/
Member; Sahana Software Foundation; http://www.sahanafoundation.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

Blog: http://sanjiva.weerawarana.org/

Re: [jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Rich, IMO this approach of opening an issue just to record a commit is
really not appropriate ... that's not what we use JIRA for!

Sanjiva.

On Mon, Sep 27, 2010 at 9:08 PM, Andreas Veithen (JIRA) <ji...@apache.org>wrote:

>
>    [
> https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915335#action_12915335]
>
> Andreas Veithen commented on AXIS2-4828:
> ----------------------------------------
>
> Rich, it would be nice if before marking an issue as resolved, you could
> read (and react to!) the comments left by others...
>
> > SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when
> doing SWA
> >
> ----------------------------------------------------------------------------------
> >
> >                 Key: AXIS2-4828
> >                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
> >             Project: Axis2
> >          Issue Type: Bug
> >          Components: kernel
> >            Reporter: Rich Scheuerle
> >            Assignee: Rich Scheuerle
> >   Original Estimate: 24h
> >  Remaining Estimate: 24h
> >
> > Background:
> > The SOAPMessageFormatter writes the message to an OutputStream in all
> cases except SWA.
> > Writing to an OutputStream is faster and allows the other components to
> access the OutputStream.
> > Proposal:
> > I am making a small change to the SOAPMessageFormatter SWA flow to use a
> ByteArrayOutputStream as the buffer.
>
> --
> 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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
Sanjiva Weerawarana, Ph.D.
Founder, Director & Chief Scientist; Lanka Software Foundation;
http://www.opensource.lk/
Founder, Chairman & CEO; WSO2; http://wso2.com/
Founder & Director; Thinkcube Systems; http://www.thinkcube.com/
Member; Apache Software Foundation; http://www.apache.org/
Member; Sahana Software Foundation; http://www.sahanafoundation.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

Blog: http://sanjiva.weerawarana.org/

Re: [jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Rich, IMO this approach of opening an issue just to record a commit is
really not appropriate ... that's not what we use JIRA for!

Sanjiva.

On Mon, Sep 27, 2010 at 9:08 PM, Andreas Veithen (JIRA) <ji...@apache.org>wrote:

>
>    [
> https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915335#action_12915335]
>
> Andreas Veithen commented on AXIS2-4828:
> ----------------------------------------
>
> Rich, it would be nice if before marking an issue as resolved, you could
> read (and react to!) the comments left by others...
>
> > SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when
> doing SWA
> >
> ----------------------------------------------------------------------------------
> >
> >                 Key: AXIS2-4828
> >                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
> >             Project: Axis2
> >          Issue Type: Bug
> >          Components: kernel
> >            Reporter: Rich Scheuerle
> >            Assignee: Rich Scheuerle
> >   Original Estimate: 24h
> >  Remaining Estimate: 24h
> >
> > Background:
> > The SOAPMessageFormatter writes the message to an OutputStream in all
> cases except SWA.
> > Writing to an OutputStream is faster and allows the other components to
> access the OutputStream.
> > Proposal:
> > I am making a small change to the SOAPMessageFormatter SWA flow to use a
> ByteArrayOutputStream as the buffer.
>
> --
> 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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
Sanjiva Weerawarana, Ph.D.
Founder, Director & Chief Scientist; Lanka Software Foundation;
http://www.opensource.lk/
Founder, Chairman & CEO; WSO2; http://wso2.com/
Founder & Director; Thinkcube Systems; http://www.thinkcube.com/
Member; Apache Software Foundation; http://www.apache.org/
Member; Sahana Software Foundation; http://www.sahanafoundation.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

Blog: http://sanjiva.weerawarana.org/

Re: [jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Rich, IMO this approach of opening an issue just to record a commit is
really not appropriate ... that's not what we use JIRA for!

Sanjiva.

On Mon, Sep 27, 2010 at 9:08 PM, Andreas Veithen (JIRA) <ji...@apache.org>wrote:

>
>    [
> https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915335#action_12915335]
>
> Andreas Veithen commented on AXIS2-4828:
> ----------------------------------------
>
> Rich, it would be nice if before marking an issue as resolved, you could
> read (and react to!) the comments left by others...
>
> > SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when
> doing SWA
> >
> ----------------------------------------------------------------------------------
> >
> >                 Key: AXIS2-4828
> >                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
> >             Project: Axis2
> >          Issue Type: Bug
> >          Components: kernel
> >            Reporter: Rich Scheuerle
> >            Assignee: Rich Scheuerle
> >   Original Estimate: 24h
> >  Remaining Estimate: 24h
> >
> > Background:
> > The SOAPMessageFormatter writes the message to an OutputStream in all
> cases except SWA.
> > Writing to an OutputStream is faster and allows the other components to
> access the OutputStream.
> > Proposal:
> > I am making a small change to the SOAPMessageFormatter SWA flow to use a
> ByteArrayOutputStream as the buffer.
>
> --
> 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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
Sanjiva Weerawarana, Ph.D.
Founder, Director & Chief Scientist; Lanka Software Foundation;
http://www.opensource.lk/
Founder, Chairman & CEO; WSO2; http://wso2.com/
Founder & Director; Thinkcube Systems; http://www.thinkcube.com/
Member; Apache Software Foundation; http://www.apache.org/
Member; Sahana Software Foundation; http://www.sahanafoundation.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

Blog: http://sanjiva.weerawarana.org/

[jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913756#action_12913756 ] 

Andreas Veithen commented on AXIS2-4828:
----------------------------------------

Rich,

In Axiom 1.2.9 I introduced a new API (meant as a replacement for MIMEOutputUtils; see WSCOMMONS-553) that entirely gets rid of the StringWriter stuff:

http://ws.apache.org/commons/axiom/apidocs/org/apache/axiom/mime/package-summary.html

The API itself even allows streaming of the parts (although the JavaMail based default implementation is not able to leverage this; see WSCOMMONS-554). Axiom uses this API internally to produce XOP/MTOM, but porting SOAPMessageFormatter to that new API is part of the unfinished work. Maybe this JIRA is an opportunity to rewrite that part of SOAPMessageFormatter properly once and for all?



> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


[jira] Resolved: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

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

Rich Scheuerle resolved AXIS2-4828.
-----------------------------------

    Resolution: Fixed

> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


[jira] Resolved: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

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

Rich Scheuerle resolved AXIS2-4828.
-----------------------------------

    Resolution: Fixed

> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


[jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913756#action_12913756 ] 

Andreas Veithen commented on AXIS2-4828:
----------------------------------------

Rich,

In Axiom 1.2.9 I introduced a new API (meant as a replacement for MIMEOutputUtils; see WSCOMMONS-553) that entirely gets rid of the StringWriter stuff:

http://ws.apache.org/commons/axiom/apidocs/org/apache/axiom/mime/package-summary.html

The API itself even allows streaming of the parts (although the JavaMail based default implementation is not able to leverage this; see WSCOMMONS-554). Axiom uses this API internally to produce XOP/MTOM, but porting SOAPMessageFormatter to that new API is part of the unfinished work. Maybe this JIRA is an opportunity to rewrite that part of SOAPMessageFormatter properly once and for all?



> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


[jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915335#action_12915335 ] 

Andreas Veithen commented on AXIS2-4828:
----------------------------------------

Rich, it would be nice if before marking an issue as resolved, you could read (and react to!) the comments left by others...

> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


[jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913756#action_12913756 ] 

Andreas Veithen commented on AXIS2-4828:
----------------------------------------

Rich,

In Axiom 1.2.9 I introduced a new API (meant as a replacement for MIMEOutputUtils; see WSCOMMONS-553) that entirely gets rid of the StringWriter stuff:

http://ws.apache.org/commons/axiom/apidocs/org/apache/axiom/mime/package-summary.html

The API itself even allows streaming of the parts (although the JavaMail based default implementation is not able to leverage this; see WSCOMMONS-554). Axiom uses this API internally to produce XOP/MTOM, but porting SOAPMessageFormatter to that new API is part of the unfinished work. Maybe this JIRA is an opportunity to rewrite that part of SOAPMessageFormatter properly once and for all?



> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


[jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915335#action_12915335 ] 

Andreas Veithen commented on AXIS2-4828:
----------------------------------------

Rich, it would be nice if before marking an issue as resolved, you could read (and react to!) the comments left by others...

> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


[jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913756#action_12913756 ] 

Andreas Veithen commented on AXIS2-4828:
----------------------------------------

Rich,

In Axiom 1.2.9 I introduced a new API (meant as a replacement for MIMEOutputUtils; see WSCOMMONS-553) that entirely gets rid of the StringWriter stuff:

http://ws.apache.org/commons/axiom/apidocs/org/apache/axiom/mime/package-summary.html

The API itself even allows streaming of the parts (although the JavaMail based default implementation is not able to leverage this; see WSCOMMONS-554). Axiom uses this API internally to produce XOP/MTOM, but porting SOAPMessageFormatter to that new API is part of the unfinished work. Maybe this JIRA is an opportunity to rewrite that part of SOAPMessageFormatter properly once and for all?



> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


[jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915335#action_12915335 ] 

Andreas Veithen commented on AXIS2-4828:
----------------------------------------

Rich, it would be nice if before marking an issue as resolved, you could read (and react to!) the comments left by others...

> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


[jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915335#action_12915335 ] 

Andreas Veithen commented on AXIS2-4828:
----------------------------------------

Rich, it would be nice if before marking an issue as resolved, you could read (and react to!) the comments left by others...

> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


[jira] Resolved: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

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

Rich Scheuerle resolved AXIS2-4828.
-----------------------------------

    Resolution: Fixed

> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


[jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915335#action_12915335 ] 

Andreas Veithen commented on AXIS2-4828:
----------------------------------------

Rich, it would be nice if before marking an issue as resolved, you could read (and react to!) the comments left by others...

> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


[jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913756#action_12913756 ] 

Andreas Veithen commented on AXIS2-4828:
----------------------------------------

Rich,

In Axiom 1.2.9 I introduced a new API (meant as a replacement for MIMEOutputUtils; see WSCOMMONS-553) that entirely gets rid of the StringWriter stuff:

http://ws.apache.org/commons/axiom/apidocs/org/apache/axiom/mime/package-summary.html

The API itself even allows streaming of the parts (although the JavaMail based default implementation is not able to leverage this; see WSCOMMONS-554). Axiom uses this API internally to produce XOP/MTOM, but porting SOAPMessageFormatter to that new API is part of the unfinished work. Maybe this JIRA is an opportunity to rewrite that part of SOAPMessageFormatter properly once and for all?



> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


[jira] Resolved: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

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

Rich Scheuerle resolved AXIS2-4828.
-----------------------------------

    Resolution: Fixed

> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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


[jira] Resolved: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

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

Rich Scheuerle resolved AXIS2-4828.
-----------------------------------

    Resolution: Fixed

> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4828
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4828
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases except SWA.
> Writing to an OutputStream is faster and allows the other components to access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a ByteArrayOutputStream as the buffer.

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