December 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: Cooking lobsters (bijection)

by pete.muir＠jboss.org

After the method calls you should see an outjected lobster - what scope are you outjecting the lobster to? You can debug this by placing breakpoints in the bijection interceptor. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115069#4115069 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115069

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - How to use log inside interceptor ?

by DiegoCoronel

this probably isnt hard, but i didnt find any way to get seam log, anyone can help me? | @Interceptor | public class LogInterceptor { | | @Logger | private static Log log; | | @AroundInvoke | public Object checkLoggedIn(InvocationContext invocation) throws Exception { | try { | log.info("Executando operacao antes"); | return invocation.proceed(); | } | finally { | log.info("Executando operacao depois"); | } | } | | } | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115068#4115068 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115068

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: Why PAGE context variable = NULL

by pete.muir＠jboss.org

Those are two different pages, so you won't have the same page context for both pages... (i.e. what you are trying to do is flawed from a design perspective) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115066#4115066 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115066

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: Error selecting object - SEAM 1.2.1GA

by pete.muir＠jboss.org

I rewrote the whole entity converter between 1.2 and 2.0 - ant its quitedeeply integrated into Seam core as well. You should be able to pull out the relevant classes though to build your own version - you'll need classes from org.jboss.seam.ui.converter and org.jboss.seam.framework. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115064#4115064 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115064

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: Parameters and @Factory

by pete.muir＠jboss.org

The first call to the method occurs to rebuild the JSF tree, the input fields aren't applied to the model after this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115063#4115063 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115063

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: Update transactions occurring prematurely in Seam app

by asookazian

Ok, thanks! I did not see a keyword hit on 'TransactionalSeamPhaseListener' in the 2.0.0.GA ref pdf so I got a little confused when comparing with the Seam chapter in Bauer/king book. thanks again. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115062#4115062 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115062

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: Update transactions occurring prematurely in Seam app

by pete.muir＠jboss.org

This is enabled by default in Seam 2. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115059#4115059 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115059

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Love the test support in seam except for...

by andrew.rw.robinson

Seam's TestNG support is quite nice, but there is one major design flaw that really affects test case design. The test classes are designed to be used as a black box. The init and cleanup methods are made to be used at the class instance level. Ramping up Seam is very slow. My project, which is still small takes a long time to initialize mainly because of: seam deployment, hibernate configuration, drools rule parsing. Having each test class ramp up all of the full stack is not feasible for time reasons. This means that it is best to put all unit tests in one class with hundreds of methods. I really don't like that design. I would prefer to build a test class for each entity bean and for each managed bean. What would be great is to re-architect the test classes so that the init and cleanup are annotated with @BeforeSuite and @AfterSuite respectively. The variables that these classes should be either static or made in such a way that there is only one instance per test suite. If they could be made in such a way that they could also be run in parallel in one JVM instance (forkMode of once) that would be great as well, as then the tests could simulate a server with many requests at once. I can probably hack this behavior into my test cases, but it would most likely break with changes to the source as I may have to use reflection to set the private variables. Any chance at getting this type of functionality in the provided test classes? Thanks, Andrew View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115057#4115057 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115057

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - javax.el.PropertyNotFoundException

by vikramchhetryy

Hi all, My code looks like this:- User.java | @Entity | @Name("userBean") | @Scope(SESSION) | @Table(name = "abcd") | public class User implements Serializable { | | private static final long serialVersionUID = -7928759431732764467L; | private String StrUserName; | private String StrPassword; | | @Id | @NotNull | public String getStrUserName() { | return StrUserName; | } | public void setStrUserName(String strUserName) { | StrUserName = strUserName; | } | @NotNull | public String getStrPassword() { | return StrPassword; | } | public void setStrPassword(String strPassword) { | StrPassword = strPassword; | } | | } | login.xhtml <div class="dialog"> | <h:panelGrid columns="2" rowClasses="prop" columnClasses="name,value"> | <h:outputLabel for="StrUserName">Username</h:outputLabel> | <h:inputText id="StrUserName" | value="#{userBean.StrUserName}"/> | <h:outputLabel for="StrPassword">Password</h:outputLabel> | <h:inputSecret id="StrPassword" | value="#{userBean.StrPassword}"/> | </h:panelGrid> | </div> I m getting following exception while loading login page javax.el.PropertyNotFoundException: /login.xhtml @26,64 value="#{userBean.StrUserName}": Property 'StrUserName' not found on type com.xyz.user.User Any help would be appreciated. Regards, Vikram View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115054#4115054 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115054

18 years, 4 months

1
0
0 / 0

[JNDI/Naming/Network] - Re: javax.naming.NameNotFoundException: queue not bound

by PeterJ

Did you change any of the files in the jms directory? Specifically, did you change hsqldb-jdbc2-service.xml (or perhaps replace it with another file)? That file directs MQ to use DefaultDS as its data source. You mentioned MySQL. Also, the error message "Access denied for user 'jbossuser'@'localhost' (using password: YES))" is a typical MySQL error message. I am assuming that you must have changed hsqldb-jdbc2-service.xml to use a different data source, or replace DefaultDS with MySQL. Until you get the database access issue solved, you will not be able to use the messaging service., and no queue or destinations will show up. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115052#4115052 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115052

18 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user December 2007