[jboss-user] [JBoss Seam] - rememberMe at security: cannot get the username

2007-06-05 Thread xtia004
Has anybody experienced this problem -- Identity cannot get the username from the cookie? By tracking into the code, the real cause is that at getCookie method FacesContext.getCurrentInstance() always returns null. The other session scope component with @Startup + @Create also has got the same

[jboss-user] [JBoss Seam] - Re: Asynchronous programming pattern

2007-05-24 Thread xtia004
In case it might be useful to someone, we resolved the problem by making the task code thread sleep for the duration. If Seam will support to make an asynchronous call from another asynchronous call, the sleep code then should be removed. View the original post :

[jboss-user] [JBoss Seam] - Asynchronous programming pattern

2007-05-13 Thread xtia004
Whenever we make an asynchronous method call, a thread will be dispatched. It works well so far but we encountered serveral asynchronous call requirements such as doing calculation when rolling over a day, sending reminder message for a payment due, expiring a registration for certain

[jboss-user] [JBoss Seam] - Re: Entity Property Not Up-To-Date

2007-04-19 Thread xtia004
Hibernate EntityManager User guide 3.9.1: Hibernate does guarantee that the Query.getResultList()/Query.getSingleResult() will never return stale data. Can we trust it??? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039121#4039121 Reply to the post :

[jboss-user] [JBoss Seam] - Re: Entity Property Not Up-To-Date

2007-04-03 Thread xtia004
Could anybody help and reply on this issue? We cannot always use em.clear() because there are more than one queries at the same SFSB. In addition, now we cannot trust the result if rerunning the query, but the system is getting bigger, it is hard to check for each query to see if em.clear

[jboss-user] [JBoss Seam] - Re: Entity Property Not Up-To-Date

2007-04-02 Thread xtia004
It is injected by @PersistenceContext(type = PersistenceContextType.EXTENDED). I also set hibernate.cache.use_query_cache to false and removed hibernate.cache.provider_class property from persistence.xml View the original post :

[jboss-user] [JBoss Seam] - Entity Property Not Up-To-Date

2007-04-01 Thread xtia004
It looks like a hibernate related topic, but I encountered it when developing using Seam and easy to describe with it. So I'd like to put it on here first. I have two SFSB, say A and B, both have an extended EntityManager em. A retrieves a list of entity Invoice. B retrieve a list of entity

[jboss-user] [JBoss Seam] - How can s:button be rendered as an image button

2007-01-29 Thread xtia004
I have tried several properies of s:button such as type=image, image=..., src=... so that it can be rendered as an image button but not successful. The reason here not using s:link is that I want a javascript confirmation before actually performing the action in case of delete. By using

[jboss-user] [JBoss Seam] - Re: How can s:button be rendered as an image button

2007-01-29 Thread xtia004
Yes, it is a good workaround. It has solved my problem. But you know, it is lack of the pressdown behaviour and if we have more kinds of such buttons, we have to style each of them. What about a request to make s:button be able to render an image button as petemuir suggested? View the original

[jboss-user] [JBoss Seam] - Re: Lazy loading problem

2007-01-21 Thread xtia004
By further probing my code, I found it is actually caused by em.clear at another component. i.e. when I select a row at dataTable, the following code is executed: | InvoiceContacts invoiceContactsAction = (InvoiceContacts) Component.getInstance(invoiceContactsAction, |

[jboss-user] [JBoss Seam] - Remoting call runtime exception at remote.js

2007-01-09 Thread xtia004
The runtime exceptions of remoting call I experienced so far are all caused by session timed out. It appears as a javascript exception Object required at line 627 char 19. I temporary fix it by detecting if doc.documentElement is null and then redirecting it to login page to restart a new

[jboss-user] [JBoss Seam] - Re: Issue Raised by Seam Upgrade

2007-01-09 Thread xtia004
Tried on jboss-seam-CVS.20070105.zip, the same exception. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3999658#3999658 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3999658 ___

[jboss-user] [JBoss Seam] - Issue Raised by Seam Upgrade

2007-01-08 Thread xtia004
After I switch from 1.0.1 to 1.1.0, I got the following exception. It worked fine on 1.0.1. anonymous wrote : | 15:16:45,296 ERROR [[/1piece]] Session event listener threw exception | javax.ejb.EJBException: java.lang.IllegalStateException: No active event context | at

[jboss-user] [JBoss Seam] - Fail to persist sub class

2006-09-11 Thread xtia004
I have the following code. CreditCardPayment is inherited from Payment and added some extra fields. @Entity | @Table(name = PAYMENT) | @Name(payment) | @Inheritance(strategy=InheritanceType.JOINED) | @DiscriminatorColumn(name=PAY_METHOD, discriminatorType=DiscriminatorType.STRING,

[jboss-user] [JBoss Seam] - Re: Session Listener: @Startup for session scoped component

2006-08-03 Thread xtia004
I applied @Startup to a class and @Create to a method of the class. At the method, I want to do something and set a component to session scope. I tried: @In Context sessionContext;, no matter set create and requested to true or not, sessionContext is always null. I also tried

[jboss-user] [JBoss Seam] - Re: Session Listener: @Startup for session scoped component

2006-08-03 Thread xtia004
Thanks, is or will be there a resolution to deal with this case? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3963039#3963039 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3963039