Trinidad and text wrapping

While using Trinidad 1.0.1 I came across a problem where text did not wrap when displaying read only text fields. This meant that everything was pushed off the right hand side of the page. I had to change the fields from: 
<tr:inputText label="#{msgs['message1']}" styleClass="labelRight"
                              required="false"
                              value="#{mybean.value}"
                              id="mybean" columns="10"
                              readOnly="true"/>
to 
<tr:panelLabelAndMessage label="#{msgs['message1']}">
                  <tr:outputText value="#{mybean.value}" />
</tr:panelLabelAndMessage>
and added the following to my style sheet: 
.af_panelFormLayout_content-cell {
    white-space: normal;
}
Note outputText instead of inputText. It was tricky to get it working in FF and IE at the same time.

Popular posts from this blog

mappings closure does not exists for class UrlMappings

I've just started working on a new grails application, and early in the piece I hit this error: 2008-03-05 18:39:20.715::WARN: Failed startup of context org.mortbay.jetty.webapp.WebAppContext@1fcb845{/jtchat,/home/prule/workspace/jtchat/web-app} org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.codehaus.groovy.grails.plugins.web.taglib.ApplicationTagLib': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'grailsUrlMappingsHolder': Cannot resolve reference to bean 'urlMappingsTargetSource' while setting bean property 'targetSource'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'urlMappingsTargetSource': Cannot resolve reference to bean 'grailsUrlMappingsHolderBean' while setting constructor argument; nested exception is org.springframework.beans....
Read more

AspectJWeaver with JDK 7 - error - only supported at Java 5 compliance level or above

I came across this problem with an older project - when I switched from jdk6 to jdk7, when the application started I encountered: nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.transaction.annotation.AnnotationTransactionAttributeSource#0': Initialization of bean failed; nested exception is java.lang.IllegalArgumentException:   error annotation type patterns are only supported at Java 5 compliance level or above I didn't want a purely maven solution because during development I run the app in Tomcat via the IDE (Intellij IDEA). In the end I just upgraded my aspectjweaver dependency to 1.7.2 (it was 1.5.4) <dependency>    <groupId>org.aspectj</groupId>    <artifactId>aspectjweaver</artifactId>    <version>1.7.2</version> </dependency> Everything seems okay now.
Read more

Over typing -Dskip.junit=true

I generally prefer Maven2, but I'm currently on a project using a custom ant build script - and I'm over having to type -Dskip.junit=true when I just want to generate a quick jar without running the tests. To easily switch off tests, I modified ant.bat so that it looks for a command line parameter 'st' and if found, it will substitute it with -Dskip.junit=true. In Ant 1.7.0, you just need to change line 68 in block ':setupArgs' from set ANT_CMD_LINE_ARGS=%ANT_CMD_LINE_ARGS% %1 to if ""%1""==""st"" (set ANT_CMD_LINE_ARGS=%ANT_CMD_LINE_ARGS% -Dskip.junit=true) else (set ANT_CMD_LINE_ARGS=%ANT_CMD_LINE_ARGS% %1) So, the whole block reads (from line 65): :setupArgs if ""%1""=="""" goto doneStart if ""%1""==""-noclasspath"" goto clearclasspath if ""%1""==""st"" (set ANT_CMD_LINE_ARGS=%ANT_CMD_LINE_ARGS% -Dskip...
Read more