Re: [Heads up] Aries JPA 2.6.0 release in two days

[Timothy Ward]

I looked only into the issues that have fix version 2.6.0.

Surely as the project area lead you should be looking at the issues that have 
affects version 2.6.0 and setting the fix version appropriately?

If you intend to implement any of these issues for 2.6.0 then please set the 
fix version. This allows me to see if a release is complete feature wise.

These issues were assigned to you, as requested, when they were created as part 
of preparing Aries JPA to be the reference implementation for the next version 
of the OSGi Spec.

Btw. I just found that we got a big issue with Aries JPA and Karaf 4.1.0. It 
seems that at least Aries JPA 2.5.0 and hibernate 5 features do not work 
together as both
jpa 2.0 and 2.1 apis are installed.

This is why we need to start using the JavaJPA contract so that this sort of 
thing works better!

Tim

On 21 Feb 2017, at 16:02, Christian Schneider 
> wrote:

I looked only into the issues that have fix version 2.6.0.
If you intend to implement any of these issues for 2.6.0 then please set the 
fix version. This allows me to see if a release is complete feature wise.

We should only pick the low hanging fruits for this release though as at least 
Giuseppe is waiting for the fix of the threading issue.

Btw. I just found that we got a big issue with Aries JPA and Karaf 4.1.0. It 
seems that at least Aries JPA 2.5.0 and hibernate 5 features do not work 
together as both
jpa 2.0 and 2.1 apis are installed.

Christian

On 21.02.2017 16:50, Timothy Ward wrote:
Hi Christian,

I see a lot more than one issue left, and several of them are easy to fix.

https://issues.apache.org/jira/browse/ARIES-1642
https://issues.apache.org/jira/browse/ARIES-1670
https://issues.apache.org/jira/browse/ARIES-1671
https://issues.apache.org/jira/browse/ARIES-1672


I can understand if you choose not to release a fix for 1671 until the OSGi JPA 
Service 1.1 specification is final, but I think that the others should be fixed 
for 2.7.

Tim

On 21 Feb 2017, at 11:19, Christian Schneider 
> wrote:

We did some bug fixes and improvements in providing the correct capapbilities.
Especially because of the threading issue found by Giuseppe I would like to do 
a release quite soon.

See here for the full list of issues fixed:

https://issues.apache.org/jira/browse/ARIES/fixforversion/12338632

There is one open issue left:
https://issues.apache.org/jira/browse/ARIES-1674
but I think we can move it to 2.7.0 if I can not get a fix in until the release.

Christian

--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com





--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

Re: [Heads up] Aries JPA 2.6.0 release in two days

[Christian Schneider]

I looked only into the issues that have fix version 2.6.0.
If you intend to implement any of these issues for 2.6.0 then please set 
the fix version. This allows me to see if a release is complete feature 
wise.


We should only pick the low hanging fruits for this release though as at 
least Giuseppe is waiting for the fix of the threading issue.


Btw. I just found that we got a big issue with Aries JPA and Karaf 
4.1.0. It seems that at least Aries JPA 2.5.0 and hibernate 5 features 
do not work together as both

jpa 2.0 and 2.1 apis are installed.

Christian

On 21.02.2017 16:50, Timothy Ward wrote:

Hi Christian,

I see a lot more than one issue left, and several of them are easy to fix.

https://issues.apache.org/jira/browse/ARIES-1642
https://issues.apache.org/jira/browse/ARIES-1670
https://issues.apache.org/jira/browse/ARIES-1671
https://issues.apache.org/jira/browse/ARIES-1672


I can understand if you choose not to release a fix for 1671 until the OSGi JPA 
Service 1.1 specification is final, but I think that the others should be fixed 
for 2.7.

Tim

On 21 Feb 2017, at 11:19, Christian Schneider 
> wrote:

We did some bug fixes and improvements in providing the correct capapbilities.
Especially because of the threading issue found by Giuseppe I would like to do 
a release quite soon.

See here for the full list of issues fixed:

https://issues.apache.org/jira/browse/ARIES/fixforversion/12338632

There is one open issue left:
https://issues.apache.org/jira/browse/ARIES-1674
but I think we can move it to 2.7.0 if I can not get a fix in until the release.

Christian

--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com






--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

[jira] [Closed] (ARIES-1648) Aries JPA does not advertise EntityManagerFactoryBuilder or EntityManagerFactory services

