Lucee 5 Extension

Currently you can create extensions for the server context, web context or
both. However, there are 2 issues with extensions that require components.
First, the docs say this:

You can make components globally available by adding them to the folder
/components.

However, this is currently not functioning as the deploy.log clearly shows
when you try it:

Extension;not supported yet!;lucee.runtime.exp.ApplicationException: not

supported yet!

For server extensions, you can get around this by using the /applications
folder, but this does not work for web contexts.

This brings us to the second issue: it appears that Lucee has a default
{lucee-web} component mapping, but not a {lucee-server} mapping. Is there a
way to add this mapping automatically upon component installation?
Otherwise, the user would need to add the mapping manually.

OK, so I circumvented most of these issues by packaging the cfc component,
along with the appropriate mapping, in a .lar file in the archives folder
of the .lex. This allows it to auto-deploy in either server or web context
and auto-map the component.

Is this the “best-practice” or just a workaround until the /component
deployment is incorporated?

Also, the .lar files do not get removed on an uninstall, so that’s still
something that needs to be looked at…

I think I have ironed out most of auto-deploy issues, so if anyone wants to
test out deployment, the extension is here:

https://github.com/Leftbower/cfspreadsheet-lucee-5On Saturday, July 16, 2016 at 6:20:27 PM UTC-7, ADK wrote:

Currently you can create extensions for the server context, web context or
both. However, there are 2 issues with extensions that require components.
First, the docs say this:

You can make components globally available by adding them to the folder
/components.

However, this is currently not functioning as the deploy.log clearly shows
when you try it:

Extension;not supported yet!;lucee.runtime.exp.ApplicationException: not

supported yet!

For server extensions, you can get around this by using the /applications
folder, but this does not work for web contexts.

This brings us to the second issue: it appears that Lucee has a default
{lucee-web} component mapping, but not a {lucee-server} mapping. Is there a
way to add this mapping automatically upon component installation?
Otherwise, the user would need to add the mapping manually.

Hi,

I must be missing something… I can’t for the life of me get cfspreadsheet
for lucee 5 to install. My windows workstation is running Lucee 5.1.0.34,
and I’m using the .lex
from: https://github.com/Leftbower/cfspreadsheet-lucee-5.

I’m dropping the .lex into: C:\lucee\tomcat\lucee-server\deploy

The error I get in C:\lucee\tomcat\lucee-server\context\logs\deploy.log is:

“ERROR”,“Thread-225115”,“11/11/2016”,“13:51:06”,"","Extension;The Extension
[C:\lucee\tomcat\lucee-server\deploy\cfspreadsheet-lucee-5.lex] is
invalid,no Manifest file was found at
[META-INF/MANIFEST.MF].;lucee.runtime.exp.ApplicationException: The
Extension [C:\lucee\tomcat\lucee-server\deploy\cfspreadsheet-lucee-5.lex]
is invalid,no Manifest file was found at [META-INF/MANIFEST.MF].
at lucee.runtime.extension.RHExtension.(RHExtension.java:199)
at
lucee.runtime.config.XMLConfigAdmin.updateRHExtension(XMLConfigAdmin.java:4585)
at
lucee.runtime.config.XMLConfigAdmin._updateRHExtension(XMLConfigAdmin.java:4573)
at lucee.runtime.config.DeployHandler.deploy(DeployHandler.java:80)
at lucee.runtime.engine.Controler.control(Controler.java:203)
at lucee.runtime.engine.Controler.access$000(Controler.java:58)
at lucee.runtime.engine.Controler$ControlerThread.run(Controler.java:108)
"On Sunday, 17 July 2016 05:38:39 UTC-4, ADK wrote:

OK, so I circumvented most of these issues by packaging the cfc component,
along with the appropriate mapping, in a .lar file in the archives folder
of the .lex. This allows it to auto-deploy in either server or web context
and auto-map the component.

Is this the “best-practice” or just a workaround until the /component
deployment is incorporated?

