[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-286) SeamTest - Add support for authenticated user
by Bradley Smith (JIRA)
[ http://jira.jboss.com/jira/browse/JBSEAM-286?page=comments#action_12347938 ]
Bradley Smith commented on JBSEAM-286:
--------------------------------------
I rechecked - yes it does work if I make the Class of the @In - principal be the interface, Principal (like your example above). However, the problem I ran into was when I had:
@In
private UserPrincipal userPrincipal
where UserPrincipal is my/our custom Principal implementation.
Would you be willing to add support for another override like this:
@Override
public String getPrincipalName() {
return "Gavin";
}
which has this signature?
@Override
public Principal getPrincipal() {
return MyCustomPrincipalClass;
}
Thanks.
> SeamTest - Add support for authenticated user
> ---------------------------------------------
>
> Key: JBSEAM-286
> URL: http://jira.jboss.com/jira/browse/JBSEAM-286
> Project: JBoss Seam
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 1.0.1
> Environment: All
> Reporter: Bradley Smith
> Assigned To: Gavin King
> Fix For: 1.1.0.CR1
>
> Attachments: MockExternalContext.java, MockExternalContext.java, MockHttpServletRequest.java, MockHttpServletRequest.java, SeamTest.java, SeamTest.java
>
>
> Add a property of type Principal and another property (maybe of type Group []?) to Script. The Principal should be used by the MockHttpServletRequest to represent and authenticated user. The Group [] property should be used by the MockHttpServletRequest to support the isUserInRole() implementation.
> These properties ideally should be settable by overriding the setup() method of Script.
--
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 month
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-537) conversation lock not unlocked
by Norman Richards (JIRA)
conversation lock not unlocked
------------------------------
Key: JBSEAM-537
URL: http://jira.jboss.com/jira/browse/JBSEAM-537
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.1.0.CR2
Reporter: Norman Richards
If a page action results in an exception, the lock on the ConversationEntry is never unlocked. If the debug page is called after that, the conversation can only be restored if the request happens to be on the same thread as the original request. If the conversation cannot be restored, the conversation state and the last exception will not be displayed.
Refreshing the page a few times may help because JBoss is likely to cycle through the threads, ultimately landing the request back on the original thread, allowing the reentrant lock to be acquired and the conversation restored. I don't entirely understand the conversation locking strategy, so I can't suggest a fix.
--
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 month
[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-286) SeamTest - Add support for authenticated user
by Gavin King (JIRA)
[ http://jira.jboss.com/jira/browse/JBSEAM-286?page=comments#action_12347886 ]
Gavin King commented on JBSEAM-286:
-----------------------------------
It works for me.
I tried
@In
private Principal userPrincipal;
Are you sure you have the right "Principal" class?
> SeamTest - Add support for authenticated user
> ---------------------------------------------
>
> Key: JBSEAM-286
> URL: http://jira.jboss.com/jira/browse/JBSEAM-286
> Project: JBoss Seam
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 1.0.1
> Environment: All
> Reporter: Bradley Smith
> Assigned To: Gavin King
> Fix For: 1.1.0.CR1
>
> Attachments: MockExternalContext.java, MockExternalContext.java, MockHttpServletRequest.java, MockHttpServletRequest.java, SeamTest.java, SeamTest.java
>
>
> Add a property of type Principal and another property (maybe of type Group []?) to Script. The Principal should be used by the MockHttpServletRequest to represent and authenticated user. The Group [] property should be used by the MockHttpServletRequest to support the isUserInRole() implementation.
> These properties ideally should be settable by overriding the setup() method of Script.
--
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 month
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-530) Seam-gen create entity using action package (build.xml)
by Wayne Zhang (JIRA)
Seam-gen create entity using action package (build.xml)
-------------------------------------------------------
Key: JBSEAM-530
URL: http://jira.jboss.com/jira/browse/JBSEAM-530
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.1.0.CR1
Environment: Windows 2k, Sun JDK 1.5.0_09
Reporter: Wayne Zhang
When new entity (seam new-entity), the created entity class package using the action package. Wrong settings are used in the build.xml line 329-331 using ${action.dir} but should be ${modle.dir}.
Also, the shell/batch file to run seam-gen (seam.bat and seam) should be improved, we should not using java directly, because the Java command is PATH may be not the same one as JAVA_HOME, the following code should be add (bash, windows also):
if [ "${JAVA_HOME}" = "" ]
then
JAVA_CMD=java
else
JAVA_CMD=${JAVA_HOME}/bin/java
fi
and in the Unix/Linux shell, the %1 %2 .... should be replaced with %*
--
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 month
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-535) Seam model objects bring generated in wrong directory
by gregorypierce (JIRA)
Seam model objects bring generated in wrong directory
-----------------------------------------------------
Key: JBSEAM-535
URL: http://jira.jboss.com/jira/browse/JBSEAM-535
Project: JBoss Seam
Issue Type: Bug
Components: Tools
Affects Versions: 1.1.0.CR1
Environment: Any
Reporter: gregorypierce
When creating new entities, they do not go into the model directory, they go into the action directory.
<property name="entity.file" value="${project.home}/src/${action.dir}/${entity.name}.java"/>
<property name="home.file" value="${project.home}/src/${action.dir}/${entity.name}Home.java"/>
<property name="list.file" value="${project.home}/src/${action.dir}/${entity.name}List.java"/>
<property name="page.file" value="${project.home}/view/${page.name}.xhtml"/>
<property name="masterPage.file" value="${project.home}/view/${masterPage.name}.xhtml"/>
action.dir should be replaced with model.dir in the entity-input task. This bug persists in RC1 as well.
--
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 month