Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
Locked
0

Extending HttpService

New Here ,
Aug 07, 2008 Aug 07, 2008
Hello,<br /><br />I am trying to extend the class mx.rpc.http.mxml.HTTPService. It works but when I try to use an inner tag for the request, I get a compilation "Could not resolve <test> to a component implementation". It seems that the compiler is trying to find a class matching for the content of the <myns:request> tag when it shouldn't.<br /><br />Exemple:<br /> <myns:HttpService<br /> result="read_result(event)" <br /> fault="main_fault(event)" <br /> showBusyCursor="true" <br /> method="POST" <br /> id="srv_read" <br /> url="{urlSvr}"> <br /> <myns:request><br /> <test>coucou<test><br /> </myns:request><br /> </myns:HttpService><br /><br />I have seen a jira case similar to this in http://bugs.adobe.com/jira/browse/SDK-14688.<br /><br />Is there a solution to this problem ?<br /><br />Thanks<br /><br />toni
TOPICS
Developers
1.6K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Aug 07, 2008 Aug 07, 2008
HTTPService has some hardcoded compiler support for its MXML parsing and it's possible we have a bug in there. Might be worth debugging the MXML compiler, look for HTTPService in the compiler and you can see where elements get parsed and used.<br /><br />Matt<br /><br /><br />On 8/7/08 7:05 AM, "aparolini" <member@adobeforums.com> wrote:<br /><br />A new discussion was started by aparolini in<br /><br />Developers --<br /> Extending HttpService<br /><br />Hello,<br /><br />I am trying to extend the class mx.rpc.http.mxml.HTTPService. It works but when I try to use an inner tag for the request, I get a compilation "Could not resolve <test> to a component implementation". It seems that the compiler is trying to find a class matching for the content of the <myns:request> tag when it shouldn't.<br /><br />Exemple:<br /><myns:HttpService result="read_result(event)" fault="main_fault(event)" showBusyCursor="true" method="POST" id="srv_read" url="{urlSvr}"><br /><myns:request><br /><test>coucou<test><br /></myns:request><br /> </myns:HttpService><br /><br />I have seen a jira case similar to this in http://bugs.adobe.com/jira/browse/SDK-14688.<br /><br />Is there a solution to this problem ?<br /><br />Thanks<br /><br />toni<br /><br />________________________________<br />View/reply at Extending HttpService <a href=http://www.adobeforums.com/webx?13@@.59b6194b><br />Replies by email are OK.<br />Use the unsubscribe <a href=http://www.adobeforums.com/webx?280@@.59b6194b!folder=.3c060fa3> form to cancel your email subscription.
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Aug 07, 2008 Aug 07, 2008
I'd imagine that we aren't checking if a component is a subclasse of <br />HTTPService when were parsing. You should looks for missing behavior <br />like that.<br /><br />On Aug 7, 2008, at 10:08 AM, "Matt Chotin" <member@adobeforums.com> <br />wrote:<br /><br />> A new message was posted by Matt Chotin in<br />><br />> Developers --<br />> Extending HttpService<br />><br />> HTTPService has some hardcoded compiler support for its MXML parsing <br />> and it's possible we have a bug in there. Might be worth debugging <br />> the MXML compiler, look for HTTPService in the compiler and you can <br />> see where elements get parsed and used.<br />><br />> Matt<br />><br />><br />> On 8/7/08 7:05 AM, "aparolini" <member@adobeforums.com> wrote:<br />><br />> A new discussion was started by aparolini in<br />><br />> Developers --<br />> Extending HttpService<br />><br />> Hello,<br />><br />> I am trying to extend the class mx.rpc.http.mxml.HTTPService. It <br />> works but when I try to use an inner tag for the request, I get a <br />> compilation "Could not resolve <test> to a component <br />> implementation". It seems that the compiler is trying to find a <br />> class matching for the content of the <myns:request> tag when it <br />> shouldn't.<br />><br />> Exemple:<br />> <myns:HttpService result="read_result(event)" <br />> fault="main_fault(event)" showBusyCursor="true" method="POST" <br />> id="srv_read" url="{urlSvr}"><br />> <myns:request><br />> <test>coucou<test><br />> </myns:request><br />> </myns:HttpService><br />><br />> I have seen a jira case similar to this in http://bugs.adobe.com/jira/browse/SDK-14688 <br />> .<br />><br />> Is there a solution to this problem ?<br />><br />> Thanks<br />><br />> toni<br />><br />> ________________________________<br />> View/reply at Extending HttpService <a href=http://www.adobeforums.com/webx?13@@.59b6194b <br />> ><br />> Replies by email are OK.<br />> Use the unsubscribe <a href=http://www.adobeforums.com/webx?280@@.59b6194b!folder=.3c060fa3 <br />> > form to cancel your email subscription.<br />><br />><br />><br />><br />> ------------------------------------------------------<br />> View/reply at <a href=http://www.adobeforums.com/webx?13@@.59b6194b/0><br />> Replies by email are OK.<br />> Use the unsubscribe form at <a href=http://www.adobeforums.com/webx?280@@.59b6194b!folder=.3c060fa3 <br />> > to cancel your email subscription.
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 07, 2008 Aug 07, 2008
Thanks for the feedback. Hardcoded stuff always sucks one time or another...
I'm not sure I have the time nor the ability to dig into the flex MXML compiler source code to provide a patch for this. Do you guys think this could be corrected for the next flex 3 IDE release ? This would be great.

