April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-172) JBossSAMLResponse to read in precreated response files

by Anil Saldhana (JIRA)

JBossSAMLResponse to read in precreated response files ------------------------------------------------------ Key: SECURITY-172 URL: http://jira.jboss.com/jira/browse/SECURITY-172 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: saml-xacml Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.GA util class that can read in a response xml. -- 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

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-171) Servlet to read in SAML requests (that contain xacml decision queries) and spit out SAML responses containing xacml decisions

by Anil Saldhana (JIRA)

Servlet to read in SAML requests (that contain xacml decision queries) and spit out SAML responses containing xacml decisions ----------------------------------------------------------------------------------------------------------------------------- Key: SECURITY-171 URL: http://jira.jboss.com/jira/browse/SECURITY-171 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: saml-xacml Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.GA We need a servlet that can pick up the SAML request. The saml request contains the xacml decision query. After the xacml query is extracted, the pdp is requested for evaluation. Once the evaluation is finished, the response is prepacked in a SAML response and sent back. -- 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

17 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5282) .jsp fails to recompile after redeployment

by Thomas Bosch (JIRA)

.jsp fails to recompile after redeployment ------------------------------------------ Key: JBAS-5282 URL: http://jira.jboss.com/jira/browse/JBAS-5282 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.0 Final, JBossAS-3.2.6 Final, JBossAS-5.0.0.Beta1, JBossAS-4.0.2 Final, JBossAS-5.0.0.Beta4, JBossAS-5.0.0.GA, JBossAS-3.2.5 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1RC1, JBossAS-3.2.8RC1, JBossAS-4.0.1 SP1, JBossAS-4.0.3RC1, Closed issues from sourceforge, JBossAS-4.0.3RC2, JBossAS-4.0.4RC1, JBossAS-4.0.3 Final, No Release, JBossAS-4.0.3 SP1, JBossAS-3.2.8.SP2, JBossAS-3.2.8 Final, JBossAS-4.0.4.CR2, JBossAS-4.0.5.CR1, JBossAS-3.2.8.SP1, JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Environment: all Reporter: Thomas Bosch Fix For: JBossAS-4.0.4.CR2 When redeploying a .ear or .war containing .jsps, there are many situations causing a .jsp that needs to be recompiled to not be recompiled, or to be recompiled continuously. Any situation causing the timestamp of the modified .jsp to be older than the timestamp of its compiled class will cause it not to be recompiled; for example: - reverting to a previous version of the .jsp using a version control - timezone difference between development and production server - .jsp never visited in production server until after change is made, which can happen for a rarely visited page, or a newly deployed server. Continuous recompilation happens in any situation causing the timestamp of the modified .jsp to be newer than the current time, and will happen until current time catches up; for example: - timezone difference between development and production server - future time assigned to .jsp -- 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

17 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1542) the nested type org.drools..... cannot be referenced by it's bnary name

by Fernando Meyer (JIRA)

the nested type org.drools..... cannot be referenced by it's bnary name ----------------------------------------------------------------------- Key: JBRULES-1542 URL: http://jira.jboss.com/jira/browse/JBRULES-1542 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.6 Reporter: Fernando Meyer Assigned To: Fernando Meyer Fix For: 4.0.7 -- 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

17 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-5366) java.lang.NullPointerException at org.jboss.deployment.EARStructure.determineStructure(EARStructure.java:155)

by Carolina Prieto Muniz (JIRA)

