You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Glen Mazza <gr...@verizon.net> on 2007/05/02 23:45:50 UTC
Re: HELP - The attachments stream can only be accessed once; either by
using the IncomingAttachmentStreams class or by getting a collection of
AttachmentPart objects. They cannot both be called within the life time of the
same service request.
This may be related to AXIOM internally (I don't know if AXIOM is used
in Axis 1, however). I googled the error message and it seems like the
only thing that could cause that error message to occur (search on "The
attachments stream" within [1]) is that you called *both* getPart() and
getIncomingAttachmentStreams() -- but you can only call one of the
methods.
Glen
[1]
http://mail-archives.apache.org/mod_mbox/ws-commons-dev/200703.mbox/%
3C20070307145929.1D46A1A9838@eris.apache.org%3E
Am Mittwoch, den 02.05.2007, 16:20 -0500 schrieb Prasad Viswatmula:
> I am using Axis 1.4 and getting the above error.
>
> Thanks,
> Prasad
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: Appropriate place for transaction code?
Posted by Mi...@servicecanada.gc.ca.
Thanks, that does help!
Michael
-----Original Message-----
From: robert lazarski [mailto:robertlazarski@gmail.com]
Sent: Monday, May 07, 2007 9:44 AM
To: axis-user@ws.apache.org
Subject: Re: Appropriate place for transaction code?
Hi Michael,
When doing hibernate transactions with web services, one way to do it is to have the transaction boundary inside a method that the web service calls. Spring does that automagically if you set it up right - but it certainly isn't mandatory to use Spring to do hibernate transactions in a web services.
What you describe by your servlet filter seems to be what spring does in its Open Session In View pattern, so on the UI layer you could use the data after the session would normally terminate. In this case you probably just need a method that you call in a web service that opens and closes the session - managed by yourself or spring - since the data would presumably be in an OMElement or the chosen databinding, and not using attached hibernate objects.
HTH,
Robert
On 5/7/07, Michael.Davis@servicecanada.gc.ca < <ma...@servicecanada.gc.ca> Michael.Davis@servicecanada.gc.ca> wrote:
Thanks, that's helpful. I'll look into Spring.
I will be adding operations that do inserts and updates soon.
Regards,
Michael
> -----Original Message-----
> From: Glen Mazza [mailto: grm7793@verizon.net <ma...@verizon.net> ]
> Sent: Thursday, May 03, 2007 8:53 PM
> To: axis-user@ws.apache.org
> Subject: Re: Appropriate place for transaction code?
>
>
> Reading the third sentence of your email, you said the service is just
> *retrieving* data from the database (i.e. SQL SELECT), is
> that correct?
> If so, commits would not be a concern for you--you may be able to keep
> your service in application scope[1] and just initialize an instance
> variable to hold the session factory.
>
> Otherwise, I don't know if you're using Spring but the Axis2 Spring
> guide[2] may give you some ideas until someone else can get
> you a better
> answer.
>
> [1] http://www.developer.com/java/web/article.php/10935_3620661_2
> [2] http://ws.apache.org/axis2/1_2/spring.html
>
> Glen
>
>
> Am Donnerstag, den 03.05.2007, 16:26 -0400 schrieb
> Michael.Davis@servicecanada.gc.ca <ma...@servicecanada.gc.ca> :
> > Hi,
> >
> > I'm new to Axis. I'm using Axis2 1.1.1.
> >
> > I'm creating a service that retrieves data from a database.
> I'm using Hibernate. For those of you not familiar with it,
> the basic pattern of usage is that you create something
> called a SessionFactory once when the application starts, and
> then for each request/response cycle you create a Session.
> When the response finishes, you commit the session.
> >
> > In regular web applications I create the session factory in
> the ApplicationContext. Then I make a servlet filter that
> creates the session and starts a transaction on the way in,
> and then commits the transaction and closes the session on
> the way out.
> >
> > I'm trying to figure out how to do this in Axis. I created
> a module called hibernateTransactionModule. I've got two
> handlers, one for the way in and one for the way out, each
> attached to a new phase. Right now they're just saying 'hello
> world' and it works, they do execute when I expect them to.
> >
> > So I've got three classes:
> >
> > HibernateTransactionModule implements
> org.apache.axis2.modules.Module
> > HibernateTransactionHandlerBegin extends AbstractHandler
> implements Handler
> > HibernateTransactionHandlerEnd extends AbstractHandler
> implements Handler
> >
> > My intuition tells me that
> HibernateTransactionModule.init() would be the appropriate
> place to create the hibernate session factory,
> HibernateTransactionHandlerBegin.invoke() could create a
> session for a request and put it into the messageContext, and
> HibernateTransactionHandlerEnd.invoke () could commit the
> transaction and close the session.
> >
> > But I can't see a place where I can store the session
> factory where it can be accessible to the handlers.
> >
> > One possibility would be to use a static field in
> HibernateTransactionHandlerBegin but that would be an ugly
> hack. Any suggestions?
> >
> > Thanks
> > Michael Davis
> > www.damaru.com
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org <ma...@ws.apache.org>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Appropriate place for transaction code?
Posted by robert lazarski <ro...@gmail.com>.
Hi Michael,
When doing hibernate transactions with web services, one way to do it is to
have the transaction boundary inside a method that the web service calls.
Spring does that automagically if you set it up right - but it certainly
isn't mandatory to use Spring to do hibernate transactions in a web
services.
What you describe by your servlet filter seems to be what spring does in its
Open Session In View pattern, so on the UI layer you could use the data
after the session would normally terminate. In this case you probably just
need a method that you call in a web service that opens and closes the
session - managed by yourself or spring - since the data would presumably be
in an OMElement or the chosen databinding, and not using attached hibernate
objects.
HTH,
Robert
On 5/7/07, Michael.Davis@servicecanada.gc.ca <
Michael.Davis@servicecanada.gc.ca> wrote:
>
> Thanks, that's helpful. I'll look into Spring.
>
> I will be adding operations that do inserts and updates soon.
>
> Regards,
> Michael
>
> > -----Original Message-----
> > From: Glen Mazza [mailto:grm7793@verizon.net]
> > Sent: Thursday, May 03, 2007 8:53 PM
> > To: axis-user@ws.apache.org
> > Subject: Re: Appropriate place for transaction code?
> >
> >
> > Reading the third sentence of your email, you said the service is just
> > *retrieving* data from the database (i.e. SQL SELECT), is
> > that correct?
> > If so, commits would not be a concern for you--you may be able to keep
> > your service in application scope[1] and just initialize an instance
> > variable to hold the session factory.
> >
> > Otherwise, I don't know if you're using Spring but the Axis2 Spring
> > guide[2] may give you some ideas until someone else can get
> > you a better
> > answer.
> >
> > [1] http://www.developer.com/java/web/article.php/10935_3620661_2
> > [2] http://ws.apache.org/axis2/1_2/spring.html
> >
> > Glen
> >
> >
> > Am Donnerstag, den 03.05.2007, 16:26 -0400 schrieb
> > Michael.Davis@servicecanada.gc.ca:
> > > Hi,
> > >
> > > I'm new to Axis. I'm using Axis2 1.1.1.
> > >
> > > I'm creating a service that retrieves data from a database.
> > I'm using Hibernate. For those of you not familiar with it,
> > the basic pattern of usage is that you create something
> > called a SessionFactory once when the application starts, and
> > then for each request/response cycle you create a Session.
> > When the response finishes, you commit the session.
> > >
> > > In regular web applications I create the session factory in
> > the ApplicationContext. Then I make a servlet filter that
> > creates the session and starts a transaction on the way in,
> > and then commits the transaction and closes the session on
> > the way out.
> > >
> > > I'm trying to figure out how to do this in Axis. I created
> > a module called hibernateTransactionModule. I've got two
> > handlers, one for the way in and one for the way out, each
> > attached to a new phase. Right now they're just saying 'hello
> > world' and it works, they do execute when I expect them to.
> > >
> > > So I've got three classes:
> > >
> > > HibernateTransactionModule implements
> > org.apache.axis2.modules.Module
> > > HibernateTransactionHandlerBegin extends AbstractHandler
> > implements Handler
> > > HibernateTransactionHandlerEnd extends AbstractHandler
> > implements Handler
> > >
> > > My intuition tells me that
> > HibernateTransactionModule.init() would be the appropriate
> > place to create the hibernate session factory,
> > HibernateTransactionHandlerBegin.invoke() could create a
> > session for a request and put it into the messageContext, and
> > HibernateTransactionHandlerEnd.invoke() could commit the
> > transaction and close the session.
> > >
> > > But I can't see a place where I can store the session
> > factory where it can be accessible to the handlers.
> > >
> > > One possibility would be to use a static field in
> > HibernateTransactionHandlerBegin but that would be an ugly
> > hack. Any suggestions?
> > >
> > > Thanks
> > > Michael Davis
> > > www.damaru.com
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-user-help@ws.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
RE: Appropriate place for transaction code?
Posted by Mi...@servicecanada.gc.ca.
Thanks, that's helpful. I'll look into Spring.
I will be adding operations that do inserts and updates soon.
Regards,
Michael
> -----Original Message-----
> From: Glen Mazza [mailto:grm7793@verizon.net]
> Sent: Thursday, May 03, 2007 8:53 PM
> To: axis-user@ws.apache.org
> Subject: Re: Appropriate place for transaction code?
>
>
> Reading the third sentence of your email, you said the service is just
> *retrieving* data from the database (i.e. SQL SELECT), is
> that correct?
> If so, commits would not be a concern for you--you may be able to keep
> your service in application scope[1] and just initialize an instance
> variable to hold the session factory.
>
> Otherwise, I don't know if you're using Spring but the Axis2 Spring
> guide[2] may give you some ideas until someone else can get
> you a better
> answer.
>
> [1] http://www.developer.com/java/web/article.php/10935_3620661_2
> [2] http://ws.apache.org/axis2/1_2/spring.html
>
> Glen
>
>
> Am Donnerstag, den 03.05.2007, 16:26 -0400 schrieb
> Michael.Davis@servicecanada.gc.ca:
> > Hi,
> >
> > I'm new to Axis. I'm using Axis2 1.1.1.
> >
> > I'm creating a service that retrieves data from a database.
> I'm using Hibernate. For those of you not familiar with it,
> the basic pattern of usage is that you create something
> called a SessionFactory once when the application starts, and
> then for each request/response cycle you create a Session.
> When the response finishes, you commit the session.
> >
> > In regular web applications I create the session factory in
> the ApplicationContext. Then I make a servlet filter that
> creates the session and starts a transaction on the way in,
> and then commits the transaction and closes the session on
> the way out.
> >
> > I'm trying to figure out how to do this in Axis. I created
> a module called hibernateTransactionModule. I've got two
> handlers, one for the way in and one for the way out, each
> attached to a new phase. Right now they're just saying 'hello
> world' and it works, they do execute when I expect them to.
> >
> > So I've got three classes:
> >
> > HibernateTransactionModule implements
> org.apache.axis2.modules.Module
> > HibernateTransactionHandlerBegin extends AbstractHandler
> implements Handler
> > HibernateTransactionHandlerEnd extends AbstractHandler
> implements Handler
> >
> > My intuition tells me that
> HibernateTransactionModule.init() would be the appropriate
> place to create the hibernate session factory,
> HibernateTransactionHandlerBegin.invoke() could create a
> session for a request and put it into the messageContext, and
> HibernateTransactionHandlerEnd.invoke() could commit the
> transaction and close the session.
> >
> > But I can't see a place where I can store the session
> factory where it can be accessible to the handlers.
> >
> > One possibility would be to use a static field in
> HibernateTransactionHandlerBegin but that would be an ugly
> hack. Any suggestions?
> >
> > Thanks
> > Michael Davis
> > www.damaru.com
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Appropriate place for transaction code?
Posted by Glen Mazza <gr...@verizon.net>.
Reading the third sentence of your email, you said the service is just
*retrieving* data from the database (i.e. SQL SELECT), is that correct?
If so, commits would not be a concern for you--you may be able to keep
your service in application scope[1] and just initialize an instance
variable to hold the session factory.
Otherwise, I don't know if you're using Spring but the Axis2 Spring
guide[2] may give you some ideas until someone else can get you a better
answer.
[1] http://www.developer.com/java/web/article.php/10935_3620661_2
[2] http://ws.apache.org/axis2/1_2/spring.html
Glen
Am Donnerstag, den 03.05.2007, 16:26 -0400 schrieb
Michael.Davis@servicecanada.gc.ca:
> Hi,
>
> I'm new to Axis. I'm using Axis2 1.1.1.
>
> I'm creating a service that retrieves data from a database. I'm using Hibernate. For those of you not familiar with it, the basic pattern of usage is that you create something called a SessionFactory once when the application starts, and then for each request/response cycle you create a Session. When the response finishes, you commit the session.
>
> In regular web applications I create the session factory in the ApplicationContext. Then I make a servlet filter that creates the session and starts a transaction on the way in, and then commits the transaction and closes the session on the way out.
>
> I'm trying to figure out how to do this in Axis. I created a module called hibernateTransactionModule. I've got two handlers, one for the way in and one for the way out, each attached to a new phase. Right now they're just saying 'hello world' and it works, they do execute when I expect them to.
>
> So I've got three classes:
>
> HibernateTransactionModule implements org.apache.axis2.modules.Module
> HibernateTransactionHandlerBegin extends AbstractHandler implements Handler
> HibernateTransactionHandlerEnd extends AbstractHandler implements Handler
>
> My intuition tells me that HibernateTransactionModule.init() would be the appropriate place to create the hibernate session factory, HibernateTransactionHandlerBegin.invoke() could create a session for a request and put it into the messageContext, and HibernateTransactionHandlerEnd.invoke() could commit the transaction and close the session.
>
> But I can't see a place where I can store the session factory where it can be accessible to the handlers.
>
> One possibility would be to use a static field in HibernateTransactionHandlerBegin but that would be an ugly hack. Any suggestions?
>
> Thanks
> Michael Davis
> www.damaru.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Appropriate place for transaction code?
Posted by Mi...@servicecanada.gc.ca.
Hi,
I'm new to Axis. I'm using Axis2 1.1.1.
I'm creating a service that retrieves data from a database. I'm using Hibernate. For those of you not familiar with it, the basic pattern of usage is that you create something called a SessionFactory once when the application starts, and then for each request/response cycle you create a Session. When the response finishes, you commit the session.
In regular web applications I create the session factory in the ApplicationContext. Then I make a servlet filter that creates the session and starts a transaction on the way in, and then commits the transaction and closes the session on the way out.
I'm trying to figure out how to do this in Axis. I created a module called hibernateTransactionModule. I've got two handlers, one for the way in and one for the way out, each attached to a new phase. Right now they're just saying 'hello world' and it works, they do execute when I expect them to.
So I've got three classes:
HibernateTransactionModule implements org.apache.axis2.modules.Module
HibernateTransactionHandlerBegin extends AbstractHandler implements Handler
HibernateTransactionHandlerEnd extends AbstractHandler implements Handler
My intuition tells me that HibernateTransactionModule.init() would be the appropriate place to create the hibernate session factory, HibernateTransactionHandlerBegin.invoke() could create a session for a request and put it into the messageContext, and HibernateTransactionHandlerEnd.invoke() could commit the transaction and close the session.
But I can't see a place where I can store the session factory where it can be accessible to the handlers.
One possibility would be to use a static field in HibernateTransactionHandlerBegin but that would be an ugly hack. Any suggestions?
Thanks
Michael Davis
www.damaru.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: HELP - The attachments stream can only be accessed once; either by
using the IncomingAttachmentStreams class or by getting a collection of
AttachmentPart objects. They cannot both be called within the life time of the
same service request.
Posted by Glen Mazza <gr...@verizon.net>.
When debugging, work backwards. The first error line of your stack
trace says go to line 546 of AttachmentsImpl[1], which appears to
indicate a mistake similar to what I mentioned earlier. You are not
showing us your code, so I cannot help you further, but I think you are
making an invalid series of function calls to cause that error to occur.
Follow the Axis1 source code[1] and your own code to figure out what
sequence of calls you are making to cause that error to occur, and then
reimplement your code so you don't do that anymore.
If I may generalize your problem, this is your error message:
"You have called function foo() after calling function bar(), which is
disallowed."
And this is your source code:
a.bar();
a.foo();
Can you simplify your problem to this level, and then come back to this
ML for help in reimplementation? I.e. "Hello everybody, this is what
I'm coding to accomplish X, but Axis 1.4 says this ordering of function
calls is disallowed. How can I code it differently?"
Glen
[1] http://preview.tinyurl.com/32t97a
Am Donnerstag, den 03.05.2007, 12:46 -0500 schrieb Prasad Viswatmula:
> Here is my stack trace. It's not from AXIOM.
>
> java.lang.IllegalStateException: The attachments stream can only be
> accessed once; either by using the IncomingAttachmentStreams class or
> by getting a collection of AttachmentPart objects. They cannot both
> be called within the life time of the same service request.
> at org.apache.axis.attachments.AttachmentsImpl.getAttachmentCount(AttachmentsImpl.java:546)
> at org.apache.axis.Message.getContentLength(Message.java:511)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.apache.axis.utils.BeanPropertyDescriptor.get(BeanPropertyDescriptor.java:127)
> at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:192)
> at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
> at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
> at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:801)
> at org.apache.axis.message.RPCParam.serialize(RPCParam.java:208)
> at org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
> at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
> at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
> at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
> at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
> at org.apache.axis.client.Call.invoke(Call.java:2757)
> at org.apache.axis.client.Call.invoke(Call.java:2443)
> at org.apache.axis.client.Call.invoke(Call.java:2366)
> at org.apache.axis.client.Call.invoke(Call.java:1812)
> at com.walsworth.od2.FileWebServiceSoapBindingStub.put(FileWebServiceSoapBindingStub.java:334)
> at com.walsworth.od2.FileWSClient.main(FileWSClient.java:51)
>
> On 5/2/07, Glen Mazza <gr...@verizon.net> wrote:
> > This may be related to AXIOM internally (I don't know if AXIOM is used
> > in Axis 1, however). I googled the error message and it seems like the
> > only thing that could cause that error message to occur (search on "The
> > attachments stream" within [1]) is that you called *both* getPart() and
> > getIncomingAttachmentStreams() -- but you can only call one of the
> > methods.
> >
> > Glen
> >
> > [1]
> > http://mail-archives.apache.org/mod_mbox/ws-commons-dev/200703.mbox/%
> > 3C20070307145929.1D46A1A9838@eris.apache.org%3E
> >
> > Am Mittwoch, den 02.05.2007, 16:20 -0500 schrieb Prasad Viswatmula:
> > > I am using Axis 1.4 and getting the above error.
> > >
> > > Thanks,
> > > Prasad
> > >
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: HELP - The attachments stream can only be accessed once; either by using the IncomingAttachmentStreams class or by getting a collection of AttachmentPart objects. They cannot both be called within the life time of the same service request.
Posted by Prasad Viswatmula <pv...@gmail.com>.
Here is my stack trace. It's not from AXIOM.
java.lang.IllegalStateException: The attachments stream can only be
accessed once; either by using the IncomingAttachmentStreams class or
by getting a collection of AttachmentPart objects. They cannot both
be called within the life time of the same service request.
at org.apache.axis.attachments.AttachmentsImpl.getAttachmentCount(AttachmentsImpl.java:546)
at org.apache.axis.Message.getContentLength(Message.java:511)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.axis.utils.BeanPropertyDescriptor.get(BeanPropertyDescriptor.java:127)
at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:192)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:801)
at org.apache.axis.message.RPCParam.serialize(RPCParam.java:208)
at org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.client.Call.invoke(Call.java:2757)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.walsworth.od2.FileWebServiceSoapBindingStub.put(FileWebServiceSoapBindingStub.java:334)
at com.walsworth.od2.FileWSClient.main(FileWSClient.java:51)
On 5/2/07, Glen Mazza <gr...@verizon.net> wrote:
> This may be related to AXIOM internally (I don't know if AXIOM is used
> in Axis 1, however). I googled the error message and it seems like the
> only thing that could cause that error message to occur (search on "The
> attachments stream" within [1]) is that you called *both* getPart() and
> getIncomingAttachmentStreams() -- but you can only call one of the
> methods.
>
> Glen
>
> [1]
> http://mail-archives.apache.org/mod_mbox/ws-commons-dev/200703.mbox/%
> 3C20070307145929.1D46A1A9838@eris.apache.org%3E
>
> Am Mittwoch, den 02.05.2007, 16:20 -0500 schrieb Prasad Viswatmula:
> > I am using Axis 1.4 and getting the above error.
> >
> > Thanks,
> > Prasad
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org