March 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Moved: (JBAS-8956) Implement the HttpService ontop of JBossWeb

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBAS-8956?page=com.atlassian.jira.plugin.... ] Thomas Diesler moved JBOSGI-308 to JBAS-8956: --------------------------------------------- Project: JBoss Application Server (was: JBoss OSGi) Key: JBAS-8956 (was: JBOSGI-308) Issue Type: Feature Request (was: Task) Fix Version/s: 7.0.0.Final (was: JBossOSGi 1.0.x) Component/s: Web (Tomcat) service (was: jboss-osgi-http) > Implement the HttpService ontop of JBossWeb > ------------------------------------------- > > Key: JBAS-8956 > URL: https://issues.jboss.org/browse/JBAS-8956 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Reporter: Thomas Diesler > Assignee: Emanuel Muckenhuber > Fix For: 7.0.0.Final > > > Resolving this issue consolidates the Http services that we ship and should replace pax-web with an HttpService implemenation based on JBossWeb. > RFC-66 (WebApp) support is also covered by this issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2926) Split Verifier to 3 parts: Assistant/Verifier/Reporting

by Toni Rikkola (JIRA)

Split Verifier to 3 parts: Assistant/Verifier/Reporting ------------------------------------------------------- Key: JBRULES-2926 URL: https://issues.jboss.org/browse/JBRULES-2926 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-verifier Reporter: Toni Rikkola Assignee: Toni Rikkola Assistant * Saves the information about fact type, field, function, query usages * Saves the more detailed info for the verifier part Verifier * The part that runs the verification rules * Finds redundancy, overlaps, gaps etc Reporting * Creates DroolsDocs based on Assistant data * Creates Verifier report based on Verifier data -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8954) jmx-console vulnerability

by Jivko Sabev (JIRA)

jmx-console vulnerability ------------------------- Key: JBAS-8954 URL: https://issues.jboss.org/browse/JBAS-8954 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-5.1.0.GA Environment: verified on linux 2.6.32/AMD64 but should be applicable to all environments Reporter: Jivko Sabev Assignee: Darran Lofthouse It is possible to deploy applications directly from jmx-console despite jmx-console being secured by username/password as described in "Securing JBoss Installations". I have noticed multiple unauthorized wars being deployed on my jboss 5.1 application server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-512) AdminObject annotation scanning is not creating correct metadata

by Stefano Maestri (JIRA)

AdminObject annotation scanning is not creating correct metadata ---------------------------------------------------------------- Key: JBJCA-512 URL: https://issues.jboss.org/browse/JBJCA-512 Project: IronJacamar Issue Type: Bug Components: Common Affects Versions: 1.0.0.Beta4 Reporter: Stefano Maestri Assignee: Jesper Pedersen Fix For: 1.0.0.Beta5 It seems there is a bug that handle @AdministeredObject in Ironjacamar. public @interface AdministeredObject { Class[] adminObjectInterfaces() default { }; } public interface AdminObject extends IdDecoratedMetadata, CopyableMetaData { public abstract XsdString getAdminobjectInterface(); public abstract XsdString getAdminobjectClass(); .... } The key line(611) in the AbstractResourceAdapterDeployer if (aoMeta.getAdminobjectClass() != null && aoMeta.getAdminobjectClass().getValue() != null) But for the annotation scan for (Annotation annotation : values) { AdministeredObject a = (AdministeredObject) annotation.getAnnotation(); if (trace) log.trace("Processing: " + a); String aoName = null; if (a.adminObjectInterfaces().length > 0) { aoName = ((Class) Array.get(a.adminObjectInterfaces(), 0)).getName(); } XsdString adminobjectInterface = new XsdString(aoName, null); adminObjs.add(new AdminObjectImpl(adminobjectInterface, null, null, null)); } So it doesn't know AdminobjectClass any time. In the JSR-311 document, it isn't clear about @AdministeredObject in the annotation section. :( regards Jeff The annotation scanning is not creating the right AdminObject since it puts always to null the Imple class in metadata. Annotation scanning should take the scanned object and use its class as impl class. Use annotation.getClassNanme to obtain the annotated class. Don't forget to implement a unit test proving the bug and documenting the solution. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-8953) Create Embedded Examples for 6.0.0.Final

by Andrew Rubinger (JIRA)

