[Seaside-dev] WANotFoundHandler

[Carlos Crosetti]

Julia, I got it working.
What I did was to deliver an URL into an email that calls a resource that is hndled by the WANotFoundhandler. This sole instance picks the query string and stores it int the image, after that I deliver a WAResponse to a new URL, that is the hyperlinked application now promoted to be top level and holding a name at the same level as the app that published the url into email.

Thanks for your effors in assisting me, regards, Carlos
  ----- Original Message ----- 
  From: Julian Fitzell 
  To: Seaside - developer list 
  Sent: Thursday, May 06, 2010 8:15 PM
  Subject: Re: [Seaside-dev] WANotFoundHandler


  I tested it in a 2.8 image and it works for me if I change the Dispatcher to have no default entry point. So I can't reproduce the problem. Perhaps you need to use Firebug or even telnet to trace through each redirect and find out exactly where the problem is. Or try to set up the simplest scenario you can that illustrates the same problem. There must be something different between your setup and mine.

  Julian


  On Thu, May 6, 2010 at 1:45 PM, Crosetti, Carlos A <carlos.a.crosetti at verizonbusiness.com> wrote:

    Yes, is called, I added 



    I coded 

        WANotFoundHandler>>handleRequest: aRequest

                aRequest explore.

            ^WAResponse rediredtTo: 'http://localhost:8080/seaside/path/myapp'





    I can see the inspector and watch to the Dictionary inside the WARequest object, my request is 

                http://localhost:8080/path/test?var1=111111&var2=22222



    That I enough for me but now I got my request parsed, I would like a good rediredt, that is happening but not getting to the right path.



    Carlos Crosetti

    Verizon Business

    +54 11 4107 7822

    VNet 410 7822

    Cell +54 9 11 5988 5921

    http://vpreso.vzbi.com/v852216/public/


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

    From: seaside-dev-bounces at lists.squeakfoundation.org [mailto:seaside-dev-bounces at lists.squeakfoundation.org] On Behalf Of Julian Fitzell
    Sent: Thursday, May 06, 2010 5:39 AM
    To: Seaside - developer list


    Subject: Re: [Seaside-dev] WANotFoundHandler



    Have you checked if that method is even being called? I think if your Dispatcher has a default entry point set, it will always use that rather than trying to raise a NOT FOUND.

    I bet if you set the dispatcher's default to "None" it will work.

    Julian

    On Thu, May 6, 2010 at 2:42 AM, Carlos Crosetti <carlos.crosetti at mostar.com.ar> wrote:

    Julia, I apologize for sending to the wrong list. Please dont blame on me for this note.

    What I am looking for is to make the WANofFoundhandler redirect back to the Seasid registed app, the URL  will look like http://locahost:8080/seaside/path/myapp



    I coded 

        WANotFoundHandler>>handleRequest: aRequest

            ^WAResponse rediredtTo: 'http://localhost:8080/seaside/path/myapp'



    and got this method working, but is leaving me back in the /seasie root-



    Carlos

      ----- Original Message ----- 

      From: Julian Fitzell 

      To: Seaside - developer list 

      Sent: Wednesday, May 05, 2010 6:26 PM

      Subject: Re: [Seaside-dev] WANotFoundHandler



      Hi Carlos,

      I'm not sure what you're asking. Are you wondering how to process the URL in Seaside? Or what the URL should look like? Or how to make the request? Are you wanting the URL to trigger a callback or just a normal rendering phase?

      By the way, I would suggest posting your questions to the "seaside" list instead of the "seaside-dev" list. The -dev list is intended for discussion of the development of the Seaside framework itself and it has a much smaller membership. You'll get a faster reply on the general list.

      Julian

      On Wed, May 5, 2010 at 8:58 PM, Crosetti, Carlos A <carlos.a.crosetti at verizonbusiness.com> wrote:

      Hi, please disregard my last note. I found class WANotFoundHandler that actually is deliverying the unhandled requests into a directory and I then got the way to trap external request.



      So, what is the standard way to deliver a reply to the some URL that in turns goes back to the Seaside application?



      Carlos Crosetti




      _______________________________________________
      seaside-dev mailing list
      seaside-dev at lists.squeakfoundation.org
      http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev




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

      _______________________________________________
      seaside-dev mailing list
      seaside-dev at lists.squeakfoundation.org
      http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev


    _______________________________________________
    seaside-dev mailing list
    seaside-dev at lists.squeakfoundation.org
    http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev




    _______________________________________________
    seaside-dev mailing list
    seaside-dev at lists.squeakfoundation.org
    http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev






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


  _______________________________________________
  seaside-dev mailing list
  seaside-dev at lists.squeakfoundation.org
  http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20100506/7e8643f0/attachment.htm