You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Bummer <sa...@gmail.com> on 2007/05/31 03:54:47 UTC
Re: java.lang.IllegalStateException: Current state not
START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE
I attached the error stack below. You can check it if you can follow the
JSR181 Orchestration sample.
The JSR181 ochestration sample just don't work. Maybe one of the WSDL
(uszip, localtime)
might be changed after you guys wrote the tutorial or it might be a bug....
gnodet wrote:
>
> Can you post the full stack trace and any code / config that
> might help to understand the problem ?
>
> On 2/21/07, migue <mi...@guadaltel.es> wrote:
>>
>> Hi,
>> I have implemented an example of Orchestration with JSR181 and I when run
>> it
>> throws the following exception:
>> java.lang.IllegalStateException: Current state not START_ELEMENT,
>> END_ELEMENT or ENTITY_REFERENCE
>> at
>> com.ctc.wstx.sr.BasicStreamReader.getLocalName(BasicStreamReader.java:708)
>> ...
>>
>> Any help?
>> Thanks a lot,
>> Migue
>> --
>> View this message in context:
>> http://www.nabble.com/java.lang.IllegalStateException%3A-Current-state-not-START_ELEMENT%2C-END_ELEMENT-or-ENTITY_REFERENCE-tf3268154s12049.html#a9085326
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Architect, LogicBlaze (http://www.logicblaze.com/)
> Blog: http://gnodet.blogspot.com/
>
>
--
View this message in context: http://www.nabble.com/java.lang.IllegalStateException%3A-Current-state-not-START_ELEMENT%2C-END_ELEMENT-or-ENTITY_REFERENCE-tf3268154s12049.html#a10886080
Sent from the ServiceMix - User mailing list archive at Nabble.com.
RE: java.lang.IllegalStateException: Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE
Posted by mr...@wipro.com.
I am also stuck at the exact place with the same exception. I don't
think it has to do with the external WSDLs. I had created my own web
services and trying to orchestrate them with the jsr example.
-----Original Message-----
From: Bummer [mailto:sangwoo.hahn@gmail.com]
Sent: Thursday, May 31, 2007 7:25 AM
To: servicemix-users@geronimo.apache.org
Subject: Re: java.lang.IllegalStateException: Current state not
START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE
I attached the error stack below. You can check it if you can follow the
JSR181 Orchestration sample.
The JSR181 ochestration sample just don't work. Maybe one of the WSDL
(uszip, localtime)
might be changed after you guys wrote the tutorial or it might be a
bug....
gnodet wrote:
>
> Can you post the full stack trace and any code / config that
> might help to understand the problem ?
>
> On 2/21/07, migue <mi...@guadaltel.es> wrote:
>>
>> Hi,
>> I have implemented an example of Orchestration with JSR181 and I when
run
>> it
>> throws the following exception:
>> java.lang.IllegalStateException: Current state not START_ELEMENT,
>> END_ELEMENT or ENTITY_REFERENCE
>> at
>>
com.ctc.wstx.sr.BasicStreamReader.getLocalName(BasicStreamReader.java:70
8)
>> ...
>>
>> Any help?
>> Thanks a lot,
>> Migue
>> --
>> View this message in context:
>>
http://www.nabble.com/java.lang.IllegalStateException%3A-Current-state-n
ot-START_ELEMENT%2C-END_ELEMENT-or-ENTITY_REFERENCE-tf3268154s12049.html
#a9085326
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Architect, LogicBlaze (http://www.logicblaze.com/)
> Blog: http://gnodet.blogspot.com/
>
>
--
View this message in context:
http://www.nabble.com/java.lang.IllegalStateException%3A-Current-state-n
ot-START_ELEMENT%2C-END_ELEMENT-or-ENTITY_REFERENCE-tf3268154s12049.html
#a10886080
Sent from the ServiceMix - User mailing list archive at Nabble.com.
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com