Re: Can't build Wonder frameworks with Eclipse Luna / El Capitan / Java 8 setup

[Elizabeth Lynch]

Hi Theodore


> On 27 Nov 2015, at 19:54, Theodore Petrosky  wrote:
> 
> have you tried to build from the command line:
> 
> cd to_Wonder_Directory
> sudo ant  frameworks frameworks.install

Thanks for getting back to me.

Yes, I already did that, and the frameworks build and install fine (I did say 
this at the end of my email but perhaps I wasn't clear!).  You are right - I 
could change my own project and remove the Wonder frameworks from my workspace 
and add the built frameworks from /Library/Frameworks to the classpath instead. 
 But if possible I would prefer to ‘fix’ Eclipse/ant so that I can use the 
Wonder source directly within the workspace.

Liz

> 
> I think that’s it
> 
>> On Nov 27, 2015, at 12:00 PM, Elizabeth Lynch > > wrote:
>> 
>> In Eclipse, if I use ‘Run As Ant build’ to build any of the Wonder 
>> frameworks, the build fails as below - the example is for WOPayPal.  I have 
>> googled this and looked at the list, but can’t find any answer which works 
>> for me. 
>> 
>> 
>> Buildfile: 
>> /Users/liz/Projects/WonderSource-Feb2014/Frameworks/BusinessLogic/WOPayPal/build.xml
>> clean:
>> WOPayPal.all:
>> global.environment:
>> global.properties:
>> global.framework.clean:
>>   [delete] Deleting directory /Users/liz/Roots/classes/WOPayPal
>>   [delete] Deleting directory /Users/liz/Roots/WOPayPal.framework
>> build:
>> WOPayPal.all:
>> global.environment:
>> global.properties:
>> global.prepare:
>>[mkdir] Created dir: /Users/liz/Roots/classes/WOPayPal
>> global.compile:
>> 
>> BUILD FAILED
>> /Users/liz/Projects/WonderSource-2015/Frameworks/BusinessLogic/WOPayPal/build.xml:12:
>>  The following error occurred while executing this line:
>> /Users/liz/Projects/WonderSource-2015/Build/build/build.xml:593: The 
>> following error occurred while executing this line:
>> /Users/liz/Projects/WonderSource-2015/Build/build/generic.xml:247: taskdef A 
>> class needed by class org.objectstyle.woproject.ant.WOCompile cannot be 
>> found: org/apache/tools/ant/taskdefs/Javac
>>  using the classloader 
>> AntClassLoader[/Users/liz/Projects/WonderSource-Feb2014/Build/lib/cayenne-1.2M12.jar:/Users/liz/Projects/WonderSource-2015/Build/lib/jdom-b7.jar:/Users/liz/Projects/WonderSource-Feb2014/Build/lib/log4j-1.2.9.jar:/Users/liz/Projects/WonderSource-2015/Build/lib/maven-ant-tasks-2.1.3.jar:/Users/liz/Projects/WonderSource-2015/Build/lib/woproject.jar]
>> 
>> 
>> 
>> If I try to build my own framework, which references some Wonder frameworks 
>> in my workspace, I get:
>> 
>> BUILD FAILED
>> /Users/liz/Projects/Test/build.xml:87: taskdef A class needed by class 
>> org.objectstyle.woproject.ant.WOCompile cannot be found: 
>> org/apache/tools/ant/taskdefs/Javac
>>  using the classloader AntClassLoader[]
>> 
>> 
>> I can build a different project, which uses the Wonder pre-built binaries in 
>> /Library/Frameworks, in Eclipse with no problems.
>> 
>> I can also build the Wonder frameworks to ~/Roots fine from the command line 
>> using ant:  ant clean frameworks
>> 
>>  
>> 
>> My development setup is:
>> 
>> El Capitan 10.11.1
>> Java 1.8.0_31
>> ant 1.9.6 installed via home-brew.
>> Eclipse Luna Service Release 2 (4.4.2)
>> WOLips 4.4.201510.13.47
>> 
>> 
>> 
>> 
>> All ideas welcomed. 
>> 
>> Liz
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> ___
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com 
>> )
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com 
>> 
>> 
>> This email sent to tedp...@yahoo.com 
 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Can't build Wonder frameworks with Eclipse Luna / El Capitan / Java 8 setup

