September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-431) Fungal 0.9.0.Beta1

by Jesper Pedersen (JIRA)

Fungal 0.9.0.Beta1 ------------------ Key: JBJCA-431 URL: https://jira.jboss.org/browse/JBJCA-431 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JASSIST-92) ExprEditor: edit "throw new Exception"-Statements

by Hans-Joerg Adel (JIRA)

ExprEditor: edit "throw new Exception"-Statements ------------------------------------------------- Key: JASSIST-92 URL: https://jira.jboss.org/jira/browse/JASSIST-92 Project: Javassist Issue Type: Feature Request Affects Versions: 3.11.0.GA Environment: WIndows Vista Java 1.6 Reporter: Hans-Joerg Adel Assignee: Shigeru Chiba Priority: Minor Hi! At the moment I am using the ExprEditor. I miss an edit-Method to access throw statements like the follwing ones: throw new RuntimeException(); try { foobar(x); } catch (IllegalArgumentException e) { doSomething(); throw e; // this statement } I think of something like this: public void edit(ThrowExpr t) { t.getType(); // returns the CtClass of the thrown Exception } Cheers Ruwen and Hans-Joerg -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2224) multi-restriction pattern throws UnsupportedOpEx

by Wolfgang Laun (JIRA)

multi-restriction pattern throws UnsupportedOpEx ------------------------------------------------ Key: JBRULES-2224 URL: https://jira.jboss.org/jira/browse/JBRULES-2224 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.0.1.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor rule "same" when $m : ShGraphType( $x25No : x25No, $trans : trans ) GoType( x25No == $x25No || == ($x25No % 2000), trans != $trans ) #!!!# $e : ShType( x25No == $x25No ) $v : View( elemSet contains $m ) then Field x25No is an int. The marked pattern is not flagged in Eclipse, passes the compiler without an error, but crashes at runtime during fact insertion with: Exception in thread "main" java.lang.UnsupportedOperationException: does not support method call isAllowed(Object object, InternalWorkingMemory workingMemoiry) at org.drools.rule.ReturnValueRestriction.isAllowedCachedRight(ReturnValueRestriction.java:252) at org.drools.rule.OrCompositeRestriction.isAllowedCachedRight(OrCompositeRestriction.java:51) at org.drools.rule.MultiRestrictionFieldConstraint.isAllowedCachedRight(MultiRestrictionFieldConstraint.java:115) at org.drools.common.DoubleBetaConstraints.isAllowedCachedRight(DoubleBetaConstraints.java:181) at org.drools.reteoo.JoinNode.assertObject(JoinNode.java:172) at org.drools.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:360) at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:344) at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:184) at org.drools.reteoo.EntryPointNode.assertObject(EntryPointNode.java:146) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:1094) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:1045) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:830) at org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:219) at rss.checker.engine.impl.DroolsEngine.insert(DroolsEngine.java:61) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2655) Enable "from" to accept [ ] for inline list creation without the "return( ... )" statement

by Edson Tirelli (JIRA)

Enable "from" to accept [ ] for inline list creation without the "return( ... )" statement ------------------------------------------------------------------------------------------ Key: JBRULES-2655 URL: https://jira.jboss.org/browse/JBRULES-2655 Project: Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.1.0.FINAL Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.2.0.M1 At the moment, "from" requires the use of "return( [ ... ] )" for inline list creation: String() from return( ["foo", "bar"] ) Ideally, we should be able to write: String() from ["foo", "bar"] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBEE-29) Add jaxrpc-api_1.1_spec

by Richard Opalka (JIRA)

Add jaxrpc-api_1.1_spec ----------------------- Key: JBEE-29 URL: https://jira.jboss.org/jira/browse/JBEE-29 Project: JBoss JavaEE APIs Issue Type: Sub-task Reporter: Richard Opalka Assignee: Shelly McGowan Fix For: 6.0.0.Alpha1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-8385) Console logging support

by David Lloyd (JIRA)

