java 6 method in gravel

[tom.baeyens]

david, i think you're using a java 6 method in gravel

11:19:56,078 DEBUG [DbPersistenceService] closing hibernate session
11:19:56,078 DEBUG [Services] closing service 'tx': org.jbpm.tx.TxService@c0d2d3
11:19:56,078 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception
java.lang.NoSuchMethodError: java.util.Properties.load(Ljava/io/Reader;)V
at org.jboss.gravel.data.handler.LoadPropertiesHandler.onComponentCreated(LoadPropertiesHandler.java:104)
at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:165)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
at com.sun.facelets.tag.ui.DefineHandler.apply(DefineHandler.java:58)
at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:128)
at com.sun.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:306)
at com.sun.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:279)
at com.sun.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:68)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248)
at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294)
at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273)
at com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:143)
at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:113)
at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248)
at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294)
at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273)
at com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:143)
at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:113)
at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:503)
at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:546)
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:178)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)

i'm now trying to get subclipse installed to get and update gravel.

[tom.baeyens]

can't find the gravel sources. a pointer would be appreciated.

the current console still needs to run on java 1.4.2. it would be good if you could help me test and fix this.

it's only the next version of the console (the one based on SEAM) that needs to run only on java 5

[dmlloyd]

The JDK6 dep has been fixed in the source. Should be committed this evening sometime.

As far as Java 1.4 compatibility - personally, I'm skeptical at this requirement, especially given the following facts:

- Organizations seem to be adopting 3.2.x for their new projects as opposed to their existing projects. New projects are rarely based on such an old VM.
- JBossAS 4.2.0 runs only on JDK5 and higher.

However, I will still provide an additional target for producing a JDK 1.4, JBossAS 4.0.x build via jbossretro as per the prior console.

[camunda]

Good point, I think at least Java 5 should be used for current jbpm versions.

[tom.baeyens]

The JDK6 dep has been fixed in the source. Should be committed this evening sometime.

where is the source ? couldn't find it in the svn repo. there only seems to be the console (new console based on seam) and the jbpm4jsf component library. ah right... now i remember it was the separate jboss project

i'll check if i can find that

As far as Java 1.4 compatibility - personally, I'm skeptical at this requirement, especially given the following facts:

- Organizations seem to be adopting 3.2.x for their new projects as opposed to their existing projects. New projects are rarely based on such an old VM.
- JBossAS 4.2.0 runs only on JDK5 and higher.

However, I will still provide an additional target for producing a JDK 1.4, JBossAS 4.0.x build via jbossretro as per the prior console.

without a good reason, we shouldn't introduce a java 5 dependency. SEAM is a good reason. if we encounter some other problem, we could consider it. but i don't know of any such problem now. so we should stick to java 1.4.2 for now

[tom.baeyens]

i found the gravel sources.

did you update the snapshot in the repository ?

[dmlloyd]

No I did not update the snapshot yet. I've got a couple other fixes in progress now. I will have things updated tonight.

[tom.baeyens]

ok good. thanks!