Also, the .lar files do not get removed on an uninstall, so that’s still
something that needs to be looked at…

I think I have ironed out most of auto-deploy issues, so if anyone wants
to test out deployment, the extension is here:

https://github.com/Leftbower/cfspreadsheet-lucee-5

On Saturday, July 16, 2016 at 6:20:27 PM UTC-7, ADK wrote:

Currently you can create extensions for the server context, web context
or both. However, there are 2 issues with extensions that require
components. First, the docs say this:

You can make components globally available by adding them to the folder
/components.

However, this is currently not functioning as the deploy.log clearly
shows when you try it:

Extension;not supported yet!;lucee.runtime.exp.ApplicationException: not

supported yet!

For server extensions, you can get around this by using the /applications
folder, but this does not work for web contexts.

This brings us to the second issue: it appears that Lucee has a default
{lucee-web} component mapping, but not a {lucee-server} mapping. Is there a
way to add this mapping automatically upon component installation?
Otherwise, the user would need to add the mapping manually.

Update:

The .lex copying installation worked perfectly in the web context:

Lex file:
https://github.com/Leftbower/cfspreadsheet-lucee-5/blob/master/cfspreadsheet-lucee-5.lex

Copying it to a web context:
ie, \website\wwwroot\WEB-INF\lucee\deploy\ [ put lex here ]On Friday, 11 November 2016 13:57:21 UTC-5, Jonathan Smith wrote:

Hi,

I must be missing something… I can’t for the life of me get
cfspreadsheet for lucee 5 to install. My windows workstation is running
Lucee 5.1.0.34, and I’m using the .lex from:
https://github.com/Leftbower/cfspreadsheet-lucee-5.

I’m dropping the .lex into: C:\lucee\tomcat\lucee-server\deploy

The error I get in C:\lucee\tomcat\lucee-server\context\logs\deploy.log
is:

“ERROR”,“Thread-225115”,“11/11/2016”,“13:51:06”,"","Extension;The
Extension [C:\lucee\tomcat\lucee-server\deploy\cfspreadsheet-lucee-5.lex]
is invalid,no Manifest file was found at
[META-INF/MANIFEST.MF].;lucee.runtime.exp.ApplicationException: The
Extension [C:\lucee\tomcat\lucee-server\deploy\cfspreadsheet-lucee-5.lex]
is invalid,no Manifest file was found at [META-INF/MANIFEST.MF].
at lucee.runtime.extension.RHExtension.(RHExtension.java:199)
at
lucee.runtime.config.XMLConfigAdmin.updateRHExtension(XMLConfigAdmin.java:4585)
at
lucee.runtime.config.XMLConfigAdmin._updateRHExtension(XMLConfigAdmin.java:4573)
at lucee.runtime.config.DeployHandler.deploy(DeployHandler.java:80)
at lucee.runtime.engine.Controler.control(Controler.java:203)
at lucee.runtime.engine.Controler.access$000(Controler.java:58)
at lucee.runtime.engine.Controler$ControlerThread.run(Controler.java:108)
"

On Sunday, 17 July 2016 05:38:39 UTC-4, ADK wrote:

OK, so I circumvented most of these issues by packaging the cfc
component, along with the appropriate mapping, in a .lar file in the
archives folder of the .lex. This allows it to auto-deploy in either server
or web context and auto-map the component.

Is this the “best-practice” or just a workaround until the /component
deployment is incorporated?

Also, the .lar files do not get removed on an uninstall, so that’s still
something that needs to be looked at…

I think I have ironed out most of auto-deploy issues, so if anyone wants
to test out deployment, the extension is here:

https://github.com/Leftbower/cfspreadsheet-lucee-5

On Saturday, July 16, 2016 at 6:20:27 PM UTC-7, ADK wrote:

Currently you can create extensions for the server context, web context
or both. However, there are 2 issues with extensions that require
components. First, the docs say this:

You can make components globally available by adding them to the folder
/components.

