The JarResourceRequestHandler works like a charm despite being "very
experimental". Lots of thanks for that!
cheers,
Lars
Am 07.07.2011 um 00:49 schrieb Henrique Prange:
> Hi Lars,
>
> And I've missed the link.
>
> [1]https://gist.github.com/1068523
>
> Cheers,
>
> Henrique
>
> On 06/07/2011, at 19:48, Henrique Prange wrote:
>
>> Hi Lars,
>>
>> The JarResourceRequestHandler [1] is very experimental, but I hope it can
>> help you.
>>
>> Add the following code to you application initialization to enable this
>> handler:
>>
>> if (isDirectConnectEnabled()) {
>> registerRequestHandler(new JarResourceRequestHandler(), "_wr_");
>>
>> if (ERXApplication.isWO54()) {
>> registerRequestHandler(new JarResourceRequestHandler(), "wr");
>> }
>> }
>>
>> Cheers,
>>
>> Henrique
>>
>> On 06/07/2011, at 15:06, Lars Sonchocky-Helldorf wrote:
>>
>>>
>>> Am 23.07.2010 um 15:08 schrieb Anjo Krank:
>>>
>>>> Hm. Then again, IIRC we use strings for paths... so you probably *could*
>>>> give these methods a "jar:xxx" string and handle that in the method. Not
>>>> the cleanest way, but what the heck.
>>>>
>>>> I'm not sure if not using the default props is that good a thing.
>>>> Sometimes these change or get added to and you would want to get the
>>>> additions.
>>>>
>>>> Cheers, Anjo
>>>
>>> Are there any new on that situation?
>>>
>>> I am currently running into something similar when trying to use the
>>> Ajax-Functionality of Wonder:
>>>
>>> Jul 06 17:48:51 Portal[5555] INFO
>>> er.extensions.appserver.ERXStaticResourceRequestHandler - Unable to get
>>> contents of file
>>> 'jar:file:/Volumes/Daten/lars.sonchocky-helldorf/.m2/repository/wonder/ajax/Ajax/5.0.0-r11323/Ajax-5.0.0-r11323-wo54.jar!/WebServerResources/wonder.js'
>>> for uri:
>>> jar:file:///Volumes/Daten/lars.sonchocky-helldorf/.m2/repository/wonder/ajax/Ajax/5.0.0-r11323/Ajax-5.0.0-r11323-wo54.jar!/WebServerResources/wonder.js
>>>
>>> and so on.
>>>
>>> I saw the workaround described in this thread and here:
>>> http://issues.objectstyle.org/jira/browse/WONDER-86. I added
>>> registerRequestHandler(requestHandlerForKey("wr"), "_wr_"); to the
>>> woapplication and it works for the above. However, I've also got several
>>> webserver-resources (images, css, js) in
>>> /Library/WebServer/Documents/IntranetImages/ and referred by f.i.
>>> http://10.11.3.152:5555/IntranetImages/ to be served by Apache. After
>>> adding the workaround to the app those resources are no longer found, they
>>> just 404. Removing the workaround gives me those resources back, but then
>>> again the "jar:file:…" stuff no longer works.
>>>
>>> What to do about this? Any ideas?
>>>
>>>
>>> cheers,
>>>
>>> Lars
>>>
>>> P.S.: WONDER-86 was closed with the comment: "We only accept 5.4 fixes now,
>>> not issues.". Is this still the case?
>>>
>>>>
>>>>
>>>>
>>>> Am 23.07.2010 um 14:56 schrieb [email protected]:
>>>>
>>>>>
>>>>>> The reason we don't do it ourself is that a lot of that stuff calls into
>>>>>> erxfileutils and that uses path names. Fixing it would be a lot of work
>>>>>> and make code more complicated without a lot of real gain (at least from
>>>>>> when I last looked at it).
>>>>>>
>>>>>> So unless any of the committers actually need to use this themselves, I
>>>>>> wouldn't hold my breath waiting for it.
>>>>>>
>>>>>> Cheers, Anjo
>>>>>
>>>>> WARN er.extensions.foundation.ERXFileUtilities - Can't get path when
>>>>> run as jar: ERNeutralLook - Properties
>>>>>
>>>>> Actually, having only Properties come from and set by my program--is a
>>>>> feature--not a bug! This "feature" has not caused me any pain--yet.
>>>>>
>>>>> I generally would look at the properties included in the framework, but
>>>>> would set the ones I want in my program's properties file. I am not sure
>>>>> what all I am missing by having to work this way.
>>>>>
>>>>> NSBundle jars have additional features that regular frameworks do not!
>>>>> (Sometimes.)
>>>>> --
>>>>>
>>>>> [email protected]
>>>>>
>>>>> _______________________________________________
>>>>> Do not post admin requests to the list. They will be ignored.
>>>>> Webobjects-dev mailing list ([email protected])
>>>>> Help/Unsubscribe/Update your Subscription:
>>>>> http://lists.apple.com/mailman/options/webobjects-dev/anjo%40krank.net
>>>>>
>>>>> This email sent to [email protected]
>>>>
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> Webobjects-dev mailing list ([email protected])
>>>> Help/Unsubscribe/Update your Subscription:
>>>> http://lists.apple.com/mailman/options/webobjects-dev/lars.sonchocky-helldorf%40hamburg.de
>>>>
>>>> This email sent to [email protected]
>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list ([email protected])
>>> Help/Unsubscribe/Update your Subscription:
>>> http://lists.apple.com/mailman/options/webobjects-dev/hprange%40gmail.com
>>>
>>> This email sent to [email protected]
>>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list ([email protected])
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/webobjects-dev/lars.sonchocky-helldorf%40hamburg.de
>
> This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