Cheers,

toni
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Aug 07, 2008 Aug 07, 2008
File a bug 🙂 Get your friends to vote.




From: aparolini < member@adobeforums.com>

Reply-To: < flexsdk-dev@adobeforums.com>

Date: Thu, 7 Aug 2008 13:21:42 -0700

To: < flexsdk-dev@adobeforums.com>

Subject: Re: Extending HttpService



A new message was posted by aparolini in



Developers --

  Extending HttpService



Thanks for the feedback. Hardcoded stuff always sucks one time or another...

I'm not sure I have the time nor the ability to dig into the flex MXML compiler source code to provide a patch for this. Do you guys think this could be corrected for the next flex 3 IDE release ?  This would be great.



Cheers,



toni




View/reply at Extending HttpService < http://www.adobeforums.com/webx?13@@.59b6194b/2>

Replies by email are OK.

Use the unsubscribe < http://www.adobeforums.com/webx?280@@.59b6194b!folder=.3c060fa3>  form to cancel your email subscription.





Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Aug 07, 2008 Aug 07, 2008
Vote for the bug, we might be able to see.<br /><br /><br />On 8/7/08 1:21 PM, "aparolini" <member@adobeforums.com> wrote:<br /><br />A new message was posted by aparolini in<br /><br />Developers --<br /> Extending HttpService<br /><br />Thanks for the feedback. Hardcoded stuff always sucks one time or another...<br />I'm not sure I have the time nor the ability to dig into the flex MXML compiler source code to provide a patch for this. Do you guys think this could be corrected for the next flex 3 IDE release ? This would be great.<br /><br />Cheers,<br /><br />toni<br /><br />________________________________<br />View/reply at Extending HttpService <a href=http://www.adobeforums.com/webx?13@@.59b6194b/2><br />Replies by email are OK.<br />Use the unsubscribe <a href=http://www.adobeforums.com/webx?280@@.59b6194b!folder=.3c060fa3> form to cancel your email subscription.
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 07, 2008 Aug 07, 2008
well, I've voted already before this post on SDK-14688. But with just one vote so far (me), and a task priority setted to "none", I guess this is going to stay unsolved forever...
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Aug 07, 2008 Aug 07, 2008
Encourage others to vote for it, enough votes and it moves from Community into New.<br /><br /><br />On 8/7/08 2:43 PM, "aparolini" <member@adobeforums.com> wrote:<br /><br />A new message was posted by aparolini in<br /><br />Developers --<br /> Extending HttpService<br /><br />well, I've voted already before this post on SDK-14688. But with just one vote so far (me), and a task priority setted to "none", I guess this is going to stay unsolved forever...<br /><br />________________________________<br />View/reply at Extending HttpService <a href=http://www.adobeforums.com/webx?13@@.59b6194b/5><br />Replies by email are OK.<br />Use the unsubscribe <a href=http://www.adobeforums.com/webx?280@@.59b6194b!folder=.3c060fa3> form to cancel your email subscription.
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 07, 2008 Aug 07, 2008
Flex 4 (and a new namespace) sure seems like a nice place to turn off these silly hardcoded exceptions to normal compilation, nudge-nudge :)

