Disabling wicket resource compression did not solve my issue, however I may
have a workaround that's faster than tinkering with oc4j's settings, which
I'm not an expert on. See my response to Alex's suggestion for details.
Joel
hillj2 wrote:
>
> I'm using OC4J 10.1.3.2, I believe it's 32-bit. I've tried it with both
> FF2 and IE6. I'm not sure about the response headers, because when I use
> my tool for extracting the headers (NetTool 4.7.0) it seems to work fine,
> so I'm not sure the headers are the same as when it doesn't work. Unless
> there's some simple thing I can override in wicket to intercept the
> response headers (which there probably is). Maybe that happens because
> technically NetTool becomes my webserver at that point (with oc4j being
> NetTool's webserver). That would seem to indicate even more that it's an
> Oracle problem.
>
> As for "junk" I mean the js file returns as random ascii, like it's binary
> data.
>
> I think I tried disabling wicket compression once before, with no success.
> But I'll try that again just to make sure. I'll also see if I can tinker
> with Oracle's settings.
>
> Thanks for the suggestions, I'll let you know how it works out.
>
> Joel
>
>
>
> Matej Knopp-2 wrote:
>>
>> Well, oracle app server doesn't have a good reputation exactly for
>> messing the output. Try disabling the compression of wicket resources
>> completely,
>>
>> Application.getResourceSettings.setDisableGZipCompression(true).
>>
>> -Matej
>>
>> On 8/3/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
>>> Seems like Oracle application server, version 10.1, 32 bits?
>>>
>>> Apparently the classloader for the app server converts the
>>> getClass().getResourceAsStream("....wicket-event.js")
>>> to use a "code-source:" protocol. I'm not sure, but it sounds like a
>>> security constraint in your setup.
>>>
>>> Martijn
>>>
>>> On 8/3/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
>>> > I doubt this is related. What app server are you using? What exactly
>>> > does it mean junk? Wha headers are set on ouput? What browser are you
>>> > using?
>>> >
>>> > -Matej
>>> >
>>
>>
>
--
View this message in context:
http://www.nabble.com/wicket-event.js-returning-unreadable-tf4158501.html#a12018236
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
