Environment:
IMB WebSphere 6.1.0.11
D:\Program Files\IBM\WebSphere61\AppServer\java\jre\binjava.exe -version
java version 1.5.0
Java(TM) 2 Runtime Environment, Standard Edition (build pwi32devifx-20070608
(SR5+IY99712))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32
Pete, can you please explain me, how can I customize reaction on
org.jboss.seam.security.AuthorizationException for different situations?
For example, for login.seam I need redirect to welcome.xhtml if user is already
loginned, for item.seam I need redirect to list.seam if parameter itemId is
Can you please tell, where can I find documentation for meaning of all tags,
attributes and their possible values in pages.xml?
Seam_reference.pdf does not have any systematical explanation of this, there
are no at all any comments in the pages-2.0.dtd or pages-2.0.xsd.
View the original post
Is there any convenient ways to check some constraints before processing the
request to any view? Something like but not so bounded to access rights.
Something like navigation rule but before execute action phase.
Simple example, and ALL needs it:
I want to redirect already loginned user to
But restrict will raise an exception?
org.jboss.seam.security.AuthorizationException? But I don't need it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4108505#4108505
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4108505
Yes, thank you, now it works. I didn't get conversationId when conversation
started and didn't use it in constructor of the next FacesRequest... Actually,
I thought it should work without explisit conversationId posting...
View the original post :
Yes, I managed to run SeamTests inside application server. I create TestNG
instance, set the list of tests and call method run with overwritten empty
startJBossEmbededdedIfNecessary(because I'm using Tomcat). And to omit previous
posted error I just start TestNG in a new Thread, so all Seam's
BTW, my last 2 problems are solved. First, with long running conversation,
shows, that it is really not so intuitive - to test Seam... In my test I didn't
get conversationId and didn't pass it to next created FacesRequest. With second
- I just start tests in a new Thread with overwritten empty
Ok, http://jira.jboss.org/jira/browse/JBSEAM-2227
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4103027#4103027
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4103027
___
I'm trying to use SeamTest and with some success.
But I have some unclear questions:
1) If Seam is not bounded to JSF, why SeamTest should be bounded to JSF Phases?
I just not really like for testing purposes use all these FacesRequest multiple
implemnetations just to call a method of the
I'm trying to test a component that uses long running conversation. Is it
possible at all? Because assertation in method marked by @Begin annotations for
long running conversation fails, and actually it looks like long-running
conversation was not started.
| @Name(basket)
|
Thank you for answer, I tried to override it and the test started, but it
breaks the application.
I get
WARNING: No active application scope
| java.lang.IllegalStateException: No active application scope
| at org.jboss.seam.core.Init.instance(Init.java:75)
|
after its work.
I have some doubts that TestNG is more convenient then JUnit, the main is -
pour support of Eclipse IMHO. Please, correct me, if I'm wrong, but you cannot
run one test method in a test class without writing xml for this test.
Actually, if you want to run any test with TestNG, you have to write
Yes, sure. But after some work it just disappeared. And I cannot say why. But
even this menu just generates temp-testng-customsuite.xml instead of running
tests without xml.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4102208#4102208
Reply to the post :
Is there any way to run integrational seam-tests inside application server?
Something that should tell SeamTest not to start a new environment but use
existing and just simulate JSF lifecycle?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4101515#4101515
May be parser tries to download dtd or scheme for some xml, check your
installation of testng and *.xml that you wrote for your TestNG test. Also try
to find where this string (hibernate.sourceforge.net) is present in your
project, in which jar or file, or try to track which url is requested.
Then you have something wrong with the way you run tests. This is a line 162
from parser: List suiteFiles = currentXmlSuite.getSuiteFiles();
So null in list of suite. Check your TestNG xml file, run examples, or post
your code, if you cannot solve it by yourself.
View the original post :
Sure, http://jira.jboss.org/jira/browse/JBSEAM-2159
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4099127#4099127
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4099127
___
Is there any way to define, which interceptors should be applied for a method
in a component, marked with @BypassInterceptors?
For example, I have a component, which contains only one method, which should
be surrouned with transactions and serialized access.
Now for this I mark all other
What do you think about adding an annotation like
@ApplyInterceptors(value={TransactionInterceptor.class,
BijectionInterceptor.class})
?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4099193#4099193
Reply to the post :
Yes, I thought about this - that such feature can influence outjection. But if
I'm sure, that I wouldn't in any place outject any property with name, equal to
my component name, I could just specify it in @Name annotation, like:
@Name(value = loginBean, limitSearchByGivenScope=true)
So in
Ok, thank you for answer about fixing perNestedConversation, I used previous CR
and didn't had this update. Now I updated seam and it works better, thank you
again :)
But...
I made a little experiment concerning lookupInStatefulContexts.
1 code:
ui:repeat value=#{itemResultList.resultList}
Or, better, to use something like this:
in BaseComponent:
@Factory(value=itemBrowseListEvent, scope=ScopeType.EVENT)
| public ItemBrowseListComp getItemBrowseList() {
| return (ItemBrowseListComp) Component.getInstance(itemBrowseList,
ScopeType.SESSION);
| }
|
and on pages:
Did anybody compared performance of s:link and h:commandLink?
I traced my application and found that switching from s:link to h:commandLink
produces decrease of RENDER_RESPONSE phase from 520ms to 250ms...
Here is the code:
s:link view-id=/item.xhtml action=#{itemManager.viewItem}
One of the key methods of Seam in class Component is:
| public static Object getInstance(String name, boolean create)
|{
| Object result = Contexts.lookupInStatefulContexts(name);
| result = getInstance(name, create, result);
| return result;
|}
|
Method
Be aware that this will work only in Web Application Sphere 6.1.0.7 and higher.
For older versions you need to install the patch. By the way, at least this
patch doesn't need Update Installer (75 MB)- you have just update one class in
one jar.
View the original post :
Did you search this forum for similar questions?
May be you can find an answer here:
http://www.jboss.com/index.html?module=bbop=viewtopict=113909
You can't construct action value dynamically in s:link tag.
View the original post :
Are there any good news according these question?
It looks like before each test class in a test suite SeamTest.init() method is
called, which doesn't start JBossEmbedded server if it is already started (that
is good :) ) but each time initializes JBossSeam - again scans all jars for new
Ok, created:
http://jira.jboss.org/jira/browse/JBSEAM-1779
But may be it will need deep refactoring in BaseSeamTest - if you will change
just annotation
@BeforeClass
|@Override
|public void init() throws Exception
|{
| super.init();
|}
to
@BeforeSuite
Thank you for answer, but I spent an hour trying to do it and didn't succeed.
I added into my components.xml next line:
component name=org.jboss.seam.web.exceptionFilter installed=false/
It didn't work:
...
| INFO 02-08 10:14:04,718 [org.jboss.seam.Component.init():239]
Component:
Then last question - what can be higher precedence component then built-in
precedence component like this ExceptionFilter? I think nothing, so it just at
all impossible to do anything with it... Isn't it an issue for JIRA?
View the original post :
Does this task was solved? In JIRA it looks like affecting only 1.3.0.ALPHA and
not closed, but I experienced this problem in 2.0.0BETA1 CVS version also.
So, do you think I can add a new JIRA issue for 2.0.0BETA1 or it is somehow
solved?
View the original post :
Did someone solve this problem? I need it to turn this filter off in tests to
be able to see errors - when I start integration tests this filter catches all
exceptions and the tool thinks that everything is ok, but it failed.
View the original post :
I had the same problem and went by second way proposed ellenzhao (thank you :) )
Just add to /resources/META-INF file drools.default.packagebuilder.conf
with next contents:
drools.dialect.default = java
| drools.dialect.java =
org.drools.rule.builder.dialect.java.JavaDialectConfiguration
|
I found the reason of the problem.
The problem was fixed when I deleted C:\Documents and Settings\dlk\.m2 folder.
It is a repository of maven where it stores all loaded jars. After that it
started to reload libraries again. It looks like it failed to load one of jars
which was needed for
I'm not sure it is a problem of Seam. It is a limitation of JSF EL. You cannot
construct JSF EL dynamically - that is what you would like to have. You cannot
have nasted EL constructions.
I just cannot understand, how would you like to fix this limitation - it will
break the logic of EL, if
I downloaded latest version of Seam 2.0.0Beta1 from cvs by this command:
But when I exectute ant I have:
| D:\ws\jboss-seam\jboss-seamant
| Buildfile: build.xml
|
| initcore:
| [echo] Build JBoss Seam Core 2.0
|
| select-compiler:
|
| antlr:
|
| compilecore:
|
Do you mean:
instead of trying to do:
s:link action=#{someBean.someMethod(someValue)} .../
to use:
s:link action=#{someBean.someMethod}
| f:param name=nameForMapping value=#{someValue}/
| /s:link
|
?
And in someMethod implementation just read this value and call what you need?
(Just
It was so long conversation... I just want to check, did I understood your
problem correctly.
So, do you mean that you would like to be able to dynamically generate the
contents of the action attribute?
So, instead of writing a lot of times:
s:link action=#{someBean.doSomeWork('value1')} .../
But why should we stop on such a simple solution? Let's evolve this idea
(dynamic EL construction) till the whole madness?
Why only parameter value should be dynamic? What about bean name or action
name? If action value used only on invoke application phase, and on rendering
phase it is
May be you should take a look at methods marked with @Remove annotation - it
looks like they try to invoke methods of facesContext object.
Do you have SFSB linkFactory? May be the problem in its @Remove method.
View the original post :
May be you should take a look at Chapter 4. Configuring Seam components in
jboss-seam-2.0.0.BETA1\doc\reference\en\pdf\seam_reference.pdf
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4067759#4067759
Reply to the post :
Hi!
I experienced similar problem with JOIN constructions in my EJBQL.
I also used EntityQuery, I had:
| public String getEjbql() {
| return SELECT item FROM Item item LEFT JOIN FETCH item.itemStorageDetails
INNER JOIN FETCH item.unitType ut INNER JOIN FETCH ut.localized utl;
| }
|
Hi!
It looks like you made a mistake in this string:
valuetimeFilter/value
In reference it is defined like:
| value#{languageFilter}/value
So, just use EL there.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4067071#4067071
Reply to the post :
44 matches
Mail list logo
