April 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBASM-29) Release JBASM 1.0.2.GA

by Shelly McGowan (JIRA)

Release JBASM 1.0.2.GA ---------------------- Key: JBASM-29 URL: https://jira.jboss.org/jira/browse/JBASM-29 Project: JBoss AS Server Manager Issue Type: Release Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 1.0.2.GA -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBAS-6716) add back securityConfig config property to JMS destination resources

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6716?page=com.atlassian.jira.plug... ] Charles Crouch updated JBAS-6716: --------------------------------- Priority: Blocker (was: Critical) > add back securityConfig config property to JMS destination resources > --------------------------------------------------------------------- > > Key: JBAS-6716 > URL: https://jira.jboss.org/jira/browse/JBAS-6716 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ProfileService > Reporter: Charles Crouch > Assignee: Emanuel Muckenhuber > Priority: Blocker > Fix For: JBossAS-5.1.0.CR1 > > Attachments: MyQueueWithSecurityConfig-service.xml > > > e.g. > <c:map-property required="false" name="securityConfig" description="The destination's security configuration"> > <c:simple-property required="false" name="tagName"/> > </c:map-property> -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-407) XACML: Configuration should allow specifying just the locators (and no policies)

by Anil Saldhana (JIRA)

XACML: Configuration should allow specifying just the locators (and no policies) -------------------------------------------------------------------------------- Key: SECURITY-407 URL: https://jira.jboss.org/jira/browse/SECURITY-407 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossXACML_2.0.3 There can be use cases where the policies may be stored at locations only the locators will know, in which the policies/policySets do not make any sense. It is important to just allow the Locators in the config file. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBID-75) Merge the STS configuration schema with the jboss-identity-fed.xsd that already exists

by Stefan Guilhen (JIRA)

Merge the STS configuration schema with the jboss-identity-fed.xsd that already exists -------------------------------------------------------------------------------------- Key: JBID-75 URL: https://jira.jboss.org/jira/browse/JBID-75 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: 1.0.0.alpha2 Reporter: Stefan Guilhen Assignee: Stefan Guilhen Fix For: 1.0.0.alpha3 The Security Token Service currently uses a separate schema for its configuration. This schema, however redefines several constructs that already exist in the jboss-identity-fed.xsd for dealing with key and trust stores. Besides, there's no need for a separate schema just for the STS. By having a single schema, not only it is easier to manage all the configuration aspects but also we can reuse existing constructs for dealing with keystores. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBID-76) Improve the current configuration tests to incorporate STS scenarios.

by Stefan Guilhen (JIRA)

Improve the current configuration tests to incorporate STS scenarios. --------------------------------------------------------------------- Key: JBID-76 URL: https://jira.jboss.org/jira/browse/JBID-76 Project: JBoss Identity Issue Type: Sub-task Components: Identity-Federation Affects Versions: 1.0.0.alpha2 Reporter: Stefan Guilhen Assignee: Stefan Guilhen Fix For: 1.0.0.alpha3 We need to add STS scenarios to ConfigUnitTestCase -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Assigned: (JBAS-6722) Hot deployment broken with JBoss 5.0.1.GA

by Ales Justin (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6722?page=com.atlassian.jira.plug... ] Ales Justin reassigned JBAS-6722: --------------------------------- Assignee: Ales Justin (was: Jason T. Greene) > Hot deployment broken with JBoss 5.0.1.GA > ----------------------------------------- > > Key: JBAS-6722 > URL: https://jira.jboss.org/jira/browse/JBAS-6722 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: JBoss 5.0.1 GA > JDK 5 update 16 > Seam trunk > Reporter: Jozef Hartinger > Assignee: Ales Justin > Priority: Critical > Fix For: JBossAS-5.1.0.CR1 > > > Hot deployment does not seem to work. I am using seam-gen to create a war packaged application and deploy it on JBoss 5.0.1 GA. It deploys fine, but: > a) deployment of XHTML template > modified facelet templates are not being picked up > b) deployment of action Java Bean > I run new-action to create a ping action component and run "explode" target. Component does not deploy. There is nothing in the server log that would indicate that server is even trying to load the component. > All mentioned above works fine on JBoss 4.2.3 and JBoss 5.0.0 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6724) ProfileService doesn't handle deployable's extensions well

by Ondrej Žižka (JIRA)

