If createobject is disabled im guessing that also the cfobject tag will
be disabled. There was a thread about this not working well on a
sandbox.
CFLOGIN is quite useful as it also allows you to lock down using roles
who has access to which cfc method which is good. Also for the j2ee
stuff with sessions across clusters I think but that's probably not
relevant for this.
Any call which creates an instance of a cfc is gonna use createobject so
I cant see how you can survive without it ?
Is there still an unprotected folder where you can run any script from
even if it is turned off else where.
If so you could create a factory or wrapper.
E.g.
<cfscript>
myTestObj=CFDeveloperObjectFactory.get("test.example");
</cfscript>
That way you could stop calls to java classes but still allow people to
use instance based cfc calls
ALEX
-----Original Message-----
From: Snake Hollywood [mailto:[EMAIL PROTECTED]
Sent: 02 December 2003 11:20
To: [EMAIL PROTECTED]
Subject: [ cf-dev ] Createobject()
I am having some issues with disabling createobject() on shared hosting
as it seems to break stuff. Obviously we have to disable this to stop
people messing with the service factory, but this also breaks other
htings that use it, such as CFLOGIN, and cfc creation.
So my question is, how important are the things that rely on
createobject().
Can u live without cflogin, is it a pain to deal with cfc's without it
etc?
I have found a few other errors cropping up in fusebox apps with
createobject() disabled, but I dunno why fusebox would be using it?
Anyone ?
russ
--
** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED] For
human help, e-mail: [EMAIL PROTECTED]
--
** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For human help, e-mail: [EMAIL PROTECTED]
