April 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: is an upgrade guide available for Seam?

by CptnKirk

I agree, an upgrade guide from release to release would be useful. However I doubt you'll get an upgrade guide that describes how to upgrade apps based on examples. I think your approach of taking the new hibernate2 example as a base and then patching in your code/config is the way to go here. All that said, I wouldn't be surprised if any new update guide made references to seam-gen as it's a nice automated way to go. Later versions have a number of project types and deployment options. If your particular hibernate2 style project isn't yet able to be bootstrapped with seam-gen I'd submit an improvement JIRA for someone to take a look at supporting it in the future. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040228#4040228 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040228

19 years

1
0
0 / 0

[JBoss Seam] - Interceptor Question

by xinhua

Hi all, I have a simple Annotation like following: | @Target(METHOD) | @Retention(RUNTIME) | @Interceptors(PrintoutInterceptor.class) | public @interface Printout { | } | and the Interceptor class: | public class PrintoutInterceptor { | | @AroundInvoke | public void printOut(InvocationContext invocation) throws Exception { | System.out.println("Method "+invocation.getMethod()+" is called"); | invocation.proceed(); | } | } And then i tried to put this annotation on a method, | .... | @Printout | public String register(.....) | ..... | BUT, the interceptor doesnot work :( can anyone help? Thanks !! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040227#4040227 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040227

19 years

1
0
0 / 0

[EJB 3.0] - OutOfMemory exception.

by d5nguyenvan

Hi all, First of all, thanks for all people to review my errors. I'm working on EJB3 and I want to persist an big content to database (about 60MB). I read the data from the file and it work well (I could read and write file size 80MB or greater), but when I persist big content to database something wrong (OutOfMemory exception). I already configured the JVM (JAVA_OPTS = -server -Xms1024M -Xmx1024M), and configured my database to accept the package with size greater than 60MB. The error log: Exception in thread "main" java.lang.RuntimeException: org.jboss.tm.JBossRollbackException: Unable to commit, tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=dungnguyen/14, BranchQual=, localId=14] status=STATUS_NO_TRANSACTION; - nested throwable: (java.lang.OutOfMemoryError: Java heap space) at org.jboss.aspects.tx.TxPolicy.handleEndTransactionException(TxPolicy.java:198) at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:180) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:87) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:197) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:227) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:398) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239) Caused by: org.jboss.tm.JBossRollbackException: Unable to commit, tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=dungnguyen/14, BranchQual=, localId=14] status=STATUS_NO_TRANSACTION; - nested throwable: (java.lang.OutOfMemoryError: Java heap space) at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:372) at org.jboss.tm.TxManager.commit(TxManager.java:240) at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:175) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:87) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:197) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:227) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:398) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239) at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:190) at org.jboss.remoting.Client.invoke(Client.java:525) at org.jboss.remoting.Client.invoke(Client.java:488) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:41) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:40) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:78) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102) at $Proxy0.save(Unknown Source) at com.inet.test.BigFileTest.main(BigFileTest.java:62) Caused by: java.lang.OutOfMemoryError: Java heap space Please show me a way to solved this error. Many thanks, Dung Nguyen. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040225#4040225 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040225

19 years

1
0
0 / 0

[JBoss Seam] - Re: Being redirected to the same page

by petemuir

And the JSF 1.2 RI outputs the errors displayed in h:messages to the console! Woooooooo :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040224#4040224 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040224

19 years

1
0
0 / 0

[JBoss Seam] - Re: Being redirected to the same page

by CptnKirk

Put an <h:messages> on your page. Skipping DOB is likely causing a conversion error, which returns you to the same page. But since you aren't displaying any error messages it can be a little confusing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040223#4040223 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040223

19 years

1
0
0 / 0

[JBoss Seam] - Re: #160; becomes a funny character on error page

by henrik.lindberg

Found that if I change the character encoding in my template to "iso-8859-1" the faulty error page shows up correct in all situations. To fix the problem I will create a separate template for the 404 page using iso-8859-1 and let the other pages have UTF-8. Curious if anyone has any ideas about the cause of the problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040222#4040222 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040222

19 years

1
0
0 / 0

[Security & JAAS/JBoss] - Re: The neverending logout topic

by Vellmont

I think I've found the root of my problem. Basic Authentication. Not many references talk about it, but it would appear that one of the major architectural differences between basic, and form based authentication is that basic authentication has no concept of a logged in user. The browser sends the credentials every time you access a protected page. It's essentially impossible to "logout" a user from a website using basic authentication because they aren't logged in. The only way to make a webpage inaccessible to a user with a site using basic authentication is to get their browser to throw away the credentials. That means restarting the browser, or clearing out cookies. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040221#4040221 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040221

19 years

1
0
0 / 0

[JBoss Portal] - Re: remove the drag and drop but keep portlet decoration

by FredF

I found out that I have the region reference in the RegionTagHandler. Now I can write my own regiontag and provide the rendercontext with the ThemeConstants.PORTAL_AJAX_OBJECT_DISABLED to the renderer. The question is if region.setProperty(ThemeConstants.PORTAL_AJAX_OBJECT_DISABLED, "true"); will write the property to the portal database or just be used in the particular page request. What happens if I set this property on a region. Will it be persisted or just used in the request? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040218#4040218 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040218

19 years

1
0
0 / 0

[JBoss jBPM] - Re: conditional trans in 3.2 - deprecated syntax doesn't wor

by dario.oliveros

I could not get 'condition' working when deploying my process definition to JBoss AS. It used to work in 3.1.3, but not 3.2. Here's my PD: <?xml version="1.0" encoding="UTF-8"?> | | <process-definition | xmlns="" name="sample"> | <swimlane name="swimlane1"> | <assignment expression="user(ernie)"></assignment> | </swimlane> | <start-state name="start1"> | <transition name="" to="task1"></transition> | </start-state> | <task-node name="task1"> | <task name="task1" swimlane="swimlane1"> | <controller> | <variable name="var1" access="read,write,required"></variable> | </controller> | </task> | <transition name="t1" to="decision1"></transition> | </task-node> | <decision name="decision1"> | <transition name="1" to="end1"> | <condition>#{contextInstance.variables.var1 == '1'}</condition> | </transition> | <transition name="2" to="task2"> | <condition>#{contextInstance.variables.var1 == '2'}</condition> | </transition> | </decision> | <end-state name="end1"></end-state> | <task-node name="task2"> | <task name="task2" swimlane="swimlane1"> | <controller> | <variable name="var1" access="read"></variable> | <variable name="var2" access="read,write,required"></variable> | </controller> | </task> | <transition name="" to="end1"></transition> | </task-node> | </process-definition> "cristim1979" wrote : correction (condition tags missing): | | | | <condition> x == 'xxx' </condition> | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040217#4040217 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040217

19 years

1
0
0 / 0

[JBoss Tools (users)] - Re: This IDE won't update?

by max.andersen＠jboss.com

not sure what we can do about that. eclipse 3.3 requires wtp 2.x to work and that is not something we can verify against yet. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040216#4040216 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040216

19 years

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 April 2007