>
> >... First question being, which JSON library do we support? As we settled on
> > johnzon, I assume thats the one...
>
> It looks like the Johnzon Mapper module [2] should support what I need
> but I haven't found real documentation about it so far. I'll have a
> look a might switch the graphql
This error is usually caused by an old version of ASM that is used for
writing the implementation of the bind/unbind methods of references if
such functions do not already exist.
This usually stems from the use of an old maven-scr-plugin, and
upgrading to a newer one will most usually fix this, or
On Sat, Jan 28, 2017 at 6:27 AM, lancedolan wrote:
> Hi friends,
>
> I've tried routing questions through stackoverflow to cut down my mails to
> this list. I'm losing lots of time on this one, though, and am stuck.
>
> I need to create APIs which don't represent Sling Resources. Example:
> /servi
>Follow the configurations I am using:
>
>R6
>
>*@Component(service=Servlet.class,*
>
>*property = { *
>
>* "sling.servlet.methods=GET",*
>
>* "sling.servlet.paths=/system/mypath1",*
>
>* "sling.servlet.paths=/system/mypath2",*
>
>* },*
>
>*immediate=true*
>
>*)*
>
>
>Am I missing som
On Mon, Nov 28, 2016 at 9:30 PM, Jörg Hoh wrote:
> Hi,
>
> please add the "@Service" annotation as well.
@Service does not exist in the R6 annotations, instead, it's the
service attribute on @Component
(which was specified in the pasted code)
>
> 2016-11-28 13:17 GMT+01:00 Júnior :
>
>> Hi S
On Mon, Nov 28, 2016 at 8:19 PM, Júnior wrote:
> Hi,
>
> I'm trying to register a servlet using the OSGI r6 annotations but It is
> not working.
>
> Follow the configurations I am using:
>
> R6
>
> *@Component(service=Servlet.class,*
>
> *property = { *
>
> * "sling.servlet.methods=GET",*
>
>
On Fri, Oct 28, 2016 at 11:55 PM, Christoph Thodte
wrote:
> Hello!
>
> What is the best and fast way to create a lot of resources in Sling? I import
> 200.000 data rows in jcr. My importer is very fast for the 30.000 nodes than
> it will be very slow down. I commit my resourceresolver ervery 100
A) Sling expects the mixin types to passed as their raw String values
and not as the JCR NameValue type.
The fact that the JCR NameValue type is being utilized instead is
causing the error you are seeing as the Sling functionality converted
it to a String (incorrectly) causing it to become invalid
This is the namespace mangling feature in the Sling Resource Resolver
Factory configuration:
Namespace Mangling
Defines whether namespace prefixes of resource names inside the path
(e.g. "jcr:" in "/home/path/jcr:content") are mangled or not. Mangling
means that any namespace prefix contained in
wen wrote:
> Ok, it would be handy to have an estimate on the approximate amount / levels
> of resources when to go for iterating vs querying :).
>
> Greets
> Roy
>> On 16 Jun 2016, at 16:06, Steven Walters wrote:
>>
>> if you know there are that few resources, then
ity as they
are.
On Thu, Jun 16, 2016 at 10:43 PM, Carsten Ziegeler wrote:
> Jason E Bailey wrote
>> Which api proposal is that?
>>
>
> https://issues.apache.org/jira/browse/SLING-4752
>
> Carsten
>
>> --
>> Jason
>>
>>
>>
>> On
if you know there are that few resources, then I say iterating would be
better performing than XPath / JCR-SQL2 queries.
This is primarily from past experience speaking in that queries have
generally turned out (often MUCH) slower than directly iterating if you
know what you're actually looking for
The other providers sling manages in its codebase don't appear to get much
TLC, such as that they're all still using the older deprecated
ResourceProvider system, instead of the new one (which the JCR
ResourceProvider does use).
Also, it appears that a number of the sling components/functionalitie
In the end, this primarily depends on the behavior of the underlying
ResourceProviders that funnel into the ResourceResolver.
For instance, if the ResourceProvider(s) support MVCC, then the data
available when the ResourceResolver was opened will be "stuck" to the
moment in time it was opened at,
On Mon, Dec 21, 2015 at 10:30 AM, Stefan Seifert wrote:
>
>>I know. But I don't want to deploy the Sling mocks library as a bundle
>>along with my Sling-based application to the OSGI container (haven't
>>checked if it's a bundle at all). I also don't want to embedd this jar file
>>into a custom bu
Jörg,
On Mon, Dec 21, 2015 at 9:10 AM, Jörg Hoh wrote:
>
> Hi Bertrand
>
> 2015-12-21 13:56 GMT+01:00 Bertrand Delacretaz :
>
> >
> > Would the Sling mocks MockSlingHttpServletRequest and response work
> > for you? Or shall we maybe refactor them to inherit from new non-Sling
> > HttpServletReque
On Thu, Oct 29, 2015 at 2:27 AM, Carsten Ziegeler wrote:
>
> Sure, enhancements are always welcome.
Opened a JIRA Ticket on this: SLING-5335
And opened a Github PR for implementing it:
https://github.com/apache/sling/pull/115
Thanks,
Steven
On Tue, Nov 24, 2015 at 5:18 PM, Roll, Kevin wrote:
>
> I have implemented a job as described here:
>
> https://sling.apache.org/documentation/bundles/apache-sling-eventing-and-job-handling.html
>
> @Component(immediate = true)
> @Service(value = JobConsumer.class)
> @Property(name = JobConsumer.P
Yes, this was a surprise to find that the plugin for/by Sling would
ignore basic Sling provided functionalities, in this scenario always
utilizing/assuming functionality of Felix instead.
Would the developers/maintainers be open to an enhancement to the
plugin to support this scenario?
On Wed, Oc
I'm trying to use the sling-maven-plugin install as described at [0].
I'm now encountering a scenario where I can not use the goal to
install a bundle in a particularly desired way.
Previously, this was being used successfully within the environment to
place the bundles under the /apps/install fol
On Wed, Oct 7, 2015 at 2:46 PM, Roll, Kevin wrote:
> I am trying to upload a PNG file to the repository, using the
> SlingPostServlet. The problem I am encountering is that the field
> jcr:mimeType on the automatically created node ends up being "image/x-png",
> which is causing me a lot of troub
On Mon, Sep 21, 2015 at 1:26 PM, Carsten Ziegeler
wrote:
> Unfortunately, the OSGi installer does not support this use case, and
> the same goes with the web console from Apache Felix.
>
> Actually, this feature has been requested several times, but so far we
> never did anything. I think the eas
On Mon, Sep 21, 2015 at 12:05 PM, Jason Bailey wrote:
> I'm a bit confused by the use case.
>
> Breakage should only occur if the bundle is exporting an API that is
> versioned, and you have a bundle that is explicitly set to not accept the
> new package version.
>
> Or is the breakage somewhere
Is it possible to control the JcrInstaller behavior (which utilizes the
OsgiInstaller functionality) to indicate whether a bundle should be
considered a "new install" rather than an "update"?
e.g.
upload guava-17.0.jar to /apps/a/install/guava-17.0.jar
This creates a new bundle registered within F
I was working with the SlingPostServlet operation :import with the XML (not
the JCR XML) format and came across the code that is implicated in
SLING-2512.
This basically renders the entire nt:file import functionality completely
blocked from utilization when going through the SlingPostServlet, as
25 matches
Mail list logo