February 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2621) debug page missing url-encoding for component viewing

by Nicklas Karlsson (JIRA)

debug page missing url-encoding for component viewing ----------------------------------------------------- Key: JBSEAM-2621 URL: http://jira.jboss.com/jira/browse/JBSEAM-2621 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.GA Environment: JBoss 4.2.2.GA Reporter: Nicklas Karlsson If I have a component named "käyttäjä", I can see it on the debug page but clicking on the link goes to .../debug.seam?name=käyttäjä&cid=1 and the component contents is not listed. The correct form in this case should be .../debug.seam?name=k%e4ytt%e4j%e4&cid=1 -- 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

18 years

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2676) JBossSeam-2.1-sun16 testsuite build failing

by Jay Balunas (JIRA)

JBossSeam-2.1-sun16 testsuite build failing ------------------------------------------- Key: JBSEAM-2676 URL: http://jira.jboss.com/jira/browse/JBSEAM-2676 Project: JBoss Seam Issue Type: Bug Components: Test Harness Affects Versions: 2.1.0.GA Reporter: Jay Balunas Assigned To: Pete Muir The JBossSeam-2.1-sun16 build started to fail on 2-19-08 with the following error turing the "jarui" target: java] [INFO] Parse config file /qa/services/hudson/hudson_workspace/workspace/JBossSeam-2.1-sun16/seam/ui/src/main/config/component/transformImageType.xml [java] [ERROR] Error on generate component [java] org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [java] at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:509) [java] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:285) [java] at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:400) [java] at org.apache.commons.digester.Digester.<init>(Digester.java:346) [java] at org.ajax4jsf.builder.config.BuilderConfig.parseConfig(BuilderConfig.java:119) [java] at org.ajax4jsf.builder.mojo.GenerateMojo.createConfig(GenerateMojo.java:253) [java] at org.ajax4jsf.builder.mojo.GenerateMojo.execute(GenerateMojo.java:92) [java] at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) [java] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) [java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) [java] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) [java] at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) [java] at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [java] Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [java] at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:420) [java] at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:502) [java] ... 24 more [java] Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Category [java] at java.lang.Class.getDeclaredConstructors0(Native Method) [java] at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) [java] at java.lang.Class.getConstructor0(Class.java:2699) [java] at java.lang.Class.getConstructor(Class.java:1657) [java] at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:417) [java] ... 25 more [java] [INFO] ------------------------------------------------------------------------ [java] [ERROR] BUILD ERROR [java] [INFO] ------------------------------------------------------------------------ [java] [INFO] Error in component generation -- 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

18 years

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2234) Documentation for "Integration Testing with Mock Data" is incomplete

by Eduardo Nieto (JIRA)

Documentation for "Integration Testing with Mock Data" is incomplete -------------------------------------------------------------------- Key: JBSEAM-2234 URL: http://jira.jboss.com/jira/browse/JBSEAM-2234 Project: JBoss Seam Issue Type: Release Components: Documentation Affects Versions: 2.0.0.GA Environment: Jboss SEAM 2.0.0.GA Project generated using seam-gen TestNg eclipse plugin PostgreSQL 8.1 Reporter: Eduardo Nieto I wanted to do a very simple test using the instructions in this chapter of the Reference Documentation: "31.3.1. Integration Testing with Mock Data" (http://docs.jboss.com/seam/2.0.0.GA/reference/en/html/testing.html#d0e19428) and I found two problems with the documentation: #1 Datasource value: Most users wouldn't know that TestNG plugin is going to look for datasources in the bootstrap/deploy directory. This should be explained and also that the "java:/DefaultDS" has no relation to the database used to generate the project. #2 Using DBMS that are not Hypersonic Tests using other DBMS should override three methods (disableReferentialIntegrity, enableReferentialIntegrity and editConfig). I've found this commented on the source of the class "DbUnitSeamTest" and this MUST be documented on the Reference Documentation -- 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

18 years

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1887) Session timeout results in javax.faces.application.ViewExpiredException

by Jacob Orshalick (JIRA)

Session timeout results in javax.faces.application.ViewExpiredException ----------------------------------------------------------------------- Key: JBSEAM-1887 URL: http://jira.jboss.com/jira/browse/JBSEAM-1887 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Reporter: Jacob Orshalick If the session times out, JSF throws a ViewExpiredException during the RESTORE_VIEW phase. The issue is described in more detail at the JBoss Form Reference. An example can be provided if required. -- 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

18 years

4
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2501) Action not being called on backing bean in default scope.

by Mark Richter (JIRA)

Action not being called on backing bean in default scope. --------------------------------------------------------- Key: JBSEAM-2501 URL: http://jira.jboss.com/jira/browse/JBSEAM-2501 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.CR1, 2.0.0.GA Environment: Java 1.5.0_10, JBoss 4.2.2.GA, Windows XP, Seam 2.0.1.CR1 Reporter: Mark Richter When you create a Stateful EJB in default conversation scope the action on a html commandButton is not always being called. Also if you change it to a seam button the action is called however the forms fields are not being set. This is best demonstrated with an example. I will attach a modified booking example. Simply replace the attached files with those in the seam booking example in 2.0.1.CR1 or 2.0.0.GA release. When you run the example, login (demo/demo) and click the find hotels button. Now click the "Html - More results" commandButton. All results are cleared because its defined action "hotelSearch.nextPage" is never called. Put the bean in session scope and it works fine. Also repeat this but this time click the "Seam - More Results" button. When you click this button the action is called correctly however the setters (i.e. setPageNo, setSearchString etc..) are not called. Apart from the inconsistency I would expect that in both cases the setters are called and then the action to be called. -- 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

18 years

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1567) Complete documentation for seam-ui

by Pete Muir (JIRA)