[Theodore Petrosky]

have you tried to build from the command line:

cd to_Wonder_Directory
sudo ant  frameworks frameworks.install

I think that’s it

> On Nov 27, 2015, at 12:00 PM, Elizabeth Lynch  wrote:
> 
> In Eclipse, if I use ‘Run As Ant build’ to build any of the Wonder 
> frameworks, the build fails as below - the example is for WOPayPal.  I have 
> googled this and looked at the list, but can’t find any answer which works 
> for me. 
> 
> 
> Buildfile: 
> /Users/liz/Projects/WonderSource-Feb2014/Frameworks/BusinessLogic/WOPayPal/build.xml
> clean:
> WOPayPal.all:
> global.environment:
> global.properties:
> global.framework.clean:
>   [delete] Deleting directory /Users/liz/Roots/classes/WOPayPal
>   [delete] Deleting directory /Users/liz/Roots/WOPayPal.framework
> build:
> WOPayPal.all:
> global.environment:
> global.properties:
> global.prepare:
>[mkdir] Created dir: /Users/liz/Roots/classes/WOPayPal
> global.compile:
> 
> BUILD FAILED
> /Users/liz/Projects/WonderSource-2015/Frameworks/BusinessLogic/WOPayPal/build.xml:12:
>  The following error occurred while executing this line:
> /Users/liz/Projects/WonderSource-2015/Build/build/build.xml:593: The 
> following error occurred while executing this line:
> /Users/liz/Projects/WonderSource-2015/Build/build/generic.xml:247: taskdef A 
> class needed by class org.objectstyle.woproject.ant.WOCompile cannot be 
> found: org/apache/tools/ant/taskdefs/Javac
>  using the classloader 
> AntClassLoader[/Users/liz/Projects/WonderSource-Feb2014/Build/lib/cayenne-1.2M12.jar:/Users/liz/Projects/WonderSource-2015/Build/lib/jdom-b7.jar:/Users/liz/Projects/WonderSource-Feb2014/Build/lib/log4j-1.2.9.jar:/Users/liz/Projects/WonderSource-2015/Build/lib/maven-ant-tasks-2.1.3.jar:/Users/liz/Projects/WonderSource-2015/Build/lib/woproject.jar]
> 
> 
> 
> If I try to build my own framework, which references some Wonder frameworks 
> in my workspace, I get:
> 
> BUILD FAILED
> /Users/liz/Projects/Test/build.xml:87: taskdef A class needed by class 
> org.objectstyle.woproject.ant.WOCompile cannot be found: 
> org/apache/tools/ant/taskdefs/Javac
>  using the classloader AntClassLoader[]
> 
> 
> I can build a different project, which uses the Wonder pre-built binaries in 
> /Library/Frameworks, in Eclipse with no problems.
> 
> I can also build the Wonder frameworks to ~/Roots fine from the command line 
> using ant:  ant clean frameworks
> 
>   
> 
> My development setup is:
> 
> El Capitan 10.11.1
> Java 1.8.0_31
> ant 1.9.6 installed via home-brew.
> Eclipse Luna Service Release 2 (4.4.2)
> WOLips 4.4.201510.13.47
> 
> 
> 
> 
> All ideas welcomed. 
> 
> Liz
> 
> 
> 
> 
> 
> 
> 
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com
> 
> This email sent to tedp...@yahoo.com

 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: El Capitan Apache Seg Fault

[Jeff Schmitz]

Thanks to help from Patrick Middleton I did get up and running on El Capitan.  
Below is a fairly long synopsis of my journey, warts and all.  Hopefully it can 
help someone else out:


My notes on upgrading from Lion to El Capitan on a remote server:

