October 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8567) Implement env-entry resource provider

by jaikiran pai (JIRA)

Implement env-entry resource provider ------------------------------------- Key: JBAS-8567 URL: https://jira.jboss.org/browse/JBAS-8567 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: jaikiran pai Assignee: jaikiran pai -- 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] Commented: (JBAS-1796) Review project dependencies and create proper abstractions

by David Lloyd (JIRA)

[ https://jira.jboss.org/browse/JBAS-1796?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on JBAS-1796: ----------------------------------- The issue is about depending implicitly on the entire class path, rather than explicitly specifying them, which we've solved. I fail to see what your naming statement really has to do with anything. AS can run without naming, though it'd be rather useless without it. And your conclusion is completely nonsensical. > Review project dependencies and create proper abstractions > ---------------------------------------------------------- > > Key: JBAS-1796 > URL: https://jira.jboss.org/browse/JBAS-1796 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Other > Reporter: Adrian Brock > Priority: Critical > Fix For: 7.0.0.M1 > > Attachments: tattletale-jboss-5.1.0.CR1-rev87856.zip > > > I am getting singlularly fed up with people doing their own integrations > in such a way that every project needs to depend directly on everything > in thirdparty and every other project. > Some people need to go on a course to learn the meaning of abstraction. > e.g. > The server module is an integration project. It should not be directly dependent > on implementation details of Xerces: > package org.jboss.webservice.metadata.wsdl; > import org.apache.xerces.xs.XSComplexTypeDefinition; > import org.apache.xerces.xs.XSTypeDefinition; > import org.jboss.webservice.metadata.wsdl.WSDLConstants; > import org.jboss.webservice.metadata.wsdl.xsd.XSDComplexType; > import org.jboss.webservice.metadata.wsdl.xsd.XSDElement; > import org.jboss.webservice.metadata.wsdl.xsd.XSDSchema; > import org.jboss.webservice.metadata.wsdl.xsd.XSDSimpleType; > import org.jboss.webservice.metadata.wsdl.xsd.XSDType; > import javax.xml.namespace.QName; > import java.io.File; > import java.io.FileWriter; > import java.io.IOException; > import java.lang.reflect.Field; > import java.lang.reflect.Method; > import java.lang.reflect.Modifier; > import java.net.URL; > import java.util.ArrayList; > import java.util.HashMap; > import java.util.Iterator; > import java.util.List; > import java.util.Map; > public class WSDLUtils > { > private String newline = System.getProperty("line.separator"); -- 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
0
0 / 0

[JBoss JIRA] Created: (JBJCA-453) Fix the JMeter integration to be platform independent.

by Jeremy Whiting (JIRA)

Fix the JMeter integration to be platform independent. ------------------------------------------------------ Key: JBJCA-453 URL: https://jira.jboss.org/browse/JBJCA-453 Project: IronJacamar Issue Type: Task Components: Performance Affects Versions: 1.0.0.Beta2 Environment: All environments. Reporter: Jeremy Whiting Assignee: Jesper Pedersen Priority: Minor Previous patches to integrate JMeter have only supported Linux platforms. To make JMeter platform independent apply the included patch. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBJCA-451) Integrating JMeter into performance branch of JBJCA.

by Jeremy Whiting (JIRA)

Integrating JMeter into performance branch of JBJCA. ---------------------------------------------------- Key: JBJCA-451 URL: https://jira.jboss.org/browse/JBJCA-451 Project: IronJacamar Issue Type: Task Components: Performance Environment: Linux only. Reporter: Jeremy Whiting Assignee: Jesper Pedersen Priority: Minor To integrate JMeter into the performance testing branch the enclosed patch makes these changes. The patch uses existing Ant tasks to setup the user environment. To download a server and change file permissions before starting the server. Additionally this integration has included Ant tasks to: * deploy a sample web application to execute a test * start a standalone memory database * load sample data into the database * start the server * start JMeter -- 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

2
8
0 / 0

[JBoss JIRA] Created: (JBJCA-452) Add documentation to performance guide for JMeter.

by Jeremy Whiting (JIRA)

Add documentation to performance guide for JMeter. -------------------------------------------------- Key: JBJCA-452 URL: https://jira.jboss.org/browse/JBJCA-452 Project: IronJacamar Issue Type: Task Components: Performance Environment: All environments. Reporter: Jeremy Whiting Assignee: Jesper Pedersen Priority: Minor Fix For: 1.0.0.Beta3 Attachments: diff-jmeter-docs.txt The inclusion of JMeter in the performance branch needs documentation to explain its use. The documentation provided details the setup steps necessary and how to execute jmeter. Also is a brief description of the test plans included. -- 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

2
13
0 / 0

[JBoss JIRA] Created: (JASSIST-133) The classpool cache overrides the search order which is expected based on ClassPath objects order

by Mooky Grand (JIRA)

The classpool cache overrides the search order which is expected based on ClassPath objects order ------------------------------------------------------------------------------------------------- Key: JASSIST-133 URL: https://jira.jboss.org/browse/JASSIST-133 Project: Javassist Issue Type: Bug Affects Versions: 3.13.0.GA Environment: Reproduced on Windows XP (32) + Java 1.6.0_16. Reporter: Mooky Grand Assignee: Shigeru Chiba 1. create a class pool that contains a class path from which you can get CtClass for class "A". 2. use the class pool to get the CtClass of class "B" which depends on class "A" (e.g. one of the return values of a method in class "B" is "A"). 3. insert a new class path to the beginning of the class pool (ClassPoll.insertClassPath) that also contains the byte array for class "A" 4. Call ClassPool.get in order to get class "A" Expected: 1. A CtClass will be returned. 2. The returned CtClass will be based on the byte array from the ClassPath object which was added in step 3 above. Actual: 1. A CtClass will be returned. 2. The returned CtClass will be based on the byte array from the ClassPath object which was added in step 1 above. Reason: The cache used by ClassPool instances has no concept of ClassPath order. Once a CtClass is added to this cache, it will override the expected search order among ClassPath objects. Suggested Work Around: 1. using classPool.getAndRename(<className>, <className>). 2. using makeClass with ByteArrayInputstream for the byte array you wish to use. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-355) JBoss Negotiation - User Guide Enhancements

by Darran Lofthouse (JIRA)

JBoss Negotiation - User Guide Enhancements ------------------------------------------- Key: SECURITY-355 URL: https://jira.jboss.org/jira/browse/SECURITY-355 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.GA Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4.GA Add additional clarification to the critical points within the user guide. -- 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

1
4
0 / 0

[JBoss JIRA] Created: (SECURITY-433) Calls to getCallerPrincipal() return session ID

by Darran Lofthouse (JIRA)

Calls to getCallerPrincipal() return session ID ----------------------------------------------- Key: SECURITY-433 URL: https://jira.jboss.org/jira/browse/SECURITY-433 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.SP1 Reporter: Darran Lofthouse Assignee: Anil Saldhana Fix For: Negotiation_2.0.3.SP2 After SPNEGO based authentication the caller principal is the session ID - it should be possible to switch this to the name of the authenticated user. Also add an option to either return the full principal name or remove the realm. -- 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

1
3
0 / 0

[JBoss JIRA] Moved: (JBAS-8561) Bundle cannot load class from dependent module

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/browse/JBAS-8561?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler moved JBOSGI-414 to JBAS-8561: --------------------------------------------- Project: JBoss Application Server (was: JBoss OSGi) Key: JBAS-8561 (was: JBOSGI-414) Component/s: OSGi integration (was: Integration (JBoss)) Fix Version/s: 7.0.0.M2 (was: JBossOSGi 1.0.x) > Bundle cannot load class from dependent module > ---------------------------------------------- > > Key: JBAS-8561 > URL: https://jira.jboss.org/browse/JBAS-8561 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi integration > Reporter: Thomas Diesler > Fix For: 7.0.0.M2 > > > We see intermittent failures where a bundle cannot load a class from a dependent module > org.osgi.framework.BundleException: Cannot start bundle: bundle12:1.0.0 > at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:243) > at org.jboss.osgi.framework.bundle.AbstractBundle.start(AbstractBundle.java:435) > at org.jboss.osgi.framework.bundle.BundleWrapper.start(BundleWrapper.java:166) > at org.jboss.as.osgi.xservice.ModuleAccessesOSGiServiceTestCase.testModuleInvokesTargetBundleService(ModuleAccessesOSGiServiceTestCase.java:179) > .... > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) > Caused by: java.lang.NoClassDefFoundError: org/jboss/as/osgi/deployment/c/Echo > at org.jboss.as.osgi.deployment.b.TargetBundleActivator.start(TargetBundleActivator.java:33) > at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:205) > ... 31 more > Investigate how the ModuleClassLoader is created and whether there are perhaps some race conditions involved -- 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
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-1796) Review project dependencies and create proper abstractions

