You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Richard Light <ri...@light.demon.co.uk> on 2006/09/20 17:11:48 UTC
FileUploadManager
Hi,
I have been trying to get the FileUploadManager to work, as described in
the FileUploadsWithFlow Wiki page, and hit an initialisation problem -
it "could not get class" FileUploadManagerImpl.
After much trial and error, I was able to get it at least start (I
haven't tried actually uploading any files yet!) by altering the
user.xroles file provided on the Wiki page. I changed the shorthand
attribute in the <role-list> element from "upload_manager" to
"upload-manager", and the loading problem went away. Strange but true!
Richard Light
--
Richard Light
SGML/XML and Museum Information Consultancy
richard@light.demon.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: FileUploadManager
Posted by Richard Light <ri...@light.demon.co.uk>.
In message <45...@gmx.de>, Joerg Heinicke
<jo...@gmx.de> writes
>On 20.09.2006 17:11, Richard Light wrote:
>
>> After much trial and error, I was able to get it at least start (I
>>haven't tried actually uploading any files yet!) by altering the
>>user.xroles file provided on the Wiki page. I changed the shorthand
>>attribute in the <role-list> element from "upload_manager" to
>>"upload-manager", and the loading problem went away. Strange but true!
>
>I think the @shorthand must only match the entry (element name) in the
>cocoon.xconf. So the wiki entry looks ok for me. Are you sure, you only
>changed it in the roles file?
Now that I have 2.1.9 installed, I'm coming back to this issue. You're
quite right: the user.xroles @shorthand simply needs to match the
element name in cocoon.xconf.
However ... what I am finding is that if they _do_ match, I get an
initialization problem:
-----------------------------------------------------
Message: org.apache.cocoon.components.upload.FileUploadManagerImpl
Description:
org.apache.avalon.framework.configuration.ConfigurationException: Could
not get class
Sender: org.apache.cocoon.servlet.CocoonServlet
Source: Cocoon Servlet
-----------------------------------------------------
The file cocoon-uploads.jar (which contains the definition of the
FileUploadManagerImpl class) is sitting in the directory WEB-INF\lib,
but Cocoon is clearly failing to find it. Do I need to declare it
somewhere else, e.g. in the sitemap?
Richard
--
Richard Light
SGML/XML and Museum Information Consultancy
richard@light.demon.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: FileUploadManager
Posted by Joerg Heinicke <jo...@gmx.de>.
On 20.09.2006 17:11, Richard Light wrote:
> After much trial and error, I was able to get it at least start (I
> haven't tried actually uploading any files yet!) by altering the
> user.xroles file provided on the Wiki page. I changed the shorthand
> attribute in the <role-list> element from "upload_manager" to
> "upload-manager", and the loading problem went away. Strange but true!
I think the @shorthand must only match the entry (element name) in the
cocoon.xconf. So the wiki entry looks ok for me. Are you sure, you only
changed it in the roles file?
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org