You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2006/01/10 05:59:21 UTC
[jira] Created: (AXIS2-372) Client API support Attachments (like
Axis 1.X)
Client API support Attachments (like Axis 1.X)
----------------------------------------------
Key: AXIS2-372
URL: http://issues.apache.org/jira/browse/AXIS2-372
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Reporter: Davanum Srinivas
Use case: want to write an intermediary that peeks just the soap
headers and forwards messages with MTOM or SwA attachments. i don't
think our users can implement this with current public API. They would
have to muck around with the internals which can change. Also, we need
streaming support similar to one that was added in Axis 1.3
--
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
Re: [jira] Created: (AXIS2-372) Client API support Attachments (like Axis 1.X)
Posted by Thilina Gunarathne <cs...@gmail.com>.
Hmmm..... Interesting....
IMHO Axis2 is not that bad... Not bad in the sense we access the attachments
only if the user wants them at the business logic. We haven't still read the
attachment when we get an binary OMText object in to the service impl or
client's program. We read the stream only when OMText.getDataHandleris
called. IIRC That's what we called double deffered building for
attachments.
It would be really nice if we can give the users direct access to the
underlying stream. A small concern I have is what to do when there are
multiple attachments.
Thanks,
~Thilina
On 1/18/06, Davanum Srinivas <da...@gmail.com> wrote:
>
> Please see http://issues.apache.org/jira/browse/AXIS-2221
>
> On 1/17/06, Thilina Gunarathne <cs...@gmail.com> wrote:
> > Hi,
> > >>we need streaming support similar to one that was added in Axis 1.3
> >
> > Can you please explain what you mean by Streaming. Idea is not clear to
> > me... I'm sure a explanation will benefit others as well..
> >
> > Thanks,
> > ~Thilina
> >
> >
> > On 1/10/06, Davanum Srinivas (JIRA) <ji...@apache.org> wrote:
> > > Client API support Attachments (like Axis 1.X)
> > > ----------------------------------------------
> > >
> > > Key: AXIS2-372
> > > URL:
> > http://issues.apache.org/jira/browse/AXIS2-372
> > > Project: Apache Axis 2.0 (Axis2)
> > > Type: Bug
> > > Reporter: Davanum Srinivas
> > >
> > >
> > > Use case: want to write an intermediary that peeks just the soap
> > > headers and forwards messages with MTOM or SwA attachments. i don't
> > > think our users can implement this with current public API. They would
> > > have to muck around with the internals which can change. Also, we need
> > > streaming support similar to one that was added in Axis 1.3
> > >
> > > --
> > > 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
> > >
> > >
> >
> >
> >
> > --
> > "May the SourcE be with u"
> > http://webservices.apache.org/~thilina/
> > http://thilinag.blogspot.com/
> > http://www.bloglines.com/blog/Thilina
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/
http://www.bloglines.com/blog/Thilina
Re: [jira] Created: (AXIS2-372) Client API support Attachments (like Axis 1.X)
Posted by Davanum Srinivas <da...@gmail.com>.
Please see http://issues.apache.org/jira/browse/AXIS-2221
On 1/17/06, Thilina Gunarathne <cs...@gmail.com> wrote:
> Hi,
> >>we need streaming support similar to one that was added in Axis 1.3
>
> Can you please explain what you mean by Streaming. Idea is not clear to
> me... I'm sure a explanation will benefit others as well..
>
> Thanks,
> ~Thilina
>
>
> On 1/10/06, Davanum Srinivas (JIRA) <ji...@apache.org> wrote:
> > Client API support Attachments (like Axis 1.X)
> > ----------------------------------------------
> >
> > Key: AXIS2-372
> > URL:
> http://issues.apache.org/jira/browse/AXIS2-372
> > Project: Apache Axis 2.0 (Axis2)
> > Type: Bug
> > Reporter: Davanum Srinivas
> >
> >
> > Use case: want to write an intermediary that peeks just the soap
> > headers and forwards messages with MTOM or SwA attachments. i don't
> > think our users can implement this with current public API. They would
> > have to muck around with the internals which can change. Also, we need
> > streaming support similar to one that was added in Axis 1.3
> >
> > --
> > 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
> >
> >
>
>
>
> --
> "May the SourcE be with u"
> http://webservices.apache.org/~thilina/
> http://thilinag.blogspot.com/
> http://www.bloglines.com/blog/Thilina
--
Davanum Srinivas : http://wso2.com/blogs/
Re: [jira] Created: (AXIS2-372) Client API support Attachments (like Axis 1.X)
Posted by Thilina Gunarathne <cs...@gmail.com>.
Hi,
>>we need streaming support similar to one that was added in Axis 1.3
Can you please explain what you mean by Streaming. Idea is not clear to
me... I'm sure a explanation will benefit others as well..
Thanks,
~Thilina
On 1/10/06, Davanum Srinivas (JIRA) <ji...@apache.org> wrote:
>
> Client API support Attachments (like Axis 1.X)
> ----------------------------------------------
>
> Key: AXIS2-372
> URL: http://issues.apache.org/jira/browse/AXIS2-372
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Davanum Srinivas
>
>
> Use case: want to write an intermediary that peeks just the soap
> headers and forwards messages with MTOM or SwA attachments. i don't
> think our users can implement this with current public API. They would
> have to muck around with the internals which can change. Also, we need
> streaming support similar to one that was added in Axis 1.3
>
> --
> 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
>
>
--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/
http://www.bloglines.com/blog/Thilina
[jira] Commented: (AXIS2-372) Client API support Attachments (like
Axis 1.X)
Posted by "Thilina Gunarathne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-372?page=comments#action_12372610 ]
Thilina Gunarathne commented on AXIS2-372:
------------------------------------------
We can use two approches for this..
One approach is to provide the needed getStreams and other neccessary methodes to the MIMEHelper...
Other solution is to introduce SOAPMessage and make it a place holder for attachments with neccessary attachment handling API..
IIRC there were loads of debates went on regarding the introduction of SOAPMessage. I can't remember whether we came to a conclusion...
> Client API support Attachments (like Axis 1.X)
> ----------------------------------------------
>
> Key: AXIS2-372
> URL: http://issues.apache.org/jira/browse/AXIS2-372
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Davanum Srinivas
> Priority: Blocker
>
> Use case: want to write an intermediary that peeks just the soap
> headers and forwards messages with MTOM or SwA attachments. i don't
> think our users can implement this with current public API. They would
> have to muck around with the internals which can change. Also, we need
> streaming support similar to one that was added in Axis 1.3
--
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
[jira] Commented: (AXIS2-372) Client API support Attachments (like
Axis 1.X)
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-372?page=comments#action_12363021 ]
Davanum Srinivas commented on AXIS2-372:
----------------------------------------
Please see http://issues.apache.org/jira/browse/AXIS-2221
> Client API support Attachments (like Axis 1.X)
> ----------------------------------------------
>
> Key: AXIS2-372
> URL: http://issues.apache.org/jira/browse/AXIS2-372
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Davanum Srinivas
>
> Use case: want to write an intermediary that peeks just the soap
> headers and forwards messages with MTOM or SwA attachments. i don't
> think our users can implement this with current public API. They would
> have to muck around with the internals which can change. Also, we need
> streaming support similar to one that was added in Axis 1.3
--
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
[jira] Resolved: (AXIS2-372) Client API support Attachments (like
Axis 1.X)
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-372?page=all ]
Davanum Srinivas resolved AXIS2-372:
------------------------------------
Resolution: Fixed
having applied with deepak's patch. marking this as fixed.
thanks,
dims
> Client API support Attachments (like Axis 1.X)
> ----------------------------------------------
>
> Key: AXIS2-372
> URL: http://issues.apache.org/jira/browse/AXIS2-372
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Davanum Srinivas
>
> Use case: want to write an intermediary that peeks just the soap
> headers and forwards messages with MTOM or SwA attachments. i don't
> think our users can implement this with current public API. They would
> have to muck around with the internals which can change. Also, we need
> streaming support similar to one that was added in Axis 1.3
--
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
[jira] Updated: (AXIS2-372) Client API support Attachments (like
Axis 1.X)
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-372?page=all ]
Davanum Srinivas updated AXIS2-372:
-----------------------------------
Priority: Blocker (was: Major)
Blocker for 1.0 release?
> Client API support Attachments (like Axis 1.X)
> ----------------------------------------------
>
> Key: AXIS2-372
> URL: http://issues.apache.org/jira/browse/AXIS2-372
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Davanum Srinivas
> Priority: Blocker
>
> Use case: want to write an intermediary that peeks just the soap
> headers and forwards messages with MTOM or SwA attachments. i don't
> think our users can implement this with current public API. They would
> have to muck around with the internals which can change. Also, we need
> streaming support similar to one that was added in Axis 1.3
--
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
[jira] Updated: (AXIS2-372) Client API support Attachments (like
Axis 1.X)
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-372?page=all ]
Davanum Srinivas updated AXIS2-372:
-----------------------------------
Priority: Major (was: Blocker)
Needs more on list discussion...adding SOAPMessage is too much change. Exposing MimeHelper may not be too much change. Lowering priority for now.
> Client API support Attachments (like Axis 1.X)
> ----------------------------------------------
>
> Key: AXIS2-372
> URL: http://issues.apache.org/jira/browse/AXIS2-372
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Davanum Srinivas
>
> Use case: want to write an intermediary that peeks just the soap
> headers and forwards messages with MTOM or SwA attachments. i don't
> think our users can implement this with current public API. They would
> have to muck around with the internals which can change. Also, we need
> streaming support similar to one that was added in Axis 1.3
--
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
[jira] Commented: (AXIS2-372) Client API support Attachments (like
Axis 1.X)
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-372?page=comments#action_12372628 ]
Davanum Srinivas commented on AXIS2-372:
----------------------------------------
+1 to "Other solution is to introduce SOAPMessage". Should go well with the related issue "lower-level MTOM support for DB frameworks" (see http://marc.theaimsgroup.com/?l=axis-dev&m=114369376121775&w=2)
thanks,
dims
> Client API support Attachments (like Axis 1.X)
> ----------------------------------------------
>
> Key: AXIS2-372
> URL: http://issues.apache.org/jira/browse/AXIS2-372
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Davanum Srinivas
> Priority: Blocker
>
> Use case: want to write an intermediary that peeks just the soap
> headers and forwards messages with MTOM or SwA attachments. i don't
> think our users can implement this with current public API. They would
> have to muck around with the internals which can change. Also, we need
> streaming support similar to one that was added in Axis 1.3
--
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