The WOFrameworksBaseURL works fine for me. All my framework resources are 
loading okay. It’s just the resources from the application itself that get a 
path with pom version in it.

I’m using an approximately year old version of Wonder, so I should be 
unaffected by recent changes to Wonder.


On Mar 7, 2016, at 11:36 AM, Fabian Peters <[email protected]> wrote:

> Hi Ramsey,
> 
> I'm guessing you're seeing 
> <https://github.com/wocommunity/wonder/pull/704#issuecomment-167605363>. 
> Markus proposed a fix in <https://github.com/wocommunity/wonder/pull/727>, of 
> which I tested a preliminary version. 
> 
> For now I just reverted the commits from #704.
> 
> Fabian
> 
>> Am 07.03.2016 um 18:26 schrieb Ramsey Gurley <[email protected]>:
>> 
>> Hi all,
>> 
>> I’m doing a split deployment with apache. When deploying a maven 
>> application, I’m able to get the proper WebServerResources for all the 
>> frameworks using WOFrameworksBaseURL. However, any resources in the 
>> application itself seem to generate urls like 
>> domain/WebObjects/AppName-1.0.0-SNAPSHOT.woa/path/to/resource.
>> 
>> Can anyone tell me the secret handshake/property to make that use 
>> domain/WebObjects/AppName.woa/path/to/resource? I tried 
>> WOApplicationBaseURL, but that just replaced the /WebObjects bit and left 
>> the app name with pom version in place.
>> 
>> Thanks,
>> 
>> Ramsey
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      ([email protected])
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.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:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to