Actually, I found out what the problem was. The return type is a bean that
had a constructor that took parameters in addition to a default constructor.
When I removed the constructor that takes parameters, everything worked
fine.
The exception/message is very deceiving...
On 5/14/07, glassfish_at_javadesktop.org <glassfish_at_javadesktop.org> wrote:
>
> You might have looked into to this already, but is there any chance you
> have a security manager enabled? I'm not an expert and could be off base,
> but perhaps this blog is relevant to your situation:
>
> http://weblogs.java.net/blog/felipegaucho/archive/2006/01/is_the_security_1.html
>
> regards,
> JP
> [Message sent by forum member 'jbeaudry' (jbeaudry)]
>
> http://forums.java.net/jive/thread.jspa?messageID=216885
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>