September 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: Seam POJO and Timer support

by pete.muir＠jboss.org

They do in Seam 2. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088449#4088449 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088449

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: Objects created from link with page params

by damianharvey

Thanks Pete, but if the object does not currently exist in the conversation, why initialize one? It can't provide a value for a link if it doesn't yet exist. Or is this needed so that Seam can push a value into the object from the link? If that is the case then why is it just not initialized when required? What would you advise for an application with a large-ish memory system comprised of s:link's? The destination for each link will be created right? Cheers, Damian. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088448#4088448 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088448

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - WARN TwoPhaseCoordinator.afterCompletion

by nwray

Hi, I'm seeing the same issue with the recurring WARN message. I get the following warning from TwoPhaseCoordinator.afterCompletion with each iteration of an async task. Nothing obvious is failing, the warning might be in error or could be due to some misconfiguration on my part. It's been annoying during development but it would be nice to resolve it before deployment. 10:45:24,468 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] TwoPhaseCoordinator.afterCo mpletion - returned failure for com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@c03bcd I've added a comment to the open JIRA below with more details, please let me know if I can add anything else. http://jira.jboss.com/jira/browse/EJBTHREE-898 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088447#4088447 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088447

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: Field processing without submitting?

by smithbstl

This is sort of heavy handed but can you call entityManager.clear() first to detach the entity? This will detach ALL entities from your pc. Unfortunately clear() is not overloaded to take a particular class or object :( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088445#4088445 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088445

18 years, 7 months

1
0
0 / 0

[JBoss Messaging] - Re: ssl accessible queue

by kadlecp

Maybe my problem would solve some kide of JNDI security... Some connection factories would be internal (accessble only from local computer) a the only accessible connection factory from outside world would be "SecureConnectionFactory" from the example.... So I have to study jndi securiy, I now little about it:-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088444#4088444 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088444

18 years, 7 months

1
0
0 / 0

[JBoss jBPM] - Re: jBPM 3.2 using CMT

by MSchmidke

Commenting myself ... I've put <property name="hibernate.ejb.cfgfile" value="/hibernate.cfg.xml" /> in my persistence.xml. Don't know if it has some other side effects, but for a first try, it seems to work ... This solves the problem that JBoss' Hibernate did not know about jBPM entities. Still unsolved is the problem how to prevent jBPM from creating a second unused Hibernate configuration. Perhaps a simple configuration, we will see. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088443#4088443 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088443

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: Please decouple seam-gen from JBoss

by Grandfatha

The problem is - I absolutely agree with your opionion *personally*. But that is not making my company/other developer teams just switch our existing hosting servers to new containers. If Seam developers choose to only support JEE containers because of that opinion (that I personally share), then thats fine. But I dont think that advertising "runs on Tomcat" is the right thing do to, if in reality you pursuit a totally different strategy. Again my personal opinion is, that abusing a servlet container for everything is not the best idea in the world. Oh well, although I think that making the existing tools aware of other containers would help Seam adoption, I am happy to at least get Glasshfish support in seam-gen in Seam 2 GA without contributing anything to the project myself. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088440#4088440 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088440

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: Objects created from link with page params

by pete.muir＠jboss.org

Because s:link transparently adds any page params referenced by s:link it has to run through all possible parameters when constructing the links. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088439#4088439 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088439

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: Layering the code in Seam

by magoicochea

I know what you mean Grandfatha, usually when working with hibernate the session was opened on the business facade layer, but I don't know how to replicate this on seam. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088438#4088438 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088438

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - login when already logged in with Seam 2

by mustaghattack

I just moved to Seam 2 and I found this little change in the Identity class. Prior to 2.0 we had : | public void authenticate() | throws LoginException | { | authenticate( getLoginContext() ); | } | Now we have : | public void authenticate() | throws LoginException | { | // If we're already authenticated, then don't authenticate again | if (!isLoggedIn()) | { | authenticate( getLoginContext() ); | } | } | If an already logged in user (say bob) try to login again (as admin) it's successful (the authenticator is no called) and you get the "Welcome, admin" message. To me the old code was better and breaks login compatibility ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088437#4088437 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088437

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