August 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBDEPLOY-209) Introduce file filter that only accepts files matched by some FileMatcher

by Ales Justin (JIRA)

Introduce file filter that only accepts files matched by some FileMatcher ------------------------------------------------------------------------- Key: JBDEPLOY-209 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-209 Project: JBoss Deployers Issue Type: Feature Request Affects Versions: JBDEPLOY-2.0.8.GA Reporter: Ales Justin Assignee: Ales Justin Fix For: JBDEPLOY-2.2.x FileStructure already implements all the needed pieces, hence it can be easily used as this filter. -- 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

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2227) nested DSL Constraints don't work because compiler adds comma at beginning

by Frederik Reifschneider (JIRA)

nested DSL Constraints don't work because compiler adds comma at beginning -------------------------------------------------------------------------- Key: JBRULES-2227 URL: https://jira.jboss.org/jira/browse/JBRULES-2227 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler-DSL Affects Versions: 5.0.1.FINAL Reporter: Frederik Reifschneider Assignee: Mark Proctor Priority: Minor The following DSL expression: [condition]When there are {facts} which dont match constraints=not( forall ( {facts}( ))) [condition]When there is a {fact} with the following constraints={fact} ( ) [condition]- {field} has a value={field} != null [condition]- {field} has no value={field} == null || matches "[\S]*" with the rule: When there are Projects which dont match constraints - description has no value - objectives has a value produces: not( forall ( ProjectRow(, description == null || matches "[S]*", objectives != null ))) everything works just as expected except the comma in front of "description". When using the rule "When there is a {fact} with the following constraints" everything works fine as described in the documentation. -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1022) S3_PING: discovery protocol using S3

by Bela Ban (JIRA)

S3_PING: discovery protocol using S3 ------------------------------------ Key: JGRP-1022 URL: https://jira.jboss.org/jira/browse/JGRP-1022 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.6.12, 2.8 -- 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

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBXB-219) SchemaBindingValidator: unbounded choice as unordered sequence

by Alexey Loubyansky (JIRA)

SchemaBindingValidator: unbounded choice as unordered sequence -------------------------------------------------------------- Key: JBXB-219 URL: https://jira.jboss.org/jira/browse/JBXB-219 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.2.Beta1 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.2.GA Unbounded choice should be equivalent to unordered sequence binding. E.g. <xsd:element name="root"> <xsd:complexType> <xsd:choice maxOccurs="unbounded"> <xsd:element name="a" type="xsd:string" maxOccurs="unbounded"/> <xsd:element name="b" type="xsd:string" maxOccurs="unbounded"/> </xsd:choice> </xsd:complexType> </xsd:element> @JBossXmlSchema(namespace="urn:jboss:xb:test", elementFormDefault=XmlNsForm.QUALIFIED) @XmlRootElement(name="root") @JBossXmlType(modelGroup=JBossXmlConstants.MODEL_GROUP_UNORDERED_SEQUENCE) public class UnorderedSequenceType { private Collection<String> a; private Collection<String> b; ... -- 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

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1005) TCPGOSSIP / TCP combination fails to find any members

by Bela Ban (JIRA)

TCPGOSSIP / TCP combination fails to find any members ----------------------------------------------------- Key: JGRP-1005 URL: https://jira.jboss.org/jira/browse/JGRP-1005 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 The TCPGOSSIP:TCP combination doesn't find an initial membership. The issue is in TCPGOSSIP, where an initial lookup doesn't return the physical addrs associated with logical addrs. Use Draw with JGroups/conf/tcpgossip.xml to reproduce -- 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

16 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-428) DecodeAction should use CryptoUtil that uses the Base64 implementation from commons rather than the Util class

by Anil Saldhana (JIRA)

DecodeAction should use CryptoUtil that uses the Base64 implementation from commons rather than the Util class -------------------------------------------------------------------------------------------------------------- Key: SECURITY-428 URL: https://jira.jboss.org/jira/browse/SECURITY-428 Project: JBoss Security and Identity Management Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: JBossSecurity_2.0.3.SP2 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossSecurity_2.0.4 -- 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

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-278) JaasSecurityManager should not "swallow" LoginExceptions thrown by LoginModules