The first issue I hit was I lost contact to my server since the upgrade changed 
my network settings to use DHCP instead of my static IP.  I had to call a 
technician and had him reset my network settings to use the proper static IP so 
I could remote access to the box again.

Once I got access again my first questions was whether to install the new 
Server app.  In the end I didn’t need to, and I was worried doing so may write 
over the existing macports apache setup when it installed its web sharing 
services.

Once logged in I saw that my existing WebObjects installation had been deleted, 
i.e. there was no longer a /System/Library/WebObjects directory.

Next I decided to use the directions here:  
https://wiki.wocommunity.org/pages/viewpage.action?pageId=1049031

NEXT QUESTION: How do I decide which WebObjects installer to use? WebObjects 
WOCommunity resources or the apple installer?

First try, try the Apple Installer.

NEXT QUESTION: At 
https://wiki.wocommunity.org/pages/viewpage.action?pageId=1049031
It says: Make sure you install "WebObjectsRuntime.pkg" which is in the 
"Packages" directory of the .dmg.
Is this in addition to the main webobjects pkg, or do you only install the 
runtime.

I went ahead and installed just the runtime.  Funny that El Capitan says the 
publisher of this software can not be trusted.

It also gave this warning saying the package is incompatible with this version 
of OS X and mail fail to install.

I went ahead and said to install anyway got a fatal error.  So… I tried the 
WOInstaller route.  I downloaded and did java -jar WOInstaller.jar and found 
out I didn’t have a java version installed.  I guess ElCapitan deleted the one 
I had on.

Off to 
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
 to get the latest jdk.

Thinking maybe the apple installer failed because of no java I tried it again 
but it failed the same way.

On to trying the WOCommunity installer.  It requires an alternate installation 
directory to be specified.  I used /opt and specified version 5.4.3:

sudo java -jar WOInstaller.jar 5.4.3 /opt

Everything went well, and since I installed in /opt, maybe next time I upgrade 
Mac OS, webobjects won’t get stomped on by Apple.

Now with webobjects installed, I was able to bring up the previously installed 
(under Lion) java monitor and wotaskd via localhost.  The apps even started up. 
 However, I was unable to reach them via http due to apache segmentation faults 
when trying to serve any webobjects app.  

Next I decided to update the macports apache with the following commands:

sudo port -d selfupdate
sudo port upgrade outdated

No luck, still getting segmentation faults.  

After some research I’d seen a few things about MPM worker vs prefork that says 
to run with MPM prefork.  When I did a httpd -V I got:


Server version: Apache/2.2.31 (Unix)
Server built:   Nov 25 2015 11:47:12
Server's Module Magic Number: 20051115:40
Server loaded:  APR 1.5.2, APR-Util 1.5.4
Compiled using: APR 1.5.2, APR-Util 1.5.4
Architecture:   64-bit
Server MPM: Prefork
threaded: no
  forked: yes (variable process count)
Server compiled with
-D APACHE_MPM_DIR="server/mpm/prefork"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP…

So  looks like I was running prefork.

Next… Going back over some other similar list emails I noticed someone was 
using apache 2.4 and a new mod_Webobjects adaptor.  What!  Great, time to find 
it and install it and update apache and see what happens.

I found this page on how to upgrade macports apache to 2.4:

http://apple.stackexchange.com/questions/130481/how-to-upgrade-apache-2-2-to-2-4-in-macosx-mavericks

https://httpd.apache.org/docs/2.4/upgrading.html

From the above links I tried the command:

sudo port -vsc install apache24-devel

rebooted the machine just to make sure and then printed out the version info:

netbrackets1:~ netbrackets$ httpd -V
Server version: Apache/2.4.17 (Unix)
Server built:   Nov 25 2015 22:03:31
Server's Module Magic Number: 20120211:51
Server loaded:  APR 1.5.2, APR-UTIL 1.5.4
Compiled using: APR 1.5.2, APR-UTIL 1.5.4
Architecture:   64-bit
Server MPM: prefork
  threaded: no
