You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Ioannis Canellos (JIRA)" <ji...@apache.org> on 2010/11/23 19:43:15 UTC

[jira] Created: (KARAF-293) Feature for Aries Transaction,JPA & JNDI modules.

Feature for Aries Transaction,JPA & JNDI modules.
-------------------------------------------------

                 Key: KARAF-293
                 URL: https://issues.apache.org/jira/browse/KARAF-293
             Project: Karaf
          Issue Type: New Feature
            Reporter: Ioannis Canellos


I think that Karaf should provide features for Aries Transaction, JPA and JNDI modules.
I think that these features should not be part of the default distribution, but the feature files should be maintained inside karaf.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (KARAF-293) Feature for Aries Transaction,JPA & JNDI modules.

Posted by "Ioannis Canellos (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ioannis Canellos reassigned KARAF-293:
--------------------------------------

    Assignee: Ioannis Canellos

> Feature for Aries Transaction,JPA & JNDI modules.
> -------------------------------------------------
>
>                 Key: KARAF-293
>                 URL: https://issues.apache.org/jira/browse/KARAF-293
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>
> I think that Karaf should provide features for Aries Transaction, JPA and JNDI modules.
> I think that these features should not be part of the default distribution, but the feature files should be maintained inside karaf.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (KARAF-293) Feature for Aries Transaction,JPA & JNDI modules.

Posted by "Ioannis Canellos (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ioannis Canellos resolved KARAF-293.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.0

> Feature for Aries Transaction,JPA & JNDI modules.
> -------------------------------------------------
>
>                 Key: KARAF-293
>                 URL: https://issues.apache.org/jira/browse/KARAF-293
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>             Fix For: 2.2.0
>
>
> I think that Karaf should provide features for Aries Transaction, JPA and JNDI modules.
> I think that these features should not be part of the default distribution, but the feature files should be maintained inside karaf.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (KARAF-293) Feature for Aries Transaction,JPA & JNDI modules.

Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935231#action_12935231 ] 

Jean-Baptiste Onofré commented on KARAF-293:
--------------------------------------------

ServiceMix NMR already provide feature for Aries transaction:

    <feature name="transaction" version="${aries.transaction.version}">
        <bundle>mvn:org.apache.aries.transaction/org.apache.aries.transaction.manager/${aries.transaction.version}</bundle>
    </feature>

I think that Karaf should be a container. ServiceMix could be the OSGI-EE server by providing features for JPA, JNDI, etc, etc.

> Feature for Aries Transaction,JPA & JNDI modules.
> -------------------------------------------------
>
>                 Key: KARAF-293
>                 URL: https://issues.apache.org/jira/browse/KARAF-293
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: Ioannis Canellos
>
> I think that Karaf should provide features for Aries Transaction, JPA and JNDI modules.
> I think that these features should not be part of the default distribution, but the feature files should be maintained inside karaf.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] [Closed] (KARAF-293) Feature for Aries Transaction,JPA & JNDI modules.

Posted by "Jamie goodyear (Closed) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jamie goodyear closed KARAF-293.
--------------------------------

    
> Feature for Aries Transaction,JPA & JNDI modules.
> -------------------------------------------------
>
>                 Key: KARAF-293
>                 URL: https://issues.apache.org/jira/browse/KARAF-293
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>             Fix For: 2.2.0
>
>
> I think that Karaf should provide features for Aries Transaction, JPA and JNDI modules.
> I think that these features should not be part of the default distribution, but the feature files should be maintained inside karaf.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (KARAF-293) Feature for Aries Transaction,JPA & JNDI modules.

Posted by "Ioannis Canellos (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935237#action_12935237 ] 

Ioannis Canellos commented on KARAF-293:
----------------------------------------

The idea is NOT to make Karaf an OSGI-EE. 
However, features like JPA and JNDI should be easy to install in Karaf (not necessarily as part of the default distro). 



 

> Feature for Aries Transaction,JPA & JNDI modules.
> -------------------------------------------------
>
>                 Key: KARAF-293
>                 URL: https://issues.apache.org/jira/browse/KARAF-293
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: Ioannis Canellos
>
> I think that Karaf should provide features for Aries Transaction, JPA and JNDI modules.
> I think that these features should not be part of the default distribution, but the feature files should be maintained inside karaf.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (KARAF-293) Feature for Aries Transaction,JPA & JNDI modules.

Posted by "Achim Nierbeck (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935505#action_12935505 ] 

Achim Nierbeck commented on KARAF-293:
--------------------------------------

OK, forget about the OSGi-EE then :)
Nevertheless I think a "Fat" distro with all available Features preInstalled could be of benefit. 
Right now at work I am doing this basically by my self, pre-Installing almost all Features, 
like webconsole, war, spring, spring-dm and blueprint. And also adding some more missed features, 
like the spring-aop and spring-web stuff and also some really needed apache commons dependencies. 


