September 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: Complex EL Expressions in JPDL decisions aren't being ev

by chawax

It looks like the problem is not limited to JPDL conditions ... The following EL expression is used in a task description : <task name="Validation d'un des responsables finals" description="[Validation RP] #{infosDemandeur} (#{datesDemandeAbsence})"> It used to work with Seam 2.0.0.BETA1. But with Seam 2.0.0.CR1, it throws this exception : Caused by javax.el.ELException with message: "Not a Valid Method Expression: [Validation RP] ${infosDemandeur} (${datesDemandeAbsence})" View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089712#4089712 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089712

18 years, 6 months

1
0
0 / 0

[JBoss Seam] - Facelets 1.1.14 released (I think)

by IGx89

There's a 1.1.14 versino of Facelets, dated September 27th, available in Java.net's Maven repository, though it's not listed on the Facelets site. There's no changelog either, though browsing through their issue tracker it appears that the fix for the nested <ui:insert/> problem people here have been experiencing is in this version. URL to POM: http://download.java.net/maven/1/com.sun.facelets/poms/jsf-facelets-1.1.1... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089711#4089711 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089711

18 years, 6 months

1
0
0 / 0

[JBoss Seam] - Re: #{conversationList} appears to be empty

by trickyvail

In order for the conversationList to display your conversations they must have descriptions set in pages.xml. Please refer to this post: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4049848#4049848 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089710#4089710 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089710

18 years, 6 months

1
0
0 / 0

[JBossCache] - Problem with ShutdownHook

by lembrand

Hi. I found possible problem in class org.jboss.cache.CacheImpl.java in method internalStart() at line ~820: "Runtime.getRuntime().addShutdownHook(shutdownHook);" It works perfectly in stand-alone environment, but in MBeanServer it may cause problems. MBean server has internal life-cycle definition for mbeans, and defines "stop" method for mbeans. When ShutdownHookMBean is processed in MBeanServer, the server stops mbeans in order reversed to their start. When MBeans depending on "CacheMBean" in stop method need to do some finalization work with cache (e.g. remove/update nodes), exception "java.lang.IllegalStateException" throwns, because Cache had already switched to stop state (due to hardcoded shutdown hook). Solution is to check runtime environment and in depend on this check to rely on shutdownhook (as it is now) or to stop method. PS: Sorry for my english. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089709#4089709 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089709

18 years, 6 months

1
0
0 / 0

[JBoss Seam] - Re: Maven, Seam, TestNG - IntegrationTests

by pete.muir＠jboss.org

I don't know how to best set this up in a maven project, but as I just added to the seam-gen src/test/readme.txt file you need to make sure your test classpath looks like this lib/test/jboss-embedded-all.jar lib/test/hibernate-all.jar lib/test/thirdparty-all.jar lib/test/jboss-deployers.jar ${everything else normally in your compile classpath + the test classes + testng} The order of the classpath is very very important here - the test/*.jar *must* come before everything else otherwise jboss embedded won't work. I'll try to blog about this soon. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089707#4089707 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089707

18 years, 6 months

1
0
0 / 0

[JBoss Seam] - Re: Why cannot I run more than one concurrent conversation S

by jacob.orshalick

This is correct behavior since if you are in a long-running conversation, you can only join that conversation or nest another conversation. Nesting may be a good option if you want to have the potential for multiple conversations within the parent conversation. If nesting is not appropriate, you can leave the current conversation with conversationPropagation="none". If you are using facelets, this can be accomplished by: <h:commandButton value="List Study" action="#{studyList.findStudy}"> | <s:conversationPropagation propagation="none"/> | </h:commanButton> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089706#4089706 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089706

18 years, 6 months

1
0
0 / 0

[Clustering/JBoss] - Re: Out of the box cluster problem

by tim.shaw

Working ... once sysadmin managed to climb out of bed and remember he'd disabled something in the ip tables! Thanks for the pointer tho' - the test programs are a boon, and i will (no doubt) be using them again. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089705#4089705 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089705

18 years, 6 months

1
0
0 / 0

[JBossWS] - Re: consume WS error after update to JBossWS 2.0

by Fantagir

Hi! I have the same problem of M.Schumpa but I don't have the jaxws-rt and jaxws-tools. What can I do? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089704#4089704 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089704

18 years, 6 months

1
0
0 / 0

[JBoss Portal] - Re: Is this a JBP 2.6.1 bug? (403 Error From Dashboard Link)

by NM-156

That is exactly what I am researching now. If I use form based authentication to the portal, everything works fine because IdentityLoginModule AND my custom JAAS LoginModule are activated. But now, I am trying to implement a Tomcat valve so that I will be able to bypass the portal login form altogether (my valve class extends org.apache.catalina.authenticator.SingleSignOn). When I add the roles and user principal to the request (inside of the valve), I am sent to the portal, and everything works fine except the dashboard link again (403 error ;). That is because, as you said, the login module call sequence in the context of form based login, appears to be providing something that my valve code is not. In the context of the execution of my valve, whatever the IdentityLoginModule (apparently) appears to be providing to enable the Dashboard is now missing again. If any of the JBoss developers could provide some insight about what is required to enable the Dashboard link (programmatically or via configuration), that would be a great. I know that Sohil talked about the exact valve scenario that I am referring to here: http://jboss.org/index.html?module=bb&op=viewtopic&t=115399&postdays=0&po... Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089702#4089702 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089702

18 years, 6 months

1
0
0 / 0

[JBossWS] - Re: Problem with inheritance and JBossWS

by thomas.diesler＠jboss.com

Hi mrokka, I encourage you to investigate this further. Please work with our testsuite and bring your usecase into it. If you find a solution that you can contribute - even better. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089701#4089701 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089701

18 years, 6 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

jboss-user September 2007