forked: yes (variable process count)
Server compiled with
 -D APR_HAS_SENDFILE
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D APR_USE_SYSVSEM_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D DYNAMIC_MODULE_LIMIT=256
 -D HTTPD_ROOT="/opt/local"
 -D SUEXEC_BIN="/opt/local/bin/suexec"
 -D DEFAULT_PIDLOG="var/run/apache2/httpd.pid"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D AP_TYP

Can't build Wonder frameworks with Eclipse Luna / El Capitan / Java 8 setup

[Elizabeth Lynch]

In Eclipse, if I use ‘Run As Ant build’ to build any of the Wonder frameworks, 
the build fails as below - the example is for WOPayPal.  I have googled this 
and looked at the list, but can’t find any answer which works for me. 


Buildfile: 
/Users/liz/Projects/WonderSource-Feb2014/Frameworks/BusinessLogic/WOPayPal/build.xml
clean:
WOPayPal.all:
global.environment:
global.properties:
global.framework.clean:
  [delete] Deleting directory /Users/liz/Roots/classes/WOPayPal
  [delete] Deleting directory /Users/liz/Roots/WOPayPal.framework
build:
WOPayPal.all:
global.environment:
global.properties:
global.prepare:
   [mkdir] Created dir: /Users/liz/Roots/classes/WOPayPal
global.compile:

BUILD FAILED
/Users/liz/Projects/WonderSource-2015/Frameworks/BusinessLogic/WOPayPal/build.xml:12:
 The following error occurred while executing this line:
/Users/liz/Projects/WonderSource-2015/Build/build/build.xml:593: The following 
error occurred while executing this line:
/Users/liz/Projects/WonderSource-2015/Build/build/generic.xml:247: taskdef A 
class needed by class org.objectstyle.woproject.ant.WOCompile cannot be found: 
org/apache/tools/ant/taskdefs/Javac
 using the classloader 
AntClassLoader[/Users/liz/Projects/WonderSource-Feb2014/Build/lib/cayenne-1.2M12.jar:/Users/liz/Projects/WonderSource-2015/Build/lib/jdom-b7.jar:/Users/liz/Projects/WonderSource-Feb2014/Build/lib/log4j-1.2.9.jar:/Users/liz/Projects/WonderSource-2015/Build/lib/maven-ant-tasks-2.1.3.jar:/Users/liz/Projects/WonderSource-2015/Build/lib/woproject.jar]



If I try to build my own framework, which references some Wonder frameworks in 
my workspace, I get:

BUILD FAILED
/Users/liz/Projects/Test/build.xml:87: taskdef A class needed by class 
org.objectstyle.woproject.ant.WOCompile cannot be found: 
org/apache/tools/ant/taskdefs/Javac
 using the classloader AntClassLoader[]


I can build a different project, which uses the Wonder pre-built binaries in 
/Library/Frameworks, in Eclipse with no problems.

I can also build the Wonder frameworks to ~/Roots fine from the command line 
using ant:  ant clean frameworks



My development setup is:

El Capitan 10.11.1
Java 1.8.0_31
ant 1.9.6 installed via home-brew.
Eclipse Luna Service Release 2 (4.4.2)
WOLips 4.4.201510.13.47




All ideas welcomed. 

Liz







 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Wrong url generation for frameworks

[Paul Yu]

What I did, was to include source in my eclipse environment and then have a 
separate Jenkins build server that will build the wonder framework and then I 
would build the project.

Paul

Sent from my iPad

