August 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3274) HTTPS LInks Contain Wrong Port

by Arron Ferguson (JIRA)

HTTPS LInks Contain Wrong Port ------------------------------ Key: JBSEAM-3274 URL: https://jira.jboss.org/jira/browse/JBSEAM-3274 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.3.CR1, 2.0.2.SP1 Environment: Ubuntu 7.10, Tomcat 6.0, Seam 2.0.2/2.0.3 Reporter: Arron Ferguson Priority: Blocker As per what Shane Bryzak suggested in this thread (Shane suggested that I assign it to him but I couldn't find that feature in this web form): http://www.seamframework.org/Community/SeamAndHTTPS I am submitting this bug report. Using Seam 2.0.2/2.0.3 with Tomcat 6, if you have pages in your web app that switch between different protocols (i.e., between HTTP and HTTPS), the Seam links are not using the correct port. This bug is reproducible 100% of the time. In order to reproduce, have Tomcat 6 running (you don't need a DB) and ensure that Tomcat 6 has the following lib in its $CATALINA_HOME/lib folder: el-api.jar The application must contain the following libs in it's class path as well: antlr.jar asm.jar cglib.jar commons-beanutils.jar commons-codec-1.3.jar commons-collections.jar commons-digester.jar commons-lang.jar commons-logging.jar dom4j.jar ejb-api.jar javassist.jar jboss-archive-browsing.jar jboss-el.jar jboss-seam-debug.jar jboss-seam-ioc.jar jboss-seam.jar jboss-seam-ui.jar jsf-api.jar jsf-facelets.jar jsf-impl.jar jstl.jar jta.jar lucene-core.jar persistence-api.jar spring.jar Your Tomcat server.xml file (found in $CATALINA_HOME/conf folder) should uncomment the following: <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" /> Don't worry about the fact that you're not specifying the keystore, if you've set up the keystore, Tomcat 6 will find it (new feature, saves typing). Having said that, you'll need to have set up the keystore (set up on your OS which is pretty brainless on either Windows or Linux) for Tomcat as per the following guide from Apache: http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html Don't worry, it's a pretty easy-to-follow set of steps creating a keystore (should take no longer than five minutes - especially if you use the default values that the quick tutorial says to use). Your pages.xml file looks like this (copy/paste): <?xml version="1.0" encoding="UTF-8"?> <pages xmlns="http://jboss.com/products/seam/pages" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.com/products/seam/pages http://jboss.com/products/seam/pages-2.0.xsd" http-port="8080" https-port="8443" no-conversation-view-id="/index.xhtml" login-view-id="/index.xhtml"> <page view-id="*" scheme="http" /> <page view-id="/register.xhtml" scheme="https"/> </pages> Also, make sure you do NOT specify any sort of security constraints in your web.xml file since we are already specifying protocol choices in the above pages.xml file (I found this out the hard way). Create a Facelets template as (copy/paste): <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets"> <head> <title>Test HTTP and HTTPS Pages</title> </head> <body> <ui:insert name="body"><div>Hello Facelets</div></ui:insert> </body> </html> Based on the template, create two pages. The first page is the index page which uses the default HTTP and so port 8080 from Tomcat default port (copy/paste): <?xml version='1.0' encoding='UTF-8' ?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:s="http://jboss.com/products/seam/taglib" > <body> <ui:composition template="./template.xhtml"> <ui:define name="body"> This page is http://localhost:8080/test/index.html <s:link view="/register.xhtml" value="register"/> Here's a Seam s:link to the register page: Here's a regular HTML anchor to the register page: <a href="./register.html">register</a> </ui:define> </ui:composition> </body> </html> Next is the register page which is using SSL (and so port 8443 in Tomcat 6 by default, copy/paste): <?xml version='1.0' encoding='UTF-8' ?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:s="http://jboss.com/products/seam/taglib" > <body> <ui:composition template="./template.xhtml"> <ui:define name="body"> This page is defined as an HTTPS page (i.e., using SSL) within the pages.xml file and thus under Seam 2.0.3 under Tomcat 6 is actually at: https://localhost:8443/test/register.html Go back to the index.html page which is not using SSL (so at port 8080): <s:link view="/index.xhtml" value="index"/> Here's a Seam s:link to the index page: Here's a regular HTML anchor to the index page: <a href="./index.html">index</a> </ui:define> </ui:composition> </body> </html> Once you start up Tomcat 6 and deploy your web app, if you type the URL of your index.html file you should see the page rendered. Check the source of that page (the index.html page) and take a look at Seam's s:link URL. It is: https://localhost:8080/test/register.html?conversationId=1 Assuming it's the first conversation started (otherwise the conversation id will be n). Notice the wrong protocol (8080). It should be 8443 due to what we specified in the pages.xml file. This appears to be a bug - in the very least seam link elements should be able to specify the correct protocol if the pages.xml file states a particular protocol for a particular page. Let me know if you have any other questions, I will provide code, confirmation files as requested. -- 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

