November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3811) VirtualFile.getPathName() returns empty string for jar files

by Thomas Diesler (JIRA)

VirtualFile.getPathName() returns empty string for jar files ------------------------------------------------------------ Key: JBAS-3811 URL: http://jira.jboss.com/jira/browse/JBAS-3811 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossAS-5.0.0.Beta -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-3797) LDAP Integeration on 3.2.3

by Yuvaraj Manogaran (JIRA)

LDAP Integeration on 3.2.3 -------------------------- Key: JBAS-3797 URL: http://jira.jboss.com/jira/browse/JBAS-3797 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: Closed issues from sourceforge Environment: LDAP Integeration. Reporter: Yuvaraj Manogaran Assigned To: Scott M Stark I have tried to integerate the LDAP with Jboss 3.2.3 Version, It authenticates well, but it will not take any role from the list of role. I need to use the role what i specified in the LDAP server. I did not get any error message on console or server.log. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-883) VersionAwareMarshaller hides true cause of marshalling failures

by Brian Stansberry (JIRA)

VersionAwareMarshaller hides true cause of marshalling failures --------------------------------------------------------------- Key: JBCACHE-883 URL: http://jira.jboss.com/jira/browse/JBCACHE-883 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.0.SP1, 1.4.0.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 1.4.1.GA >From objectFromByteBuffer: try { return marshaller.objectFromStream(in); } catch (Exception e) { if (marshaller instanceof LegacyTreeCacheMarshaller) { // the default marshaller IS the legacy marshaller!! throw e; } else { // retry with legacy marshaller - this is probably because the version id was incorrectly read. if (log.isInfoEnabled()) { log.info("Caught exception unmarshalling stream with specific versioned marshaller " + marshaller.getClass() + ". Attempting to try again with legacy marshaller " + LegacyTreeCacheMarshaller.class); } // create a more 'compatible' ObjectInputStream. in = new MarshalledValueInputStream(new ByteArrayInputStream(buf)); return getMarshaller(VERSION_LEGACY).objectFromStream(in); } } Problem is the else block in the catch block, which assumes the LegacyTreeCacheMarshaller will work. There should be a try/catch there as well, and if the assumption is wrong and there is a failure with the LegacyTreeCacheMarshaller as well, the original exception should be thrown. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-878) Documment SyncCommitPhase

by Galder Zamarreno (JIRA)

Documment SyncCommitPhase ------------------------- Key: JBCACHE-878 URL: http://jira.jboss.com/jira/browse/JBCACHE-878 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.4.0.SP1, 2.0.0.ALPHA1 Reporter: Galder Zamarreno Assigned To: Manik Surtani Fix For: 1.4.1.GA, 2.0.0.ALPHA2 Document SyncCommitPhase -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-881) get() and remove() calls on non-existent nodes create intermediate nodes before returning a null

by Manik Surtani (JIRA)

get() and remove() calls on non-existent nodes create intermediate nodes before returning a null ------------------------------------------------------------------------------------------------ Key: JBCACHE-881 URL: http://jira.jboss.com/jira/browse/JBCACHE-881 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.0.SP1, 1.3.0.SP3 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 1.3.0.SP4, 1.4.1.GA, 2.0.0.ALPHA2, 2.0.0.GA Applies to the pessimistic lock interceptor only. "When doing a get on a node that doesn't exist, intermediate nodes are created. E.g., cache2.get("/one/two/three", "key1") actually ends up creating /one/two/three first, and after the JBCACHE-875 fix, /, /one and /one/two will be WL'd for a get() on a nonexistent node!! Shouldn't the loop just be short-circuited such that at any point, if the next node does not exist and the lock_type requested is READ, just return a null? Saves us a whole bunch of unnecessary WL's ..." Don't bother creating such intermediate nodes. If the intermediate nodes don't exist, how could the final one exist? :S -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBAOP-37) Before, After, After Throwing support

