You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Joshua Oransky <ca...@gmail.com> on 2008/09/29 23:08:17 UTC
Trying to upload a package in CRX from dev to test... getting error
I create and download a package fine on my dev machine. I upload the
zip to the main test in CRX and I get:
javax.jcr.RepositoryException: Unable to import node.: no matching
property definition found for {http://sling.apache.org/jcr/sling/
1.0}resourceSuperType: Unable to import node.: no matching property
definition found for {http://sling.apache.org/jcr/sling/
1.0}resourceSuperType
at
com
.day
.jcr
.vault
.fs.imprt.GenericArtifactHandler.accept(GenericArtifactHandler.java:75)
Any ideas?
-Josh
Re: Trying to upload a package in CRX from dev to test... getting error
Posted by Joshua Oransky <ca...@gmail.com>.
Ok, I tried the instructions on http://dev.day.com/microsling/content/blogs/main/updatecrxqs.html
However, it doesn't seem to work. I still get the
sling:resourceSuperType not found error when uploading my apps.
My version of CRX does not have the bundle Sling - Jackrabbit Embedded
Repository and the bundle that gets built per the instructions is the
Sling - Repo Accessor anyway...
Am I missing something? Can I just package up the
sling:resourceSuperType mixin?
On Sep 29, 2008, at 11:25 PM, Tobias Bocanegra wrote:
> hi josh,
> make sure you installed all recent sling bundles on your target crx.
> it seems that some node have a wrong nodetype.
>
> regards, toby
>
> On 9/29/08, Joshua Oransky <ca...@gmail.com> wrote:
>> I create and download a package fine on my dev machine. I upload
>> the zip to
>> the main test in CRX and I get:
>>
>> javax.jcr.RepositoryException: Unable to import node.: no matching
>> property
>> definition found for
>> {http://sling.apache.org/jcr/sling/1.0}resourceSuperType:
>> Unable to import node.: no matching property definition found for
>> {http://sling.apache.org/jcr/sling/1.0}resourceSuperType
>> at
>> com
>> .day
>> .jcr
>> .vault
>> .fs.imprt.GenericArtifactHandler.accept(GenericArtifactHandler.java:
>> 75)
>>
>> Any ideas?
>>
>> -Josh
>>
Re: Trying to upload a package in CRX from dev to test... getting error
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, Sep 30, 2008 at 10:09 AM, Carsten Ziegeler <cz...@apache.org> wrote:
> ...I think we should do a full release (like last time) and target it for
> the end of october. Given that this takes approx two weeks to get it
> out, we should think about doing the release around the 20th of October....
+1 to a full release and to the timeframe.
-Bertrand
Re: Trying to upload a package in CRX from dev to test... getting
error
Posted by Carsten Ziegeler <cz...@apache.org>.
Jukka Zitting wrote:
> Hi,
>
> On Tue, Sep 30, 2008 at 8:52 AM, Bertrand Delacretaz
> <bd...@apache.org> wrote:
>> Note that [1] explains how to update crx with the latest bleeding edge
>> Sling stuff.
>
> On that note, should we make another Sling release?
>
Yes :)
I think we should do a full release (like last time) and target it for
the end of october. Given that this takes approx two weeks to get it
out, we should think about doing the release around the 20th of October.
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: Trying to upload a package in CRX from dev to test... getting error
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Tue, Sep 30, 2008 at 8:52 AM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> Note that [1] explains how to update crx with the latest bleeding edge
> Sling stuff.
On that note, should we make another Sling release?
BR,
Jukka Zitting
Re: Trying to upload a package in CRX from dev to test... getting error
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Tue, Sep 30, 2008 at 8:25 AM, Tobias Bocanegra
<to...@day.com> wrote:
> ...make sure you installed all recent sling bundles on your target crx.
> it seems that some node have a wrong nodetype....
Note that [1] explains how to update crx with the latest bleeding edge
Sling stuff.
-Bertrand
[1] http://dev.day.com/microsling/content/blogs/main/updatecrxqs.html
Re: Trying to upload a package in CRX from dev to test... getting
error
Posted by Felix Meschberger <fm...@gmail.com>.
Hi,
Another option might be to configure WebDAV in Sling such, that for
collection resources, sling:Folder nodes are created instead of
nt:folder nodes.
Regards
Felix
Joshua Oransky schrieb:
> Ok, I know what the issue is... by default, when creating a folder with
> webDAV, they are created as nt:folder.
>
> I needed to use the sling:resourceSuperType mixin so that I can have
> inheritance on my templates. This works on the system you are developing
> on fine. However, if you try to package it up, you run into the
> aforementioned issue when you upload the package on another system.
>
> The solution is very specific, but there is no easy way (I can see) that
> anyone would have found this out. You need to make sure your folders are
> of the type sling:Folder, NOT nt:folder. Which means you can not create
> them using webDAV; you need to use the Content Explorer. They will
> package and deploy on other systems just fine.
>
> -Josh
>
> On Sep 29, 2008, at 11:25 PM, Tobias Bocanegra wrote:
>
>> hi josh,
>> make sure you installed all recent sling bundles on your target crx.
>> it seems that some node have a wrong nodetype.
>>
>> regards, toby
>>
>> On 9/29/08, Joshua Oransky <ca...@gmail.com> wrote:
>>> I create and download a package fine on my dev machine. I upload the
>>> zip to
>>> the main test in CRX and I get:
>>>
>>> javax.jcr.RepositoryException: Unable to import node.: no matching
>>> property
>>> definition found for
>>> {http://sling.apache.org/jcr/sling/1.0}resourceSuperType:
>>> Unable to import node.: no matching property definition found for
>>> {http://sling.apache.org/jcr/sling/1.0}resourceSuperType
>>> at
>>> com.day.jcr.vault.fs.imprt.GenericArtifactHandler.accept(GenericArtifactHandler.java:75)
>>>
>>>
>>> Any ideas?
>>>
>>> -Josh
>>>
>
>
Re: Trying to upload a package in CRX from dev to test... getting error
Posted by Joshua Oransky <ca...@gmail.com>.
Ok, I know what the issue is... by default, when creating a folder
with webDAV, they are created as nt:folder.
I needed to use the sling:resourceSuperType mixin so that I can have
inheritance on my templates. This works on the system you are
developing on fine. However, if you try to package it up, you run into
the aforementioned issue when you upload the package on another system.
The solution is very specific, but there is no easy way (I can see)
that anyone would have found this out. You need to make sure your
folders are of the type sling:Folder, NOT nt:folder. Which means you
can not create them using webDAV; you need to use the Content
Explorer. They will package and deploy on other systems just fine.
-Josh
On Sep 29, 2008, at 11:25 PM, Tobias Bocanegra wrote:
> hi josh,
> make sure you installed all recent sling bundles on your target crx.
> it seems that some node have a wrong nodetype.
>
> regards, toby
>
> On 9/29/08, Joshua Oransky <ca...@gmail.com> wrote:
>> I create and download a package fine on my dev machine. I upload
>> the zip to
>> the main test in CRX and I get:
>>
>> javax.jcr.RepositoryException: Unable to import node.: no matching
>> property
>> definition found for
>> {http://sling.apache.org/jcr/sling/1.0}resourceSuperType:
>> Unable to import node.: no matching property definition found for
>> {http://sling.apache.org/jcr/sling/1.0}resourceSuperType
>> at
>> com
>> .day
>> .jcr
>> .vault
>> .fs.imprt.GenericArtifactHandler.accept(GenericArtifactHandler.java:
>> 75)
>>
>> Any ideas?
>>
>> -Josh
>>
Re: Trying to upload a package in CRX from dev to test... getting error
Posted by Tobias Bocanegra <to...@day.com>.
hi josh,
make sure you installed all recent sling bundles on your target crx.
it seems that some node have a wrong nodetype.
regards, toby
On 9/29/08, Joshua Oransky <ca...@gmail.com> wrote:
> I create and download a package fine on my dev machine. I upload the zip to
> the main test in CRX and I get:
>
> javax.jcr.RepositoryException: Unable to import node.: no matching property
> definition found for
> {http://sling.apache.org/jcr/sling/1.0}resourceSuperType:
> Unable to import node.: no matching property definition found for
> {http://sling.apache.org/jcr/sling/1.0}resourceSuperType
> at
> com.day.jcr.vault.fs.imprt.GenericArtifactHandler.accept(GenericArtifactHandler.java:75)
>
> Any ideas?
>
> -Josh
>