Yes, it works fine. Thank you and thank to every body who tried to
understand the problem.

I ever not understand why I have to specify these properties, my file to
upload size is less than 1Mb when the default Cocoon max value is 10Mb.
Files to upload with a size less than 100kb have ever been uploaded, only
files bigger than 100kb were not uploaded.

Now I specify 10Mb in a "uploadsettings.properties" configuration file and
it's ok also for files bigger than 100kb. Strange.

Thank again

PS (for ohter users), my property file in
"/META-INF/cocoon/perperties/uploadsettings.properties" contains just :
org.apache.cocoon.uploads.maxsize=10000000
org.apache.cocoon.uploads.enable=true


2008/1/28, Joerg Heinicke <[EMAIL PROTECTED]>:
>
> On 28.01.2008 05:34, Grzegorz Kossakowski wrote:
>
> >> Like you said, I tried to add an "upload-max-size" init param in the
> >> Spring configuration of the Cocoon SitemapServlet but I have still the
> >> same error.
> >>
> >> Here is what I wrote :
> >>     <bean id="zzz.ma-adminui.block"
> >> class="org.apache.cocoon.sitemap.SitemapServlet">
> >>         <servlet:context mount-path="/ui"
> >> context-path="blockcontext:/ma-adminui/" >
> >>
> >>             <servlet:init-params>
> >>                 <entry key="upload-max-size" value="10000000" />
> >>             </servlet:init-params>
> >>
> >>             <servlet:connections>
> >>                 <entry key="ajax"
> >> value-ref="org.apache.cocoon.ajax.impl.servlet" />
> >>                 <entry key="forms"
> >> value-ref="org.apache.cocoon.forms.impl.servlet" />
> >>                 <entry key="services" value-ref="zzz.ma-service.block
> "/>
> >>             </servlet:connections>
> >>         </servlet:context>
> >>     </bean>
> >>
> >> Perhaps is my syntax wrong, I am still looking for it on the net.
> >
> > Your syntax is right. I have taken a closer look and found that we have
> changed whole mechanism and
> > configuration for it.
> >
> > Now you need to configure it using properties, the list of them you can
> find there [1]. I hope you
> > know how to set them in your block.
>
> Hmm, I might misss something, but what's the point of enforcing
> splitting configuration into different files? I can see the possible
> advantages of the properties, but not of preventing the user from
> explicitly configuring such a property directly on the bean.
>
> Joerg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to