However, this is currently not functioning as the deploy.log clearly
shows when you try it:

Extension;not supported yet!;lucee.runtime.exp.ApplicationException: not

supported yet!

For server extensions, you can get around this by using the
/applications folder, but this does not work for web contexts.

This brings us to the second issue: it appears that Lucee has a default
{lucee-web} component mapping, but not a {lucee-server} mapping. Is there a
way to add this mapping automatically upon component installation?
Otherwise, the user would need to add the mapping manually.

That is odd? Check your download, perhaps it’s corrupted?

I just checked and the manifest is definitely in the META_INF folder in the
Github repo (which has been untouched in ~4 months.)

I wonder if it is an issue with case sensitivity on Linux? I’ve only ever
tested it on Windows. The file is “Manifest.mf” lowercase in the archive.
You could try renaming it in the .lex (a LEX file is just a zip) and see if
that works, but that’s just a pot-shot guess…On Friday, November 11, 2016 at 10:57:21 AM UTC-8, Jonathan Smith wrote:

Hi,

I must be missing something… I can’t for the life of me get
cfspreadsheet for lucee 5 to install. My windows workstation is running
Lucee 5.1.0.34, and I’m using the .lex from:
https://github.com/Leftbower/cfspreadsheet-lucee-5.

I’m dropping the .lex into: C:\lucee\tomcat\lucee-server\deploy

The error I get in C:\lucee\tomcat\lucee-server\context\logs\deploy.log
is:

“ERROR”,“Thread-225115”,“11/11/2016”,“13:51:06”,"","Extension;The
Extension [C:\lucee\tomcat\lucee-server\deploy\cfspreadsheet-lucee-5.lex]
is invalid,no Manifest file was found at
[META-INF/MANIFEST.MF].;lucee.runtime.exp.ApplicationException: The
Extension [C:\lucee\tomcat\lucee-server\deploy\cfspreadsheet-lucee-5.lex]
is invalid,no Manifest file was found at [META-INF/MANIFEST.MF].
at lucee.runtime.extension.RHExtension.(RHExtension.java:199)
at
lucee.runtime.config.XMLConfigAdmin.updateRHExtension(XMLConfigAdmin.java:4585)
at
lucee.runtime.config.XMLConfigAdmin._updateRHExtension(XMLConfigAdmin.java:4573)
at lucee.runtime.config.DeployHandler.deploy(DeployHandler.java:80)
at lucee.runtime.engine.Controler.control(Controler.java:203)
at lucee.runtime.engine.Controler.access$000(Controler.java:58)
at lucee.runtime.engine.Controler$ControlerThread.run(Controler.java:108)
"

On Sunday, 17 July 2016 05:38:39 UTC-4, ADK wrote:

OK, so I circumvented most of these issues by packaging the cfc
component, along with the appropriate mapping, in a .lar file in the
archives folder of the .lex. This allows it to auto-deploy in either server
or web context and auto-map the component.

Is this the “best-practice” or just a workaround until the /component
deployment is incorporated?

Also, the .lar files do not get removed on an uninstall, so that’s still
something that needs to be looked at…

I think I have ironed out most of auto-deploy issues, so if anyone wants
to test out deployment, the extension is here:

https://github.com/Leftbower/cfspreadsheet-lucee-5

On Saturday, July 16, 2016 at 6:20:27 PM UTC-7, ADK wrote:

Currently you can create extensions for the server context, web context
or both. However, there are 2 issues with extensions that require
components. First, the docs say this:

You can make components globally available by adding them to the folder
/components.

However, this is currently not functioning as the deploy.log clearly
shows when you try it:

Extension;not supported yet!;lucee.runtime.exp.ApplicationException: not

supported yet!

For server extensions, you can get around this by using the
/applications folder, but this does not work for web contexts.

This brings us to the second issue: it appears that Lucee has a default
{lucee-web} component mapping, but not a {lucee-server} mapping. Is there a
way to add this mapping automatically upon component installation?
Otherwise, the user would need to add the mapping manually.

