February 2011 - jboss-jira - Jboss List Archives

[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

13 years, 3 months

2
9
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

13 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8838) Provide initial WS subsystem functionalities

by Alessio Soldano (JIRA)

Provide initial WS subsystem functionalities -------------------------------------------- Key: JBAS-8838 URL: https://issues.jboss.org/browse/JBAS-8838 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 Provide initial WS subsystem for basic jaxws / pojo endpoint functionalities. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (LOGTOOL-11) Refactor into Core Generation and Specific Annotation Processing Modules

by Ken Finnigan (JIRA)

Refactor into Core Generation and Specific Annotation Processing Modules ------------------------------------------------------------------------ Key: LOGTOOL-11 URL: https://issues.jboss.org/browse/LOGTOOL-11 Project: Log Tool Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta3 Reporter: Ken Finnigan Assignee: David Lloyd JBoss Solder/Seam would like to use their own annotations for generating message classes instead of those found within JBoss Logging, as recommended by David Lloyd. At present the Annotation processor in Logging Tools specifically references the JBoss Logging annotations by package and imports them to use in generating the classes. What we'd like is to create a core processing module that has common functionality that is agnostic of whatever annotations need to be processed, or what methods those annotations may have, and then modules bolted on top of that for specific JBoss Logging annotation processing. This then allows the creation of a Solder/Seam specific annotation processor module that utilizes the core, without having to fork the entire project to achieve it. Have discussed this with both James and David, and James is currently working on a prototype. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBJCA-480) Add jmx monitoring to jvm.

by Jeremy Whiting (JIRA)

Add jmx monitoring to jvm. -------------------------- Key: JBJCA-480 URL: https://jira.jboss.org/browse/JBJCA-480 Project: IronJacamar Issue Type: Task Components: Performance Environment: All environments. Reporter: Jeremy Whiting Assignee: Jesper Pedersen Priority: Minor This contribution changes the jmeter benchmarking to provide JMX monitoring. Also the in memory database used is changed to HSQLDB due to it's ability to shutdown a standalone database. The performance guide documentation has also been updated with instructions to control jvm processes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
8
0 / 0

[JBoss JIRA] Created: (JBCL-94) Spaces in URLs returned by getResource() should in vfszip: handler

by Ondrej Medek (JIRA)

Spaces in URLs returned by getResource() should in vfszip: handler ------------------------------------------------------------------ Key: JBCL-94 URL: https://jira.jboss.org/jira/browse/JBCL-94 Project: JBoss ClassLoader Issue Type: Bug Components: ClassLoader Environment: JBoss AS 5.0.1, WinXP, JDK 1.6.0u12 Reporter: Ondrej Medek Priority: Minor Hi, I have an EAR deployed as directory (not as JAR). Inside I have one service bean and a config directory. I have tried to deploy config directory as a plain directory and packed in the JAR. I have spotted different behaviour of handling spaces in the resource URLS returned by org.jboss.classloader.spi.base.BaseClassLoader when accessing the config directory. My service bean reads config direcory by: this.getClass().getClassLoader().getResource("conf/") I get the URL: vfsfile:/C:/Program%20Files/JBoss/jboss-5.0.1.GA/server/default/deploy/prinsee-ear.ear/conf/ (Space is '%20') however, when I put the resource in the JAR and access it by: this.getClass().getClassLoader().getResource("prinsee-client.jar/conf") I get the URL: vfszip:/C:/Program Files/JBoss/jboss-5.0.1.GA/server/default/deploy/prinsee-ear.ear/prinsee-client.jar/conf/ (Space is ' '). I think, the behaviour of vfszip: handler is wrong. The space should be always '%20'. Cheers andy -- 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

13 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBVFS-60) Need better hasBeenModified implementation

by Scott M Stark (JIRA)

Need better hasBeenModified implementation ------------------------------------------ Key: JBVFS-60 URL: https://jira.jboss.org/jira/browse/JBVFS-60 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR1 Reporter: Scott M Stark Fix For: 2.0.0.GA The current hasBeenModified implementation relies on the URLConnection.getLastModified() value. This has relatively low resolution (~1ms) on some systems and rapid changes to the underlying files is not be reflected. One example of this was the JBVFS-59 repeated updates to a link file not been seen. -- 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

13 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBVFS-50) Don't use host names in custom vfs urls

by Adrian Brock (JIRA)

Don't use host names in custom vfs urls --------------------------------------- Key: JBVFS-50 URL: https://jira.jboss.org/jira/browse/JBVFS-50 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Adrian Brock The InMemory vfs and AssembledDirectory vfs are using host names as part of their urls/uris. This is causing the JDK to do some kind of security check which involves going to the dns to try to determine the ip address of the host. This is obviously inefficent. The URL schemes should be changed not to use host names. -- 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

13 years, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBBUILD-633) Nexus Audit plugin doesn't save user name for files uploaded through the Nexus GUI

by Paul Gier (JIRA)

Nexus Audit plugin doesn't save user name for files uploaded through the Nexus GUI ---------------------------------------------------------------------------------- Key: JBBUILD-633 URL: https://jira.jboss.org/browse/JBBUILD-633 Project: JBoss Build System Issue Type: Feature Request Components: Artifact Repositories Reporter: Paul Gier Assignee: John Casey Fix For: Repository Support 2010 The audit plugin doesn't appear to be saving the user for files that were uploaded directly through the Nexus GUI. This can be seen by browsing artifacts in the "thirdparty uploads" directory. -- 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

13 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-569) Release JBoss Negotiation 2.0.4

by Darran Lofthouse (JIRA)

Release JBoss Negotiation 2.0.4 ------------------------------- Key: SECURITY-569 URL: https://issues.jboss.org/browse/SECURITY-569 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2011