October 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2635) Support for OC4J - 10.1.3

by Chris Simons (JIRA)

Support for OC4J - 10.1.3 ------------------------- Key: JBSEAM-2635 URL: http://jira.jboss.com/jira/browse/JBSEAM-2635 Project: JBoss Seam Issue Type: Feature Request Components: Platform interoperability Environment: Solaris, Linux, Windows Reporter: Chris Simons Fix For: 2.0.0.GA To gauge interest in Seam support, whether it be detailed documentation or actual changes to baseline, within the Oracle Container For Java (OC4J) 10.1.3. 10.1.3 is also known as Oracle Application Server 10g Release 3. Our personal example... After receiving the go-ahead to use the JBoss AS on our application development contract to a U.S. military organization we were disappointed to find that ongoing software standardization efforts, of which were not communicated to contractors, are starting to take affect. Our client is currently running a distributed Oracle AS 10g Release 2 infrastructure but we're hoping we can convince them to move to Release 3 in the near future. Therefore, 10.1.3 support for Seam, seeing as we have invested at least a few months into the development cycle, might prove to be critical. Please vote for this issue if you are interested in supporting this feature request. -- 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, 3 months

7
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-216) Add simple URLs to s:link tag

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-216?page=com.atlassian.jira.plu... ] Pete Muir closed JBSEAM-216. ---------------------------- Resolution: Rejected I don't really see the point of this. > Add simple URLs to s:link tag > ----------------------------- > > Key: JBSEAM-216 > URL: https://jira.jboss.org/jira/browse/JBSEAM-216 > Project: Seam > Issue Type: Feature Request > Components: JSF Controls > Reporter: Dig > Attachments: faces-config.xml, HtmlLink.java > > > The s:link tag does not currently support custom html links but linking to actions and to JSF views is supported. By extending the current s:link implementation Seam can support URL rewriting techniques. This will enable users to hide JSF and Seam URLs behind custom URLs. > For further background please refer to the forum post linked from this entry. > I propose to add a new attribute to the s:link tag (named 'link', 'href' or similar). This attribute would contain the desired URL to link to. The s:link tag would process this URL as for other URLs by adding the conversation ID, etc. Here is an example: > <s:link value="view" link="#{mycomponent.niceUrl}"/> > The users application would be responsible for creating the URL and for ensuring that a request to that URL can be processed (url rewriting). > As a proof of concept I have already implemented this feature. Some details of my changes are in the forum post. The modified files are HtmlLink.java and faces-config.xml. I will attempt to attach these files to this entry. > It would be great if this feature could be added to release 1.0 of Seam as I'm currently using this functionality now! Many thanks in advance. -- 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, 3 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2121) Support for an SMPC per nested conversation

by Jacob Orshalick (JIRA)

Support for an SMPC per nested conversation ------------------------------------------- Key: JBSEAM-2121 URL: http://jira.jboss.com/jira/browse/JBSEAM-2121 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.CR2 Reporter: Jacob Orshalick Currently an open issue and ongoing discussion with respect to the existing nested conversation implementation is master-details editing. If a Seam-managed Persistence Context (SMPC) is shared between the outer and nested conversation, any changes made in the nested conversation will be flushed by the SMPC in the outer conversation and vice versa if a flush is initiated. Support for initialization of a new SMPC within a nested conversation would allow state changes in the nested conversation to be confined to that conversation, thus resolving this issue. Perhaps something like the following could be supported: <persistence:managed-persistence-context name="bookingDatabase" auto-create="true" per-nested-conversation-"true" persistence-unit-jndi-name="java:/EntityManagerFactories/bookingData"/> It would also be nice to be able to use annotations (i.e. something similar to @PerNestedConversation). For further information on this approach please see the forum posting. Thanks. -- 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, 3 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1009) optionally login-require in a more specific page should be able to override a wildcard login-require

by Leo Baschy (JIRA)

optionally login-require in a more specific page should be able to override a wildcard login-require ---------------------------------------------------------------------------------------------------- Key: JBSEAM-1009 URL: http://jira.jboss.com/jira/browse/JBSEAM-1009 Project: JBoss Seam Issue Type: Patch Components: Security Affects Versions: 1.2.0.GA Environment: all Reporter: Leo Baschy This should be optional to switch on, so no one's existing expectations of security get broken. The point is about having a generic wildcard <page view-id="*" scheme="http" login-required="true"> to secure the whole site, and then allowing specific pages or specific wildcards to have login-required="false". E.g. for a registration (with preview) section as one cannot be logged in if one isn't registered yet. Some may suggest instead forcing pages into dedicated secure and not-secure directories, but in reality if there are multiple reasons to force pages into directories different ways (security, hyperlink management, publishability of URLs, etc.), one cannot serve all of them. -- 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, 3 months

