You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by Karl Kildén <an...@apache.org> on 2013/10/10 13:24:19 UTC
CMS diff: OpenWebBeans SPI
Clone URL (Committers only):
https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openwebbeans.apache.org/openwebbeans-spi.mdtext
Karl Kildén
Index: trunk/content/openwebbeans-spi.mdtext
===================================================================
--- trunk/content/openwebbeans-spi.mdtext (revision 1530832)
+++ trunk/content/openwebbeans-spi.mdtext (working copy)
@@ -18,5 +18,55 @@
# OpenWebBeans SPI
-Coming soon...
+###What is an SPI?
+> Service Provider Interface (SPI) is an API intended to be implemented
+> or extended by a third party. It can be used to enable framework
+> extension and replaceable components.
+- [wikipedia][1]
+
+
+###How does the SPI functionality work in OpenWebBeans?
+First off reading about [OpenWebBeans Core](openwebbeans-impl.html) will give you the overall idea. Now as mentioned in that description the SPI is
+simply used to integrate other frameworks with OpenWebBeans. The point of gravity for Java EE is definitely going
+towards CDI today and the SPI pattern ensures that OpenWebBeans can manage this handily.
+
+From a more technical standpoint it's nothing more then a bunch of interfaces. For example a part of the SPI is the following interface:
+
+
+ package org.apache.webbeans.spi;
+
+ /**
+ * Conversation related SPI.
+ * @version $Rev$ $Date$
+ */
+ public interface ConversationService
+ {
+ /**
+ * Gets the current conversation id or null
+ * if there is no conversation.
+ * @return the current conversation id
+ */
+ public String getConversationId();
+
+ /**
+ * Gets the session id of the current session.
+ * @return the session id of the current user session
+ */
+ public String getConversationSessionId();
+
+ }
+
+
+After seeing this interface one can easily conclude that frameworks that want to utilize the Conversation Id functionality must implement this interface.
+Now since this is part of the specification for JSF 2.x the JSF plugin of course implements it and actually the JSF 1.2 plugin as well. Supporting the Conversation Id in another plugin should be rather intuitive and this is true for the SPI in general.
+
+
+
+
+
+
+
+
+
+ [1]: http://en.wikipedia.org/wiki/Service_provider_interface
\ No newline at end of file
Re: CMS diff: OpenWebBeans SPI
Posted by Karl Kildén <ka...@gmail.com>.
Hello Mark! You can apply it. Of course it might need polishing / reworking
I've been busy at work because we got a new coworker and at home.... time
get's short sometimes ;)
But I will try to get two new pages or so done this week
On 16 October 2013 11:01, Mark Struberg <st...@yahoo.de> wrote:
>
>
> Hi Karl!
>
> I'm now back again from a conference. Doest this still need to be applied?
>
> Or do you have a newer version?
>
>
> LieGrue,
> strub
>
>
>
>
>
> >________________________________
> > From: Karl Kildén <an...@apache.org>
> >To: dev@openwebbeans.apache.org
> >Sent: Thursday, 10 October 2013, 13:24
> >Subject: CMS diff: OpenWebBeans SPI
> >
> >
> >Clone URL (Committers only):
> >
> https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openwebbeans.apache.org/openwebbeans-spi.mdtext
> >
> >Karl Kildén
> >
> >Index: trunk/content/openwebbeans-spi.mdtext
> >===================================================================
> >--- trunk/content/openwebbeans-spi.mdtext (revision 1530832)
> >+++ trunk/content/openwebbeans-spi.mdtext (working copy)
> >@@ -18,5 +18,55 @@
> >
> ># OpenWebBeans SPI
> >
> >-Coming soon...
> >+###What is an SPI?
> >
> >+> Service Provider Interface (SPI) is an API intended to be implemented
> >+> or extended by a third party. It can be used to enable framework
> >+> extension and replaceable components.
> >+- [wikipedia][1]
> >+
> >+
> >+###How does the SPI functionality work in OpenWebBeans?
> >+First off reading about [OpenWebBeans Core](openwebbeans-impl.html) will
> give you the overall idea. Now as mentioned in that description the SPI is
> >+simply used to integrate other frameworks with OpenWebBeans. The point
> of gravity for Java EE is definitely going
> >+towards CDI today and the SPI pattern ensures that OpenWebBeans can
> manage this handily.
> >+
> >+From a more technical standpoint it's nothing more then a bunch of
> interfaces. For example a part of the SPI is the following interface:
> >+
> >+
> >+ package org.apache.webbeans.spi;
> >+
> >+ /**
> >+ * Conversation related SPI.
> >+ * @version $Rev$ $Date$
> >+ */
> >+ public interface ConversationService
> >+ {
> >+ /**
> >+ * Gets the current conversation id or null
> >+ * if there is no conversation.
> >+ * @return the current conversation id
> >+ */
> >+ public String getConversationId();
> >+
> >+ /**
> >+ * Gets the session id of the current session.
> >+ * @return the session id of the current user session
> >+ */
> >+ public String getConversationSessionId();
> >+
> >+ }
> >+
> >+
> >+After seeing this interface one can easily conclude that frameworks that
> want to utilize the Conversation Id functionality must implement this
> interface.
> >+Now since this is part of the specification for JSF 2.x the JSF plugin
> of course implements it and actually the JSF 1.2 plugin as well. Supporting
> the Conversation Id in another plugin should be rather intuitive and this
> is true for the SPI in general.
> >+
> >+
> >+
> >+
> >+
> >+
> >+
> >+
> >+
> >+ [1]: http://en.wikipedia.org/wiki/Service_provider_interface
> >\ No newline at end of file
> >
> >
> >
> >
>
Re: CMS diff: OpenWebBeans SPI
Posted by Mark Struberg <st...@yahoo.de>.
Hi Karl!
I'm now back again from a conference. Doest this still need to be applied?
Or do you have a newer version?
LieGrue,
strub
>________________________________
> From: Karl Kildén <an...@apache.org>
>To: dev@openwebbeans.apache.org
>Sent: Thursday, 10 October 2013, 13:24
>Subject: CMS diff: OpenWebBeans SPI
>
>
>Clone URL (Committers only):
>https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openwebbeans.apache.org/openwebbeans-spi.mdtext
>
>Karl Kildén
>
>Index: trunk/content/openwebbeans-spi.mdtext
>===================================================================
>--- trunk/content/openwebbeans-spi.mdtext (revision 1530832)
>+++ trunk/content/openwebbeans-spi.mdtext (working copy)
>@@ -18,5 +18,55 @@
>
># OpenWebBeans SPI
>
>-Coming soon...
>+###What is an SPI?
>
>+> Service Provider Interface (SPI) is an API intended to be implemented
>+> or extended by a third party. It can be used to enable framework
>+> extension and replaceable components.
>+- [wikipedia][1]
>+
>+
>+###How does the SPI functionality work in OpenWebBeans?
>+First off reading about [OpenWebBeans Core](openwebbeans-impl.html) will give you the overall idea. Now as mentioned in that description the SPI is
>+simply used to integrate other frameworks with OpenWebBeans. The point of gravity for Java EE is definitely going
>+towards CDI today and the SPI pattern ensures that OpenWebBeans can manage this handily.
>+
>+From a more technical standpoint it's nothing more then a bunch of interfaces. For example a part of the SPI is the following interface:
>+
>+
>+ package org.apache.webbeans.spi;
>+
>+ /**
>+ * Conversation related SPI.
>+ * @version $Rev$ $Date$
>+ */
>+ public interface ConversationService
>+ {
>+ /**
>+ * Gets the current conversation id or null
>+ * if there is no conversation.
>+ * @return the current conversation id
>+ */
>+ public String getConversationId();
>+
>+ /**
>+ * Gets the session id of the current session.
>+ * @return the session id of the current user session
>+ */
>+ public String getConversationSessionId();
>+
>+ }
>+
>+
>+After seeing this interface one can easily conclude that frameworks that want to utilize the Conversation Id functionality must implement this interface.
>+Now since this is part of the specification for JSF 2.x the JSF plugin of course implements it and actually the JSF 1.2 plugin as well. Supporting the Conversation Id in another plugin should be rather intuitive and this is true for the SPI in general.
>+
>+
>+
>+
>+
>+
>+
>+
>+
>+ [1]: http://en.wikipedia.org/wiki/Service_provider_interface
>\ No newline at end of file
>
>
>
>