June 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss jBPM] - Re: security in the console

by david.lloyd＠jboss.com

"tom.baeyens(a)jboss.com" wrote : i also removed the comments in the web.xml about the security warning around the gpd deployment servlet. that should be in the documentation, i think. Fine, we can put it in the documentation - but we should also put it back in the web.xml. It does no harm being there, and it is an important indication that there is a security issue. Which there is. With security, you can not have too many warnings. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054794#4054794 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054794

18 years, 9 months

1
0
0 / 0

[Design of JBossCache] - Re: Need to make enhacements to CacheListener API

by jason.greene＠jboss.com

"jason.greene(a)jboss.com" wrote : "manik.surtani(a)jboss.com" wrote : 1. Even with using a thread pool, notifications for each call or transaction are performed by the same thread (see Notifier.invokeQueuedNotifications()) - a single Runnable is used to loop thru all registered listeners, for all registered notification events. So you will get pre and post events in order, and not concurrently. | | | | Yes, but the listener instances are shared across all threads, so there could be two runnables running at the same time (unless the pool size is 1). Alternatively the pre and post phase could be combined to one method call with the before and after data. | Hmm, or did you mean using the thread-id for correlation? If so that would work (provided there is a tx start stop), but that ties the implementation of notification delivery to single thread semantics. Having a tx id or some kind of special change id would allow for future threading behavior changes. This is of course assuming that others using the the CacheListener API want to do similar things. -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054786#4054786 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054786

18 years, 9 months

1
0
0 / 0

[Design of JBoss Portal] - Re: missing getter/setter in CASAuthenticationValve

by sohil.shah＠jboss.com

Surely- JIRA should send you an email notification when the case is updated. Again thanks for the feedback View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054780#4054780 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054780

18 years, 9 months

1
0
0 / 0

[Design of JBossCache] - Re: Need to make enhacements to CacheListener API

by jason.greene＠jboss.com

"manik.surtani(a)jboss.com" wrote : 1. Even with using a thread pool, notifications for each call or transaction are performed by the same thread (see Notifier.invokeQueuedNotifications()) - a single Runnable is used to loop thru all registered listeners, for all registered notification events. So you will get pre and post events in order, and not concurrently. | Yes, but the listener instances are shared across all threads, so there could be two runnables running at the same time (unless the pool size is 1). Alternatively the pre and post phase could be combined to one method call with the before and after data. anonymous wrote : | 2. Hmm, this could be a useful callback - txStarted, txCommitted, txROlledBack (with a Transaction object passed in? Is this useful?) Can't help but feel we're reinventing something here though. | Well currently events are only delivered on commit, so rollback wouldn't be useful, although start and commit would be. -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054779#4054779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054779

18 years, 9 months

1
0
0 / 0

[Design of JBoss Portal] - Re: missing getter/setter in CASAuthenticationValve

by advaittrivedi

Hi Sohil, I have raised JIRA, JBPORTAL-1487. Will i know when the fix is applied, so that I can dowload source code and build/deploy/test ? Thanks & Regards, Advait Trivedi View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054763#4054763 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054763

18 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Performance problem in VFS

by david.lloyd＠jboss.com

Looks like the logger creation, which was high up on the hot spots list, is now completely gone from that list. I'd call it a win. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054761#4054761 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054761

18 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Performance problem in VFS

by david.lloyd＠jboss.com

"alesj" wrote : What about if you changed this temp and try to run it again? I just replaced the logger with a simple static one and so far, the results are dramatically better. Don't have numbers yet though. How important is it to have the logger name set to the concrete class for these classes? If it's very important, I can put in an abstract method to grab a static logger from the concrete class. Or you can. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054753#4054753 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054753

18 years, 9 months

1
0
0 / 0

[Design of JBoss Portal] - Re: missing getter/setter in CASAuthenticationValve

by sohil.shah＠jboss.com

Advait- Best would be to post an issue in JIRA and attach the bug fix to it. It can be better tracked that way. Here is the Portal JIRA: http://jira.jboss.com/jira/browse/JBPORTAL Also, can make sure to reference this forum post on it as well? Thanks in advance View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054747#4054747 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054747

18 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: security in the console

by david.lloyd＠jboss.com

"tom.baeyens(a)jboss.com" wrote : i think that exposing the usernames and passwords on the home page is good. then it's good for evaluation purposes. and also people know immediately that you can't put this into production as is. with the god identity management UI that you've added, people can easily delete all users and avoid that security risk. But you can put this into production as is! That's the whole point. Just change the config files. Putting the user names on the login page means that the user actually has to change the xhtml to put this into production. I think that this steps over the line and makes the console worse for both evaluation and deployment. It's a far greater benefit to the end user to just drop it in to their development environment and immediately become productive. I believe it's more valuable for our customers as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054746#4054746 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054746

18 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: why is the job servlet removed ?

by david.lloyd＠jboss.com

It's not removed. It's just moved down in the file. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054739#4054739 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054739

18 years, 9 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-dev-forums June 2007