java.lang.NullPointerException at org.jboss.deployment.EARStructure.determineStructure(EARStructure.java:155) ------------------------------------------------------------------------------------------------------------- Key: JBAS-5366 URL: http://jira.jboss.com/jira/browse/JBAS-5366 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta4 Environment: JDK 1.6 Linux Debian Etch, Windows XP Reporter: Carolina Prieto Muniz Assigned To: Scott M Stark I have been running Jboss 4.2.2 GA for several months, when I switched last week to JBossAS-5.0.0 Beta 4, I started getting this exception after deploying the ear file several times while in the development process. It never happens the first time I deploy it. 17:19:19,328 WARN [HDScanner] Scan failed org.jboss.deployers.spi.DeploymentException: Exception determining structure: Ab stractVFSDeployment(Arkit.ear) at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentExcept ion(DeploymentException.java:49) at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers .determineStructure(AbstractStructuralDeployers.java:85) at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure( MainDeployerImpl.java:743) at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainD eployerImpl.java:280) at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainD eployerImpl.java:237) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDSca nner.java:270) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScan ner.java:221) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:44 1) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java :317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask. access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask. runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask. run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec utor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:907) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.RuntimeException: Error determining structure: Arkit.ear at org.jboss.deployment.EARStructure.determineStructure(EARStructure.jav a:274) at org.jboss.deployers.vfs.plugins.structure.StructureDeployerWrapper.de termineStructure(StructureDeployerWrapper.java:65) at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl. doDetermineStructure(VFSStructuralDeployersImpl.java:194) at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl. determineStructure(VFSStructuralDeployersImpl.java:218) at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers .determineStructure(AbstractStructuralDeployers.java:77) ... 14 more Caused by: java.lang.NullPointerException at org.jboss.deployment.EARStructure.determineStructure(EARStructure.jav a:155) ... 18 more -- 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

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-170) ResponseContext: readResponse(Node)

by Anil Saldhana (JIRA)

ResponseContext: readResponse(Node) ----------------------------------- Key: SECURITY-170 URL: http://jira.jboss.com/jira/browse/SECURITY-170 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossXACML Affects Versions: 2.0.2-BETA5 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.GA Add a new method called as readResponse(Node node) -- 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

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-169) Status Detail needs getNodeName change

by Anil Saldhana (JIRA)

Status Detail needs getNodeName change --------------------------------------- Key: SECURITY-169 URL: http://jira.jboss.com/jira/browse/SECURITY-169 Project: JBoss Security and Identity Management Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jboss-sunxacml Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.GA -- 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

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1235) Defining a home-jndi-name for an EJB 3 bean is illegal

by Carlo de Wolf (JIRA)

Defining a home-jndi-name for an EJB 3 bean is illegal ------------------------------------------------------ Key: EJBTHREE-1235 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1235 Project: EJB 3.0 Issue Type: Bug Components: core Reporter: Carlo de Wolf Assigned To: Alexey Loubyansky Priority: Critical Fix For: AS 5.0.0.CR1 It should not be possible to set a home-jndi-name on an EJB 3 bean. This must be reported to the user and deployment must stop. IllegalStateException: "EJBTHREE-XXX: EJB3 bean <ejb-name> defines home-jndi-name '<home-jndi-name>' in jboss.xml" -- 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

17 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMETA-11) Defining a home-jndi-name for an EJB 3 bean is illegal

by Alexey Loubyansky (JIRA)

Defining a home-jndi-name for an EJB 3 bean is illegal ------------------------------------------------------ Key: JBMETA-11 URL: http://jira.jboss.com/jira/browse/JBMETA-11 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta6 Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: 1.0.0.CR1 This issue is opened for EJBTHREE-1235. -- 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

17 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1477) Custom render modes should be documented

by Andrew Oliver (JIRA)

Custom render modes should be documented ---------------------------------------- Key: JBPORTAL-1477 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1477 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.6.CR1, 2.4.1 SP1 Reporter: Andrew Oliver Assigned To: Julien Viet It appears via: The blanket statement of support is based on: http://jira.jboss.com/jira/browse/JBPTL-20 and http://www.jbossworld.com/jbwv_2006/integration_and_presentation/LAPRUN_J... and http://labs.jboss.com/portal/authors/articles/portal/magicbullet/ That custom render modes are supported. However the documentation is completely vague on support just saying the spec allows for custom modes and saying nothing about portals support for them. The doc also does not say HOW to define them. From these 3 I gather: Basically the last url states: "Some vendors define custom portlet modes that your portlets can implement. Support for custom portlet modes is briefly defined in the specification, and is as simple as adding a custom-portlet-mode node to the portlet descriptor and any other vendor-specific modifications to the descriptor or the portlet class." I suspect you define it in the portlet descriptor, the vendor specific descriptor and portal configuration and it should work. However I think the documentation should explicitly state support or non-support (I think it is the former) and in the case of the former demonstrate how (which I think matches the above)... -- 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

17 years, 8 months

3
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2008