Create Embedded Examples for 6.0.0.Final ---------------------------------------- Key: JBAS-8953 URL: https://issues.jboss.org/browse/JBAS-8953 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Reporter: Andrew Rubinger Assignee: Andrew Rubinger Fix For: No Release Tag the Embedded example for 6.0.0.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-8949) when tab-completing the only possible node type return its children as candidates

by Alexey Loubyansky (JIRA)

when tab-completing the only possible node type return its children as candidates --------------------------------------------------------------------------------- Key: JBAS-8949 URL: https://issues.jboss.org/browse/JBAS-8949 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Since node types in the node path are kind of intermediate steps and don't allow anything more then go to a child node, I think it'd somewhat improve the usability if tab-completion of the only possible node type resulted in its child node names as well in addition to the complete node type. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8929) CLI address parsing is overly restrictive

by Brian Stansberry (JIRA)

CLI address parsing is overly restrictive ----------------------------------------- Key: JBAS-8929 URL: https://issues.jboss.org/browse/JBAS-8929 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Alexey Loubyansky This should work: [~] host=pingguo.local:read-resource The node name is not a valid identifier 'pingguo.local' or the format is wrong for prefix 'null' The validation in Util.isValidIdentifier() is limiting things to Character.isJavaIdentifierPart(c[i]) || c[i] == '-' The org.jboss.as.controller.PathElement class is what validates address elements as we create them from dmr nodes. It uses the following patterns to validate: /** * A valid key contains alphanumerics and underscores, cannot start with a number, and cannot start or end with * {@code -}. */ private static final Pattern VALID_KEY_PATTERN = Pattern.compile("[_a-zA-Z](?:[-_a-zA-Z0-9]*[_a-zA-Z0-9])?"); private static final Pattern VALID_VALUE_PATTERN = Pattern.compile("\\*|[^*\\p{Space}\\p{Cntrl}]+"); Since '=', ':', ',' and '(' have special significance in the CLI there will need to be a mechanism to quote or escape those if used in path element values. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2900) Consider concurrency tasks optimization (both Jacoby and Gauss-Seidel iterations)

by Michał Warecki (JIRA)

Consider concurrency tasks optimization (both Jacoby and Gauss-Seidel iterations) --------------------------------------------------------------------------------- Key: JBRULES-2900 URL: https://issues.jboss.org/browse/JBRULES-2900 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-docs-planner Affects Versions: FUTURE Reporter: Michał Warecki Assignee: Mark Proctor Fix For: FUTURE Will be great to support concurrency tasks optimization. In example we have 3 tasks A, B, C and objective function 2A^2 + A*B + B^2 + AC. With Gass-Saidel iteration (where task B in time+2 depends on A in time+1 and C in time+2 depends on A in time+1) we can execute tasks A,B,C in order: A and BC cocurrently, so in 2 iterations. Without optimization tasks will be executed in 3 iterations (A , B, C). We should support Jocoby iteration as well where tasks B and C does not depend on A in previous iteration. This can be done with Gradient Method. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
9
0 / 0

[JBoss JIRA] Created: (JBRULES-2924) Planner scala friendly: Solution.getScore() should return Score<S> or Score shouldn't have a <S> type

by Geoffrey De Smet (JIRA)

Planner scala friendly: Solution.getScore() should return Score<S> or Score shouldn't have a <S> type ----------------------------------------------------------------------------------------------------- Key: JBRULES-2924 URL: https://issues.jboss.org/browse/JBRULES-2924 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet See http://stackoverflow.com/questions/5279149/implementing-methods-having-ra... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-8863) Enable SAAJ functionalities

by Alessio Soldano (JIRA)

Enable SAAJ functionalities --------------------------- Key: JBAS-8863 URL: https://issues.jboss.org/browse/JBAS-8863 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 7.0.0.Alpha2 Currently we have the javax.xml.soap.api module which contains jboss-saaj-api_1.3_spec-1.0.0.Final . That tries to load the com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl class when asked for a SAAJMetaFactory instance and no specific configuration is provided. That class is in saaj-impl.jar, so either we ship that too in AS7 or we fix our saaj API for referencing the internal JDK SAAJMetaFactory impl. After a brief chat with David on IRC, it seems the best solution is shipping saaj-impl.jar (com.sun.xml.messaging.saaj:saaj-impl) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
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 March 2011