My earlier claims of success were overly optimistic. Just getting
everything to load into osgi was one hurdle, but getting jaxb running is a
completely different story.
With the configuration mentioned below,
g! lb | grep -i jax
65|Active | 30|jaxb-api (2.2.11)
66|Active |
Forgot to mention, I did try the JAXB version 2.1.0 that Steffan
recommended.
This rippled through my application code and got to the point where it
would no longer build with a versions so old of some of the dependencies.
I wasn’t able to locate version 2.1.0 for all components either.
Is
hello bruce.
this can become tricky. my recommendation was to do not deploy any JAXB bundle,
but to use the version embedded in the JDK and make sure the system bundle
exports its packages as well. additionally JAXB is not fully OSGi-compatible
concerning class loading, so some additional
Hi,
I have a ResourceResolver.getResource call which I would like to replace
with a sling:include / .
What I currently have
Resource configResource =
resolver.getResource(my/component/config.js.jsp);
cq:include script=%=configResource.getPath()% /
What I
Ok. Thanks for clarifying. I could setup OsgiConfig nodes manually as well
but in any case, the setting done via console would override.
On Mon, Feb 2, 2015 at 7:16 PM, Bertrand Delacretaz bdelacre...@apache.org
wrote:
On Mon, Feb 2, 2015 at 2:39 PM, connuser1 connuser1 connus...@gmail.com
currently the nosql-generic part does not even compile... I plan to work it on
the next day at least to have a running proof-of-concept, but cannot give a
precise promise when it will be ready.
stefan
-Original Message-
From: connuser1 connuser1 [mailto:connus...@gmail.com]
Sent:
Thanks Stefan for sharing this. I was going through the nosql generic part.
Though I haven't gone into much detail yet but I'll check how to use it
with dynamodb. Any idea if and when it could be a part of sling?
On Mon, Feb 2, 2015 at 7:24 PM, Stefan Seifert sseif...@pro-vision.de
wrote:
Hi Julian,
On Wed, Feb 4, 2015 at 1:51 PM, Julian Sedding jsedd...@gmail.com wrote:
Hi Robert
You could always do the following:
sling:include path=%= resource.getPath() %.config.js
resourceType=my/component/
That works, thank you!
Robert
Regards
Julian
On Wed, Feb 4, 2015
Hi Robert
You could always do the following:
sling:include path=%= resource.getPath() %.config.js
resourceType=my/component/
Regards
Julian
On Wed, Feb 4, 2015 at 12:47 PM, Robert Munteanu romb...@apache.org wrote:
Hi,
I have a ResourceResolver.getResource call which I would like
