[
https://issues.apache.org/jira/browse/ARIES-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847362#comment-13847362
]
Richard Ellis commented on ARIES-1140:
--
No problem Andrei. I now understand that
[
https://issues.apache.org/jira/browse/ARIES-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847315#comment-13847315
]
Richard Ellis commented on ARIES-1140:
--
There are two different proxies in play
[
https://issues.apache.org/jira/browse/ARIES-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846504#comment-13846504
]
Richard Ellis commented on ARIES-1140:
--
Does the generated inter
[
https://issues.apache.org/jira/browse/ARIES-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406966#comment-13406966
]
Richard Ellis commented on ARIES-868:
-
As per the OSGi core spec WeavingHooks add
[
https://issues.apache.org/jira/browse/ARIES-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398267#comment-13398267
]
Richard Ellis commented on ARIES-706:
-
The function from ARIES-786 (for sy
15:47, schrieb Richard Ellis:
> I believe that this problem is limited to the subclass proxy and not the
> newer improved WeavingHook based proxy. So for cases where people want
to
> use both a very recent JVM and a class that does not have an accessible
> zero-arg constructor there is the
I believe that this problem is limited to the subclass proxy and not the
newer improved WeavingHook based proxy. So for cases where people want to
use both a very recent JVM and a class that does not have an accessible
zero-arg constructor there is the option to move up to use proxy 0.4 and
an
I also like the sound of this change it would be a nice customization to
have.
Rich
From: Timothy Ward
To:
Date: 06/02/2012 17:26
Subject:RE: Customising the behaviour of the weaving proxy
implementation
Sent by:
Hi,
I like the principle behind this change, and
Hi Guillaume,
There are 3 kinds of proxy support currently available in the proxy
bundle. They are used in this order, falling back to the next level if the
conditions are not met:
1. Weaving proxy (if OSGi level is 4.3 i.e. WeavingHooks are supported and
ASM is available) - can proxy just abou
[
https://issues.apache.org/jira/browse/ARIES-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Ellis updated ARIES-775:
Attachment: Aries-775-Test.txt
Aries-775.txt
Patch to get the super constructors
[
https://issues.apache.org/jira/browse/ARIES-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144221#comment-13144221
]
Richard Ellis commented on ARIES-775:
-
This appears to be a problem where a c
[
https://issues.apache.org/jira/browse/ARIES-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Ellis updated ARIES-770:
Attachment: Aries-770-patch.txt
Patch to append using an LDAP syntax OR group instead of
Issue Type: Bug
Components: Application
Affects Versions: 0.3
Reporter: Richard Ellis
The CompositeServiceFilter-Import header represents an OSGi service filter and
therefore needs to use LDAP syntax. The code in the
BundleFrameworkConfigurationFactoryImpl loops through
[
https://issues.apache.org/jira/browse/ARIES-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Ellis updated ARIES-769:
Attachment: Aries-769-patch.txt
Patch that checks the equality of the BundleContext class of the
: JNDI
Affects Versions: 0.3
Reporter: Richard Ellis
I was trying to perform a JNDI lookup from a WAB inside an EBA and I hit this
problem.
java.lang.ClassCastException:
org.eclipse.osgi.internal.serviceregistry.ServiceReferenceImpl incompatible
with
[
https://issues.apache.org/jira/browse/ARIES-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Ellis updated ARIES-762:
Attachment: Aries-762-patch.txt
Trivial patch to add activation="lazy" to the bundle
Versions: 0.3, 0.4
Reporter: Richard Ellis
The bundle-framework-management.xml does not mark the
equinox-bundle-framework-manager lazy, so the shared bundle frameworks are
created too early. This intermittently prevents customized services from
registering ahead of the aries defaults
[
https://issues.apache.org/jira/browse/ARIES-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Ellis updated ARIES-760:
Attachment: Aries-760-patch.txt
Patch that resolves the issue by only setting the default Import
: Application
Affects Versions: 0.3, 0.4
Reporter: Richard Ellis
It is possible to register a BundleFrameworkConfigurationFactory that will be
used by the SharedBundleFramework to obtain a BundleFrameworkConfiguration
object which is wrapped by the
[
https://issues.apache.org/jira/browse/ARIES-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Ellis updated ARIES-669:
Attachment: SyntheticModifier.txt
I've attached another patch SyntheticModifier.txt which
[
https://issues.apache.org/jira/browse/ARIES-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Ellis updated ARIES-669:
Attachment: static_init_patch.txt
A patch to avoid using the StaticInitMerger code, allowing us to
As Tim mentioned
in his comment on Aries-669 we will try to implement a solution avoiding
any ASM source.
Rich
From:
David Jencks
To:
dev@aries.apache.org
Date:
06/06/2011 21:57
Subject:
Re: Yet another proxy/weaving problem
On Jun 6, 2011, at 5:30 AM, Richard Ellis wrote:
> David
David,
I don't think it is easy to mark the WovenProxy class as synthetic because
it is a real interface with source in the org.apache.aries.proxy.weaving
package. AFAIK there is no way to mark an interface as synthetic only on
the implementing class, but not on the interface class itself. It i
[
https://issues.apache.org/jira/browse/ARIES-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044815#comment-13044815
]
Richard Ellis commented on ARIES-669:
-
David,
Firstly, I think it would be helpfu
I'm sorry if I wasn't clear in making my point, which I believe has now
been clarified by Tim. It was in fact that the specific Aries proxy
methods under discussion were marked final for a reason other than
performance and that reason was so that they could not be overridden.
Rich
From:
Timo
I'm not going to comment on whether final methods perform better or not,
but the other reason the methods are marked final is to stop people
overriding them when they shouldn't. There is no reason for another proxy
(or anything outside of Aries) to override the methods added by the Aries
proxy.
[
https://issues.apache.org/jira/browse/ARIES-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019900#comment-13019900
]
Richard Ellis commented on ARIES-633:
-
I think it is worth pointing out as well
27 matches
Mail list logo
