August 2006 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Re: Specifying Default Client Binding

by ALRubinger

Great. Any leads to where I should post for some direction in fixing? Couldn't find a forum for the Binding Manager or the varia package... And thanks, Bill. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968459#3968459 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968459

18 years, 5 months

1
0
0 / 0

[Design of JBoss Build System] - Updating apache.commons.classpath

by chilin

The Admin Console project uses the apache.commons.classpath in its build path. Recently the commons-lang.jar has been upgraded to version 2.1 in thirdparty (of jboss 5.0), but the pathelement in apache.commons.classpath still references commons-lang-2.0.jar, this caused problems with the Console build. I've figured out that apache.commons.classpath is defined in trunk\tools\etc\buildmagic\aliases.ent, but I'm not sure if making the change will have any other side effect. Can someone familiar in this area give your bless before I change it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968456#3968456 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968456

18 years, 5 months

1
0
0 / 0

[Design of Security on JBoss] - Re: JBoss Security Service Provider Interface Extension

by anil.saldhana＠jboss.com

Agree on the non-need to add SPML dependency into JBossSX. The current interface for Cache (CachePolicy) does hold the ability to flush. So we can end the discussion on SecurityCache Flushing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968453#3968453 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968453

18 years, 5 months

1
0
0 / 0

[Design of Security on JBoss] - Re: SecurityContext

by anil.saldhana＠jboss.com

Similar to the SPNEGO authentication sequence because the trust decision (if using SAML) can involve http redirects before the correct saml token arrives with the necessary information (the other alternative is the backdoor soap interaction). That was my reference wrt JASPI. For the trust spi, how does the following look: | /** | Principal can be null. The Contextual map can contain additional subjectInfo plus other info including a SAML Token assertion/domainInfo from the source application domain | */ | Principal getTargetIdentity(Principal p, Map contextualMap); | If there is a need to know additional information about the target identity (like roles), then we will need another method in the authorization manager (The AM implementation will have to query for the attributes of the identity from an external application domain): | Group getTargetRoles(Principal targetIdentity, Map contextualMap) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968450#3968450 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968450

18 years, 5 months

1
0
0 / 0

[Design of JBoss Portal] - Deployment option to title portal pages (Enhancement?)

by evl123

Dear portal developers, As best as I understand JBossPortal 2.4 server\default\deploy\jboss-portal.sar\portal-core.war\layouts\generic index.jsp maximized.jsp Has the HTML page title set to PortalConstants.VERSION.toString() It would be much nicer to have a page title property set in the deployment xml file. deployment/page elment would have (optional) page.title deployment/portal should have a default page.title (in case the page didn't define one) This way you get flexible global portal title or individual page titles This may already be doable, if someone could explain what objects are available in the layout jsps (e.g. how can one access Page properties?) to replace the PortalConstants.VERSION.toString() with the property instead. Thanks, Eric View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968449#3968449 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968449

18 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Setting up JBoss Messaging integration tests

by ovidiu.feodorov＠jboss.com

rachmatowicz(a)jboss.com wrote : | 1. Making use of release-admin.xml directly makes sense from the point of view of centralizing the code to create configurations. However, at present, we are pulling only pulling in jboss-messaging.jar into testsuite/thirdparty from repository.jboss.com, and don't have direct access to release-admin.xml. We are looking for a way to set up the configuration which makes life easy as well as being well-suited to the existing testsuite organization. | Ruel may have a say on this. The repository also provides a "resources" directory, that can be used for auxiliary scripts, I reckon. Quote from http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBuild anonymous wrote : | | Repository File Structure | | ... | repository.jboss.com\component name\version\lib | repository.jboss.com\component name\version\resources | ... | | resources - contains idl files, properties files, things of that nature | | ... | rachmatowicz(a)jboss.com wrote : | 2. The JBAS build and testsuite makes use of a number of names for directories relating to JMS and the existing JBossMQ implementation: | trunk/messaging | trunk/testsuite/src/main/jms | trunk/testsuite/src/main/jmsra | trunk/testsuite/src/main/jbossmq | trunk/tetstsuite/src/resources/messaging | trunk/testsuite/src/resources/jbossmq | | "trunk/messaging" is a wrong name for JBossMQ related stuff to start with, I would change it to "jbossmq" everywhere it shows up in the source tree. Now with SVN is easy. This leaves messaging for us. As Tim said, messaging5 is bad. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968448#3968448 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968448

18 years, 5 months

1
0
0 / 0

[Design of Security on JBoss] - Re: SecurityContext

by scott.stark＠jboss.org

The trust spi needs to support the mapping of one identity to another. SPENGO is an example of a full authentication sequence, not a trust decision. When I think of a trust spi, I'm thinking of having an identity/subject from one authentication domain and I need to map it to the current domain. Currently you have to have the full authentication info for the target domain. A trust spi allows one to query if and what the target domain identity is without performing full reauthentication. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968441#3968441 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968441

18 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Setting up JBoss Messaging integration tests

by timfox

I don't think messaging5 is a good name since it ties us to the 5.x release. Something like jbossmessaging sounds like a better choice to me. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968438#3968438 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968438

18 years, 5 months

1
0
0 / 0

[Design of Security on JBoss] - Re: JBoss Security Service Provider Interface Extension

by scott.stark＠jboss.org

Explain why SPML is needed for this. Any push for SPML needs to be coming from the container MC project or the ESB as just introducing an SPML dependency in jbosssx does not make sense. In terms of JMX, there has to be a POJO api for flushing that cache that can be fronted via JMX if desired. JMX is a managment implementation detail, not a dependency that we want to propagate further. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968436#3968436 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968436

18 years, 5 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Specifying Default Client Binding

by bill.burke＠jboss.com

then this is probably a binding manager problem, not an EJB3 problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968430#3968430 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968430

18 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums August 2006