[jira] [Issue Comment Edited] (COCOON3-93) Concurrency issues with ComponentProvider
[ https://issues.apache.org/jira/browse/COCOON3-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230079#comment-13230079 ] Thorsten Scherler edited comment on COCOON3-93 at 3/15/12 11:28 AM: I applied the patch in revision 1300923 even if we still discuss it since it fixes the concurrency problem in our customer app. That is as well the reason why I leave the issue open. was (Author: thorsten): I applied the patch in revision 1300923 even if we still discuss it since it fixes the concurrency problem in our customer app. > Concurrency issues with ComponentProvider > - > > Key: COCOON3-93 > URL: https://issues.apache.org/jira/browse/COCOON3-93 > Project: Cocoon 3 > Issue Type: Bug > Components: cocoon-sitemap >Affects Versions: 3.0.0-beta-1 >Reporter: Javier Puerto > Labels: patch > Attachments: SpringComponentProvider.diff, concurrency.tar.gz > > > http://cocoon.markmail.org/thread/3kgfye55zxavikwo > "we are working in a project based on C3 and we found a strange behaviour > when loading the static resources. We are developing a Web 2.0 application > and therefore we have a lot of resources (js, images and css). The weird > thing is that sometimes the system is returning the wrong resources, > returning a js instead of a css or switching images..." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (COCOON3-85) cocoon-spring-configurator doesn't work with latest (> 1.6.6) AspectJ's static optimizer
[ https://issues.apache.org/jira/browse/COCOON3-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177189#comment-13177189 ] Thorsten Scherler edited comment on COCOON3-85 at 12/29/11 2:23 PM: Actually @Francesco r1224754 broke the Stringtemplate example, meaning it seems that everything is fine but in runtime that is not like that any more. It seems as Igor described a problem of the class loader. Not sure though whether it is "fault" of the RCL or the configurator, but I will try now to apply the patch on my system and look whether that solves the problem. To reproduce, * just mvn clean install current Head * cd cocoon-sample * mvn jetty:run * http://localhost:/string-template/generator -> BANG! 2011-12-29 15:08:16.138:INFO:/:Initializing Spring root WebApplicationContext 2011-12-29 15:08:19.347:INFO:/:Apache Cocoon Spring Configurator v2.1.0 is running in mode 'dev'. 2011-12-29 15:08:23.468:INFO:/:DispatcherServlet: Block dispatcher was initialized successfully. 2011-12-29 15:08:23.581:INFO::Started SelectChannelConnector@0.0.0.0: [INFO] Started Jetty Server 2011-12-29 15:08:35.365:INFO:/:Apache Cocoon Spring Configurator v2.1.0 is running in mode 'dev'. java.lang.Error: Unresolved compilation problem: STRenderer cannot be resolved at org.apache.cocoon.stringtemplate.StringTemplateGenerator.renderTemplate(StringTemplateGenerator.java:152) at org.apache.cocoon.stringtemplate.StringTemplateGenerator.execute(StringTemplateGenerator.java:172) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:91) at org.apache.cocoon.profiling.aspects.InvocationDispatcher.dispatch(InvocationDispatcher.java:68) at org.apache.cocoon.profiling.aspects.PipelineComponentProfilingAspect.handleInvocation(PipelineComponentProfilingAspect.java:41) at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202) at $Proxy46.execute(Unknown Source) at org.apache.cocoon.pipeline.AbstractPipeline.invokeStarter(AbstractPipeline.java:150) at org.apache.cocoon.pipeline.AbstractPipeline.execute(AbstractPipeline.java:80) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at org.apache.cocoon.servlet.collector.ResponseHeaderCollector.interceptInvoke(ResponseHeaderCollector.java:94) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Native
[jira] [Issue Comment Edited] (COCOON3-77) Text and JSON serializers
[ https://issues.apache.org/jira/browse/COCOON3-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158430#comment-13158430 ] Thorsten Scherler edited comment on COCOON3-77 at 11/28/11 1:25 PM: Hi Andre, you misunderstood me. I was looking for one diff file based on the c3 root like the example one I attached. I needed to comment some code and remove some imports since they use classes that not have been in the patch. Can you please place your new classes in a fresh c3 checkout and make sure that all imports are resolvable. BTW I did the patch with svn diff >COCOON3-77.sample.patch.txt was (Author: thorsten): Hi Andre, you misunderstood me. I was looking for one diff file based on the c3 root like the example one I attached. I needed to comment some code and remove some imports since they use classes that not have been in the patch. Can you please place your new classes in a fresh c3 checkout and make sure that all imports are resolvable. > Text and JSON serializers > - > > Key: COCOON3-77 > URL: https://issues.apache.org/jira/browse/COCOON3-77 > Project: Cocoon 3 > Issue Type: Improvement > Components: cocoon-optional >Affects Versions: 3.0.0-alpha-3 >Reporter: Andre Juffer >Priority: Minor > Attachments: COCOON3-77.sample.patch.txt, > EncodingJsonSerializer.java, EncodingTextSerializer.java, > JsonSerializer.java, TextEncoder.java, TextSerializer.java, pom.xml, > tribc-cocoon-3.xml > > > Serveral classes have been created for serializing text and JSON in the > sitemap. The JsonSerializer also checks whether the JSON text actually is > valid. The organization of the classes follows the encoding serializers (such > as the EncodingHTMLSerializer). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