> Feature for Aries Transaction,JPA & JNDI modules.
> -------------------------------------------------
>
>                 Key: KARAF-293
>                 URL: https://issues.apache.org/jira/browse/KARAF-293
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: Ioannis Canellos
>
> I think that Karaf should provide features for Aries Transaction, JPA and JNDI modules.
> I think that these features should not be part of the default distribution, but the feature files should be maintained inside karaf.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (KARAF-293) Feature for Aries Transaction,JPA & JNDI modules.

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935522#action_12935522 ] 

Guillaume Nodet commented on KARAF-293:
---------------------------------------

I think this could be debated.  OSGi-EE is not JEE.  Geronimo is a JEE server, but there's no OSGi-EE server at Apache.
ServiceMix is an ESB, so the goal is slightly different from being an OSGi-EE server imho, for example, Camel has no place in a pure OSGi-EE server, while it would be central to an OSGi-EE server.   Aries provides most of the OSGi EE components but does not aim at providing a runtime.
So I'd be in favor to at least make all OSGi-EE components easy to install.

As for building the fat distro, I still think we should work on the features maven plugin to help creating very easily a karaf distribution with a few features to be installed.
Currently, one has to unpack the whole distrib and use the assembly plugin, but it could be way easier to do (there's a JIRA about that).

> Feature for Aries Transaction,JPA & JNDI modules.
> -------------------------------------------------
>
>                 Key: KARAF-293
>                 URL: https://issues.apache.org/jira/browse/KARAF-293
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: Ioannis Canellos
>
> I think that Karaf should provide features for Aries Transaction, JPA and JNDI modules.
> I think that these features should not be part of the default distribution, but the feature files should be maintained inside karaf.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Issue Comment Edited: (KARAF-293) Feature for Aries Transaction,JPA & JNDI modules.

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935522#action_12935522 ] 

Guillaume Nodet edited comment on KARAF-293 at 11/24/10 6:28 PM:
-----------------------------------------------------------------

I think this could be debated.  OSGi-EE is not JEE.  Geronimo is a JEE server, but there's no OSGi-EE server at Apache.
ServiceMix is an ESB, so the goal is slightly different from being an OSGi-EE server imho, for example, Camel has no place in a pure OSGi-EE server, while it would be central in ServiceMix as an ESB.   Aries provides most of the OSGi EE components but does not aim at providing a runtime.
So I'd be in favor to at least make all OSGi-EE components easy to install.

As for building the fat distro, I still think we should work on the features maven plugin to help creating very easily a karaf distribution with a few features to be installed.
Currently, one has to unpack the whole distrib and use the assembly plugin, but it could be way easier to do (there's a JIRA about that).

      was (Author: gnt):
    I think this could be debated.  OSGi-EE is not JEE.  Geronimo is a JEE server, but there's no OSGi-EE server at Apache.
ServiceMix is an ESB, so the goal is slightly different from being an OSGi-EE server imho, for example, Camel has no place in a pure OSGi-EE server, while it would be central to an OSGi-EE server.   Aries provides most of the OSGi EE components but does not aim at providing a runtime.
So I'd be in favor to at least make all OSGi-EE components easy to install.

As for building the fat distro, I still think we should work on the features maven plugin to help creating very easily a karaf distribution with a few features to be installed.
Currently, one has to unpack the whole distrib and use the assembly plugin, but it could be way easier to do (there's a JIRA about that).
  
> Feature for Aries Transaction,JPA & JNDI modules.
> -------------------------------------------------
>
>                 Key: KARAF-293
>                 URL: https://issues.apache.org/jira/browse/KARAF-293
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: Ioannis Canellos
>
> I think that Karaf should provide features for Aries Transaction, JPA and JNDI modules.
> I think that these features should not be part of the default distribution, but the feature files should be maintained inside karaf.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (KARAF-293) Feature for Aries Transaction,JPA & JNDI modules.

Posted by "Achim Nierbeck (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935086#action_12935086 ] 

Achim Nierbeck commented on KARAF-293:
--------------------------------------

Maybe we should also provide an additional Karaf Full distribution where all optional features are preinstalled. 
A minimal is already provided.
This way it looks more like a OSGi-EE Server :)


> Feature for Aries Transaction,JPA & JNDI modules.
> -------------------------------------------------
>
>                 Key: KARAF-293
>                 URL: https://issues.apache.org/jira/browse/KARAF-293
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: Ioannis Canellos
>
> I think that Karaf should provide features for Aries Transaction, JPA and JNDI modules.
> I think that these features should not be part of the default distribution, but the feature files should be maintained inside karaf.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.