Console logging support ----------------------- Key: JBAS-8385 URL: https://jira.jboss.org/browse/JBAS-8385 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Logging Reporter: David Lloyd Assignee: David Lloyd Fix For: 7.0.0.M1 Add support for console logging in both a standalone and domain setting. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1240) Upgrade to Remoting 2.2.3.SP3

by Ron Sigal (JIRA)

Upgrade to Remoting 2.2.3.SP3 ----------------------------- Key: JBREM-1240 URL: https://jira.jboss.org/browse/JBREM-1240 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.3.SP3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JGRP-1245) Programmatic API to create channel and protocol stack

by Bela Ban (JIRA)

Programmatic API to create channel and protocol stack ----------------------------------------------------- Key: JGRP-1245 URL: https://jira.jboss.org/browse/JGRP-1245 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 E.g. JChannel ch=new JChannel(); ProtocolStack stack=new ProtocolStack(); ch.setStack(stack); stack.add(new NAKACK(...)); stack.add(new UNICAST(...)); ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-8352) Stacked login with subclassed Principal does not work.

by Craig Horrell (JIRA)

Stacked login with subclassed Principal does not work. ------------------------------------------------------ Key: JBAS-8352 URL: https://jira.jboss.org/browse/JBAS-8352 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.1.0.GA Environment: Windows XP; Jboss 5.1.0.GA; Reporter: Craig Horrell Assignee: Anil Saldhana The Principal is not propagated from login module to login module when using stacked logins. Instead, a new Principal is created, but only the first one survives. Code references: 1. org.jboss.security.auth.spi.UsernamePasswordLoginModule: Method login(): Object username = sharedState.get("javax.security.auth.login.name"); if (username instanceof Principal) { identity = (Principal) username; } else { String name = username.toString(); try { identity = createIdentity(name); } catch (Exception e) { log.debug("Failed to create principal", e); throw new LoginException("Failed to create principal: " + e.getMessage()); } } The code above checks to see if the Object stored in the shared state is a Principal. This code is correct. 2. Later in the same method: if (getUseFirstPass() == true) { // Add the username and password to the shared state map sharedState.put("javax.security.auth.login.name", username); sharedState.put("javax.security.auth.login.password", credential); } This is part of the bug. It stores the name instead of the Object, which causes the second login module to create a new Principal. 3. org.jboss.security.auth.spi.AbstractServerLoginModule: Method: commit(): Principal identity = getIdentity(); principals.add(identity); 'principals' is a Set. The add will not replace an existing identity, so the one created by the second login module is ignored. If the second login module got the object from the first, it could update it. As it is the second login module cannot do anything with the principal, as it is discarded. Complications: Some thought would have to be given as to what would happen if two different principal classes were specified in the config. Perhaps disallow that ? Our specific issue: We have a subclassed SimplePrincipal that holds context based security information for that user that is checked as part of the authorization in our web services. We stack a LDAP login module for the user-id and password, then a subclass of DatabaseServerLoginModule that gets the roles and other context based data from a database. Work Around: in the subclassed DatabaseServerLoginModule's getRoleSets() method we do: // To overcome stacked login bugs, we must replace the existing principal // with a new one created here. Principal pr = this.getIdentity(); log.trace("SlDbServerLoginModule: getRoleSets(): " + "Got Principal from parent: user: " + pr.getName()); SlIdentity slId = new SlIdentity(pr.getName()); slId.addClientList(getSlClientList(username, roleSet)); slId.addSiteList(getSlSiteList(username, roleSet)); Set<Principal> prs = this.subject.getPrincipals(); prs.remove(pr); prs.add(slId); log.trace("SlDbServerLoginModule: getRoleSets(): " + "Replaced Principal with SlIdentity: user: " + slId.getName()); return roleSets; Thanks, Craig. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-7984) DataSource UNKNOWN run state

by Emanuel Muckenhuber (JIRA)

DataSource UNKNOWN run state ---------------------------- Key: JBAS-7984 URL: https://jira.jboss.org/jira/browse/JBAS-7984 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-6.0.0.M2, JBossAS-5.1.0.GA Reporter: Emanuel Muckenhuber Assignee: Emanuel Muckenhuber Fix For: JBossAS-6.0.0.M3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2010