[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1457) ui example doesnt work in tomcat 5.5.23
by Bieth Bruno (JIRA)
ui example doesnt work in tomcat 5.5.23
---------------------------------------
Key: JBSEAM-1457
URL: http://jira.jboss.com/jira/browse/JBSEAM-1457
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.2.1.GA
Environment: Tomcat 5.5.23
Reporter: Bieth Bruno
Can't run the ui example with tomcat 5.5.23 :
After clicking one of the link on the main page I get :
15:10:49,124 ERROR [ExceptionFilter] could not roll back transaction
javax.naming.NamingException: Local server is not initialized
at org.jnp.interfaces.LocalOnlyContextFactory.getInitialContext(LocalOnlyContextFactory.java:45)
...
15:10:50,265 ERROR [SeamPhaseListener] uncaught exception
javax.faces.el.EvaluationException: Cannot set value for expression '#{personHome.id}' to a new valu
e of type java.lang.Integer
at org.apache.myfaces.el.ValueBindingImpl.setValue(ValueBindingImpl.java:310)
--
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
15 years, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1173) HibernateSessionProxy ClassCastException
by dazhu tang (JIRA)
HibernateSessionProxy ClassCastException
----------------------------------------
Key: JBSEAM-1173
URL: http://jira.jboss.com/jira/browse/JBSEAM-1173
Project: JBoss Seam
Issue Type: Bug
Components: Framework
Affects Versions: 1.2.0.GA
Reporter: dazhu tang
Priority: Critical
1. i want to inject the hibernate session in seam,so i config the component.xml as follows:
<core:hibernate-session-factory name="hibernateSessionFactory" />
<core:managed-hibernate-session name="session" auto-create="true"
session-factory-jndi-name="java:/HibernateSessionFactory" />
2. Inside managed Bean , i use @in to inject the Hibernate Session,
but when i am using DetachedCriteria in my application
DetachedCriteria criteria =
DetachedCriteria.forClass(Smartform.class);
criteria.getExecutableCriteria(session)
i got the HibernateSessionProxy ClassCastException,i debug the application and found that seam injected HibernateSessionProxy not the real HibernateSession object . So DetachedCriteria can't work.
--
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
15 years, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1000) Propagation of conversations with pageflow in testing environment.
by Denis Karpov (JIRA)
Propagation of conversations with pageflow in testing environment.
------------------------------------------------------------------
Key: JBSEAM-1000
URL: http://jira.jboss.com/jira/browse/JBSEAM-1000
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.2.0.GA
Environment: windows 2000 jboss-4.0.5.GA
Reporter: Denis Karpov
I think there is bug in testing environment (propagation of conversations with pageflow does not work)
In this test there is 2 requests .
In the first I start conversation and pageflow
In the second conversation is lost.
If I do not start pageflow then conversation propagates.
Code:
public class TOrdTest extends SeamTest{
private static final Log log = LogFactory.getLog( TOrdTest.class );
@Test
public void Test1() throws Exception
{
String id = new FacesRequest(){
@Override
protected void invokeApplication() throws Exception {
Conversation.instance().begin();
Pageflow.instance().begin("val_buy"); // uses start-state
setOutcome("browse");
log.info("##### 1 Conversation_ID "+ Conversation.instance().getId());
assert isLongRunningConversation();
}
@Override
protected void renderResponse() throws Exception {
}
}.run();
id = new FacesRequest("/exchange/buy_readonly.xhtml",id){
@Override
protected void beforeRequest()
{
log.info("#####beforeRequest Conversation_ID "+ getConversationId());
}
@Override
protected void applyRequestValues() throws Exception {
log.info("##### 2 Conversation_ID "+ Conversation.instance().getId()+" "+getConversationId());
}
@Override
protected void invokeApplication() throws Exception {
//Conversation.instance().beginNested();
log.info("##### 3 Conversation_ID "+ Conversation.instance().getId()+" "+getConversationId());
assert isLongRunningConversation();
}
}.run();
}
}
--
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
15 years, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1526) Support selective validation with a:region
by Christian Bauer (JIRA)
Support selective validation with a:region
------------------------------------------
Key: JBSEAM-1526
URL: http://jira.jboss.com/jira/browse/JBSEAM-1526
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Reporter: Christian Bauer
In complex forms I'd like to be able to customize validation per region:
<h:form>
<a:region>
<h:inputText value="#{foo.bar}"/>
<a:region>
<h:inputText value="#{bar.foo}"/>
<a:commandButton action="#{bar.baz}"/>
</a>
<a:commandButton action="#{foo.baz}"/>
</a>
</h:form>
If the nested button is pressed, I only want #{bar.foo} validated (there is an <s:validateAll> around it). If the outer button is pressed, I want both properties validated. I realize that this is a major issue regarding model updates, however, I don't need to update the model for any non-validated property because
a) it is not decoded on the server anyway (? I don't understand the a:region docs)
b) i don't need an updated model because my action doesn't expect it
c) i don't need an updated model because i am re-rendering an area that doesn't expect it
--
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
15 years, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2325) ejb3/seam-gwt-remoting/gwt security integration
by darren hartford (JIRA)
ejb3/seam-gwt-remoting/gwt security integration
-----------------------------------------------
Key: JBSEAM-2325
URL: http://jira.jboss.com/jira/browse/JBSEAM-2325
Project: JBoss Seam
Issue Type: Task
Components: Remoting, Security
Affects Versions: 2.0.0.GA
Environment: jboss 4.2.1
seam 2.0.0.GA
win2k
Any security-domain will work with name 'SpringPoweredRealm' with a user having 'security_role' role.
Reporter: darren hartford
Assigned To: Shane Bryzak
Attachments: ejb3-gwt-security-sample.zip
Attached is a sample project showing a problem related to Seam-GWT-Remoting integration with a GWT app, and security integration challenge.
Error is detailed in forum link, top level server-side error is "[[/sample-ejb3-gwt-client]] Exception while dispatching incoming RPC call org.jboss.seam.security.NotLoggedInException "
Not sure what integration method would be the best approach for secured methods for Seam-GWT-Remoting on the server side to the GWT client side.
Expectations:
*Once logged into web application, use of secured method/services to succeed automatically with appropriate roles without additional login (role based security assumed with Seam @Restrict annotation).
*Once logged into web application, use of secured method/services to fail for insufficient role authorization, with sufficient information to determine it was a security failure instead of a service failure.
*Anonymous web application login with a GWT widget requesting a secured Seam Remoting service/method would require either re-routing to web-app login page, or login to ONLY use the requested secured Seam service/method. This could be managed with GWT code to meet this expectation.
thanks, learning as best as I can with available documentation. Permission given under LGPL license to use as an example in future documentation/examples.
--
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
15 years, 11 months