In the past I've done this by just having the method implementations throwing the errors.
Usually, it doesn't really matter too much whether the error gets thrown as soon as the component is initialized, or when the first method is fired. You could probably hack around with the core java classes of the ColdFusion server and use the TemplateProxy or something similar, but I wouldn't recommend this. Spike -------------------------------------------- Stephen Milligan Code poet for hire http://www.spike.org.uk Do you cfeclipse? http://cfeclipse.tigris.org >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of >Mark Mandel >Sent: Monday, July 26, 2004 5:50 PM >To: CFAussie Mailing List >Subject: [cfaussie] CFC Abstract Base Class > >Hey all - > >Just wondering what the best way to implement a abstract base class, >to ensure that the class cannot be instantiated, but can be inherited >from. > >I tried dropping <cfthrow type="com.AbstractBaseClassException" >message="This class cannot be instantiated" > in the top of the cfc, >but that fires when a CFC that extends it is created (which makes a >degree of sense). > >So I'm a bit stuck. > >Any thoughts? > >Mark > >-- >E: [EMAIL PROTECTED] >W: www.compoundtheory.com >ICQ: 3094740 > >--- >You are currently subscribed to cfaussie as: [EMAIL PROTECTED] >To unsubscribe send a blank email to >[EMAIL PROTECTED] >Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