> On Nov 27, 2015, at 3:49 AM, Frank Stock  wrote:
> 
> Hi All,
> 
> Is there an easy way to build Wonder?
> I can add all the Wonder frameworks int Eclipse, I understand that my 
> development machine will work with these sources.
> But how can I build my frameworks for deployment. I am not used to work with 
> ant or maven.
> This is not clear to me:
> 
> Ant Builds on your Development Machine
> Icon
> WOlips' "Incremental Builder" is an incredibly helpful feature during 
> development, but it does things that the Ant deployment build does not do. If 
> you are either using WOLips to build your WebObjects Applications (WOLips Ant 
> Tools > Install) or are running Hudson/Jenkins locally to do it, you must 
> also build and install your workspace's Frameworks that your Application 
> depends upon – including your own, Project Wonder's and any others. The 
> standard Ant build does NOT do this for you.
> 
> Thanks,
> Frank
>> Op 26 nov. 2015, om 15:27 heeft Dr. Markus Stoll, junidas GmbH 
>>  het volgende geschreven:
>> 
>> Hi Frank,
>> 
>> you might give my pull request
>> 
>> https://github.com/wocommunity/wonder/pull/704
>> 
>> a try, this fix automatically fixes the URL for WebServerResources for 
>> embedded frameworks
>> 
>> Markus
>> 
>> 
>> 
>>> Am 26.11.2015 um 14:58 schrieb Frank Stock :
>>> 
>>> Hi Werner,
>>> 
>>> 
>>> I did a complete new install of WO on another Mac, with a new Wonder 
>>> project an I get the same result. My old application are running normal.
>>> App resources are working fine.
>>> 
>>> Frank
 Op 26 nov. 2015, om 12:56 heeft Frank Stock  het 
 volgende geschreven:
 
 Hi Werner,
 
 
 This is exactly what I have!
 I have created a new Wonder project and did a test on 2 servers with the 
 same result.
 
 
 Frank
> Op 26 nov. 2015, om 12:45 heeft Johann Werner  het 
> volgende geschreven:
> 
> Hi Frank,
> 
> you probably have an outdated build.xml file in your project. Within the 
> ant target build.woapp the woapplication task takes an attribute 
> „frameworksBaseURL“ that is either not set or set incorrectly in your 
> setup. From one of my build.xml I have:
> 
>  frameworksBaseURL="/WebObjects/${build.app.name}.woa/Frameworks" 
> destDir="${dest.dir}" customInfoPListContent="${customInfoPListContent}" 
> principalClass="${principalClass}" webXML="${webXML}" 
> webXML_CustomContent="${webXML_CustomContent}" 
> servletAdaptor="er.extensions.jspservlet.ERXServletAdaptor“>
> …
> 
> 
> This will put the necessary command line argument into the startup script 
> of your packaged application which should resolve your URL problem.
> 
> HTH
> jw
> 
> 
>> Am 26.11.2015 um 11:53 schrieb Frank Stock :
>> 
>> Hi all,
>> 
>> 
>> I have update my app on the server and I get a wrong url for the 
>> resources of the frameworks:
>> 
>> the url should be:
>> 
>> /WebObjects/xx.woa/Frameworks/Ajax.framework/WebServerResources/modalbox.css
>> 
>> but since today I get:
>> 
>> /WebObjects/Frameworks/Ajax.framework/WebServerResources/modalbox.css
>> 
>> Resources in the app are working fine:
>> 
>> /WebObjects/xxx.woa/Contents/WebServerResources/PageWrapper.css
>> 
>> Did I do something wrong? 
>> 
>> 
>> Thanks in advance!
>> Frank Stock
>> Belgium
> 
> 
 
>>> 
>>> ___
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/webobjects-dev/markus.stoll%40junidas.de
>>> 
>>> This email sent to markus.st...@junidas.de
>> 
> 
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/pyu%40mac.com
> 
> This email sent to p...@mac.com
 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Wrong url generation for frameworks

[Frank Stock]

Hi All,

Is there an easy way to build Wonder?
I can add all the Wonder frameworks int Eclipse, I understand that my 
development machine will work with these sources.
But how can I build my frameworks for deployment. I am not used to work with 
ant or maven.
This is not clear to me:

Ant Builds on your Development Machine
Icon
WOlips' "Incremental Builder" is an incredibly helpful feature during 
development, but it does things that the Ant deployment build does not do. If 
you are either using WOLips to build your WebObjects Applications (WOLips Ant 
Tools > Install) or are running Hudson/Jenkins 

 locally to do it, you must also build and install your workspace's Frameworks 
that your Application depends upon – including your own, Project Wonder's and 
any others. The standard Ant build does NOT do this for you.

Thanks,
Frank
> Op 26 nov. 2015, om 15:27 heeft Dr. Markus Stoll, junidas GmbH 
>  het volgende geschreven:
> 
> Hi Frank,
> 
> you might give my pull request
> 
> https://github.com/wocommunity/wonder/pull/704
> 
> a try, this fix automatically fixes the URL for WebServerResources for 
> embedded frameworks
> 
> Markus
> 
> 
> 
>> Am 26.11.2015 um 14:58 schrieb Frank Stock :
>> 
>> Hi Werner,
>> 
>> 
>> I did a complete new install of WO on another Mac, with a new Wonder project 
>> an I get the same result. My old application are running normal.
>> App resources are working fine.
>> 
>> Frank
>>> Op 26 nov. 2015, om 12:56 heeft Frank Stock  het 
>>> volgende geschreven:
>>> 
>>> Hi Werner,
>>> 
>>> 
>>> This is exactly what I have!
>>> I have created a new Wonder project and did a test on 2 servers with the 
>>> same result.
>>> 
>>> 
>>> Frank
 Op 26 nov. 2015, om 12:45 heeft Johann Werner  het 
 volgende geschreven:
 
 Hi Frank,
 
 you probably have an outdated build.xml file in your project. Within the 
 ant target build.woapp the woapplication task takes an attribute 
 „frameworksBaseURL“ that is either not set or set incorrectly in your 
 setup. From one of my build.xml I have:
 
 >>> frameworksBaseURL="/WebObjects/${build.app.name}.woa/Frameworks" 
 destDir="${dest.dir}" customInfoPListContent="${customInfoPListContent}" 
 principalClass="${principalClass}" webXML="${webXML}" 
 webXML_CustomContent="${webXML_CustomContent}" 
 servletAdaptor="er.extensions.jspservlet.ERXServletAdaptor“>
 …
 
 
 This will put the necessary command line argument into the startup script 
 of your packaged application which should resolve your URL problem.
 
 HTH
 jw
 
 
> Am 26.11.2015 um 11:53 schrieb Frank Stock :
> 
> Hi all,
> 
> 
> I have update my app on the server and I get a wrong url for the 
> resources of the frameworks:
> 
> the url should be:
> 
> /WebObjects/xx.woa/Frameworks/Ajax.framework/WebServerResources/modalbox.css
> 
> but since today I get:
> 
> /WebObjects/Frameworks/Ajax.framework/WebServerResources/modalbox.css
> 
> Resources in the app are working fine:
> 
> /WebObjects/xxx.woa/Contents/WebServerResources/PageWrapper.css
> 
> Did I do something wrong? 
> 
> 
> Thanks in advance!
> Frank Stock
> Belgium
 
 
>>> 
>> 
>> ___
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/markus.stoll%40junidas.de
>> 
>> This email sent to markus.st...@junidas.de
> 

 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Odd backtracking error

[CHRISTOPH WICK | i4innovation GmbH, Bonn]

Hi Mark,

if you are using the new window to show a PDF (which should not have any 
further links or buttons), it may be a better solution to use a direct action 
to show it and pass all necessary params to it.

C.U.CW
--
The three great virtues of a programmer are Laziness, Impatience and Hubris. 
(Randal Schwartz)

