October 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3119) Multiple WAR in EAR verification, example, and document

by Jay Balunas (JIRA)

Multiple WAR in EAR verification, example, and document ------------------------------------------------------- Key: JBSEAM-3119 URL: http://jira.jboss.com/jira/browse/JBSEAM-3119 Project: Seam Issue Type: Feature Request Components: Documentation Issues, Examples, Platform interoperability Affects Versions: 2.1.0.A1 Reporter: Jay Balunas Assigned To: Jay Balunas Fix For: 2.1.0.GA Create an example of two seam WAR applications inside of an EAR. There has been quite a bit of forum traffic on the subject and it would be good to nail down an example and document. There may also be errors and other issue that need to be worked out. An admin console type application to the standard booking application may be a good way to go. It would be a real world/useful example. -- 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, 11 months

16
61
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4393) seam-gen produces wrong persistence unit configuration for unit tests

by Christian Bauer (JIRA)

seam-gen produces wrong persistence unit configuration for unit tests --------------------------------------------------------------------- Key: JBSEAM-4393 URL: https://jira.jboss.org/jira/browse/JBSEAM-4393 Project: Seam Issue Type: Bug Reporter: Christian Bauer Assignee: Dan Allen I've just generated a seam-gen project from 2.2 head and added a unit test. The test setup is wrong in build.xml: <target name="buildtest" depends="init,compiletest,copytestclasses" description="Build the tests"> <copy todir="${test.dir}"> <fileset dir="${basedir}/resources"> <exclude name="META-INF/persistence*.xml"/> <exclude name="import*.sql"/> <exclude name="${project.name}-*-ds.xml"/> <exclude name="components-*.properties"/> </fileset> <fileset dir="${basedir}/view"/> </copy> <copy tofile="${test.dir}/META-INF/persistence.xml" file="${basedir}/resources/META-INF/persistence-test.xml"/> <copy tofile="${test.dir}/import.sql" file="${basedir}/resources/import-test.sql"/>   <copy tofile="${test.dir}/components.properties" file="${basedir}/resources/components-test.properties"> <filterset > <filter token="puJndiName" value="java:/${project.name}EntityManagerFactory"/> </filterset> </copy> <copy todir="${test.dir}" flatten="true"> <fileset dir="${src.test.dir}"> <include name="**/*Test.xml" /> </fileset> </copy> </target> The components.properties had hardcoded values for persistence unit configuration, which were wrong. I've added this filter to build.xml and modified the components-test.properties: # These properties are used to replace Ant-style tokens in the component descriptor (components.xml) at runtime. jndiPattern=#{ejbName}/local debug=true seamBootstrapsPu=true # Wrong! #seamEmfRef=#{entityManagerFactory} #puJndiName=#{null} # Fix! seamEmfRef=#{null} puJndiName=@puJndiName@ Also, the readme.txt in the generated test folder doesn't mention that this Ant target has to run before you run the tests in the IDE and that you have to add the ${test.dir} folder to your classpath and NOT create a module dependency on your core application build output classpath etc. I don't know how that works in Eclipse but in IntelliJ I had to create a separate module with a completely separate list of classpath entries, and enable the 'buildtest' Ant target before the test suite runs. -- 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, 11 months

3
4
0 / 0

[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, 11 months

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

16 years

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

16 years

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

16 years

2
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4096) Seam Remoting: connection hangs on IE 6 when the answer is fast

by Francesco Dandrea (JIRA)

Seam Remoting: connection hangs on IE 6 when the answer is fast --------------------------------------------------------------- Key: JBSEAM-4096 URL: https://jira.jboss.org/jira/browse/JBSEAM-4096 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.1.1.GA Reporter: Francesco Dandrea Assignee: Shane Bryzak Priority: Minor With IE when a remoting connection is fast, it hangs. In FF and Chrome it works. I did this following advice on: http://seamframework.org/Community/211GAIE7BugInRemotejs Since I didn't find the bug I opened this one. -- 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

16 years

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4455) Seamspace -- incorrect viewIds lead to missing page parameter propagation

by Wolfgang Schwendt (JIRA)

Seamspace -- incorrect viewIds lead to missing page parameter propagation -------------------------------------------------------------------------- Key: JBSEAM-4455 URL: https://jira.jboss.org/jira/browse/JBSEAM-4455 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.2.0.GA Environment: Seam 2.2 Rev. 11569 http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_2 Reporter: Wolfgang Schwendt Priority: Trivial When s:link and s:button are used in the facelets view template files of the Seamspace example, the JSF viewId to link to is written incorrectly. Right now in the Seamspace example, the viewId to link to is written as follows: s:link view="/friendrequest.seam" value="Send a friend request" propagation="none"... Instead of using the suffix/extension ".seam", the viewId to link to must be correctly written with the suffix/extension ".xhtml": s:link view="/friendrequest.seam" value="Send a friend request" propagation="none"... If ".seam" is used rather than ".xhtml", it leads to the missing propagation of page parameters. When an s:link/s:button is rendered, UISeamCommandBase.getUrl() retrieves the set of page parameters from Pages.getStringValuesFromModel(). The Pages component holds metadata for pages defined in pages.xml, including page parameters. When the wrong viewId is used, Pages.getStringValuesFromModel() does not find the page parameters for the JSF view to link to, and therefore page parameters are omitted when rendering the link. For example, when the viewID is written with '.seam', the link for sending a friend request is rendered with the target URL http://127.0.0.1:8080/seamspace/friendrequest.seam, but it should be http://127.0.0.1:8080/seamspace/friendrequest.seam?name=shadowman -- 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

16 years

2
8
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

16 years

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4202) I should be able to modify my profile without rewriting my password

by Francisco Jose Peredo Noguez (JIRA)

I should be able to modify my profile without rewriting my password ------------------------------------------------------------------- Key: JBSEAM-4202 URL: https://jira.jboss.org/jira/browse/JBSEAM-4202 Project: Seam Issue Type: Bug Components: Wiki Affects Versions: 2.1.1.GA Reporter: Francisco Jose Peredo Noguez Assignee: Christian Bauer If I enter my profile http://www.seamframework.org/userHome_d.seam?userId=XXXX and try to modify, for example, my Bio, or my WebSite, or anything but my password, I am still asked to rewrite my password. I should not have to do that, I already wrote my password to log in. -- 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

16 years

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues October 2009