6
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1384) Support for Eclipse WTP in seam-gen projects

by Mariusz Smykula (JIRA)

Support for Eclipse WTP in seam-gen projects -------------------------------------------- Key: JBSEAM-1384 URL: http://jira.jboss.com/jira/browse/JBSEAM-1384 Project: JBoss Seam Issue Type: Feature Request Components: Test Harness, Tools Affects Versions: 1.2.1.GA Reporter: Mariusz Smykula Auto deploy system and support for web application in Eclipse WTP is simple, easy and fast. This is much better solution than deploying with ant. Eclipse WTP 2.0 is comming in near time, so I think better support for WTP will be good. Now, users of WTP cant use Dynamic Web Project for working with application. -- 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, 3 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2141) Support for EL without reflection for better JSF performance

by Mikhail Grushinskiy (JIRA)

Support for EL without reflection for better JSF performance ------------------------------------------------------------ Key: JBSEAM-2141 URL: http://jira.jboss.com/jira/browse/JBSEAM-2141 Project: JBoss Seam Issue Type: Feature Request Components: EL Reporter: Mikhail Grushinskiy Support for EL without reflection for better JSF performance. The idea is to add a new tag to declare types of the variables used on a page and use this type information to compile EL expressions into byte-code during initialization (deployment) Ex: If the page contains at the beginning <s:typedef var="myBean" class="com.company.package.Bean" /> then all EL expressions can be compiled into bytecode at initialization time (and no reflection will be used for myBean access. <h:outputText value="#{myBean.subBean.property}" rendered="#{myBean.renderText}" /> Some examples of implementation of compiled EL can be found here http://sixlegs.com/blog/java/compiled-el.html This should help much with JSF performance issues Thanks -- 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, 3 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2864) Injection not working with concurrent clients

by Marcell Barbacena (JIRA)

Injection not working with concurrent clients --------------------------------------------- Key: JBSEAM-2864 URL: http://jira.jboss.com/jira/browse/JBSEAM-2864 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.GA, 2.0.1.CR2, 2.0.1.CR1 Environment: Jboss AS 4.2.2.GA, Windows Reporter: Marcell Barbacena When I was loading testing my application I was getting some NPE. I narrowed down the error and created the example app based on a seam-gen one (just stripped the lib directory). Basically, what I want to execute the place GET at the following URLs: http://localhost:8080/myproject/performance/startsession.seam http://localhost:8080/myproject/performance/start.seam http://localhost:8080/myproject/performance/search.seam?parameter=1&cid=2 http://localhost:8080/myproject/performance/end.seam?cid=2 If after you start jboss you execute the above it goes ok. The debug page shows that the long-running conversation is gone and everything is ok. Then I created a JMeter test, just capturing the "cid" from start, and use it at search and end page (see attached jmeter test). If you run the script with 1 thread no loop, it goes ok. If you run with 5 (in my pc) it goes ok. But when you put more then 20, it starts to get NPE at SimpleAction#search when it calls the DAO. The log at search.xhtml shows the error and the sysos at SimpleAction#search shows it as well. Please, provide a workaround in 2.0.1.CR1. -- 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, 3 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2198) Hot deployment of Seam EJB3 components

by Pete Muir (JIRA)

Hot deployment of Seam EJB3 components -------------------------------------- Key: JBSEAM-2198 URL: http://jira.jboss.com/jira/browse/JBSEAM-2198 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.CR3 Reporter: Pete Muir -- 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, 3 months

1
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1596) Unique Constraint Validator

by Pete Muir (JIRA)

Unique Constraint Validator --------------------------- Key: JBSEAM-1596 URL: http://jira.jboss.com/jira/browse/JBSEAM-1596 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Priority: Blocker We could have a generic unique constrain validator as part of the model validation. http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059691#4059691 -- 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, 3 months

8
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-164) Kill all conversations

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-164?page=com.atlassian.jira.plu... ] Pete Muir commented on JBSEAM-164: ---------------------------------- Stuart, I think your approach is correct, but we should offer this programatically as a method on Manager, more like Srinivasan has done. Srinivasan, doing this through a timeout isn't correct, otherwise I think what you have is ok - remove that stuff and I'll take a look again :-) > Kill all conversations > ---------------------- > > Key: JBSEAM-164 > URL: https://jira.jboss.org/jira/browse/JBSEAM-164 > Project: Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Fix For: 2.1.1.CR1 > > Attachments: kill-all-other-conversations.diff, seam-endall-patch-v1.diff > > > Users want an operation to kill all conversations, and they want that to happen in the same action as beginning a new conversation. -- 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, 3 months

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

seam-issues October 2008