by Flavia Rainone (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-37?page=comments#action_12347840 ] Flavia Rainone commented on JBAOP-37: ------------------------------------- The annotation names Thrown and Invocation are temporary. We need to choose the names for advice parameters of the types Invocation and Throwable. > Before, After, After Throwing support > ------------------------------------- > > Key: JBAOP-37 > URL: http://jira.jboss.com/jira/browse/JBAOP-37 > Project: JBoss AOP > Issue Type: Feature Request > Affects Versions: 2.0.0.alpha1 > Reporter: Bill Burke > Assigned To: Flavia Rainone > Fix For: 2.0.0.alpha3 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > This should be optimized as well. I've done a non-CVS-checked-in prototype of this. > Feature Details: > To use this feature, one should use the xml tags 'before', 'after' and 'throwing'. > The signature of these advices should take any annotated arguments (annotation rules follow) and 'after' can return a value in order to overwrite/replace the intercepted join point returned value. > Besides, to continue using the advice around, the user should just continue using the 'advice' xml tag. > Around advices should either stick to the signature > Object [advice_name](Invocation invocation) > Or they can now use annotated parameters, as in 'before', 'after' and 'throwing' > The parameters can be annotated with JoinPoint, Invocation, Return, Throwable, Arg, Args, Callee, Caller and Target. > Parameter Annotation Rules: > Except for around default signature, all parameters must be annotated with one of the annotations defined in package org.jboss.aop.advice. We have annotations that are allowed only for specific types of join points, and we have annotations that are allowed only for specific types of advices. > These annotations are allowed depending on the advice type: > - JoinPoint: Before, After, Throwing > - Invocation: Around > - Return: Around, After > - Throwable: Throwing > These annotations are allowed depending on the join point type: > - Callee: call join points > - Caller: call join points > - Target: every non-static join point that is not a call > Finally, we have the mutually exclusive annotations Arg and Args. Both can always be used (but not on the same advice method). The first one must annotate every advice parameter whose value is the value of a join point argument. The second one annotates parameters of type Object[] that must receive all join point arguments values. > Advice Matching Rules > Every Arg parameter is bound to a join point argument of the same type. If there is more than one join point argument with the requested type, then the Arg parameter will be bound to the first join point argument that has not been bound yet. > When there are overloaded advice methods, JBoss AOP will use a priority order to pick the best match. The advice method with the most suitable type of the highest priority annotated parameter type is chosen. > The increasing priority order of arguments is: Arg/Args, Return/Throwable, Target/Callee/Caller , JoinPoint/Invocation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBXB-91) Need a valid maven repo release

by Scott M Stark (JIRA)

Need a valid maven repo release ------------------------------- Key: JBXB-91 URL: http://jira.jboss.com/jira/browse/JBXB-91 Project: JBoss XML Binding (JBossXB) Issue Type: Task Reporter: Scott M Stark Fix For: JBossXB-1.0 The current jbossxb-1.0.1.TEST in the maven repository: http://repository.jboss.com/maven2/jboss/jbossxb/jbossxb/1.0.1.TEST/jboss... is invalid due to its dependency on invalid jboss common artifacts: <dependency> <groupId>jboss.logging</groupId> <artifactId>jboss-logging-spi</artifactId> <version>1.0.1.TEST</version> </dependency> <dependency> <groupId>jboss.common.core</groupId> <artifactId>jboss-common-core</artifactId> <version>1.0.1.TEST</version> <scope>compile</scope> </dependency> The current release of the common core is: http://repository.jboss.com/maven2/jboss/jboss-common-core/2.0.2.GA/ The current release of the logging spi is: http://repository.jboss.com/maven2/jboss/jboss-logging-spi/2.0.2.GA/ We need a valid maven repo release of jbossxb. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-245) Attachments are Serializable?

by Mark Little (JIRA)

Attachments are Serializable? ----------------------------- Key: JBESB-245 URL: http://jira.jboss.com/jira/browse/JBESB-245 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Maintenance Pack 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 RC1 Are Attachments assumed to be Java Serialized? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-246) Support non-Java Serialized attachments in the XML Message format

by Mark Little (JIRA)

Support non-Java Serialized attachments in the XML Message format ----------------------------------------------------------------- Key: JBESB-246 URL: http://jira.jboss.com/jira/browse/JBESB-246 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Maintenance Pack 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 Use the same marshal/unmarshal approach that we have for the message Body. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

1
0
0 / 0

Tus ganas de navegar y nuestras ADSL, es la mejor combinación.

by ADSL Pyme

19 years, 8 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-jira November 2006