Re: Embeded Frameworks and WebServerResources

2009-06-26 Thread Ricardo J. Parada
Disclaimer... I have not used ERXFileUtilities yet. But just keep in mind that in the deployed app you should have the image in the same images folder you mentioned. The directory structure of stuff in there is kept. It's not like the Resources folder which is flattened. On Jun 26, 20

Re: Embeded Frameworks and WebServerResources

2009-06-26 Thread Ricardo J. Parada
I don't think WebServerResources are flattened. So may be try "/ images/HorizontalWatermark.png" On Jun 26, 2009, at 4:00 PM, Johnny Miller wrote: Hmmm still stuck. In my Framework I have a method that includes the following line of code: String horizontalWatermark = ERXFileUti

Re: Embeded Frameworks and WebServerResources

2009-06-26 Thread Johnny Miller
Hmmm still stuck. In my Framework I have a method that includes the following line of code: String horizontalWatermark = ERXFileUtilities.pathForResourceNamed("HorizontalWatermark.png", null, null); This code functions as expected in debug mode but when I deploy the application t

Re: Embeded Frameworks and WebServerResources

2009-06-26 Thread Johnny Miller
Thank you, this was driving me crazy last week. On Jun 26, 2009, at 4:16 AM, Ricardo J. Parada wrote: I believe WOFrameworksBaseURL and WOApplicationBaseURL are used for that. If you are on WO 5.4.3 then those too are broken and I put this in my application constructor to make them work:

Re: Embeded Frameworks and WebServerResources

2009-06-26 Thread Ricardo J. Parada
Cool... I'll be able to remove that code from my wonderized app then. :-) On Jun 26, 2009, at 10:22 AM, Mike Schrag wrote: committed to wonder ... not sure why i didn't put this in when we first identified the problem On Jun 26, 2009, at 10:16 AM, Ricardo J. Parada wrote: I believe

Re: Embeded Frameworks and WebServerResources

2009-06-26 Thread Mr. Frank Cobia
Thanks. I did this and set WOFrameworksBaseURL to /WebObjects/App.woa/ Frameworks and it is working now. Frank On Jun 26, 2009, at 10:16 AM, Ricardo J. Parada wrote: I believe WOFrameworksBaseURL and WOApplicationBaseURL are used for that. If you are on WO 5.4.3 then those too are broken

Re: Embeded Frameworks and WebServerResources

2009-06-26 Thread Mike Schrag
committed to wonder ... not sure why i didn't put this in when we first identified the problem On Jun 26, 2009, at 10:16 AM, Ricardo J. Parada wrote: I believe WOFrameworksBaseURL and WOApplicationBaseURL are used for that. If you are on WO 5.4.3 then those too are broken and I put this in

Re: Embeded Frameworks and WebServerResources

2009-06-26 Thread Ricardo J. Parada
On Jun 26, 2009, at 10:16 AM, Ricardo J. Parada wrote: If you are on WO 5.4.3 then those too are broken and I put this in my application constructor to make them work: I meant to say "those two are broken" :-) ___ Do not post admin requests to

Re: Embeded Frameworks and WebServerResources

2009-06-26 Thread Ricardo J. Parada
I believe WOFrameworksBaseURL and WOApplicationBaseURL are used for that. If you are on WO 5.4.3 then those too are broken and I put this in my application constructor to make them work: public Application() { super(); // WOFrameworksBaseURL and WOApplicationBaseURL propertie

Embeded Frameworks and WebServerResources

2009-06-26 Thread Mr. Frank Cobia
I am building my application with the frameworks embedded so that I do not have to worry about different versions of the frameworks for different apps. I have checked and the build does put the WebServerResources inside the application's WebServerResources. However, when accessing the app i