by egor kolesnikov (JIRA)

JaasSecurityManager should not "swallow" LoginExceptions thrown by LoginModules ------------------------------------------------------------------------------- Key: SECURITY-278 URL: https://jira.jboss.org/jira/browse/SECURITY-278 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.2.GA Environment: JBoss AS 4.2.2.GA Reporter: egor kolesnikov Assignee: Anil Saldhana http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/jboss/src/main/o... JaasSecurityManager.authenticate(String beanName, Principal principal, Object credential) has the following block: try { // call login modules and authenticate } catch (Exception ex) { ex.printStackTrace(); return false; } Disregarding the fact that "ex.printStackTrace()" is a definitely bad code style, swallowing all exceptions violates the JAAS specifications regarding the fact that login modules could return false or throw LoginException if login attempt has failed (see http://java.sun.com/j2se/1.5.0/docs/api/javax/security/auth/spi/LoginModu... for details). This also affects Jboss SEAM framework which raises special event if LoginException has been thrown. Observed behavior: When LoginModule throws LoginException, JaasSecurityManager.authenticate() returns false without any additional checks. Expected behavior: When LoginModule throws LoginException, JaasSecurityManager should not catch (or at least re-throw) it and allow the exception to reach the client code. -- 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

16 years, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-208) Create easy to extend grouping structure deployer

by Ales Justin (JIRA)

Create easy to extend grouping structure deployer ------------------------------------------------- Key: JBDEPLOY-208 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-208 Project: JBoss Deployers Issue Type: Feature Request Components: structure Affects Versions: JBDEPLOY-2.0.8.GA Reporter: Ales Justin Assignee: Ales Justin Fix For: JBDEPLOY-2.2.x Some of the legacy structures still use grouping directories; e.g. ESB deployments or SAR's lib directory Apart from using DirectoryStructure or hacking with JarStructure there is no easy way to define such structures programaticaly. -- 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

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2443) Resource serving doesn't work with Partial refresh

by Marek Posolda (JIRA)

Resource serving doesn't work with Partial refresh -------------------------------------------------- Key: JBPORTAL-2443 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2443 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.7.2 Final Environment: JBoss Portal 27 - compiled from branch https://svn.jboss.org/repos/portal/branches/JBoss_Portal_Branch_2_7/ JBoss AS 4.2.3.GA Sun JDK 1.5 Reporter: Marek Posolda Fix For: 2.8 Final Resource serving doesn't work correctly on portlets, which have partial refresh property enabled (Portlet is on the page with enabled partial refresh). If you have this in your portlet doView method: ResourceURL resUrl = response.createResourceURL(); response.getWriter().write("<div><a href=\"" + resUrl.toString() + "\">Resource URL</a></div><br>"); and you click to the link, then serveResource method is invoked but nothing is displayed in the browser and there is Javascript error. The same situation occured when you use form instead of link response.getWriter().write("<form method=\"POST\" action=\"" + resUrl + "\"><input type=\"submit\" value=\"Submit\"></form>"); Please look to https://jira.jboss.org/jira/browse/JBPORTAL-2377 when is described the easy scenario how the error could be simulated with usage of Header Portlet from portal-samples-basic. -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7156) Corrupted HTML in code listing

by Peter HagstrÃ¶m (JIRA)

Corrupted HTML in code listing ------------------------------ Key: JBAS-7156 URL: https://jira.jboss.org/jira/browse/JBAS-7156 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Docs/Installation and Getting Started Guide Reporter: Peter HagstrÃ¶m Priority: Trivial In section "12.3. EJB3 Session Beans" the code listing for "Business interface: TodoDaoInt.java" has corrupted HTML and does not render properly (displays HTML source). -- 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

16 years, 6 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 August 2009