Tapestry 5 and EZproxy

2009-10-16 Thread Blower, Andy 
We need to support users and institutions who use EZproxy 
(http://www.oclc.org/ezproxy/default.htm) which should be pretty easy.

I've been trying it, and things work okay until AJAX is used and then T5 throws 
this exception:

(services.TapestryModule.RequestExceptionHandler:62) - Processing of request 
failed with uncaught exception: A component event handler method returned the 
value {result:success,numMsg:1 new,method:add}. Return type 
org.apache.tapestry5.json.JSONObject can not be handled.  Configured return 
types are java.lang.Class, java.lang.String, java.net.URL, 
org.apache.tapestry5.Link, org.apache.tapestry5.StreamResponse, 
org.apache.tapestry5.runtime.Component.

And the Ajax JS gets a 500 internal server error.


I'm going to be investigating this next week, but I thought I'd enquire whether 
anyone on the list has tried T5 or even just Prototype based websites with 
EZproxy? If you have I'd really like to hear from you, especially if you know 
what's going wrong for us.

Thanks,

Andy.

Re: Tapestry 5 and EZproxy

2009-10-16 Thread Thiago H. de Paula Figueiredo 
Em Fri, 16 Oct 2009 13:05:23 -0300, Blower, Andy  
andy.blo...@proquest.co.uk escreveu:
(services.TapestryModule.RequestExceptionHandler:62) - Processing of  
request failed with uncaught exception: A component event handler method  
returned the value {result:success,numMsg:1 new,method:add}.  
Return type org.apache.tapestry5.json.JSONObject can not be handled.   
Configured return types are java.lang.Class, java.lang.String,  
java.net.URL, org.apache.tapestry5.Link,  
org.apache.tapestry5.StreamResponse,  
org.apache.tapestry5.runtime.Component.


Tapestry checks if an HTTP header named 'X-Requested-With' has the value  
'XMLHttpRequest'. If not, it is not considered an AJAX request.

One possibility is that the proxy is removing this HTTP header.

--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

RE: Tapestry 5 and EZproxy

2009-10-16 Thread Blower, Andy 
Thiago, 

Thank you for such a quick and insightful response - I've just checked and 
EZproxy does appear to be removing this header.

I'll email EZproxy support and see what they say. If they have to update 
EZproxy to cope with this then we could be in trouble. Customers may not be 
happy being forced to upgrade their EZproxy installations so they can use our 
product.

Is there any way round this you can think of?


Thanks,

Andy.

 -Original Message-
 From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com]
 Sent: 16 October 2009 17:15
 To: Tapestry users
 Subject: Re: Tapestry 5 and EZproxy
 
 Em Fri, 16 Oct 2009 13:05:23 -0300, Blower, Andy
 andy.blo...@proquest.co.uk escreveu:
  (services.TapestryModule.RequestExceptionHandler:62) - Processing of
  request failed with uncaught exception: A component event handler
 method
  returned the value {result:success,numMsg:1
 new,method:add}.
  Return type org.apache.tapestry5.json.JSONObject can not be handled.
  Configured return types are java.lang.Class, java.lang.String,
  java.net.URL, org.apache.tapestry5.Link,
  org.apache.tapestry5.StreamResponse,
  org.apache.tapestry5.runtime.Component.
 
 Tapestry checks if an HTTP header named 'X-Requested-With' has the
 value
 'XMLHttpRequest'. If not, it is not considered an AJAX request.
 One possibility is that the proxy is removing this HTTP header.
 
 --
 Thiago H. de Paula Figueiredo
 Independent Java consultant, developer, and instructor
 http://www.arsmachina.com.br/thiago
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
 For additional commands, e-mail: users-h...@tapestry.apache.org
 



-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Re: Tapestry 5 and EZproxy

2009-10-16 Thread Thiago H. de Paula Figueiredo 
Em Fri, 16 Oct 2009 13:33:33 -0300, Blower, Andy  
andy.blo...@proquest.co.uk escreveu:



Thiago,


Hi!

Thank you for such a quick and insightful response - I've just checked  
and EZproxy does appear to be removing this header.


You're welcome!

I'll email EZproxy support and see what they say. If they have to update  
EZproxy to cope with this then we could be in trouble. Customers may not  
be happy being forced to upgrade their EZproxy installations so they can  
use our product.


You could give two options to your clients: using an AJAX-less product or  
upgrading (or reconfiguring, I don't know) their proxy installations. :)


--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org