-Josh

On Fri, Aug 8, 2008 at 7:43 AM, aparolini < member@adobeforums.com> wrote:

A new message was posted by aparolini in



Developers --

  Extending HttpService



well, I've voted already before this post on SDK-14688. But with just one vote so far (me), and a task priority setted to "none", I guess this is going to stay unsolved forever...






--
"Therefore, send not to know For whom the bell tolls. It tolls for thee."

:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: josh@gfunk007.com


Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Aug 07, 2008 Aug 07, 2008
We've certainly thought about that. But then the syntax would change, instead of:<br /><br /><mx:RemoteObject ...><br /> <mx:method name="foo" /><br /></mx:RemoteObject><br /><br />You would have to write:<br /><mx:RemoteObject><br /> <mx:Operation name="..."/><br /></><br /><br />And similar changes in WebService. Do you think we should consider this? All the shortcuts for the request tag in HTTPService might also need to change.<br /><br />I really wish we had done this before, at the time when I wrote this code it was early in Flex 2 and we thought we were going to attempt compatibility with Flex 1.5 :-)<br /><br />Matt<br /><br />On 8/7/08 3:07 PM, "Josh McDonald" <member@adobeforums.com> wrote:<br /><br />A new message was posted by Josh McDonald in<br /><br />Developers --<br /> Extending HttpService<br /><br />Flex 4 (and a new namespace) sure seems like a nice place to turn off these silly hardcoded exceptions to normal compilation, nudge-nudge :)<br /><br />-Josh<br /><br />On Fri, Aug 8, 2008 at 7:43 AM, aparolini <member@adobeforums.com> wrote:<br />A new message was posted by aparolini in<br /><br />Developers --<br /> Extending HttpService<br /><br />well, I've voted already before this post on SDK-14688. But with just one vote so far (me), and a task priority setted to "none", I guess this is going to stay unsolved forever...
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 07, 2008 Aug 07, 2008
I'd really like to see all the hard-coded cases inside MXMLC go away for the MXML 2009 namespace. Besides that, something like this:

http://bugs.adobe.com/jira/browse/FB-12296


...is all I want to see in the Flex 4 compiler that's not already in there. I love the changes to [DefaultProperties] and the <Declarations> tag. I don't like the naming of <Private> as I'd *really* like to see that used to declare private vars rather than public for components with ids sometime in the future.


Sorry if I sound like a whinger, because I'm not - I'm really looking forward to 4! DefaultProperty inheritance is enough to make me smile :)

IMO, there's absolutely no need to include (undocumented AFAIK) compiler tricks for supporting Fx 1.5 when compiling the 2009 namespace.


-Josh

On Fri, Aug 8, 2008 at 9:30 AM, Matt Chotin < member@adobeforums.com> wrote:

A new message was posted by Matt Chotin in



Developers --

 Extending HttpService



We've certainly thought about that.  But then the syntax would change, instead of:



<mx:RemoteObject ...>

 <mx:method name="foo" />

</mx:RemoteObject>



You would have to write:

<mx:RemoteObject>

 <mx:Operation name="..."/>

</>



And similar changes in WebService.  Do you think we should consider this?  All the shortcuts for the request tag in HTTPService might also need to change.



I really wish we had done this before, at the time when I wrote this code it was early in Flex 2 and we thought we were going to attempt compatibility with Flex 1.5 :-)



Matt



On 8/7/08 3:07 PM, "Josh McDonald" < memberadobeforums.com> wrote:



A new message was posted by Josh McDonald in



Developers --

 Extending HttpService



Flex 4 (and a new namespace) sure seems like a nice place to turn off these silly hardcoded exceptions to normal compilation, nudge-nudge :)



-Josh