[Timothy Ward (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARIES-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Ward closed ARIES-1648.
---

> Aries JPA does not advertise EntityManagerFactoryBuilder or 
> EntityManagerFactory services
> -
>
> Key: ARIES-1648
> URL: https://issues.apache.org/jira/browse/ARIES-1648
> Project: Aries
>  Issue Type: Bug
>  Components: JPA
>Affects Versions: jpa-2.5.0
>Reporter: Timothy Ward
>Assignee: Christian Schneider
> Fix For: jpa-2.6.0
>
>
> The Aries JPA container provides an extender for persistence bundles. This 
> extender results in the registration of EntityManagerFactory and/or 
> EntityManagerFactoryBuilder services. These services are then used by clients 
> to make use of JPA.
> The problem is that there are no capabilities advertising this feature. 
> Ideally there would be a Provide-Capability added automatically to every 
> persistence bundle, but this is true for few, if any, persistence bundles, 
> and also most persistence bundles do not make use of the org.osgi.service.jpa 
> package, making the uses constraint impossible to apply.
> Therefore the Provide Capability header should go on the Aries JPA container:
> Provide-Capability: 
> osgi.service;objectClass=javax.persistence.EntityManagerFactory;effective:=active;uses:=javax.persistence,osgi.service;objectClass=org.osgi.service.jpa.EntityManagerFactoryBuilder;effective:=active";uses:=org.osgi.service.jpa



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [Heads up] Aries JPA 2.6.0 release in two days

[Timothy Ward]

Hi Christian,

I see a lot more than one issue left, and several of them are easy to fix.

https://issues.apache.org/jira/browse/ARIES-1642
https://issues.apache.org/jira/browse/ARIES-1670
https://issues.apache.org/jira/browse/ARIES-1671
https://issues.apache.org/jira/browse/ARIES-1672


I can understand if you choose not to release a fix for 1671 until the OSGi JPA 
Service 1.1 specification is final, but I think that the others should be fixed 
for 2.7.

Tim

On 21 Feb 2017, at 11:19, Christian Schneider 
> wrote:

We did some bug fixes and improvements in providing the correct capapbilities.
Especially because of the threading issue found by Giuseppe I would like to do 
a release quite soon.

See here for the full list of issues fixed:

https://issues.apache.org/jira/browse/ARIES/fixforversion/12338632

There is one open issue left:
https://issues.apache.org/jira/browse/ARIES-1674
but I think we can move it to 2.7.0 if I can not get a fix in until the release.

Christian

--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

Re: [VOTE] Release Apache Aries Remote Service Admin 1.10.0

[Christian Schneider]

I just got in an issue for this release: 
https://issues.apache.org/jira/browse/ARIES-1693


It is not a blocker but as we do not yet have votes I take the chance to 
cancel the release and try to fix this.

I will do another build tomorrow.

Christian

On 20.02.2017 16:06, Christian Schneider wrote:

Highlights:

- Streams and async calls for fastbin
- Capabilities and requirements from the rsa spec 1.1


I've staged the release at

https://repository.apache.org/content/repositories/orgapachearies-1098

For a list of issues resolved see:

https://issues.apache.org/jira/browse/ARIES/fixforversion/12338250


Release Notes - Aries - Version rsa-1.10.0

** Bug
* [ARIES-1623] - FilterHelper OBJECTCLASS_EXPRESSION excludes 
inner classes

* [ARIES-1632] - fastbin does not throw an error for unknown services

** Improvement
* [ARIES-1595] - Support capabilities and requirements specified 
in RSA 1.1


** New Feature
* [ARIES-1586] - Async calls in fastbin
* [ARIES-1587] - Support streams in fastbin


Please review and vote

Here is my
+1

Christian






--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

[jira] [Created] (ARIES-1693) ClassloaderObjectInputStream can not load InputStreamProxy class

[Christian Schneider (JIRA)]

Christian Schneider created ARIES-1693:
--

 Summary: ClassloaderObjectInputStream can not load 
InputStreamProxy class
 Key: ARIES-1693
 URL: https://issues.apache.org/jira/browse/ARIES-1693
 Project: Aries
  Issue Type: Bug
  Components: Remote Service Admin
Affects Versions: rsa-1.10.0
Reporter: Christian Schneider
Assignee: Christian Schneider


This was reported by Nick Baker over E-Mail.

The problem seems to be that the ClassLoaderObjectInputStream only looks into 
the user bundle classloader. This will fail when loading the InputStreamProxy.

This code should make sure the class can be loaded:
https://github.com/apache/aries-rsa/commit/09771c940422a3f83d3779d6d8b482959605f95a
but apparently it uses the wrong classloader.

This should work:
return Class.forName(className, false, getClass().getClassLoader());





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1674) Multiple inharitance levels with generics cause ClassCastException when JPA is enabled

[Felix Wassmer (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15875912#comment-15875912
 ] 

Felix Wassmer commented on ARIES-1674:
--

I didn't try to compile that example on linux, so there was some relative path 
issue,
which is now fixed. (successfully compiles on linux)

So please try again.

If it somehow still doesn't work for you, I can paste the stacktraces.

> Multiple inharitance levels with generics cause ClassCastException when JPA 
> is enabled
> --
>
> Key: ARIES-1674
> URL: https://issues.apache.org/jira/browse/ARIES-1674
> Project: Aries
>  Issue Type: Bug
>  Components: JPA
>Affects Versions: jpa-2.5.0
> Environment: Win 7 x64, JDK 1.8.0_73, Karaf 4.0.4
>Reporter: Felix Wassmer
>Assignee: Christian Schneider
> Fix For: jpa-2.6.0
>
>
> I'm using inheritance with generics over multiple levels.
> Injecting properties to those beans works fine, but on access of a property 
> of the lowest class, there is a ClassCastException thrown.
> I could narrow it down to enabling JPA in the blueprint causing the issue:
> When disabling JPA, the proper bean class is resolved,
> enabled the type resolving stopped at the parent abstract class of the 
> expected class, thus throwing a ClassCastException.
> Example project to reproduce this issue:
> https://github.com/fwassmer/inheritance



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1674) Multiple inharitance levels with generics cause ClassCastException when JPA is enabled

[Christian Schneider (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15875862#comment-15875862
 ] 

Christian Schneider commented on ARIES-1674:


I was not able to build your project. I got this exception:
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install) 
on project features: Failed to install artifact 
org.broken:features:xml:datasource:1.0-SNAPSHOT: 
/home/cschneider/checkout/inheritance/features/src/main/java/../resources/datasource-h2.xml
 (No such file or directory) -> [Help 1]

Can you give some more information about the ClassCastException you see?

> Multiple inharitance levels with generics cause ClassCastException when JPA 
> is enabled
> --
>
> Key: ARIES-1674
> URL: https://issues.apache.org/jira/browse/ARIES-1674
> Project: Aries
>  Issue Type: Bug
>  Components: JPA
>Affects Versions: jpa-2.5.0
> Environment: Win 7 x64, JDK 1.8.0_73, Karaf 4.0.4
>Reporter: Felix Wassmer
>Assignee: Christian Schneider
> Fix For: jpa-2.6.0
>
>
> I'm using inheritance with generics over multiple levels.
> Injecting properties to those beans works fine, but on access of a property 
> of the lowest class, there is a ClassCastException thrown.
> I could narrow it down to enabling JPA in the blueprint causing the issue:
> When disabling JPA, the proper bean class is resolved,
> enabled the type resolving stopped at the parent abstract class of the 
> expected class, thus throwing a ClassCastException.
> Example project to reproduce this issue:
> https://github.com/fwassmer/inheritance



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[Heads up] Aries JPA 2.6.0 release in two days

[Christian Schneider]

We did some bug fixes and improvements in providing the correct 
capapbilities.
Especially because of the threading issue found by Giuseppe I would like 
to do a release quite soon.


See here for the full list of issues fixed:

https://issues.apache.org/jira/browse/ARIES/fixforversion/12338632

There is one open issue left:
https://issues.apache.org/jira/browse/ARIES-1674
but I think we can move it to 2.7.0 if I can not get a fix in until the 
release.


Christian

--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

[jira] [Commented] (ARIES-1689) JpaInterceptor is not thread safe

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15875730#comment-15875730
 ] 

ASF subversion and git services commented on ARIES-1689:


Commit 1783861 from [~ch...@die-schneider.net] in branch 'aries/trunk'
[ https://svn.apache.org/r1783861 ]

[ARIES-1689] Improve performance

> JpaInterceptor is not thread safe
> -
>
> Key: ARIES-1689
> URL: https://issues.apache.org/jira/browse/ARIES-1689
> Project: Aries
>  Issue Type: Bug
>  Components: JPA
>Affects Versions: jpa-2.4.0, jpa-2.5.0
>Reporter: Giuseppe Gerla
>Assignee: Giuseppe Gerla
> Fix For: jpa-2.6.0
>
>
> If two thread try to access to JpaInterceptor could happen that first thread 
> set the value of coordinator but not yet the em. The second one found the 
> coordinator setted and try to access to em.
> NullPointerException is raised



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)