Hi Joe,
thanks a lot for all your help through IM. I got everything working
and implemented a wrapper HttpServletRequest and a dummy
ServletContext class. I also succeeded in adding some tests that now
check that DWR is correctly integrated into RIFE. This makes it much
easier to check future releases. Until now I had to always validate
the integration manually through an example project.
Take care and happy new-year!
Geert
On 29 Dec 2006, at 12:27, Geert Bevin wrote:
Hi Hoe,
thanks a lot for this, however I think that the easy way out for
DwrRifeProcessor will not work.
The request and response that you obtain from the element are the
raw ones. The pathinfo and URLs are not the same ones as the
element versions. Basically, there's only one RIFE servlet/filter
and in terms of the servlet API, every URL that comes in as a
pathinfo. However, elements can be mounted at any RIFE URL and also
with wildcards for pathinfo-like functionality inside RIFE itself.
So I suppose that creating the request/response wrappers is the
best next step. I'll try to look into this today, but this flu does
seem to be going away quickly, I'm still resting a lot :-/
Take care,
Geert
On 29 Dec 2006, at 12:19, Joe Walker wrote:
Hi,
I've attached a DWR patch to keep RIFE in sync with the latest DWR
changes.
What changed? 2 main changes:
- We separated the embedders interfaces from the users interfaces
- We made some changes to allow embedders to have more control
over decomposing URLs.
The attached patch will probably need tweaking, but it is a good
start.
- DwrServiceDeployer.java: Changed method name. Simple fix
- DwrService.java: Changes for URL decomposition
- DwrRifeProcessor.java: I've taken what is probably a too simple
way out, and forwarded the handle code onto the UrlProcessor
avoiding all the cut and paste. This means that the content is set
on the Servlet objects and not the Element. I'm sure this will be
breaking something because if it was that easy, we would have done
this before. I would rather create a wrapper for the Servlet
objects to proxy back to the Element (so it could then proxy back
to the Servlet objects!) and do this once, than be continually re-
writing the DwrRifeProcessor.
Please could you copy me in on replies - I'm not keeping up with
mails very well, and there is a good chance that I'll miss replies
sent to the RIFE list.
Thanks,
Joe.
<rife-dwr2.zip>
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
