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

[Design of JBoss Web Services] - Re: SOAP/ WSDL version used in JBOSS AS 4.2.0 GA

by thomas.diesler＠jboss.com

Certified soap-1.2 support (verified by javaee5 CTS) you get with jbossws-2.0.x View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077671#4077671 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077671

18 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: SOAP/ WSDL version used in JBOSS AS 4.2.0 GA

by palin

Afaik JBoss WS 1.2.1.GA should support both soap 1.1 and 1.2 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077652#4077652 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077652

18 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Restart Server & ConnectionFactories

by clebert.suconic＠jboss.com

Just an update.. this was fixed! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077567#4077567 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077567

18 years, 7 months

1
0
0 / 0

[Design of Security on JBoss] - Re: SimplePrincipal - equals() Implementation

by scott.stark＠jboss.org

"darran.lofthouse(a)jboss.com" wrote : But it fails the following two requirements for an equals implementation: - | | anonymous wrote : | | # It is symmetric: for any non-null reference values x and y, x.equals(y) should return true if and only if y.equals(x) returns true. | | # It is transitive: for any non-null reference values x, y, and z, if x.equals(y) returns true and y.equals(z) returns true, then x.equals(z) should return true. | | | | The following requirement from hashCode will also not be met: - | | anonymous wrote : If two objects are equal according to the equals(Object) method, then calling the hashCode method on each of the two objects must produce the same integer result. | | Basically you can not put different principal implementation in a HashMap and expect consistent behaviour. Its not the SimplePrincipal.equals/hashCode that is breaking these constraints. Symmetry and transitivity exist for any Principal implementation relying on the Principal.getName() alone. Any other implementation introducing additional information, such as the KerberosPrincipal, is separating itself into a new category. There is nothing our implementation can do to change this. You would have to create a Map with an ordered collection like TreeMap(Comparator<? super Principal> c) with a Comparator implementation that uses the least common denominator Principal.getName. What is the context in which this is a problem? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077540#4077540 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077540

18 years, 7 months

1
0
0 / 0

[Design of Security on JBoss] - Re: SimplePrincipal - equals() Implementation

by darran.lofthouse＠jboss.com

But it fails the following two requirements for an equals implementation: - anonymous wrote : | # It is symmetric: for any non-null reference values x and y, x.equals(y) should return true if and only if y.equals(x) returns true. | # It is transitive: for any non-null reference values x, y, and z, if x.equals(y) returns true and y.equals(z) returns true, then x.equals(z) should return true. | The following requirement from hashCode will also not be met: - anonymous wrote : If two objects are equal according to the equals(Object) method, then calling the hashCode method on each of the two objects must produce the same integer result. Basically you can not put different principal implementation in a HashMap and expect consistent behaviour. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077526#4077526 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077526

18 years, 7 months

1
0
0 / 0

[Design of Security on JBoss] - Re: SimplePrincipal - equals() Implementation

by scott.stark＠jboss.org

Which is expected. The KerberosPrincipal is more restrictive and should not view the jboss implementation as equivalent. I don't see what your asking for as you started by saying we go too far. I'm saying we go the minimal distance for a meaningful Principal equals implementation. The only other Principal implementations for which mutual equality exists are those for which the name is sufficient. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077525#4077525 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077525

18 years, 7 months

1
0
0 / 0

[Design of Security on JBoss] - Re: SimplePrincipal - equals() Implementation

by darran.lofthouse＠jboss.com

But our SimplePrincipal is going to claim it is the same as the KerberosPrincipal if they both happen to have the same name - this is opposite to what the equals method of the KerberosPrincipal would return if called with the SimplePrincipal. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077514#4077514 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077514

18 years, 7 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Failover MessageRedelivery

by kurt.stam＠jboss.com

http://jbossesb.blogspot.com/2007/08/service-clustering.html for some back ground info on this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077511#4077511 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077511

18 years, 7 months

1
0
0 / 0

[Design of the JBoss EJB Container] - Re: jndi lookup during restart

by bstansberry＠jboss.com

This should be fixed in the JBoss_4_0_5_GA_JBAS-4574 branch and in trunk. I'll close the JIRA once I get a thumbs up from Jimmy Wilson on his test case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077497#4077497 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077497

18 years, 7 months

1
0
0 / 0

[Design of JBossCache] - Re: Tracking whether nodes are in-memory vs persisted

by bstansberry＠jboss.com

Casting to NodeSPI from the application is cheating. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077395#4077395 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077395

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-dev-forums August 2007