On Fri, Aug 8, 2008 at 7:43 AM, aparolini < memberadobeforums.com> wrote:

A new message was posted by aparolini in



Developers --

 Extending HttpService



well, I've voted already before this post on SDK-14688. But with just one vote so far (me), and a task priority setted to "none", I guess this is going to stay unsolved forever...











------------------------------------------------------

View/reply at < http://www.adobeforums.com/webx?13@.59b6194b/8>

Replies by email are OK.

Use the unsubscribe form at < http://www.adobeforums.com/webx?280@.59b6194b!folder=.3c060fa3> to cancel your email subscription.





--
"Therefore, send not to know For whom the bell tolls. It tolls for thee."

:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: josh@gfunk007.com


Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Aug 08, 2008 Aug 08, 2008
LATEST
I moved that FR to be SDK: http://bugs.adobe.com/jira/browse/SDK-16416<br /><br />We'll look into the compiler work, but if it takes more than a day it might not make it (unless someone else were to do the work).<br /><br />Matt<br /><br /><br />On 8/7/08 5:13 PM, "Josh McDonald" <member@adobeforums.com> wrote:<br /><br />A new message was posted by Josh McDonald in<br /><br />Developers --<br /> Extending HttpService<br /><br />I'd really like to see all the hard-coded cases inside MXMLC go away for the MXML 2009 namespace. Besides that, something like this:<br /><br />http://bugs.adobe.com/jira/browse/FB-12296<br /><br />...is all I want to see in the Flex 4 compiler that's not already in there. I love the changes to [DefaultProperties] and the <Declarations> tag. I don't like the naming of <Private> as I'd *really* like to see that used to declare private vars rather than public for components with ids sometime in the future.<br /><br />Sorry if I sound like a whinger, because I'm not - I'm really looking forward to 4! DefaultProperty inheritance is enough to make me smile :)<br /><br />IMO, there's absolutely no need to include (undocumented AFAIK) compiler tricks for supporting Fx 1.5 when compiling the 2009 namespace.<br /><br />-Josh<br /><br />On Fri, Aug 8, 2008 at 9:30 AM, Matt Chotin <member@adobeforums.com> wrote:<br />A new message was posted by Matt Chotin in<br /><br />Developers --<br /> Extending HttpService<br /><br />We've certainly thought about that. But then the syntax would change, instead of:<br /><br /><mx:RemoteObject ...><br /> <mx:method name="foo" /><br /></mx:RemoteObject><br /><br />You would have to write:<br /><mx:RemoteObject><br /> <mx:Operation name="..."/><br /></><br /><br />And similar changes in WebService. Do you think we should consider this? All the shortcuts for the request tag in HTTPService might also need to change.<br /><br />I really wish we had done this before, at the time when I wrote this code it was early in Flex 2 and we thought we were going to attempt compatibility with Flex 1.5 :-)<br /><br />Matt<br /><br />On 8/7/08 3:07 PM, "Josh McDonald" <member@adobeforums.com> wrote:<br /><br />A new message was posted by Josh McDonald in<br /><br />Developers --<br /> Extending HttpService<br /><br />Flex 4 (and a new namespace) sure seems like a nice place to turn off these silly hardcoded exceptions to normal compilation, nudge-nudge :)<br /><br />-Josh<br /><br />On Fri, Aug 8, 2008 at 7:43 AM, aparolini <member@adobeforums.com> wrote:<br />A new message was posted by aparolini in<br /><br />Developers --<br /> Extending HttpService<br /><br />well, I've voted already before this post on SDK-14688. But with just one vote so far (me), and a task priority setted to "none", I guess this is going to stay unsolved forever...<br /><br /><br /><br /><br /><br />------------------------------------------------------<br />View/reply at <a href=http://www.adobeforums.com/webx?13@@.59b6194b/8><br />Replies by email are OK.<br />Use the unsubscribe form at <a href=http://www.adobeforums.com/webx?280@@.59b6194b!folder=.3c060fa3 <a href=http://www.adobeforums.com/webx?280@@.59b6194b%21folder=.3c060fa3> > to cancel your email subscription.
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines