any solution in the interim? I'm using the EntityManager directly right now
to work around this?
Is this in 6.5M1?
On Fri, Jul 25, 2008 at 4:16 PM, Peter Liu <Peter.Liu_at_sun.com> wrote:
> Hi Patrick,
>
> For NB 6.5, we have enhanced the generated code to not use the UriResolver
> if the input document contains the id that can be used internally to look up
> the reference instead of issuing a http request.
>
> Peter
>
>
> Paul Sandoz wrote:
>
>> Hi Patrick,
>>
>> This is a good place to post, the NetBeans guys responsible for developing
>> of the generated code are listening in and will hopefully reply to you soon.
>>
>> Paul.
>>
>> Patrick Julien wrote:
>>
>>> Not sure where to post this since this involves some code automatically
>>> generated by NetBeans. I have created some rest services using the wizard
>>> and some entity classes.
>>>
>>> The problem I am having is that the generated UriResolver makes a new
>>> http connection to resolve any references that are made in a post. If it
>>> so happens those services are protected by the container, this is a new http
>>> connection and so will get rejected by the container.
>>>
>>> There are at least 2 bugs here:
>>>
>>> 1. UriResolver has no idea how to forward any security tokens made by the
>>> original requester
>>> 2. The real http status code is thrown away in favor of a generic not
>>> found error (404) message. In this case, the error was a 401 (auth denied).
>>>
>>> --
>>> http://www.spectrumdt.com
>>> http://codepimps.org
>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>
--
http://www.spectrumdt.com
http://codepimps.org