Anjo,

I wrote that years ago and lost a lot of time trying to find out why  
everything stopped working. It was certainly true at the time. I have  
no idea about now. I think it's much nicer to stop using global  
WebObjects.properties files for properties on particular servers and  
to use per user files like Properties.wolive and Properties.wostaging.  
I guess that requires using Wonder.

Regards
James

On 2 Sep 2009, at 16:52, Anjo Krank wrote:

> From the wiki:
>
>> wotaskd relies on direct connect being enabled so that the adaptor
>> can communicate with it. Do not globally disable direct connect on
>> your servers. For example, if you disable direct connect from the
>> WebObjects.properties file in the application server's home
>> directory, you will prevent wotaskd from responding to requests on
>> its assigned port.
>
> This one is stupid and a bug if it's true, isn't it?
>
> Cheers, Anjo
>
>
>
> Am 02.09.2009 um 16:48 schrieb Mike Schrag:
>
>> Yeah, I'm not saying that having a policy of not using DC is wrong,
>> either -- Most of the caveats the wiki page layout are valid. I'm
>> just not quite as adamant about its evilness as I was a few years  
>> ago.
>>
>> ms
>>
>> On Sep 2, 2009, at 10:37 AM, John Bruce wrote:
>>
>>> Fair enough I didn't realise that Wonder had improved this and the
>>> simplified development is nice. For me, I find deveoping with a full
>>> Apache + extras setup important because in deployment we use nginx  
>>> as
>>> a reverse proxy which serves content from memcache via
>>> X-Accel-Redirect headers and it's good to run with this in
>>> development
>>> so that we catch config errors early on.
>>>
>>> Cheers
>>>
>>> John
>>>
>>> On Wed, Sep 2, 2009 at 1:09 PM, Mike Schrag<[email protected]>
>>> wrote:
>>>>> Also why developing with Direct Connect is Evil:
>>>>>
>>>>>
>>>>> http://wiki.objectstyle.org/confluence/display/WO/Web+Applications-Development-Direct+Connect
>>>>
>>>> I used to think DC was evil, too, but I've come around ... It's
>>>> just so easy
>>>> to do, and Wonder makes it behave in a pretty similar way. We even
>>>> support
>>>> DC w/ SSL now. The things Chuck lists on that page are still
>>>> valid, so I
>>>> think it's more that you should be AWARE of the differences, but
>>>> it's pretty
>>>> rare that I run into a prod/dev difference between the two these
>>>> days.
>>>>
>>>> ms
>>>>
>>>> _______________________________________________
>>>> 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/wolists%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/mschrag%40mdimension.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/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/jbrook%40upcbroadband.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/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to