currently uploaded files are handled like 'normal' fields and their
value is read via the MultipartPostParameter's getString(). the result
is that the properties get the string content of the uploaded files. i
think this is not what people want.
i suggest to implement a default behaviour that
Hi Toby,
This is actually two problems, probably: (1) absolute resource types are
not currently supported correctly and (2) the DefaultHtmlRender.render
should certainly not NPE.
Could you please create JIRA's to not forget about it. Thanks.
Regards
Felix
Am Dienstag, den 15.01.2008, 22:45
NPE in DefaultHtmlRenderer if resource type not found via include
-
Key: SLING-162
URL: https://issues.apache.org/jira/browse/SLING-162
Project: Sling
Issue Type: Bug
Absolute resource types do no resolve
-
Key: SLING-163
URL: https://issues.apache.org/jira/browse/SLING-163
Project: Sling
Issue Type: Bug
Components: Resource
Reporter: Tobias
ok:
SLING-162 NPE in DefaultHtmlRenderer if resource type not found via include
SLING-163 Absolute resource types do no resolve
On 1/16/08, Felix Meschberger [EMAIL PROTECTED] wrote:
Hi Toby,
This is actually two problems, probably: (1) absolute resource types are
not currently supported
Thanks. Regards
Felix
Am Mittwoch, den 16.01.2008, 09:46 +0100 schrieb Tobias Bocanegra:
ok:
SLING-162 NPE in DefaultHtmlRenderer if resource type not found via include
SLING-163 Absolute resource types do no resolve
On 1/16/08, Felix Meschberger [EMAIL PROTECTED] wrote:
Hi Toby,
Hi all,
Jackrabbbit 1.4 has been released, so I suggest we upgrade all
references to Jackrabbit to version 1.4.
WDYT ?
Regards
Felix
Why not make this the default behaviour, without using the magic
trailing slash:
right.
And we could use the @TypeHint if we want to store the file data in a
binary property, i .e:
form action=/home/tripod/profile method=post
enctype=multipart/form-data
input type=file name=./portrait
On Jan 16, 2008 10:15 AM, Tobias Bocanegra [EMAIL PROTECTED] wrote:
... input type=hidden name=./portrait/@TypeHint value=jcr:Property/
... or:
input type=hidden name=./[EMAIL PROTECTED] value=BINARY/
avoiding potential collision with node types. jcr:Property is more
likely to be a node
Jackrabbbit 1.4 has been released, so I suggest we upgrade all
references to Jackrabbit to version 1.4.
WDYT ?
+1
--
- [EMAIL PROTECTED] ---
Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97
... input type=hidden name=./[EMAIL PROTECTED] value=nt:resource/
would create just the resource node, right?..
Not sure what you mean by create just the resource node, can you clarify?
i might be desirable not to have the nt:file node at all, and just the
nt:resource node. eg:
+ home
+
On Jan 16, 2008 10:27 AM, Tobias Bocanegra [EMAIL PROTECTED] wrote:
...i might be desirable not to have the nt:file node at all, and just the
nt:resource node
Ok, got it, agreed.
-Bertrand
On Jan 16, 2008 9:51 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...I suggest we upgrade all
references to Jackrabbit to version 1.4
+1
-Bertrand
JcrResourceResolver.adaptTo(ObjectContentManager.class) returns (in most cases)
null
Key: SLING-164
URL: https://issues.apache.org/jira/browse/SLING-164
Project:
[
https://issues.apache.org/jira/browse/SLING-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-157.
-
Resolution: Fixed
Resolved in Rev. 612405 (with minor fix in 612407) by wrapping the
JavaScript: Support dynamic scopes
--
Key: SLING-165
URL: https://issues.apache.org/jira/browse/SLING-165
Project: Sling
Issue Type: Improvement
Components: Scripting
Reporter: Felix
[
https://issues.apache.org/jira/browse/SLING-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-165.
---
Resolution: Fixed
Fixed in Rev. 612408 by adding a Rhino ContextFactory which enables the
Felix Meschberger wrote:
As promised, I created a prototype of this concept. The main noteworthy
points of this prototype are:
* OCM has been split into a separate bundle, support is available
through a registered AdapterFactory
Nice :)
* New osgi/commons bundle providing helper
[
https://issues.apache.org/jira/browse/SLING-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-166:
Component/s: Scripting
JavaScript: Enable request processing limitation
Hi,
Am Mittwoch, den 16.01.2008, 11:22 +0100 schrieb Carsten Ziegeler:
* New osgi/commons bundle providing helper functionality and the
AdapterManager
While I like the design of Adaptable, the manager etc., I'm not sure if
an osgi-commons is the place to have the impl. especially
[
https://issues.apache.org/jira/browse/SLING-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz reopened SLING-157:
---
Assignee: (was: Felix Meschberger)
Reopening as I don't think the fix includes
[
https://issues.apache.org/jira/browse/SLING-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-164.
--
Resolution: Fixed
This issue has been fixed some minutes ago.
Default JSON rendering with selectable depth
Key: SLING-167
URL: https://issues.apache.org/jira/browse/SLING-167
Project: Sling
Issue Type: Improvement
Components: JSON
Felix Meschberger wrote:
Agreed. I could imagine to move the AdapterFactory and AdapterManager
interfaces to the Sling API, which would also somewhat illustrate more
about the underlying concept.
Ok.
Still, I cannot decide where to put the AdapterManagerImpl and the
SlingAdaptle classes
another idea:
if the parent node is a nt:folder, create a nt:file. otherwise create
an nt:resource.
further should the /* suffix use the local filename as hint for
creating the new node.
if the file is not specified in the upload, the node must not be deleted.
btw: in the current ujax servlet,
[
https://issues.apache.org/jira/browse/SLING-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-150.
---
Resolution: Fixed
Initial build of a WebDAV bundle committed. This just works out of the box.
Hi all,
I added a WebDAV bundle (jcr/webdav) which adds functionality to Sling
to expose a repository over WebDAV. By default, the bundle exposes the
repository under /dav, which of course is configurable through Config
Admin.
At the moment, the bundle also requires the HTTP Client bundle. I am
Update jackrabbit references to 1.4
---
Key: SLING-169
URL: https://issues.apache.org/jira/browse/SLING-169
Project: Sling
Issue Type: Improvement
Components: Core
Affects Versions: 2.0.0
[
https://issues.apache.org/jira/browse/SLING-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padraic Hannon updated SLING-169:
-
Attachment: sling-jackrabbit-1.4.patch
Here is a patch to upgrade pom and readme files.
Update
hi,
i attached a patch of the first version for the fileupload for ujax
post servlet to [0].
i also added some tests.
regards, toby
[0] https://issues.apache.org/jira/browse/SLING-168
--
- [EMAIL PROTECTED] ---
Tobias Bocanegra, Day Management AG,
Hi Paddy,
Am Mittwoch, den 16.01.2008, 09:25 -0800 schrieb Padraic Hannon:
I created a jira ticket: https://issues.apache.org/jira/browse/SLING-169
Thanks. So, I suggest you just go ahead and apply the patch :-)
Regards
Felix
31 matches
Mail list logo