• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Current status of WO Adaptors
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Current status of WO Adaptors


  • Subject: Re: Current status of WO Adaptors
  • From: Q <email@hidden>
  • Date: Mon, 16 Feb 2009 12:01:47 +1000


On 16/02/2009, at 9:59 AM, Miguel Arroz wrote:

Hi!

On 2009/02/15, at 23:41, Q wrote:

/Developer/WebObjects543/Developer/Examples/WebObjects/Source/ Adaptors

Why don't I have that directory? Do I have to install some extra package?



My bad. /Developer/Examples/WebObjects/Source/Adaptors

- What about the Wonder adaptor? I saw, in the repository history, that there's a recent commit with a description close to "Merging with apple code". Is this the same adaptor Apple ships in 5.4? Or these are two different adaptors?

They are virtually identical, although the wonder sources have extra build support for other platforms as well as a couple of minor additions and bug fixes.

OK. The bug I described in the webobjects-deploy list is driving me insane. I finally figured why it doesn't happen on our production and stage servers, nor in my Mac. That's because all those machines are using modern version sof the adaptor (Wonder 4.0 or higher). I used some old version of the FreeBSD WO port on the VM I setup this week, and that still installed the Wonder 3 plugin.

I haven't updated the freebsd port in quite some time. It's on my todo list. honest. Actually there are very few changes between the current wonder code that the source the woport uses.


What amazes me most is that it appears that the bug is still there, but it's not triggered due to what could be another bug. There's this code:

#ifdef APACHE_SECURITY_ENABLED
	/******client cert support***** */

	if (req_is_https(r)) {
		const char *hdrValue;
		const char *cert;
		int certLen = 0;

		WOLog(WO_DBG,"We have ssl");

Well, on Leopard I never see the "we have ssl" on the logs.

Grep the binary for the string "We have ssl". It's possible that APACHE_SECURITY_ENABLED was not defined for the adaptor you are using.


On my mac this code isn't compiled into the standard system binary. But if I build the adaptor from source it is.

:/ I don't know if that's normal, because the comment says "client cert support", and I'm not using any. But the code says "req_is_https". Anyway, on the Mac it works, and the only difference I see is the OpenSSL version (the FreeBSD version is slightly newer).

If you can email me offline with exactly what I need to do to reproduce the problem I will look into it when I have time.


--
Seeya...Q

Quinton Dolan - email@hidden
Gold Coast, QLD, Australia (GMT+10)
Ph: +61 419 729 806



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Current status of WO Adaptors (From: Miguel Arroz <email@hidden>)
 >Re: Current status of WO Adaptors (From: Q <email@hidden>)
 >Re: Current status of WO Adaptors (From: Miguel Arroz <email@hidden>)

  • Prev by Date: Re: Current status of WO Adaptors
  • Next by Date: Re: WOProject: First Time Maven User
  • Previous by thread: Re: Current status of WO Adaptors
  • Next by thread: Component with bindings in dictionary.
  • Index(es):
    • Date
    • Thread