> I found this in the taglib file:
> =====================
> Provide access to CFML application scope. in CF5 and
> earlier, applications must have a name. ...
>
> Either way, java can share variables with a legacy cf
> application by prepending the application name onto the
> servlet context key name. For example, if a cf application
> is called "myapp", then in java/jsp you can get variables
> like so:
>
> <code> application.getAttribute("myapp.variableName"); <;/code>
>
> ...
>
> I didn't previously know this, but it seems to be quite
> handy. especially the unnamed applications cope which will
> share variables on the page (if I read it right).
This is in the documentation. However, even if you give your application a
name, you can still share variables between it and a servlet or JSP page; in
the Java code, you'd have to explicitly reference the named application
instead of just using "application.". On the other hand, if you have a Java
application that is already written, this approach will let you use CF with
it without rewriting your Java.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
This list and all House of Fusion resources hosted by CFHosting.com. The place for
dependable ColdFusion Hosting.
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