17 years, 7 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3295) Major reentrancy problem with "Application Scope" components and injection/disinjection

by Denis Forveille (JIRA)

Major reentrancy problem with "Application Scope" components and injection/disinjection --------------------------------------------------------------------------------------- Key: JBSEAM-3295 URL: https://jira.jboss.org/jira/browse/JBSEAM-3295 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.2.SP1 Environment: WebSphere v6.1.0.17 in POJO Mode Reporter: Denis Forveille Priority: Blocker There is a major reentrancy problem with "Application Scope" components and injection/disinjection As in any component @In dependent object are injected/disinjected with the BijectionInterceptor interceptor As there is one instance of BijectionInterceptor per Component (It seems), there is only one instance of BijectionInterceptor in the JVM for an Application Scope Component, instance shared by all threads With that in mind, take: - 2 running thread (T1, T2) - One application scope component (C1) with many@In attributes (All referecing Application Scope components too..) T1 enters method M1 of C1. BijectionInterceptor inject @In depedencies of C1, and set the "reentrant" attribute of the instance of BijectionInterceptor attached to C1 to "true" T2 enters method M1of C1. BijectionInterceptor does nothing as "reentrant" is true T1 exits method M1 of C1. As this is thios thread (T1) that set "reentrant" initially, it performs the "disinjection" and set all the @In attribues of C1 to null T2 then fails with NPE as all the @In attributes of C1 are set to null !!!!! Core of the org.jboss.seam.core.BijectionInterceptor class: private boolean reentrant; //OK, since all Seam components are single-threaded @AroundInvoke public Object aroundInvoke(InvocationContext invocation) throws Exception{ if (reentrant) { return invocation.proceed(); } else { reentrant = true; try { Component component = getComponent(); boolean enforceRequired = !component.isLifecycleMethod( invocation.getMethod() ); component.inject( invocation.getTarget(), enforceRequired ); Object result = invocation.proceed(); component.outject( invocation.getTarget(), enforceRequired ); component.disinject( invocation.getTarget() ); return result; } finally { reentrant = false; } } } -- 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

17 years, 7 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3083) urlBase on <m:message> does not work

by Dan Allen (JIRA)

urlBase on <m:message> does not work ------------------------------------- Key: JBSEAM-3083 URL: http://jira.jboss.com/jira/browse/JBSEAM-3083 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.0.A1, 2.0.2.SP1 Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.3.CR1, 2.1.0.BETA1 The attribute urlBase on <m:message> is broken in two fundamental ways. First, the logic as to whether to use the urlBase doesn't make any sense at all, resulting in the urlBase never being used. The second problem is that EL value expressions in the urlBase are not getting resolved. I am proposing a strategy as part of this fix. If the urlBase is used, it is taken verbatim, without appending the current context path. The reason is, if urlBase is overridden, it may be because it is pointing to a completely different application. If the developer want to reuse the context path, the expression #{facesContext.externalContext.requestContextPath} must be included in the urlBase attribute. -- 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

17 years, 7 months

2
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2996) Imported seam-gen project does not show content assist on project specific components

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-2996?page=com.atlassian.jira.pl... ] Pete Muir updated JBSEAM-2996: ------------------------------ Fix Version/s: 2.1.0.BETA2 (was: 2.1.0.BETA1) Slip, out of time > Imported seam-gen project does not show content assist on project specific components > ------------------------------------------------------------------------------------- > > Key: JBSEAM-2996 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2996 > Project: Seam > Issue Type: Bug > Components: Tools > Affects Versions: 2.0.2.CR2 > Reporter: Jay Balunas > Assignee: Max Rydahl Andersen > Fix For: 2.1.0.BETA2 > > > Following seam release-process.txt I imported a project I created with seam-gen using 2.0.2.CR2. > I used "import an existing project" option. Then added seam support to the project using a seam runtime I configured with 2.0.2.CR2. > When I opened a view file and tried out the content assist it showed a lot of Seam components, but none of the components in the project itself. -- 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

