[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3136) Consider Remvoing Client State Saving Suggestion
by Steve Roy (JIRA)
Consider Remvoing Client State Saving Suggestion
------------------------------------------------
Key: JBSEAM-3136
URL: http://jira.jboss.com/jira/browse/JBSEAM-3136
Project: Seam
Issue Type: Task
Components: Documentation Issues
Affects Versions: 2.0.2.GA
Reporter: Steve Roy
The Reference Guide has the following information:
Some JSF implementations have a broken implementation of server-side state saving that
interferes with Seam's conversation propagation. If you have problems with conversation
propagation during form submissions, try switching to client-side state saving. You'll need this in
web.xml:
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
</context-param>
per the forum thread, http://www.seamframework.org/Community/StateSavingMethod, this information appears to be out of date.
Although we found no server-side state issues in our application, we found this statement concerning with regard to our application since moving to client state changed the size of some rendered pages significantly.
It may be helpful to remove this out of date information to reduce confusion.
--
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, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3134) role and permission shold be with an additonal property as full name
by Jie Situ (JIRA)
role and permission shold be with an additonal property as full name
--------------------------------------------------------------------
Key: JBSEAM-3134
URL: http://jira.jboss.com/jira/browse/JBSEAM-3134
Project: Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.1.0.BETA1
Reporter: Jie Situ
Fix For: 2.1.0.BETA1
For development purpose, role is represented as name in English, and permission is represented as a combination of target and action. But when it's used, the name in English is not enough. In other language application, usually role and perrmission should be with a name in native language for display in the view-tier. Althought the property can set myself in the Entity. But always the role and permssion are managed by the manager Seam provide. So the Role in security package and the Permission in security.permission package should be with an addtional property as fullname.
--
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, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3130) Release Notes on promoted builds are incomplete
by Glenn Marcus (JIRA)
Release Notes on promoted builds are incomplete
-----------------------------------------------
Key: JBSEAM-3130
URL: http://jira.jboss.com/jira/browse/JBSEAM-3130
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.0.A1, 2.0.3.CR1, 2.0.2.SP1, 2.0.2.GA, 2.0.2.CR2, 2.0.2.CR1, 2.0.1.GA, 2.0.1.CR2, 2.0.1.CR1, 2.0.0.GA, 2.0.0.CR3, 2.0.0.CR2, 2.0.0.CR1, 2.0.0.BETA1, 1.3.0.ALPHA, 1.2.1.GA, 1.2.0.GA, 1.1.7.CR1, 1.1.6.GA, 1.1.5.GA, 1.1.1.GA, 1.1.0.GA, 1.1.0.CR2, 1.1.0.CR1, 1.1.0.BETA2, 1.1.0.BETA1, 1.0.1, 1.0, 1.0 beta 2, 1.0 beta 1, 2.0.3.GA, 2.1.0.BETA1, 2.1.0.BETA2, 2.1.0.GA, The future
Reporter: Glenn Marcus
To reproduce:
1. Go to downloads page for promoted JBoss Seam versions
2. Click and read release notes for any version
Expected Behavior:
The release notes should reflect all changes since the previous promoted build within the same version family. As new intermediate releases are made available, the changes should be added to the release note.
Current Behavior:
The release notes only show the last set of changes of current promoted build instead of all cummulative changes since the previous version.
--
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, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3128) SEAM Unit Test is not working when run as TestNG test from Eclipse
by mca.ambrish@gmail.com (JIRA)
SEAM Unit Test is not working when run as TestNG test from Eclipse
-------------------------------------------------------------------
Key: JBSEAM-3128
URL: http://jira.jboss.com/jira/browse/JBSEAM-3128
Project: Seam
Issue Type: Task
Components: Test Harness
Affects Versions: 2.0.2.CR1
Environment: Windows XP, Mozilla FireFox
Reporter: mca.ambrish(a)gmail.com
I am running a testng.xml file from eclipse TestNG.
My test class is
public class AsmSurveyListTest extends SeamTest
{
@Test
public void unitTestGetList() throws Exception {
EntityManager em = getEntityManagerFactory().createEntityManager();
em.getTransaction().begin();
AsmSurveyList asmSurveyList = new AsmSurveyList();
assert asmSurveyList.getList().size()== 9;
em.getTransaction().commit();
em.close();
}
private EntityManagerFactory emf;
public EntityManagerFactory getEntityManagerFactory()
{
return emf;
}
@BeforeTest
public void init() throws Exception
{
super.init();
emf = Persistence.createEntityManagerFactory("TalentPact");
}
@AfterTest
public void destroy() throws Exception
{
emf.close();
}
}
and my testng.xml file is :
<!DOCTYPE suite SYSTEM "http://beust.com/testng/testng-1.0.dtd" >
<suite name="AsmSurveyList" verbose="2" parallel="false">
<test name="AsmSurveyList">
<classes>
<class name="com.talentpact.test.AsmSurveyListTest"/>
</classes>
</test>
</suite>
Now when I am running the testng.xml file as TestNG from Eclipse, I get the following error:
FAILED CONFIGURATION: @BeforeTest init
java.lang.NoClassDefFoundError: org/jboss/deployers/spi/IncompleteDeploymentException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at org.jboss.seam.mock.BaseSeamTest.embeddedJBossAvailable(BaseSeamTest.java:1015)
at org.jboss.seam.mock.BaseSeamTest.startJbossEmbeddedIfNecessary(BaseSeamTest.java:1003)
at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:929)
at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42)
at com.talentpact.test.AsmSurveyListTest.init(AsmSurveyListTest.java:41)
... Removed 19 stack frames
FAILED CONFIGURATION: @BeforeMethod begin
java.lang.IllegalStateException: Attempted to invoke a Seam component outside the an initialized application
at org.jboss.seam.contexts.Lifecycle.getApplication(Lifecycle.java:36)
at org.jboss.seam.contexts.Lifecycle.beginSession(Lifecycle.java:173)
at org.jboss.seam.contexts.ServletLifecycle.beginSession(ServletLifecycle.java:124)
at org.jboss.seam.mock.BaseSeamTest.begin(BaseSeamTest.java:918)
at org.jboss.seam.mock.SeamTest.begin(SeamTest.java:28)
... Removed 24 stack frames
SKIPPED CONFIGURATION: @AfterMethod end
SKIPPED CONFIGURATION: @AfterClass cleanup
SKIPPED CONFIGURATION: @AfterTest destroy
SKIPPED: unitTestGetList
===============================================
com.talentpact.test.AsmSurveyListTest
Tests run: 1, Failures: 0, Skips: 1
Configuration Failures: 2, Skips: 3
===============================================
===============================================
TalentPact
Total tests run: 1, Failures: 0, Skips: 1
Configuration Failures: 2, Skips: 3
===============================================
--
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, 7 months