ProfileService doesn't handle deployable's extensions well ---------------------------------------------------------- Key: JBAS-6724 URL: https://jira.jboss.org/jira/browse/JBAS-6724 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ProfileService Affects Versions: JBossAS-5.1.0.CR1 Reporter: Ondrej Žižka Assignee: Scott M Stark JBoss AS allows to deploy an app in ZIP format, but has not a usual name - e.g. WAR can have .zip extension, and JBoss AS deploys it as WAR. But ProfileService seems not to support this well. During EmbJopr testing, it behaves this way: WAR in file "hellothere-DUD_RETRY.zip" is deployed succesfully **using hot-deploy**. EmbJopr reports the app without an extension - "hellothere-DUD_RETRY". When I try to do some operation with it (undeploy, stop), I get an exception - see below. ----------------------------------------------------------------------------------------------------------------------- Delete operation: Failed to delete Web Application (WAR) 'hellothere-DUD_RETRY' - java.lang.Exception at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:101) at org.rhq.plugins.jbossas5.ManagedDeploymentComponent.deleteResource(ManagedDeploymentComponent.java:203) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.RuntimeException: org.jboss.profileservice.spi.NoSuchDeploymentException: Failed to find deployment in file: vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere-DUD_RETRY.zip/hellothere-DUD_RETRY/ at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:313) at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.remove(StreamingDeploymentTarget.java:229) at org.jboss.profileservice.management.upload.DeploymentProgressImpl.remove(DeploymentProgressImpl.java:318) at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:94) at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:97) ... 11 more Caused by: org.jboss.profileservice.spi.NoSuchDeploymentException: Failed to find deployment in file: vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere-DUD_RETRY.zip/hellothere-DUD_RETRY/ at org.jboss.system.server.profileservice.repository.AbstractDeploymentRepository.getDeployment(AbstractDeploymentRepository.java:134) at org.jboss.system.server.profileservice.repository.BasicDeploymentRepository.removeDeployment(BasicDeploymentRepository.java:208) at org.jboss.profileservice.management.upload.remoting.DeployHandler.removeDeployment(DeployHandler.java:171) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.remove(AbstractDeployHandler.java:322) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:185) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305) ... 15 more ----------------------------------------------------------------------------------------------------------------------------- Stop operation: 16:59:21,515 INFO [DeployHandler] Stop, [vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere-DUD_RETRY.zip/hellothere-DUD_RETRY/] 16:59:21,516 INFO [DeployHandler] Failed to complete command: [stop] for deployment: names=[vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere-DUD_RETRY.zip/hellothere-DUD_RETRY/], copyContent=true org.jboss.profileservice.spi.NoSuchDeploymentException: Failed to find deployment in file: vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere-DUD_RETRY.zip/hellothere-DUD_RETRY/ at org.jboss.system.server.profileservice.repository.AbstractDeploymentRepository.getDeployment(AbstractDeploymentRepository.java:134) at org.jboss.profileservice.management.upload.remoting.DeployHandler.scheduleStop(DeployHandler.java:153) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.stop(AbstractDeployHandler.java:297) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.stop(AbstractDeployHandler.java:287) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:181) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305) at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.stop(StreamingDeploymentTarget.java:208) at org.jboss.profileservice.management.upload.DeploymentProgressImpl.stop(DeploymentProgressImpl.java:273) at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:91) at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:97) at org.rhq.plugins.jbossas5.ManagedDeploymentComponent.invokeOperation(ManagedDeploymentComponent.java:189) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) -- 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, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAOP-714) Classloader leaks in the new classpools

by Kabir Khan (JIRA)

Classloader leaks in the new classpools --------------------------------------- Key: JBAOP-714 URL: https://jira.jboss.org/jira/browse/JBAOP-714 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.0.CR2 Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 2.1.0.CR3 There were hard references to Module and ClassPoolDomain -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1796) Upgrade to 1.0.0-CR1 jboss-jpa-deployers

by jaikiran pai (JIRA)

Upgrade to 1.0.0-CR1 jboss-jpa-deployers ---------------------------------------- Key: EJBTHREE-1796 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1796 Project: EJB 3.0 Issue Type: Thirdparty Change Components: core Affects Versions: 1.1.3 Reporter: jaikiran pai Assignee: jaikiran pai Right now, the ejb3-core has a dependency on 1.0.0-Beta5 of jboss-jpa-deployers. A CR1 of jboss-jpa-deployers is available since a few weeks now. We should move to the CR1 version. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6740) Upgrade JBoss Threads to 1.0.0.CR4

by David Lloyd (JIRA)

Upgrade JBoss Threads to 1.0.0.CR4 ---------------------------------- Key: JBAS-6740 URL: https://jira.jboss.org/jira/browse/JBAS-6740 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: JBossAS-5.1.0.CR1 -- 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, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2009