Judging from the error messages, the bundles cannot be resolved because of
the missing package of
package=org.osgi.service.framework)(version>=1.0.0)(!(version>=2.0.0)). I
had a quick look at the bundle lists. The bundle
org.apache.aries.util-0.3-SNAPSHOT and
org.apache.aries.blueprint-0.3-SNA
xico; (918)560-3500 in
> Oklahoma; or (972)766-6900 in Texas.
>
>
>
Hi Matt,
I recall you reported the hang problem a few days. Are you still
experiencing the hang problem even though you use pax exam 1.2.3 suggested
by Toni?
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
and inserted
>>>> 1.2.3 after _every_ pax-exam artifact. This seems to do
>>>> it.
>>>>
>>>> Here is a subsection of the pom:
>>>>
>>>>
>>>> org.ops4j.pax.exam
>>>> pax-exam-junit-e
I am out of the office until 07/03/2011.
For urgent Aries queries, please contact my manager Andy Gatford (Andrew K
Gatford/UK/IBM)
MentorPlace programme, please contact Hannah Ramlee (Jasmin H
Ramlee/UK/IBM)
Hursley Chinese Connect, please contact Jenny He (Jenny He/UK/IBM).
Thanks
Emily
No
che.aries.application.resolver.obr not,
> why? org.apache.aries.application.resolver.obr should be xported also
>
> org.apache.aries.application.resolver.obr.ext;
>
> --
>
The package
> viola
>
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
ies.blueprint.container.Parser.populate(Parser.java:277)
>
> at
> org.apache.aries.blueprint.container.ParserServiceImpl.validateAndPop
> ulate(ParserServiceImpl.java:83)
> at
> org.apache.aries.blueprint.container.ParserServiceImpl.parse(ParserSe
> rviceImpl.java:70)
> at
> org.apache.aries.blueprint.container.ParserServiceImpl.parse(ParserSe
>
>
>
>
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
po.
>How do I do that?
>
> Thanks
> Matt
>
> On Wed, Aug 17, 2011 at 11:55 AM, Emily Jiang wrote:
>
>> Hi Matt,
>> I think you have hit a defect. This is caused due to the absence of the
>> Transaction namespace handler bundle. Please raise a jira and I wil
plus, you don't need to create a jira any more as I have done so.
On Wed, Aug 17, 2011 at 11:51 PM, Emily Jiang wrote:
> You need to sign up with JIRA in order to raise a bug.
>
> For more information on JIRA, see: http://www.atlassian.com/software/jira
> For creating Ari
Thu, Aug 18, 2011 at 2:00 AM, Matt Madhavan wrote:
> Cool! Thx Emily
> On Aug 17, 2011 5:53 PM, "Emily Jiang" wrote:
> > plus, you don't need to create a jira any more as I have done so.
> >
> > On Wed, Aug 17, 2011 at 11:51 PM, Emily Jiang >wrote:
> >
xception=org/apache/aries/blueprint/utils/HeaderParser] for bundle
> ch.eugster.herakles.datasource.derby
> [org.apache.aries.blueprint.container.BlueprintExtender] : Scanning bundle
> org.easymock for blueprint application
> [org.apache.aries.blueprint.container.BlueprintEventDispatcher] : Sending
> blueprint container event BlueprintEvent[type=FAILURE,
> exception=org/apache/aries/blueprint/utils/HeaderParser] for bundle
> org.easymock
> [org.apache.aries.blueprint.container.BlueprintExtender] : Scanning bundle
> org.apache.aries.proxy for blueprint application
> [org.apache.aries.blueprint.container.BlueprintEventDispatcher] : Sending
> blueprint container event BlueprintEvent[type=FAILURE,
> exception=org/apache/aries/blueprint/utils/HeaderParser] for bundle
> org.apache.aries.proxy
>
>
> --
> Anatoly Osiko
> Software Engineer, Integration
> SolveIT Software Pty Ltd
>
> Adelaide | Brisbane | Chisinau | Melbourne | Perth
>
> D: +61 8 7071 4918
> T: +61 8 8221 5533
> M: +61 4 1980 0386
> F: +61 8 8221 5677
>
> SolveIT Software Building
> Level 1, 99 Frome Street,
> Adelaide, SA 5000
> www.SolveITSoftware.com
>
>
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
5:${asmVersion}
>
>
>
> On 18/10/2012 8:22 PM, Emily Jiang wrote:
>
> I think Aries 1.0.0 comes with asm 4.0.
>
> On Thu, Oct 18, 2012 at 8:43 AM, Anatoly Osiko
> wrote:
>
>> aries 1.0.0 comes with asm-all-3.2.jar, that what I have for my
>> ru
>>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
>>> at
>>> org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
>>> at
>>> org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
>>> at
>>>
>>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
>>> at
>>>
>>> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582
>>> )
>>>
>>> Reading the code I see that Aries JNDI wants to determine
>>> what bundle the JNDI call is coming from.
>>> How can I solve this?
>>>
>>> Thanks
>>> Mike Wilson
>>>
>>> Mike Wilson wrote:
>>> > We are using Aries JNDI inside Karaf, which is in turn
>>> > embedded within an existing application. We need to use
>>> > JNDI also from the wrapping application, whose classes
>>> > are not handled by OSGI.
>>> >
>>> > How is this best set up?
>>> > - application JNDI calls are handled by Aries JNDI
>>> > implementation
>>> > - or, somehow make OSGI bundles have their JNDI calls
>>> > directed to a static implementation outside the
>>> > OSGI container
>>> > - or, something else?
>>> >
>>> > Thanks
>>> > Mike Wilson
>>>
>>>
>>
>
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
rent versions of same bundle.
>
> ** **
>
> Regards,
>
> Jay Rajani
>
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
ache.aries.blueprint.container.BeanRecipe$UnwrapperedBeanHolder@10867a57when
> instanciating bean extBean
> >
> > The problem seems to be the tx:transaction decoration on simpleBean.
> When I leave this away, I can start the bundle.
> >
> > Is this a bug or intended behaviour?
> >
> >
> > Daniel
>
> --
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
>> IIUIC this also helps setting the appropriate import version ranges when
>> using the bundle plugin.
>>
>
> It does introduce an additional compile-time dependency though. Isn't that
> a little awkward?
>
> Cheers,
>
> David
>
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
info definitely supports version, not sure it supports
> @Export but this one is rarely used if you ask me and packageinfo could be
> easily extended to support that one as well...
>
> Cheers,
>
> David
>
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
rabs the version you want it
> compared to.
>
>
> --
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
;>>
>>>>
>>>> I don't see how having extensions is related to scopes and lifecycle.
>>>> Supporting extensions is a must-have in CDI. What you implied is that
>>>> because you want to support extensions, we can't use custom scopes. I
>>>> think I was the one to suggest using generic capabilities to support
>>>> extension in the RFC years ago.
>>>>
>>>> And to answer your other email, I do not pretend to have a really good
>>>> knowledge of CDI (really, I don't). I may be missing things in using custom
>>>> scopes, but I'd like to understand what exactly, if any.
>>>>
>>>>
>>>>>
>>>>> Does that make sense?
>>>>> - Ray
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> But this is just my opinion,
>>>>>>> - Ray
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Nov 23, 2016 at 11:38 AM, Christian Schneider <
>>>>>>> ch...@die-schneider.net> wrote:
>>>>>>>
>>>>>>>> I think it would be great if Guillaume and Ray could work on the
>>>>>>>> impl together. Ray could then feed the experiences back into the RFC.
>>>>>>>> In any case I would support having Ray as an aries committer.
>>>>>>>>
>>>>>>>> Christian
>>>>>>>>
>>>>>>>> On 23.11.2016 17:30, David Bosschaert wrote:
>>>>>>>>
>>>>>>>>> Hi Guillaume,
>>>>>>>>>
>>>>>>>>> My understanding is that the technical design of the RFC will be
>>>>>>>>> significantly changed to better support the OSGi dynamics - hopefully
>>>>>>>>> we'll
>>>>>>>>> see an update soon at https://github.com/osgi/des
>>>>>>>>> ign/tree/master/rfcs/rfc0193
>>>>>>>>>
>>>>>>>>> If I understand things correctly then Ray's CDI implementation
>>>>>>>>> will support the improved design.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>>
>>>>>>>>> David
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Christian Schneider
>>>>>>>> http://www.liquid-reality.de
>>>>>>>>
>>>>>>>> Open Source Architect
>>>>>>>> http://www.talend.com
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>>>>>>> (@rotty3000)
>>>>>>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com/>
>>>>>>> (@Liferay)
>>>>>>> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org/>
>>>>>>> (@OSGiAlliance)
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Guillaume Nodet
>>>>>>
>>>>>> Red Hat, Open Source Integration
>>>>>>
>>>>>> Email: gno...@redhat.com
>>>>>> Web: http://fusesource.com
>>>>>> Blog: http://gnodet.blogspot.com/
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>>>>> (@rotty3000)
>>>>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com/>
>>>>> (@Liferay)
>>>>> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org/>
>>>>> (@OSGiAlliance)
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Guillaume Nodet
>>>>
>>>> Red Hat, Open Source Integration
>>>>
>>>> Email: gno...@redhat.com
>>>> Web: http://fusesource.com
>>>> Blog: http://gnodet.blogspot.com/
>>>>
>>>>
>>>
>>>
>>> --
>>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>>> (@rotty3000)
>>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com/>
>>> (@Liferay)
>>> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org/>
>>> (@OSGiAlliance)
>>>
>>
>>
>>
>> --
>>
>> Guillaume Nodet
>>
>> Red Hat, Open Source Integration
>>
>> Email: gno...@redhat.com
>> Web: http://fusesource.com
>> Blog: http://gnodet.blogspot.com/
>>
>>
>>
>
>
> --
>
> Guillaume Nodet
>
> Red Hat, Open Source Integration
>
> Email: gno...@redhat.com
> Web: http://fusesource.com
> Blog: http://gnodet.blogspot.com/
>
>
--
Thanks
Emily
=
Emily Jiang
eji...@apache.org
18 matches
Mail list logo