Hi,
I had the same problem on a linux machine, and solved by opening the .lex
file and changing the case from Manifest.mf file to MANIFEST.MF like ADK
suggested.

Thank you!Em sexta-feira, 11 de novembro de 2016 17:49:09 UTC-2, ADK escreveu:

That is odd? Check your download, perhaps it’s corrupted?

I just checked and the manifest is definitely in the META_INF folder in
the Github repo (which has been untouched in ~4 months.)

I wonder if it is an issue with case sensitivity on Linux? I’ve only ever
tested it on Windows. The file is “Manifest.mf” lowercase in the archive.
You could try renaming it in the .lex (a LEX file is just a zip) and see if
that works, but that’s just a pot-shot guess…

On Friday, November 11, 2016 at 10:57:21 AM UTC-8, Jonathan Smith wrote:

Hi,

I must be missing something… I can’t for the life of me get
cfspreadsheet for lucee 5 to install. My windows workstation is running
Lucee 5.1.0.34, and I’m using the .lex from:
https://github.com/Leftbower/cfspreadsheet-lucee-5.

I’m dropping the .lex into: C:\lucee\tomcat\lucee-server\deploy

The error I get in C:\lucee\tomcat\lucee-server\context\logs\deploy.log
is:

“ERROR”,“Thread-225115”,“11/11/2016”,“13:51:06”,"","Extension;The
Extension [C:\lucee\tomcat\lucee-server\deploy\cfspreadsheet-lucee-5.lex]
is invalid,no Manifest file was found at
[META-INF/MANIFEST.MF].;lucee.runtime.exp.ApplicationException: The
Extension [C:\lucee\tomcat\lucee-server\deploy\cfspreadsheet-lucee-5.lex]
is invalid,no Manifest file was found at [META-INF/MANIFEST.MF].
at lucee.runtime.extension.RHExtension.(RHExtension.java:199)
at
lucee.runtime.config.XMLConfigAdmin.updateRHExtension(XMLConfigAdmin.java:4585)
at
lucee.runtime.config.XMLConfigAdmin._updateRHExtension(XMLConfigAdmin.java:4573)
at lucee.runtime.config.DeployHandler.deploy(DeployHandler.java:80)
at lucee.runtime.engine.Controler.control(Controler.java:203)
at lucee.runtime.engine.Controler.access$000(Controler.java:58)
at lucee.runtime.engine.Controler$ControlerThread.run(Controler.java:108)
"

On Sunday, 17 July 2016 05:38:39 UTC-4, ADK wrote:

OK, so I circumvented most of these issues by packaging the cfc
component, along with the appropriate mapping, in a .lar file in the
archives folder of the .lex. This allows it to auto-deploy in either server
or web context and auto-map the component.

Is this the “best-practice” or just a workaround until the /component
deployment is incorporated?

Also, the .lar files do not get removed on an uninstall, so that’s still
something that needs to be looked at…

I think I have ironed out most of auto-deploy issues, so if anyone wants
to test out deployment, the extension is here:

https://github.com/Leftbower/cfspreadsheet-lucee-5

On Saturday, July 16, 2016 at 6:20:27 PM UTC-7, ADK wrote:

Currently you can create extensions for the server context, web context
or both. However, there are 2 issues with extensions that require
components. First, the docs say this:

You can make components globally available by adding them to the folder
/components.

However, this is currently not functioning as the deploy.log clearly
shows when you try it:

Extension;not supported yet!;lucee.runtime.exp.ApplicationException:

not supported yet!

For server extensions, you can get around this by using the
/applications folder, but this does not work for web contexts.

This brings us to the second issue: it appears that Lucee has a default
{lucee-web} component mapping, but not a {lucee-server} mapping. Is there a
way to add this mapping automatically upon component installation?
Otherwise, the user would need to add the mapping manually.

I’ve updated the extension now to uppercase that filename:

https://github.com/Leftbower/cfspreadsheet-lucee-5/releases/tag/v3.0.2.0On Monday, December 5, 2016 at 9:40:09 AM UTC-8, Fábio Jr. wrote:

Hi,
I had the same problem on a linux machine, and solved by opening the .lex
file and changing the case from Manifest.mf file to MANIFEST.MF like ADK
suggested.

Thank you!

Em sexta-feira, 11 de novembro de 2016 17:49:09 UTC-2, ADK escreveu:

That is odd? Check your download, perhaps it’s corrupted?

I just checked and the manifest is definitely in the META_INF folder in
the Github repo (which has been untouched in ~4 months.)

I wonder if it is an issue with case sensitivity on Linux? I’ve only ever
tested it on Windows. The file is “Manifest.mf” lowercase in the archive.
You could try renaming it in the .lex (a LEX file is just a zip) and see if
that works, but that’s just a pot-shot guess…

On Friday, November 11, 2016 at 10:57:21 AM UTC-8, Jonathan Smith wrote:

Hi,

I must be missing something… I can’t for the life of me get
cfspreadsheet for lucee 5 to install. My windows workstation is running
Lucee 5.1.0.34, and I’m using the .lex from:
https://github.com/Leftbower/cfspreadsheet-lucee-5.

I’m dropping the .lex into: C:\lucee\tomcat\lucee-server\deploy

The error I get in C:\lucee\tomcat\lucee-server\context\logs\deploy.log
is:

“ERROR”,“Thread-225115”,“11/11/2016”,“13:51:06”,"","Extension;The
Extension [C:\lucee\tomcat\lucee-server\deploy\cfspreadsheet-lucee-5.lex]
is invalid,no Manifest file was found at
[META-INF/MANIFEST.MF].;lucee.runtime.exp.ApplicationException: The
Extension [C:\lucee\tomcat\lucee-server\deploy\cfspreadsheet-lucee-5.lex]
is invalid,no Manifest file was found at [META-INF/MANIFEST.MF].
at lucee.runtime.extension.RHExtension.(RHExtension.java:199)
at
lucee.runtime.config.XMLConfigAdmin.updateRHExtension(XMLConfigAdmin.java:4585)
at
lucee.runtime.config.XMLConfigAdmin._updateRHExtension(XMLConfigAdmin.java:4573)
at lucee.runtime.config.DeployHandler.deploy(DeployHandler.java:80)
at lucee.runtime.engine.Controler.control(Controler.java:203)
at lucee.runtime.engine.Controler.access$000(Controler.java:58)
at lucee.runtime.engine.Controler$ControlerThread.run(Controler.java:108)
"

On Sunday, 17 July 2016 05:38:39 UTC-4, ADK wrote:

OK, so I circumvented most of these issues by packaging the cfc
component, along with the appropriate mapping, in a .lar file in the
archives folder of the .lex. This allows it to auto-deploy in either server
or web context and auto-map the component.

Is this the “best-practice” or just a workaround until the /component
deployment is incorporated?

Also, the .lar files do not get removed on an uninstall, so that’s
still something that needs to be looked at…

I think I have ironed out most of auto-deploy issues, so if anyone
wants to test out deployment, the extension is here:

https://github.com/Leftbower/cfspreadsheet-lucee-5

On Saturday, July 16, 2016 at 6:20:27 PM UTC-7, ADK wrote:

Currently you can create extensions for the server context, web
context or both. However, there are 2 issues with extensions that require
components. First, the docs say this:

You can make components globally available by adding them to the
folder /components.

However, this is currently not functioning as the deploy.log clearly
shows when you try it:

Extension;not supported yet!;lucee.runtime.exp.ApplicationException:

not supported yet!

For server extensions, you can get around this by using the
/applications folder, but this does not work for web contexts.

This brings us to the second issue: it appears that Lucee has a
default {lucee-web} component mapping, but not a {lucee-server} mapping. Is
there a way to add this mapping automatically upon component installation?
Otherwise, the user would need to add the mapping manually.