February 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2305) GWT 1.4 DTO support for java.io.Serializable

by darren hartford (JIRA)

GWT 1.4 DTO support for java.io.Serializable -------------------------------------------- Key: JBSEAM-2305 URL: http://jira.jboss.com/jira/browse/JBSEAM-2305 Project: JBoss Seam Issue Type: Task Components: Remoting Affects Versions: 2.0.0.GA Reporter: darren hartford Assigned To: Shane Bryzak GWT 1.4 supports java.io.Serializable, but the SEAM remoting to GWT still --requires-- any DTO to implement com.google.gwt.user.client.rpc.IsSerializable. This is not documented anywhere and should be documented for 2.0.0.GA (to avoid frustrations) as well as examine support in the future to no longer require IsSerializable for SEAM-GWT-Remoting. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2144) s:link builds absolute path URL with private IP address

by koen handekyn (JIRA)

s:link builds absolute path URL with private IP address ------------------------------------------------------- Key: JBSEAM-2144 URL: http://jira.jboss.com/jira/browse/JBSEAM-2144 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR1 Environment: the same on windows/linux with jboss 4.2.1 Reporter: koen handekyn link to view "/example.xhtml" becomes "http://10.0.0.1:8080/example.seam" (including private server address and protocol) which breaks when run behind an apache proxy from my code: <li><s:link view="/mobistar/portal.xhtml" value="portal" /></li> becomes rendered as <li><a href="http://localhost:8080/up-docstore/mobistar/portal.seam?cid=44" id="j_id15">portal</a></li> while it should be <li><a href="/up-docstore/mobistar/portal.seam?cid=44" id="j_id15">portal</a></li> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3946) LdapIdentityStore can not use backup server (failover)

by Raimund Hölle (JIRA)

LdapIdentityStore can not use backup server (failover) ------------------------------------------------------ Key: JBSEAM-3946 URL: https://jira.jboss.org/jira/browse/JBSEAM-3946 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.1.GA, 2.1.1.CR2, 2.1.1.CR1, 2.1.0.SP1 Reporter: Raimund Hölle Since LdapIdentityStore assembles the provider URL internally, it is not possible to use extended URL's, e. g., a primary and a backup server like this: env.setProperty(Context.PROVIDER_URL, "ldap://srv01:389 ldap://srv02:389"); It would be nice if we would be able to set the providerUrl directly. For compatibility reasons, i suggest the following change: // new property settable from components.xml private String providerUrl = null; protected final InitialLdapContext initialiseContext(String principal, String credentials) throws NamingException { ... String url = providerUrl; if (url == null || url.equals("")) { url = String.format("ldap://%s:%d", getServerAddress(), getServerPort()); } env.setProperty(Context.PROVIDER_URL, url); ... Additionally it would be nice if initialiseContext() wouldn't be final so we are able to extend the class. Regards, Raimund -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3225) Seam Remoting JS memory leak in IE

by Joshua Davis (JIRA)

Seam Remoting JS memory leak in IE ---------------------------------- Key: JBSEAM-3225 URL: https://jira.jboss.org/jira/browse/JBSEAM-3225 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.0.2.GA, 2.0.1.GA Environment: IE 6 Reporter: Joshua Davis Assignee: Shane Bryzak Issuing many Seam Remoting calls can cause IE6 to fail with an 'out of memory' error. The problem seems to be related to the fact that the AJAX request object is a COM object in IE, so it doesn't get garbage collected in the same way. On a P3 machine with 512M of RAM, IE6 can handle about 30k calls before failing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2292) Resources from resource servlet can't be re-rendered

by Christian Bauer (JIRA)

Resources from resource servlet can't be re-rendered ---------------------------------------------------- Key: JBSEAM-2292 URL: http://jira.jboss.com/jira/browse/JBSEAM-2292 Project: JBoss Seam Issue Type: Bug Components: JSF Reporter: Christian Bauer Found this after using the captcha: <div class="input"> <a:region> <s:validateAll> <h:graphicImage value="/seam/resource/captcha" style="vertical-align:text-bottom;"/> <h:inputText tabindex="1" size="6" maxlength="6" required="true" id="verifyCaptcha" value="#{captcha.response}"> <a:support status="#{statusId}" event="onblur" reRender="verifyCaptchaEntry"/> </h:inputText> </s:validateAll> </a:region> </div> This is a re-rendered s:decorate form field, so that onblur we get a new challenge (if the captcha repsonse was wrong). However, the graphicImage is not reloaded from the server, the browser caches it. To prevent browser caching, this is a quick hack: <div class="input"> <a:region> <s:validateAll> <h:graphicImage value="/seam/resource/captcha?nocache=#{wiki:generateRandomNumber()}" style="vertical-align:text-bottom;"/> <h:inputText tabindex="1" size="6" maxlength="6" required="true" id="verifyCaptcha" value="#{captcha.response}"> <a:support status="#{statusId}" event="onblur" reRender="verifyCaptchaEntry"/> </h:inputText> </s:validateAll> </a:region> </div> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3401) Translating Seam into your own language (pt-BR)

by Ricardo Martinelli Oliveira (JIRA)

Translating Seam into your own language (pt-BR) ----------------------------------------------- Key: JBSEAM-3401 URL: https://jira.jboss.org/jira/browse/JBSEAM-3401 Project: Seam Issue Type: Feature Request Components: Documentation Translation Reporter: Ricardo Martinelli Oliveira I would like to begin the process of translating Seam into Portuguese. (pt-BR) Language: Portuguese Locale: Brazil -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1712) Allow options for SMPC per Nested Conversation

by Andy Gibson (JIRA)

