[Lucee] ThoughtWorks Technology Radar Mai 2015 - OSGI again on hold

fyi


“… Projects that rely on OSGi to define a component system quickly realize that it solves only a small part of the overall problem, and often adds its own accidental complexity to projects such as more complex builds. Most projects now either use old-fashioned JAR files or microservice architectures to manage components, and await the native solution in Java in the Jigsaw module specification. …”

Maybe the Lucee team could share their opinion about this statement, especially in the light of the new Lucee 5 OSGI implementation?

Thanks,
Harry

Small addition. For me personally this question is similar to the question:
Do I needs repository like git?
Once you started using a repo you see what you missed before. when we
started the OSGi implementation so many thing fallen into place and maked
finally sense, also the core handling functionality that was custom made
before and now is also OSGi based.

MichaAm Donnerstag, 7. Mai 2015 schrieb Michael Offner :

A major shortcoming of the Java language is that there is no support of
versioning of jar files, you cannot unload or update jars at runtime. OSGi
jumped in and filled this gap, there is not only one implementation of
it, no there is a couple.
Osgi is the standard of jar management in Lucee and essential to any
enterprise environment in Java.

Why is OSGi essential for Lucee?
We always had troubles in Lucee (and Railo) to update/unload extension
because Lucee had limited control over jars, you had for example always to
restart the engine that extension with jars take effect, on windows you
could not even touch jars because they are locked by the system (you
personally know that problem). That has limit the possibilities with
extensions trasticly. With Lucee 5 extension are completely rewritten and
get a much bigger role, we have moved out a lot of functionality from the
core to extensions, you can now load/update for example the hibernate
extension with a single click in the admin and use it right away. In the
future we will even support that you can do this in your code, for example
in the application.cfc, all this would not be possible without OSGi.

If you use a library in a different version than Lucee does in your custom
code you are lost without OSGi, this is s discussion coming up in our
mailing list all the time and clients approached us about this all the
time.

So for a enterprise environment OSGi is essential!

Micha

Am Mittwoch, 6. Mai 2015 schrieb Harry Klein :

fyi

http://www.thoughtworks.com/radar/platforms/osgi

“… Projects that rely on OSGi to define a component system quickly
realize that it solves only a small part of the overall problem, and often
adds its own accidental complexity to projects such as more complex builds.
Most projects now either use old-fashioned JAR files or microservice
architectures to manage components, and await the native solution in Java
in the Jigsaw module specification. …”

Maybe the Lucee team could share their opinion about this statement,
especially in the light of the new Lucee 5 OSGI implementation?

Thanks,

Harry


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.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/F5A941E045A6FE4288ABB2E3D797146FA73A1C54%40SRV-DC1.contens.local
https://groups.google.com/d/msgid/lucee/F5A941E045A6FE4288ABB2E3D797146FA73A1C54%40SRV-DC1.contens.local?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

A major shortcoming of the Java language is that there is no support of
versioning of jar files, you cannot unload or update jars at runtime. OSGi
jumped in and filled this gap, there is not only one implementation of
it, no there is a couple.
Osgi is the standard of jar management in Lucee and essential to any
enterprise environment in Java.

Why is OSGi essential for Lucee?
We always had troubles in Lucee (and Railo) to update/unload extension
because Lucee had limited control over jars, you had for example always to
restart the engine that extension with jars take effect, on windows you
could not even touch jars because they are locked by the system (you
personally know that problem). That has limit the possibilities with
extensions trasticly. With Lucee 5 extension are completely rewritten and
get a much bigger role, we have moved out a lot of functionality from the
core to extensions, you can now load/update for example the hibernate
extension with a single click in the admin and use it right away. In the
future we will even support that you can do this in your code, for example
in the application.cfc, all this would not be possible without OSGi.

If you use a library in a different version than Lucee does in your custom
code you are lost without OSGi, this is s discussion coming up in our
mailing list all the time and clients approached us about this all the
time.

So for a enterprise environment OSGi is essential!

MichaAm Mittwoch, 6. Mai 2015 schrieb Harry Klein :

fyi

http://www.thoughtworks.com/radar/platforms/osgi

“… Projects that rely on OSGi to define a component system quickly realize
that it solves only a small part of the overall problem, and often adds its
own accidental complexity to projects such as more complex builds. Most
projects now either use old-fashioned JAR files or microservice
architectures to manage components, and await the native solution in Java
in the Jigsaw module specification. …”

Maybe the Lucee team could share their opinion about this statement,
especially in the light of the new Lucee 5 OSGI implementation?

Thanks,

Harry


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
<javascript:_e(%7B%7D,‘cvml’,‘lucee%2Bunsubscribe@googlegroups.com’);>.
To post to this group, send email to lucee@googlegroups.com
<javascript:_e(%7B%7D,‘cvml’,‘lucee@googlegroups.com’);>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/F5A941E045A6FE4288ABB2E3D797146FA73A1C54%40SRV-DC1.contens.local
https://groups.google.com/d/msgid/lucee/F5A941E045A6FE4288ABB2E3D797146FA73A1C54%40SRV-DC1.contens.local?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.