Complete documentation for seam-ui ---------------------------------- Key: JBSEAM-1567 URL: http://jira.jboss.com/jira/browse/JBSEAM-1567 Project: JBoss Seam Issue Type: Task Components: JSF Reporter: Pete Muir Many of the attributes on seam ui controls have descriptions, not all. As JBossTools is now in play, this is more important, as they are actually displayed in the IDE ootb! -- 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

18 years

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2230) Allow Seam to work with the WebLogic JAAS server authentication without any source code modifications

by Krasimir Chobantonov (JIRA)

Allow Seam to work with the WebLogic JAAS server authentication without any source code modifications ----------------------------------------------------------------------------------------------------- Key: JBSEAM-2230 URL: http://jira.jboss.com/jira/browse/JBSEAM-2230 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.GA Environment: BEA WebLogic Server v. 10 MP1 (The issue should be observable from version 8 and up) Reporter: Krasimir Chobantonov Priority: Optional When using JBoss Identity for server delegated security authentication using the jaas-config-name attribute in security:identity XML element inside JBoss SEAM components.xml file and deploying that on BEA WebLogic Server then the authentication is always failing if the default WebLogic JAAS module is used. Follows the WebLogic server JAAS configuration file content : myrealm { weblogic.security.auth.login.UsernamePasswordLoginModule required authOnLogin="true" debug="false"; }; The problem is that the WebLogic server passes JAAS callback weblogic.security.auth.callback.URLCallback on which Seam throws an UnsupportedCallbackException class exception. To make this functionality to work you have to either 1) create custom JAAS module for WebLogic server 2) Extend org.jboss.seam.security.Identity and org.jboss.seam.security.RuleBasedIdentity classes to override protected CallbackHandler getDefaultCallbackHandler() method and include a new else branch before the default that throws UnsupportedCallbackException } else if (callbacks[i].getClass().getName().equals ("weblogic.security.auth.callback.URLCallback")) { // deliberately ignored. } 3) Include the code in 2 inside the JBoss Seam Identity class - not having the User to debug why it is not working and then to create a new class to extend that in order to make it workable In my opinion performing 3 will be the easier from User's point of view and will allow Seam to use WebLogic JAAS server authentication without any coding from JBoss Seam User point of view. Note that the proposed code doesn't depend on any BEA WebLogic specific classes. -- 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

18 years

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1997) ConversationList not refreshed when beginning a long-running conversation

by Jacob Orshalick (JIRA)

ConversationList not refreshed when beginning a long-running conversation ------------------------------------------------------------------------- Key: JBSEAM-1997 URL: http://jira.jboss.com/jira/browse/JBSEAM-1997 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR1 Reporter: Jacob Orshalick If an action executes with an @Begin and returns the user to the same page, the conversationList is not updated with the new ConversationEntry. It appears that the problem is the current implementation of conversationList is a factory method scoped to the PAGE. A patch that works is to make the ConversationList a manager component rather than a factory method. I will attach the patch. Please see the forum reference for more information. -- 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

18 years

2
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2377) Conversation Switcher broken when using Explicit Conversations

by Samuel Mendenhall (JIRA)

Conversation Switcher broken when using Explicit Conversations -------------------------------------------------------------- Key: JBSEAM-2377 URL: http://jira.jboss.com/jira/browse/JBSEAM-2377 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Samuel Mendenhall Priority: Minor My test project consists of CatHome and KittenHome (hey, I like cats) with the respective entities, ect... On the create method of CatHome and KittenHome I have: @Begin(id="TheKittenConversation") @Begin(id="TheCatConversation") I have the standard conversation switcher syntax from the Docs. Now when I create a cat, then a kitten, then I go to switch back to the cat with the switcher, the page just refreshes and does not go anywhere. I did some debugging and the "actualOutcome" from the ./src/main/org/jboss/seam/faces/Switcher.java is the explicit id which in this case is "TheCatConversation". Ok, so the method returns this string, nothing happens, nothing is redirected, why would anything happen. However, if I just do @Begin instead of the explicit ids and rerun the project then this piece of code is hit and the redirect happens: else{ ConversationEntry ce = ConversationEntries.instance().getConversationEntry(conversationIdOrOutcome); if (ce!=null) { resultingConversationIdOrOutcome = ce.getId(); System.out.println("ce.getId(): " + ce.getId() + " redirection..."); ce.redirect(); } } But if I use explict, that is never encountered because isOutcome is true and the else is not evaluated: if (isOutcome) { resultingConversationIdOrOutcome = conversationIdOrOutcome; actualOutcome = conversationIdOrOutcome; } So I removed the if else completely and Explicit conversations and the conversation switcher worked perfect. The resulting select method looks like: public String select() { String actualOutcome; ConversationEntry ce = ConversationEntries.instance().getConversationEntry(conversationIdOrOutcome); if (ce!=null) { resultingConversationIdOrOutcome = ce.getId(); ce.redirect(); } actualOutcome = null; return actualOutcome; } which means the outcome returned will always be null, versus in the case of explicit conversations, be the explict conversation name. -- 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

18 years

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2604) parsing page.xml is not thread safe

by Norman Richards (JIRA)

parsing page.xml is not thread safe ----------------------------------- Key: JBSEAM-2604 URL: http://jira.jboss.com/jira/browse/JBSEAM-2604 Project: JBoss Seam Issue Type: Bug Reporter: Norman Richards Assigned To: Norman Richards When a view is accessed for the first time, the Pages.parse() is called to create a new Page object. The object is immediately put in pagesByViewId, which makes it available (in an incomplete state) to concurrent requests. The result can be incorrect page state (and incorrect processing) or even concurrent modification errors if the parsing is inserting values into lists in the Page object that are being iterated over on another thread. -- 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

18 years

2
3
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 February 2008