Allow options for SMPC per Nested Conversation ---------------------------------------------- Key: JBSEAM-1712 URL: http://jira.jboss.com/jira/browse/JBSEAM-1712 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.BETA1 Environment: Windows XP, Seam 2.0 Beta, JBoss 4.2 Reporter: Andy Gibson I'd like to request the option to specify that a nested conversation gets it's own entity manager instance as opposed to sharing it with it's parent conversation and other nested conversations. The problem with nested conversations is that you can't actually use them to edit multiple entities since when you flush the PC, you flush it for all conversations. This makes nested conversations only really useful for browsing data, and creating new top level conversation to edit items to isolate the flushes. The only alternative is to use a non-Seam managed PC, and make use of the "PC per stateful bean" rule to map a single PC to a single backing bean, but you lose the benefits of a seam managed PC. What might be nice is something like : @Begin(nested=true, newPC=true) and <begin-conversation nested="true" newPC="true"/> which would indicate that this new nested conversation gets it's own entity manager instance. The attribute would be ignored if this wasn't a nested conversation, and obviously, by default, the attribute is set to false, and a shared PC would be used in the nested conversation in such cases. I'm already using one PC per conversation by using top level conversations to edit items, I'd just like to use one PC per nested conversation (where applicable) to get the benefits of nested conversations. There are a couple of posts in the forums where I've touched on some of my problems with this issue : http://www.jboss.com/index.html?module=bb&op=viewtopic&t=111681 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=111384 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=113362 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

7
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1498) inject JBoss service EJB with @In

by koen handekyn (JIRA)

inject JBoss service EJB with @In --------------------------------- Key: JBSEAM-1498 URL: http://jira.jboss.com/jira/browse/JBSEAM-1498 Project: JBoss Seam Issue Type: Feature Request Components: EJB3 Reporter: koen handekyn Priority: Minor to inject a Service EJB into a seam component, for consistency it would certainly be very nice to be able to inject it within SEAM with @In and optionally adding an @Name attribute to the service class. it would be more consistent and shorter than the standard jboss approach (below) private GlobalConfigurationMBean globalConfiguration; @Depends ("upr:service=globalConfiguration") public void setGlobalConfiguration(final GlobalConfigurationMBean globalConfiguration) { this.globalConfiguration = globalConfiguration; } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1707) @Destroy method on APPLICATION scope bean throws IllegalState(no context) at server stop time

by Frits Jalvingh (JIRA)

@Destroy method on APPLICATION scope bean throws IllegalState(no context) at server stop time --------------------------------------------------------------------------------------------- Key: JBSEAM-1707 URL: http://jira.jboss.com/jira/browse/JBSEAM-1707 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Environment: Tomcat 6.0.10, JavaBean mode, Hibernate 3.2.3, HBEM 3.3.1 Reporter: Frits Jalvingh I have a bean defined as follows: @Name("initBean") @Startup() @Scope(ScopeType.APPLICATION) public class InitBean { containing a method: @Destroy public void destroy() { Builder.getInstance().terminate(); BuildBot.getInstance().stop(); } It is meant to shutdown some daemons when the server stops. When the server stops I get an exception: 01:15:39,703 WARN [Component] Exception calling component @Destroy method: initBean java.lang.IllegalStateException: no event context active at org.jboss.seam.web.ServletContexts.instance(ServletContexts.java:40) at org.jboss.seam.web.Parameters.getRequestParameters(Parameters.java:39) at org.jboss.seam.faces.Parameters.getRequestParameters(Parameters.java:64) at org.jboss.seam.Component.injectParameters(Component.java:1334) at org.jboss.seam.Component.inject(Component.java:1304) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:45) 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:106) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:151) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:87) at to.etc.saram.beans.InitBean_$$_javassist_0.destroy(InitBean_$$_javassist_0.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:124) at org.jboss.seam.Component.callComponentMethod(Component.java:1957) at org.jboss.seam.Component.callDestroyMethod(Component.java:1888) at org.jboss.seam.Component.destroy(Component.java:1217) at org.jboss.seam.contexts.Contexts.destroy(Contexts.java:251) at org.jboss.seam.contexts.Lifecycle.endApplication(Lifecycle.java:52) at org.jboss.seam.contexts.ServletLifecycle.endApplication(ServletLifecycle.java:121) at org.jboss.seam.servlet.SeamListener.contextDestroyed(SeamListener.java:39) at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3866) at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4502) at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1068) at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1068) at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:448) at org.apache.catalina.core.StandardService.stop(StandardService.java:510) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744) at org.apache.catalina.startup.Catalina.stop(Catalina.java:602) at org.apache.catalina.startup.Catalina.start(Catalina.java:577) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) which seems to be caused by the bean Injector trying to access the request context which of course is no longer there. The bean contains only a single injected thingy which is the entityManager. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1879) Magic mime type detection support

by Christian Bauer (JIRA)

Magic mime type detection support --------------------------------- Key: JBSEAM-1879 URL: http://jira.jboss.com/jira/browse/JBSEAM-1879 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Christian Bauer Priority: Minor A component I can call to find out what mime type a particular byte[] or ByteInputStream is. The only existing solution in Java is http://sourceforge.net/projects/jmimemagic/ but it's basically an unmaintained half-working pile of junk. It's interesting that nobody ever build a simple port of file(1), which you get on every unix box, together with a fantastic (/etc/magic or /usr/share/file/magic on the Mac) database of magic bytes found in file headers. We should just take that database (or the source database from which it is generated) and write our own file(1) for Seam. Search for "mime magic java" with Google and you see why it's needed. Try "file myfile.foo" on every unix box (well, younger than 10 years) and you see how it works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2009