> On 27.11.2015, at 09:08, René Bock  wrote:
> 
> Hi Mark,
> 
> last week, we had a similar issue.  The problem was that, between two regular 
> POST requests, the client requested for /App.woa
> 
> 
> As noted in http://sourceforge.net/p/wonder/mailman/message/11756245/ 
>  this request will 
> create a new session.
> 
> 
> Some "research" revealed, that
> 
>   WORequest._lookForIDsInCookiesFirst()
> 
> always will return false.  This seems the root cause of the problem. 
> Unfortunately, static methods can't overridden...
> 
> 
> Regards,
> 
>   René
> 
> 
>> Am 26.11.2015 um 23:29 schrieb Mark Wardle > >:
>> 
>> Thanks Chuck. I’m not sure. How can I check that? I haven’t got a favicon 
>> set presently. It shouldn’t default to accessing it via WO should it? I had 
>> thought it independent and a function of apache but of course, I do have a 
>> rewrite rule which redirects / to my WOA so it might well be doing that! Not 
>> entirely sure how to check or indeed fix!
>> 
>> Mark
>> 
>> 
>>> On 26 Nov 2015, at 22:25, Chuck Hill >> > wrote:
>>> 
>>> Is your web server (or Wonder) protecting /favicon.ico from getting to your 
>>> app or handling it?  That request won’t contain the cookies (IIRC) which 
>>> results in a new session getting created and the app will return the cookie 
>>> from the new session (usually with an error response as it is not handling 
>>> the request.
>>> 
>>> Chuck
>>> 
>>> 
>>> From: >> > on 
>>> behalf of Mark Wardle mailto:m...@wardle.org>>
>>> Date: Thursday, November 26, 2015 at 2:18 PM
>>> To: Paul Hoadley mailto:pa...@logicsquad.net>>
>>> Cc: webobjects-dev >> >
>>> Subject: Re: Odd backtracking error
>>> 
>>> Paul,
>>> 
>>> That sounds like what might be happening and explain the inconsistency 
>>> depending on, perhaps, the URL entered.
>>> 
>>> I’ll give it a go. Thank you!
>>> 
>>> Mark
>>> 
 On 26 Nov 2015, at 22:16, Paul Hoadley >>> > wrote:
 
 Hi Mark,
 
 On 27 Nov 2015, at 6:50 am, Mark Wardle >>> > wrote:
 
> I’m getting a weird backtracking error. I have a component which mainly 
> uses component actions and one of these component actions uses 
> target=“_new” to show a PDF document in a new window.
> 
> The action uses
> WOResponse response = 
> WOApplication.application().createResponseInContext(context);
> to create a new response.
> 
> Sessions are stored in cookies.
> 
> On some computers (but not all), when one clicks the link, I get a login 
> page and in the log a session restoration error with no session. It works 
> fine on other computers running the same version of IE. I can’t reproduce 
> the problem at all on my development machine.
> 
> Any ideas?
 
 I’m not sure this would explain everything you’re seeing here, but you can 
 get session loss (and the resulting unexpected bounce to a login page) 
 when using cookies for session ID storage if 
 WOSession.domainForIDCookies() is returning something “too specific” for 
 your deployment setup. By default, that method returns the application’s 
 full path, right down to the “.woa” extension. So, for example, if you’re 
 using URL re-writing in deployment, there could easily be a mismatch. I 
 usually override it to return “/”. Again, not sure it explains everything 
 you’re seeing there, but it’s something to rule out.
 
 
 --
 Paul Hoadley
 http://logicsquad.net/ 
 
 
 
>>> 
>> 
>> ___
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com 
>> )
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/bock%40salient.de 
>> 
>> 
>> This email sent to b...@salient.de
> 
> --
> salient doremus
> 
> salient GmbH
> Kontorhaus -  Lindleystraße 12
> 60314 Frankfurt Main
> 
> Fon +49 (0)69 - 650096 -0, Durchwahl: - 18, Fax: -70
> 
> http://www.salient.de 
> http://www.doremus.com
> http://www.openforms.de
> 
> Geschäftsführer: Peter Biler, Alexander Gerling, Lars Ohlerich
> Amtsgericht Frankfurt Main, HRB 48693
> 
> // Neuer Schwung auf a

Re: Odd backtracking error

[René Bock]

Hi Mark,

last week, we had a similar issue.  The problem was that, between two regular 
POST requests, the client requested for /App.woa