17 years, 7 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2508) openId support components

by koen handekyn (JIRA)

openId support components ------------------------- Key: JBSEAM-2508 URL: http://jira.jboss.com/jira/browse/JBSEAM-2508 Project: JBoss Seam Issue Type: Feature Request Reporter: koen handekyn Priority: Optional provide standard components to allow easy setup for openId support in a seam application. the seam identity contains both username and password fields. an openId identity consist soly of an identity string. ideally an openId authenticator takes in just a single openId identity, performs the openId logn procedures and concludes (in case of succesful authentication in a logged in session, with the identifier confirmed. -- 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

17 years, 7 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3296) actions in .xhtml specified without parentheses do not match equivalent pages.xml navigation rules that do have parentheses, and vice verse

by Ian Springer (JIRA)

actions in .xhtml specified without parentheses do not match equivalent pages.xml navigation rules that do have parentheses, and vice verse -------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3296 URL: https://jira.jboss.org/jira/browse/JBSEAM-3296 Project: Seam Issue Type: Bug Components: Framework Affects Versions: 2.0.1.GA Reporter: Ian Springer I was banging my head against the wall for quite a while before I figured out why my pages.xml nav rule wasn't kicking in. In my .xhtml file, I had: <h:commandButton value="#{messages['button.ok']}" action="#{operationAction.invokeOperation}"/> which was not matching the following rule in my pages.xml: <navigation from-action="#{operationAction.invokeOperation()}"> <redirect view-id="/secure/resourceInstanceOperation.xhtml"/> </navigation> (Note the h:commandButton action does not have parens, but the navigation from-action does have parens. action.foo should match action.foo(), as well action.foo, and vice verse, being as they mean the exact same thing semantically. The current behavior is not intuitive and will cost users a lot of wasted time and frustration. Note, this bug exists for actions on s:buttons, as well as actions on h:commandButtons. -- 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

17 years, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3289) 2 versions of ant used in the project distribution

by Jay Balunas (JIRA)

2 versions of ant used in the project distribution -------------------------------------------------- Key: JBSEAM-3289 URL: https://jira.jboss.org/jira/browse/JBSEAM-3289 Project: Seam Issue Type: Bug Components: Build Affects Versions: 2.0.3.CR2, 2.1.0.BETA2 Reporter: Jay Balunas Priority: Critical Fix For: 2.0.3.CR2, 2.1.0.BETA1 2 versions of ant used in the project distribution seam/lib/ant.jar --> 1.6.5 seam/build/lib/ant.jar --> 1.7.0 Should standardize on 1.7.00 -- 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

17 years, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1891) Decouple page fragment caching from JBoss Cache

by Christian Bauer (JIRA)

Decouple page fragment caching from JBoss Cache ----------------------------------------------- Key: JBSEAM-1891 URL: http://jira.jboss.com/jira/browse/JBSEAM-1891 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Christian Bauer Priority: Minor The code in UICache and PojoCache only works with this component: return (org.jboss.cache.aop.PojoCache) Component.getInstance(PojoCache.class, ScopeType.APPLICATION); Make this generic so that other cache providers can be used. -- 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

17 years, 7 months

6
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3293) make itext created pdf file names configurable

by arne anka (JIRA)

make itext created pdf file names configurable ---------------------------------------------- Key: JBSEAM-3293 URL: https://jira.jboss.org/jira/browse/JBSEAM-3293 Project: Seam Issue Type: Feature Request Affects Versions: 2.0.1.GA Reporter: arne anka pdf files created with itext have as file name the name of the facelet they were created from. ie the page creating my pdf is named foo.xhtml thus the created pdf file is named foo.pdf. i'd like to be able to configure the name depending on arbitrary criteria (date, time, username, what ever ...) -- 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

17 years, 7 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3288) Booking example - wrong message is displayed when canceling hotel booking

by Jozef Hartinger (JIRA)

Booking example - wrong message is displayed when canceling hotel booking ------------------------------------------------------------------------- Key: JBSEAM-3288 URL: https://jira.jboss.org/jira/browse/JBSEAM-3288 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.A1, 2.0.2.SP1, 1.2.1.GA Environment: JDK 5 update 16 JBoss AS 4.2.3.GA Fedora 9 Reporter: Jozef Hartinger Priority: Minor 1.) Log in and make at least 2 reservations 2.) Cancel one of the reservations 3.) Message confirming reservation cancelation will contain wrong confirmation number Looks like all the booking derives are affected. -- 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

17 years, 7 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2008