by Carlo de Wolf (JIRA)

[ https://jira.jboss.org/browse/JBAS-1796?page=com.atlassian.jira.plugin.sy... ] Carlo de Wolf reopened JBAS-1796: --------------------------------- That only takes care of identifying the pain points, but not resolving them. So I consider the issue still unresolved as such. By way of adding a review process on AS 7 we can try and guard against, but already we see the codebase overlapping its scope. For example naming. In its minimalist form no naming implementation is needed to run AS. So I very much doubt there is a proper abstraction between naming and msc, in fact naming depends directly on msc. Ergo the review process has failed. > Review project dependencies and create proper abstractions > ---------------------------------------------------------- > > Key: JBAS-1796 > URL: https://jira.jboss.org/browse/JBAS-1796 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Other > Reporter: Adrian Brock > Priority: Critical > Fix For: 7.0.0.M1 > > Attachments: tattletale-jboss-5.1.0.CR1-rev87856.zip > > > I am getting singlularly fed up with people doing their own integrations > in such a way that every project needs to depend directly on everything > in thirdparty and every other project. > Some people need to go on a course to learn the meaning of abstraction. > e.g. > The server module is an integration project. It should not be directly dependent > on implementation details of Xerces: > package org.jboss.webservice.metadata.wsdl; > import org.apache.xerces.xs.XSComplexTypeDefinition; > import org.apache.xerces.xs.XSTypeDefinition; > import org.jboss.webservice.metadata.wsdl.WSDLConstants; > import org.jboss.webservice.metadata.wsdl.xsd.XSDComplexType; > import org.jboss.webservice.metadata.wsdl.xsd.XSDElement; > import org.jboss.webservice.metadata.wsdl.xsd.XSDSchema; > import org.jboss.webservice.metadata.wsdl.xsd.XSDSimpleType; > import org.jboss.webservice.metadata.wsdl.xsd.XSDType; > import javax.xml.namespace.QName; > import java.io.File; > import java.io.FileWriter; > import java.io.IOException; > import java.lang.reflect.Field; > import java.lang.reflect.Method; > import java.lang.reflect.Modifier; > import java.net.URL; > import java.util.ArrayList; > import java.util.HashMap; > import java.util.Iterator; > import java.util.List; > import java.util.Map; > public class WSDLUtils > { > private String newline = System.getProperty("line.separator"); -- 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
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 October 2010