As noted in http://sourceforge.net/p/wonder/mailman/message/11756245/ 
 this request will 
create a new session.  


Some "research" revealed, that 

WORequest._lookForIDsInCookiesFirst()

always will return false.  This seems the root cause of the problem. 
Unfortunately, static methods can't overridden...


Regards,

René


> Am 26.11.2015 um 23:29 schrieb Mark Wardle :
> 
> Thanks Chuck. I’m not sure. How can I check that? I haven’t got a favicon set 
> presently. It shouldn’t default to accessing it via WO should it? I had 
> thought it independent and a function of apache but of course, I do have a 
> rewrite rule which redirects / to my WOA so it might well be doing that! Not 
> entirely sure how to check or indeed fix!
> 
> Mark
> 
> 
>> On 26 Nov 2015, at 22:25, Chuck Hill > > wrote:
>> 
>> Is your web server (or Wonder) protecting /favicon.ico from getting to your 
>> app or handling it?  That request won’t contain the cookies (IIRC) which 
>> results in a new session getting created and the app will return the cookie 
>> from the new session (usually with an error response as it is not handling 
>> the request.
>> 
>> Chuck
>> 
>> 
>> From: > > on 
>> behalf of Mark Wardle mailto:m...@wardle.org>>
>> Date: Thursday, November 26, 2015 at 2:18 PM
>> To: Paul Hoadley mailto:pa...@logicsquad.net>>
>> Cc: webobjects-dev > >
>> Subject: Re: Odd backtracking error
>> 
>> Paul,
>> 
>> That sounds like what might be happening and explain the inconsistency 
>> depending on, perhaps, the URL entered.
>> 
>> I’ll give it a go. Thank you!
>> 
>> Mark
>> 
>>> On 26 Nov 2015, at 22:16, Paul Hoadley >> > wrote:
>>> 
>>> Hi Mark,
>>> 
>>> On 27 Nov 2015, at 6:50 am, Mark Wardle >> > wrote:
>>> 
 I’m getting a weird backtracking error. I have a component which mainly 
 uses component actions and one of these component actions uses 
 target=“_new” to show a PDF document in a new window.
 
 The action uses 
 WOResponse response = 
 WOApplication.application().createResponseInContext(context);
 to create a new response.
 
 Sessions are stored in cookies.
 
 On some computers (but not all), when one clicks the link, I get a login 
 page and in the log a session restoration error with no session. It works 
 fine on other computers running the same version of IE. I can’t reproduce 
 the problem at all on my development machine.
 
 Any ideas?
>>> 
>>> I’m not sure this would explain everything you’re seeing here, but you can 
>>> get session loss (and the resulting unexpected bounce to a login page) when 
>>> using cookies for session ID storage if WOSession.domainForIDCookies() is 
>>> returning something “too specific” for your deployment setup. By default, 
>>> that method returns the application’s full path, right down to the “.woa” 
>>> extension. So, for example, if you’re using URL re-writing in deployment, 
>>> there could easily be a mismatch. I usually override it to return “/”. 
>>> Again, not sure it explains everything you’re seeing there, but it’s 
>>> something to rule out.
>>> 
>>> 
>>> -- 
>>> Paul Hoadley
>>> http://logicsquad.net/ 
>>> 
>>> 
>>> 
>> 
> 
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/bock%40salient.de
> 
> This email sent to b...@salient.de

--
salient doremus

salient GmbH
Kontorhaus -  Lindleystraße 12
60314 Frankfurt Main

Fon +49 (0)69 - 650096 -0, Durchwahl: - 18, Fax: -70

http://www.salient.de
http://www.doremus.com
http://www.openforms.de

Geschäftsführer: Peter Biler, Alexander Gerling, Lars Ohlerich
Amtsgericht Frankfurt Main, HRB 48693

// Neuer Schwung auf allen Endgeräten für den Automobilclub von Deutschland: 
http://www.avd.de/

 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com