[JBoss Tools (users)] - Re: How to configure visual editor
by tynor
anonymous wrote :
| It seems you are asking about multiple things here.
|
| 1) You ask about how to setup css rendering, but also says it just works for you so i'm unsure what is your problem in this context ?
|
Yes - probably true. I included the CSS config in my description because it was the only element of the Page Design Options that I configured in a way that actually made any change in the visual rendering of the page.
I would note that none of the RichFaces components used on the screen are rendered with proper styles (e.g. a "panel header" is rendered with the default grey background while our app configures a custom "skin" which should cause the header to render with a green background). I did not mention this in the original since I assume that this is just not possible/practical in eclipse since these styles are computed at run time by the rich faces runtime (yes?).
anonymous wrote :
| 2) WYSIWYG rendering of seam tags should just work (at least if you are using the correct xmlns for them. Please report in jira with sample page source and screenshot of the rendering.
|
Done: http://jira.jboss.com/jira/browse/JBIDE-1575
anonymous wrote :
| 3) WYSIWYG rendering of your own tags. JSF components does not have a "preview" mode builtin so for each component we have to define such a mode and that is done via .vpe template files. We haven't exposed a public api for that yet but if you want to digg into it search for .vpe in our plugins and you can find examples on how to do it.
|
My tags are not custom JSF components - they are simple Facelet compositions -- e.g. here's the implementation of our "outputCurrency" tag. If custom taglibs such as these are not supported by the VPE, what exactly does the URI/Prefix section of the Page Design Options page configure?
Taglib definition:
| <!DOCTYPE facelet-taglib PUBLIC
| "-//Sun Microsystems, Inc.//DTD Facelet Taglib 1.0//EN"
| "http://java.sun.com/dtd/faces-taglib_1_0.dtd">
|
| <facelet-taglib>
| <namespace>http://mydomain.com/jsf/myproject</namespace>
| ...
| <tag>
| <tag-name>inputCurrency</tag-name>
| <source>facelets/tags/inputCurrency.xhtml</source>
| </tag>
|
Tag source:
| <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
| "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
| <html xmlns="http://www.w3.org/1999/xhtml"
| xmlns:ui="http://java.sun.com/jsf/facelets"
| xmlns:h="http://java.sun.com/jsf/html"
| xmlns:f="http://java.sun.com/jsf/core"
| xmlns:c="http://java.sun.com/jstl/core"
| xmlns:s="http://jboss.com/products/seam/taglib">
|
| <ui:composition>
| <h:outputText value="$" />
| <h:outputText value="#{value}">
| <f:convertNumber pattern="#,##0.00" />
| </h:outputText>
| </ui:composition>
| </html>
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116730#4116730
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116730
18 years, 3 months
[JBoss Seam] - IllegalArgumentException: Stack must not be null
by laksu
Hello,
I am trying to cook my first component test:
public class CategoryInteraction extends SeamTest {
|
| @Test
| public void testMest() throws Exception {
|
| new ComponentTest(){
|
| @Override
| protected void testComponents() throws Exception {
| String result=(String)invokeMethod("#{categoryAction.nevv('E')}");
| assert result.equals("categoryDefine");
| }
| }.run();
| }
| }
I get this weird stack trace:
| java.lang.IllegalArgumentException: Stack must not be null
| at org.jboss.seam.core.ConversationEntry.<init>(ConversationEntry.java:39)
| at org.jboss.seam.core.ConversationEntries.createConversationEntry(ConversationEntries.java:53)
| at org.jboss.seam.core.Manager.createConversationEntry(Manager.java:537)
| at org.jboss.seam.core.Manager.beginConversation(Manager.java:558)
| at org.jboss.seam.core.ConversationInterceptor.beginConversation(ConversationInterceptor.java:229)
| at org.jboss.seam.core.ConversationInterceptor.beginConversationIfNecessary(ConversationInterceptor.java:166)
| at org.jboss.seam.core.ConversationInterceptor.aroundInvoke(ConversationInterceptor.java:57)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
| at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
| at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
| at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166)
| at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102)
| at datassist.payroll.action.CategoryAction_$$_javassist_0.nevv(CategoryAction_$$_javassist_0.java)
| at datassist.payroll.test.CategoryInteraction$1.testComponents(CategoryInteraction.java:22)
| at org.jboss.seam.mock.BaseSeamTest$ComponentTest.run(BaseSeamTest.java:167)
| at datassist.payroll.test.CategoryInteraction.testMest(CategoryInteraction.java:31)
| ... Removed 22 stack frames
I went to debug it to some level: It looks like Manager object is not initialized properly or something.
I am using Seam 2.0.1.CR1
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116720#4116720
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116720
18 years, 3 months