i should get first token then issueKey then remoteComment object but
in envelope i get first remoteComment next token next issueKey. I
must have this in right order my server expects it and i get error
response: org.xml.sax.SAXException: SimpleDeserializer encountered a
child element, which is NOT expected, in something it was trying to
deserialize.
Currently SoapObjects are treated differently than properties, and are not able to be ordered. SoapObjects are printed first, followed by properties. For now you will have change your server code.
I will work on a fix for this, since it seems to keep on coming up.
On Thursday, January 12, 2012, Dawid Drozd <drozddawid....@gmail.com> wrote: > Hello
> I have a litle bit problem with that:
> In code:
> SoapObject remoteComment = new SoapObject("http:// > beans.soap.rpc.jira.atlassian.com", > "RemoteComment"); > SoapObject addComment = new
> i should get first token then issueKey then remoteComment object but > in envelope i get first remoteComment next token next issueKey. I > must have this in right order my server expects it and i get error > response: org.xml.sax.SAXException: SimpleDeserializer encountered a > child element, which is NOT expected, in something it was trying to > deserialize.
> Currently SoapObjects are treated differently than properties, and are not > able to be ordered. SoapObjects are printed first, followed by properties. > For now you will have change your server code.
> I will work on a fix for this, since it seems to keep on coming up.
> On Thursday, January 12, 2012, Dawid Drozd <drozddawid....@gmail.com> wrote: >> Hello
>> i should get first token then issueKey then remoteComment object but >> in envelope i get first remoteComment next token next issueKey. I >> must have this in right order my server expects it and i get error >> response: org.xml.sax.SAXException: SimpleDeserializer encountered a >> child element, which is NOT expected, in something it was trying to >> deserialize.
> Ok then i will try fix it too because i can't edit server code :) and > i must do it quick so i will try. If i do it good i will do pull > request.
> Thanks again.
> 2012/1/13 Andrew Oppenlander <andrew.oppenlan...@gmail.com>: > > Currently SoapObjects are treated differently than properties, and are > not > > able to be ordered. SoapObjects are printed first, followed by > properties. > > For now you will have change your server code.
> > I will work on a fix for this, since it seems to keep on coming up.
> > On Thursday, January 12, 2012, Dawid Drozd <drozddawid....@gmail.com> > wrote: > >> Hello
> >> i should get first token then issueKey then remoteComment object but > >> in envelope i get first remoteComment next token next issueKey. I > >> must have this in right order my server expects it and i get error > >> response: org.xml.sax.SAXException: SimpleDeserializer encountered a > >> child element, which is NOT expected, in something it was trying to > >> deserialize.
> On Thu, Jan 12, 2012 at 6:51 PM, Dawid Drozd <drozddawid....@gmail.com>wrote:
>> Ok then i will try fix it too because i can't edit server code :) and >> i must do it quick so i will try. If i do it good i will do pull >> request.
>> Thanks again.
>> 2012/1/13 Andrew Oppenlander <andrew.oppenlan...@gmail.com>: >> > Currently SoapObjects are treated differently than properties, and are >> not >> > able to be ordered. SoapObjects are printed first, followed by >> properties. >> > For now you will have change your server code.
>> > I will work on a fix for this, since it seems to keep on coming up.
>> > On Thursday, January 12, 2012, Dawid Drozd <drozddawid....@gmail.com> >> wrote: >> >> Hello
>> >> i should get first token then issueKey then remoteComment object but >> >> in envelope i get first remoteComment next token next issueKey. I >> >> must have this in right order my server expects it and i get error >> >> response: org.xml.sax.SAXException: SimpleDeserializer encountered a >> >> child element, which is NOT expected, in something it was trying to >> >> deserialize.
Sorry but i pull changes from you and they don't work i have exception:
: org.ksoap2.serialization.SoapObject : java.lang.ClassCastException: org.ksoap2.serialization.SoapObject : at org.ksoap2.serialization.SoapObject.toString(SoapObject.java:518) : at java.lang.StringBuilder.append(StringBuilder.java:203) : at jira.For.Android.Connector.Connector.getResponseFromServer(Connector.java:8 2)
When i try to do this:
System.out.println("Tak wygląda to co chce wysłac: " + ENVELOPE.bodyOut);
> I will pull this in and cut a new release early next week..
> On Jan 12, 2012 10:21 PM, "Andrew Oppenlander" > <andrew.oppenlan...@gmail.com> wrote:
>> I've completed the patch and sent a pull request. Some more testing should >> probably be done to ensure that it's all working properly though. >> Here is my git repo and here is a link to the assembly with dependencies.
>> On Thu, Jan 12, 2012 at 6:51 PM, Dawid Drozd <drozddawid....@gmail.com> >> wrote:
>>> Ok then i will try fix it too because i can't edit server code :) and >>> i must do it quick so i will try. If i do it good i will do pull >>> request.
>>> Thanks again.
>>> 2012/1/13 Andrew Oppenlander <andrew.oppenlan...@gmail.com>: >>> > Currently SoapObjects are treated differently than properties, and are >>> > not >>> > able to be ordered. SoapObjects are printed first, followed by >>> > properties. >>> > For now you will have change your server code.
>>> > I will work on a fix for this, since it seems to keep on coming up.
>>> > On Thursday, January 12, 2012, Dawid Drozd <drozddawid....@gmail.com> >>> > wrote: >>> >> Hello
>>> >> i should get first token then issueKey then remoteComment object but >>> >> in envelope i get first remoteComment next token next issueKey. I >>> >> must have this in right order my server expects it and i get error >>> >> response: org.xml.sax.SAXException: SimpleDeserializer encountered a >>> >> child element, which is NOT expected, in something it was trying to >>> >> deserialize.
> System.out.println("Tak wygląda to co chce wysłac: " + ENVELOPE.bodyOut);
> Previously it works.
> 2012/1/13 Manfred Moser <mosa...@gmail.com>: >> I will pull this in and cut a new release early next week..
>> On Jan 12, 2012 10:21 PM, "Andrew Oppenlander" >> <andrew.oppenlan...@gmail.com> wrote:
>>> I've completed the patch and sent a pull request. Some more testing should >>> probably be done to ensure that it's all working properly though. >>> Here is my git repo and here is a link to the assembly with dependencies.
>>> On Thu, Jan 12, 2012 at 6:51 PM, Dawid Drozd <drozddawid....@gmail.com> >>> wrote:
>>>> Ok then i will try fix it too because i can't edit server code :) and >>>> i must do it quick so i will try. If i do it good i will do pull >>>> request.
>>>> Thanks again.
>>>> 2012/1/13 Andrew Oppenlander <andrew.oppenlan...@gmail.com>: >>>> > Currently SoapObjects are treated differently than properties, and are >>>> > not >>>> > able to be ordered. SoapObjects are printed first, followed by >>>> > properties. >>>> > For now you will have change your server code.
>>>> > I will work on a fix for this, since it seems to keep on coming up.
>>>> > On Thursday, January 12, 2012, Dawid Drozd <drozddawid....@gmail.com> >>>> > wrote: >>>> >> Hello
>>>> >> i should get first token then issueKey then remoteComment object but >>>> >> in envelope i get first remoteComment next token next -- > Pozdrawiam > Dawid Drozd.
andrew.oppenlan...@gmail.com> wrote: > I probably broke SoapObject.toString. Can you make a test service call and > see if the out body is correct?
> On Friday, January 13, 2012, Dawid Drozd <drozddawid....@gmail.com> wrote: > > Sorry but i pull changes from you and they don't work i have exception:
> > : org.ksoap2.serialization.SoapObject > > : java.lang.ClassCastException: org.ksoap2.serialization.SoapObject > > : at > org.ksoap2.serialization.SoapObject.toString(SoapObject.java:518) > > : at java.lang.StringBuilder.append(StringBuilder.java:203) > > : at > jira.For.Android.Connector.Connector.getResponseFromServer(Connector.java:8 2)
> > When i try to do this:
> > System.out.println("Tak wygląda to co chce wysłac: " + ENVELOPE.bodyOut);
> > Previously it works.
> > 2012/1/13 Manfred Moser <mosa...@gmail.com>: > >> I will pull this in and cut a new release early next week..
> >> On Jan 12, 2012 10:21 PM, "Andrew Oppenlander" > >> <andrew.oppenlan...@gmail.com> wrote:
> >>> I've completed the patch and sent a pull request. Some more testing > should > >>> probably be done to ensure that it's all working properly though. > >>> Here is my git repo and here is a link to the assembly with > dependencies.
> >>> On Thu, Jan 12, 2012 at 6:51 PM, Dawid Drozd <drozddawid....@gmail.com
> >>> wrote:
> >>>> Ok then i will try fix it too because i can't edit server code :) and > >>>> i must do it quick so i will try. If i do it good i will do pull > >>>> request.
> >>>> Thanks again.
> >>>> 2012/1/13 Andrew Oppenlander <andrew.oppenlan...@gmail.com>: > >>>> > Currently SoapObjects are treated differently than properties, and > are > >>>> > not > >>>> > able to be ordered. SoapObjects are printed first, followed by > >>>> > properties. > >>>> > For now you will have change your server code.
> >>>> > I will work on a fix for this, since it seems to keep on coming up.
> I was right with my assumption. SoapObject.toString was trying to convert > all object in properties to PropertyInfo. It should all be working now. > Again here is my github, and here is the jar with dependencies.
> On Fri, Jan 13, 2012 at 6:02 PM, Andrew Oppenlander > <andrew.oppenlan...@gmail.com> wrote:
>> I probably broke SoapObject.toString. Can you make a test service call and >> see if the out body is correct?
>> On Friday, January 13, 2012, Dawid Drozd <drozddawid....@gmail.com> wrote: >> > Sorry but i pull changes from you and they don't work i have exception:
>> > : org.ksoap2.serialization.SoapObject >> > : java.lang.ClassCastException: org.ksoap2.serialization.SoapObject >> > : at >> > org.ksoap2.serialization.SoapObject.toString(SoapObject.java:518) >> > : at java.lang.StringBuilder.append(StringBuilder.java:203) >> > : at >> > jira.For.Android.Connector.Connector.getResponseFromServer(Connector.java:8 2)
>> > When i try to do this:
>> > System.out.println("Tak wygląda to co chce wysłac: " + >> > ENVELOPE.bodyOut);
>> > Previously it works.
>> > 2012/1/13 Manfred Moser <mosa...@gmail.com>: >> >> I will pull this in and cut a new release early next week..
>> >> On Jan 12, 2012 10:21 PM, "Andrew Oppenlander" >> >> <andrew.oppenlan...@gmail.com> wrote:
>> >>> I've completed the patch and sent a pull request. Some more testing >> >>> should >> >>> probably be done to ensure that it's all working properly though. >> >>> Here is my git repo and here is a link to the assembly with >> >>> dependencies.
>> >>> On Thu, Jan 12, 2012 at 6:51 PM, Dawid Drozd >> >>> <drozddawid....@gmail.com> >> >>> wrote:
>> >>>> Ok then i will try fix it too because i can't edit server code :) and >> >>>> i must do it quick so i will try. If i do it good i will do pull >> >>>> request.
>> >>>> Thanks again.
>> >>>> 2012/1/13 Andrew Oppenlander <andrew.oppenlan...@gmail.com>: >> >>>> > Currently SoapObjects are treated differently than properties, and >> >>>> > are >> >>>> > not >> >>>> > able to be ordered. SoapObjects are printed first, followed by >> >>>> > properties. >> >>>> > For now you will have change your server code.
>> >>>> > I will work on a fix for this, since it seems to keep on coming up.
>> >>>> >> i should get first token then issueKey then remoteComment object >> >>>> >> but >> >>>> >> in envelope i get first remoteComment next token next --
On Sat, Jan 14, 2012 at 1:23 AM, Dawid Drozd <drozddawid....@gmail.com> wrote: > Yeah it works great work! Thanks a lot.
> 2012/1/14 Andrew Oppenlander <andrew.oppenlan...@gmail.com>: >> I was right with my assumption. SoapObject.toString was trying to convert >> all object in properties to PropertyInfo. It should all be working now. >> Again here is my github, and here is the jar with dependencies.
>> On Fri, Jan 13, 2012 at 6:02 PM, Andrew Oppenlander >> <andrew.oppenlan...@gmail.com> wrote:
>>> I probably broke SoapObject.toString. Can you make a test service call and >>> see if the out body is correct?
>>> On Friday, January 13, 2012, Dawid Drozd <drozddawid....@gmail.com> wrote: >>> > Sorry but i pull changes from you and they don't work i have exception:
>>> > : org.ksoap2.serialization.SoapObject >>> > : java.lang.ClassCastException: org.ksoap2.serialization.SoapObject >>> > : at >>> > org.ksoap2.serialization.SoapObject.toString(SoapObject.java:518) >>> > : at java.lang.StringBuilder.append(StringBuilder.java:203) >>> > : at >>> > jira.For.Android.Connector.Connector.getResponseFromServer(Connector.java:8 2)
>>> > When i try to do this:
>>> > System.out.println("Tak wygląda to co chce wysłac: " + >>> > ENVELOPE.bodyOut);
>>> > Previously it works.
>>> > 2012/1/13 Manfred Moser <mosa...@gmail.com>: >>> >> I will pull this in and cut a new release early next week..
>>> >> On Jan 12, 2012 10:21 PM, "Andrew Oppenlander" >>> >> <andrew.oppenlan...@gmail.com> wrote:
>>> >>> I've completed the patch and sent a pull request. Some more testing >>> >>> should >>> >>> probably be done to ensure that it's all working properly though. >>> >>> Here is my git repo and here is a link to the assembly with >>> >>> dependencies.
>>> >>> On Thu, Jan 12, 2012 at 6:51 PM, Dawid Drozd >>> >>> <drozddawid....@gmail.com> >>> >>> wrote:
>>> >>>> Ok then i will try fix it too because i can't edit server code :) and >>> >>>> i must do it quick so i will try. If i do it good i will do pull >>> >>>> request.
>>> >>>> Thanks again.
>>> >>>> 2012/1/13 Andrew Oppenlander <andrew.oppenlan...@gmail.com>: >>> >>>> > Currently SoapObjects are treated differently than properties, and >>> >>>> > are >>> >>>> > not >>> >>>> > able to be ordered. SoapObjects are printed first, followed by >>> >>>> > properties. >>> >>>> > For now you will have change your server code.
>>> >>>> > I will work on a fix for this, since it seems to keep on coming up.
>>> >>>> >> i should get first token then issueKey then remoteComment object >>> >>>> >> but >>> >>>> >> in envelope i get first remoteComment next token next --