Hi Adam,
I wanted to check the source code history to see where it stopped working. Unfortunately, I can not find a working version…
The Lucee source file in question is: https://github.com/lucee/Lucee4/blob/master/lucee-java/lucee-core/src/coldfusion/server/ServiceFactory.java
The oldest commit in the Lucee GitHub repo is named “inital commit”: Lucee4/lucee-java/lucee-core/src/coldfusion/server/ServiceFactory.java at b582cd1f3286f16eb1a4fea7d1d3774815c0476e · lucee/Lucee4 · GitHub
The Railo source on github has an initial version dated june 24, 2009: railo/railo-java/railo-core/src/coldfusion/server/ServiceFactory.java at 99e969e528c6f5a9f726a229879a5e16a3112bdb · getrailo/railo · GitHub
In all those cases, it threw the “missingService” exception. Are you sure it worked in Railo and Lucee?
Kind regards,
Paul Klinkenberg
Taffy uses this factory to determine if there is a server level /resources mapping. It’s part of a method used to find the resources the developer is defining, which could be in a variety of locations.
For more context, see the function guessResourcesPath, here: https://github.com/atuttle/Taffy/blob/master/core/api.cfc#L928
But my position is this:
- It exists and works in current supported versions ACF
- It existed and worked in Railo
- It existed and worked in earlier versions of Lucee
Therefore, if you’re going to remove functionality from the platform, shouldn’t you provide another reasonable way to accomplish the same goal?
For Taffy’s purposes, asking for a CF Admin password is simply unacceptable.
In my opinion, the burden is on Lucee to justify why it was removed, rather than on the community to justify why it’s needed. Even if that were not the case, in my opinion, Taffy’s usage is a reasonable and clear justification.
Is there a specific reason your taffy mappings need to exist at the server level? Their docs show that App-level mappings are acceptable: http://docs.taffy.io/3.0.0/ http://docs.taffy.io/3.0.0/
It’s much easier to handle those mappings at the app level and checking for them is as simple as a structKeyExists().
if(!structKeyExists(getApplicationSettings().mappings,‘/mymapping’)){
}
Server-level mappings seems so… 2008. :)Op 14 aug. 2015, om 17:36 heeft Adam Tuttle <@Adam_Tuttle> het volgende geschreven:
On Wednesday, July 22, 2015 at 3:18:38 PM UTC-4, Jon Clausen wrote:
On July 22, 2015 at 1:51:07 PM, Tony Junkes (tonyj...@gmail.com <javascript:>) wrote:
The code below runs in ACF,
writeDump( createObject(“java”, “coldfusion.server.ServiceFactory”).getRuntimeService().getMappings() );
In Lucee it results in: “the service [RuntimeService] is currently missing. At the moment you can use cfadmin tag instead”
I’ve found the way to get similar results using the tag but the process is a bit more involved since it either requires a password or making read access open from the admin.
Is there a reason why this hasn’t been implemented similar to ACF?
The reason I ask is currently, the Taffy REST framework is making use of the above object creation to check if a server-level mapping exists. For compatibility reasons, this would be ideal to have available from ACF and Lucee unless there’s another method that I’m not aware of.
Cheers.
You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com <javascript:>.
To post to this group, send email to lu...@googlegroups.com <javascript:>.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/d51811ea-1244-4193-a5b5-896d0f970f86%40googlegroups.com https://groups.google.com/d/msgid/lucee/d51811ea-1244-4193-a5b5-896d0f970f86%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.
–
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your ticket NOW - http://www.cfcamp.org/ http://www.cfcamp.org/
You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com mailto:lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/d377e6cf-c05a-4bfb-8733-d7adb46a09f2%40googlegroups.com https://groups.google.com/d/msgid/lucee/d377e6cf-c05a-4bfb-8733-d7adb46a09f2%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.
