Sorry to break these bad news - again - but the assertion errors are back:
java.lang.AssertionError
at
org.apache.myfaces.trinidadinternal.style.util.CSSUtils.getBaseSkinStyleSheetURI(CSSUtils.java:139)
at
Btw, this happens on the trinidad-1.0.1 release.
On 7/2/07, Francisco Passos [EMAIL PROTECTED] wrote:
Sorry to break these bad news - again - but the assertion errors are back:
java.lang.AssertionError
at
Tried today's nightly build and the error no longer appears.
Thank you.
Francisco
On 5/30/07, Francisco Passos [EMAIL PROTECTED] wrote:
Excellent news!
Thank you,
Francisco
On 5/30/07, Adam Winer [EMAIL PROTECTED] wrote:
http://issues.apache.org/jira/browse/TRINIDAD-44
Fixed.
-- Adam
http://issues.apache.org/jira/browse/TRINIDAD-44
Fixed.
-- Adam
On 5/29/07, Francisco Passos [EMAIL PROTECTED] wrote:
Thank you.
Are there plans to address this bug soon?
On 5/29/07, Adam Winer [EMAIL PROTECTED] wrote:
Looks like a (minor) bug in Trinidad. Code should be clearing
Excellent news!
Thank you,
Francisco
On 5/30/07, Adam Winer [EMAIL PROTECTED] wrote:
http://issues.apache.org/jira/browse/TRINIDAD-44
Fixed.
-- Adam
On 5/29/07, Francisco Passos [EMAIL PROTECTED] wrote:
Thank you.
Are there plans to address this bug soon?
On 5/29/07, Adam Winer
Thank you.
Are there plans to address this bug soon?
On 5/29/07, Adam Winer [EMAIL PROTECTED] wrote:
Looks like a (minor) bug in Trinidad. Code should be clearing
RenderingContext.setCurrentClientId() but isn't, and the assert
is catching that. We should be running our tests with asserts
Good afternoon.
I'm developing an application with Trinidad on Weblogic Application Server
9.2.
It works fine in normal circumstances, but whenever I start weblogic in
debug mode (to attach by socket in Eclipse), pages cease to render and this
error is presented instead.
Error 500--Internal
(Accidentally depressed 'Send')
Is this a known problem? I didn't find references to any problems regarding
AssertionErrors in Weblogic.
Francisco Passos
On 5/29/07, Francisco Passos [EMAIL PROTECTED] wrote:
Good afternoon.
I'm developing an application with Trinidad on Weblogic Application
Looks like a (minor) bug in Trinidad. Code should be clearing
RenderingContext.setCurrentClientId() but isn't, and the assert
is catching that. We should be running our tests with asserts
enabled, IMO, which I think would have caught this particular
problem.
-- Adam
On 5/29/07, Francisco
9 matches
Mail list logo