Just for your information you can't put the <cfimport> in the
application.cfm.
You have to put it in each .cfm where you want to use it.
And, you can't have overlapping name spaces because, each time you
<cfimport> a taglib, you specify the corresponding tag prefix, you're going
to use in the page.
Ex. (from the CF doc) :
<cfimport
prefix="myprefix"
taglib="/WEB-INF/lib/myjsptags.jar">
<myprefix:helloTag message="Hello" />
Benoit
-----Message d'origine-----
De : S. Isaac Dealey [mailto:[EMAIL PROTECTED]]
Envoy� : mardi 20 ao�t 2002 21:09
� : CF-Talk
Objet : RE: CFMX and Java Libraries
Oh awesome. :) I obviously haven't gotten to CFMX yet, although I'm headed
there... Very excited about it actually... but this actually reduces the
risk ( or at least I would expect it to ) of major issues when upgrading to
a new version of cf server since you would be telling the application where
to find the additional Java libraries in the application.cfm file or
similar. ( Pardon me, I haven't had the time to go look up the docs yet
either. :)
Isaac Dealey
Certified Advanced ColdFusion Developer
www.turnkey.to
954-776-0046
> You have to use the <cfimport> tag are the start of any CFM that is
> going to use a tag library.
> Matt Liotta
> President & CEO
> Montara Software, Inc.
> http://www.montarasoftware.com/
> V: 415-577-8070
> F: 415-341-8906
> P: [EMAIL PROTECTED]
>> -----Original Message-----
>> From: S. Isaac Dealey [mailto:[EMAIL PROTECTED]]
>> Sent: Tuesday, August 20, 2002 11:54 AM
>> To: CF-Talk
>> Subject: CFMX and Java Libraries
>>
>> It's my understanding ( though I could be entirely mistaken ) that now
>> that
>> CFMX is a J2EE server it is possible to create new Java libraries to
> allow
>> for new tags like coldfusion tags which would not require being
> registered
>> in the cf administrator... i.e.
>>
>> <cfmycustomjavatag>
>>
>> which would function for all intents and purposes exactly the same way
>> that
>> the core coldfusion tags function because they're created as Java
>> libraries
>> and stored alongside similar Java libraries for the ColdFusion core
> tags.
>>
>> Has anyone done this with MX ? Any thoughts on the subject ?
>>
>> I have mixed emotions about it...
>>
>> In some case I think it might be really nice to be able to seamlessly
>> extend
>> the functionality without having to go through cfx tag registration,
> or to
>> be able to dig into the existing tag architecture to add new features,
>> such
>> as having a <cfpath directory="c:\physical\path"> tag that would allow
> you
>> to add custom-tags directory paths to a given <cfapplication> in a
> similar
>> fashion as the PATH command adds executable search paths in DOS or a
> DOS
>> shell.
>>
>> ( This would allow applications on shared hosting to create their own
>> custom
>> tags directorie(s) within a sandbox, thereby eliminating problems
> related
>> to
>> applications needing certain tags to be located in the custom-tags
>> directory
>> which is inaccessible to shared hosting users. I know CF 5 and later
> allow
>> additional CT paths to be defined in the CF administrator, but being
> able
>> to
>> do it using script and only within a given cfapplication would still
>> provide
>> more flexibility and eliminate hassle. )
>>
>> On the other hand, I could see this causing problems particularly
> during
>> upgrades or with overlapping items in name spaces...
>>
>> Is anyone else thinking about this also or am I just spinning my
> wheels?
>> Or
>> completely crazy?
>>
>>
>> Isaac Dealey
>> Certified Advanced ColdFusion Developer
>>
>> New Epoch
>> www.turnkey.to
>> 954-776-0046
>>
>
______________________________________________________________________
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
