You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Tadas Šubonis <ta...@gmail.com> on 2011/08/19 16:28:25 UTC
[Trinidad] Compiling trinidad-impl produces "broken" jar
I am writing in response to my previous mail (It seems that I can't reply to
that thread because I wasn't subscribed till then...)
I took my original JS and after building it fails to produce me jar that
wouldn't throw that exception :/. Seems like it is somehow related to my
build environment...
Without your JS, it's hard to tell, but JS on the client can
absolutely cause exceptions on the server if they
are not made correctly.
As for Trinidad 1.0, it's in maintenance mode only, which means there
is likely to be no more releases of the product.
Sent from my iPhone
On Aug 11, 2011, at 7:37 AM, Tadas Šubonis <tadas.subonis <at> gmail.com> wrote:
Hello,
I am using Trinidad 1.0.10 version. I made some little changes to javascript
and tried to rebuild trinidad (to distribute new libs
(trinidad-impl-1.0.10.jar) and their changes to other internal projects).
There was ONLY javascript SMALL tweaks. After rebuild, our custom components
(seems like it) stopped working with this, not so clear, exception:
javax.el.ELException: /layout/components/commandLink/commandLink.jspx: Bean:
lt.it.info.demo.backing.menu.ProjectMenuBacking, property: someAction
at
com.sun.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:53)
at
com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39)
at
com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:242)
at
com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249)
at
com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249)
at
com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:594)
at
org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:182)
at
org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:140)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
<.....>
If I use old libs all is ok again. How it comes that after javascript
changes breaks Java? Could someone point me to possible causes of this
problem? I understand that this lib I am using is out-of-date, but It
doesn't seem like it will be updated soon.
.
Any ideas welcome, how to fix this.
--
Tadas Šubonis
Re: [Trinidad] Compiling trinidad-impl produces "broken" jar
Posted by Tadas Šubonis <ta...@gmail.com>.
Problem was in path resolution for maven-trinidad-plugin - reported bug
here:
https://issues.apache.org/jira/browse/TRINIDAD-2132
On Fri, Aug 19, 2011 at 6:28 PM, Scott O'Bryan <da...@gmail.com> wrote:
> Cool, so you believe things are working as expected then?
>
>
> On 08/19/2011 08:28 AM, Tadas Šubonis wrote:
>
>> I am writing in response to my previous mail (It seems that I can't reply
>> to
>> that thread because I wasn't subscribed till then...)
>>
>> I took my original JS and after building it fails to produce me jar that
>> wouldn't throw that exception :/. Seems like it is somehow related to my
>> build environment...
>>
>> Without your JS, it's hard to tell, but JS on the client can
>> absolutely cause exceptions on the server if they
>> are not made correctly.
>>
>> As for Trinidad 1.0, it's in maintenance mode only, which means there
>> is likely to be no more releases of the product.
>>
>> Sent from my iPhone
>>
>> On Aug 11, 2011, at 7:37 AM, Tadas Šubonis<tadas.subonis<at> gmail.com>
>> wrote:
>>
>> Hello,
>>
>>
>> I am using Trinidad 1.0.10 version. I made some little changes to
>> javascript
>> and tried to rebuild trinidad (to distribute new libs
>> (trinidad-impl-1.0.10.jar) and their changes to other internal projects).
>> There was ONLY javascript SMALL tweaks. After rebuild, our custom
>> components
>> (seems like it) stopped working with this, not so clear, exception:
>>
>> javax.el.ELException: /layout/components/**commandLink/commandLink.jspx:
>> Bean:
>> lt.it.info.demo.backing.menu.**ProjectMenuBacking, property: someAction
>> at
>> com.sun.facelets.compiler.**AttributeInstruction.write(**
>> AttributeInstruction.java:53)
>> at
>> com.sun.facelets.compiler.**UIInstructions.encodeBegin(**
>> UIInstructions.java:39)
>> at
>> com.sun.facelets.tag.jsf.**ComponentSupport.**encodeRecursive(**
>> ComponentSupport.java:242)
>> at
>> com.sun.facelets.tag.jsf.**ComponentSupport.**encodeRecursive(**
>> ComponentSupport.java:249)
>> at
>> com.sun.facelets.tag.jsf.**ComponentSupport.**encodeRecursive(**
>> ComponentSupport.java:249)
>> at
>> com.sun.facelets.**FaceletViewHandler.renderView(**
>> FaceletViewHandler.java:594)
>> at
>> org.apache.myfaces.**trinidadinternal.application.**
>> ViewHandlerImpl.renderView(**ViewHandlerImpl.java:182)
>> at
>> org.apache.myfaces.lifecycle.**RenderResponseExecutor.**execute(**
>> RenderResponseExecutor.java:**41)
>> at org.apache.myfaces.lifecycle.**LifecycleImpl.render(**
>> LifecycleImpl.java:132)
>> at javax.faces.webapp.**FacesServlet.service(**FacesServlet.java:140)
>> at
>> org.apache.catalina.core.**ApplicationFilterChain.**internalDoFilter(**
>> ApplicationFilterChain.java:**290)
>> at
>> org.apache.catalina.core.**ApplicationFilterChain.**doFilter(**
>> ApplicationFilterChain.java:**206)
>> <.....>
>>
>> If I use old libs all is ok again. How it comes that after javascript
>> changes breaks Java? Could someone point me to possible causes of this
>> problem? I understand that this lib I am using is out-of-date, but It
>> doesn't seem like it will be updated soon.
>> .
>>
>> Any ideas welcome, how to fix this.
>>
>>
>
--
Pagarbiai,
Tadas Šubonis
Re: [Trinidad] Compiling trinidad-impl produces "broken" jar
Posted by Scott O'Bryan <da...@gmail.com>.
Cool, so you believe things are working as expected then?
On 08/19/2011 08:28 AM, Tadas Šubonis wrote:
> I am writing in response to my previous mail (It seems that I can't reply to
> that thread because I wasn't subscribed till then...)
>
> I took my original JS and after building it fails to produce me jar that
> wouldn't throw that exception :/. Seems like it is somehow related to my
> build environment...
>
> Without your JS, it's hard to tell, but JS on the client can
> absolutely cause exceptions on the server if they
> are not made correctly.
>
> As for Trinidad 1.0, it's in maintenance mode only, which means there
> is likely to be no more releases of the product.
>
> Sent from my iPhone
>
> On Aug 11, 2011, at 7:37 AM, Tadas Šubonis<tadas.subonis<at> gmail.com> wrote:
>
> Hello,
>
>
> I am using Trinidad 1.0.10 version. I made some little changes to javascript
> and tried to rebuild trinidad (to distribute new libs
> (trinidad-impl-1.0.10.jar) and their changes to other internal projects).
> There was ONLY javascript SMALL tweaks. After rebuild, our custom components
> (seems like it) stopped working with this, not so clear, exception:
>
> javax.el.ELException: /layout/components/commandLink/commandLink.jspx: Bean:
> lt.it.info.demo.backing.menu.ProjectMenuBacking, property: someAction
> at
> com.sun.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:53)
> at
> com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39)
> at
> com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:242)
> at
> com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249)
> at
> com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249)
> at
> com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:594)
> at
> org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:182)
> at
> org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
> at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:140)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> <.....>
>
> If I use old libs all is ok again. How it comes that after javascript
> changes breaks Java? Could someone point me to possible causes of this
> problem? I understand that this lib I am using is out-of-date, but It
> doesn't seem like it will be updated soon.
> .
>
> Any ideas welcome, how to fix this.
>