Luka,
What version of maven are using? I am on 3.0.3.
Max
On 7/20/2011 8:35 AM, Luka Surija wrote:
Hi Max,
I'll try it as soon i get some spare time.
P.S. Last couple of months I have problems compiling trinidad 2 trunk:
Plugin org.apache.myfaces.trinidadbuild:maven-xrts-plugin:2.0.6 or one
of its dependencies could not be resolved: Failed to read artifact
descriptor for
org.apache.myfaces.trinidadbuild:maven-xrts-plugin:jar:2.0.6: Could
not find artifact
org.apache.myfaces.trinidadbuild:maven-xrts-plugin:pom:2.0.6 in
central (http://repo1.maven.org/maven2) -> [Help 1]
Do you have any idea how to solve this?
Tnx and regards,
Luka Surija
On 19.07.2011 20:51, Max Starets wrote:
Luka,
I updated the JIRA with two workarounds for this issue. I will also
provide a fix soon.
For now, you can just disable debug output in trinidad-config (you
don't want to have it in production anyways).
Max
On 7/18/2011 10:43 AM, Max Starets wrote:
Luka,
I know that you have logged TRINIDAD-2107. I haven't been able to
take a look at it yet unfortunately, but will do so this week.
Were there other problems?
Max
On 7/17/2011 6:23 PM, Luka Surija wrote:
Welcome to the club, something in development of this combination
Trinidad 2 + Facelets + JSF2 went terribly wrong. After couple of
years using Trinidad 1.2 + JSF 1.2 + Facelets in big enterprise
applications, I've spent more then a MONTH to make something more
complicated then "Hello World" application without big success. My
heavy and painful decision (now I have to rewrite all existing apps
in something other - Vaadin) was to finally give up from Trinidad
and JSF2 technology because it's a joke in terms of stability. And
in other hand, Java 5 EE reached some time ago EOL!?
Luka Surija
On 07/17/2011 03:11 AM, Manuel Hartl wrote:
Hi list,
my rearch to get trinidad2 with facelets working gets more
confusing..
the following was tested with
mojarra 2.0.2-b10 and 2.0.6
trinidad-2.0.0 and trinidad-2.0.1-SNAPSHOT (executed von 17th of
July)
web.xml-parameters:
<context-param>
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
<param-value>.xhtml</param-value>
</context-param>
<context-param>
<param-name>javax.faces.PARTIAL_STATE_SAVING</param-name>
<param-value>false</param-value>
</context-param>
<context-param>
<param-name>javax.faces.PROJECT_STAGE</param-name>
<param-value>Development</param-value>
</context-param>
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
</context-param>
<context-param>
<param-name>org.apache.myfaces.COMPRESS_STATE_IN_CLIENT</param-name>
<param-value>true</param-value>
</context-param>
<context-param>
<param-name>org.apache.myfaces.trinidad.CACHE_VIEW_ROOT</param-name>
<param-value>false</param-value>
</context-param>
<context-param>
<param-name>org.apache.myfaces.trinidad.CLIENT_STATE_METHOD</param-name>
<param-value>token</param-value>
</context-param>
<context-param>
<param-name>org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION</param-name>
<param-value>true</param-value>
</context-param>
<context-param>
<param-name>org.apache.myfaces.trinidad.ENABLE_LIGHTWEIGHT_DIALOGS</param-name>
<param-value>true</param-value>
</context-param>
<context-param>
<param-name>org.apache.myfaces.trinidadinternal.ENABLE_PPR_OPTIMIZATION</param-name>
<param-value>false</param-value>
</context-param>
1) the problem with tr/trh tags not rendered can be workaround by
setting the renderKitId-Attribut of f:view/f:subview to
"org.apache.myfaces.trinidad.core".
it seems that the default-render-kit-id in the faces-config.xml is
just
ignored.
Can someone explain this?
2) Now the first page is displayed, any following page gives the
following exception. It seems this is a problem with the format of
viewState stored in the hidden form field:
java.io.IOException: Not in GZIP format
at
java.util.zip.GZIPInputStream.readHeader(GZIPInputStream.java:143)
at java.util.zip.GZIPInputStream.<init>(GZIPInputStream.java:58)
at java.util.zip.GZIPInputStream.<init>(GZIPInputStream.java:67)
at
com.sun.faces.renderkit.ClientSideStateHelper.doGetState(ClientSideStateHelper.java:231)
at
com.sun.faces.renderkit.ClientSideStateHelper.getState(ClientSideStateHelper.java:198)
at
com.sun.faces.renderkit.ResponseStateManagerImpl.getState(ResponseStateManagerImpl.java:100)
at
com.sun.faces.renderkit.ResponseStateManagerImpl.getTreeStructureToRestore(ResponseStateManagerImpl.java:148)
at
org.apache.myfaces.trinidadinternal.application.StateManagerImpl.restoreView(StateManagerImpl.java:584)
at
com.sun.faces.application.view.ViewHandlingStrategy.restoreView(ViewHandlingStrategy.java:123)
at
com.sun.faces.application.view.FaceletViewHandlingStrategy.restoreView(FaceletViewHandlingStrategy.java:448)
at
com.sun.faces.application.view.MultiViewHandler.restoreView(MultiViewHandler.java:148)
at
javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:288)
The more i dig into this, the more doubts raise, that anyone is using
trinidad2 (with facelets) really...
Regards,
Manuel.
