March 2009 - jboss-jira - Jboss List Archives

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

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-1796?page=com.atlassian.jira.plug... ] Jesper Pedersen updated JBAS-1796: ---------------------------------- Attachment: (was: tattletale-report-rev84586.zip) > Review project dependencies and create proper abstractions > ---------------------------------------------------------- > > Key: JBAS-1796 > URL: https://jira.jboss.org/jira/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: Backlog > > > 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-373) Release Security 2.0.2.SP7

by Stefan Guilhen (JIRA)

Release Security 2.0.2.SP7 -------------------------- Key: SECURITY-373 URL: https://jira.jboss.org/jira/browse/SECURITY-373 Project: JBoss Security and Identity Management Issue Type: Release Security Level: Public (Everyone can see) Components: ACL, Identity, JBossSX, Security SPI Reporter: Stefan Guilhen Assignee: Stefan Guilhen Release version 2.0.2.SP7 of Security-SPI and Security-JBoss SX. -- 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

17 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6467) Update to Security 2.0.2.SP5

by Jason T. Greene (JIRA)

Update to Security 2.0.2.SP5 ---------------------------- Key: JBAS-6467 URL: https://jira.jboss.org/jira/browse/JBAS-6467 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: Jason T. Greene Assignee: Anil Saldhana -- 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

17 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1750) Cluster node shutdown thats allow ongoing transactions to finish gracefully

by Galder Zamarreno (JIRA)

Cluster node shutdown thats allow ongoing transactions to finish gracefully --------------------------------------------------------------------------- Key: EJBTHREE-1750 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1750 Project: EJB 3.0 Issue Type: Feature Request Components: Clustering Reporter: Galder Zamarreno Extend EJBTHREE-1116 so that in-flight transactions, specially those initiated remotely, are allowed to finish and no new transactions are allowed. EJBTHREE-1116 just blocks the shutdown until in-flight *invocations* complete, not until *transactions* complete. So a tx that's initiated on the client side that spans multiple invocations can see the node disappear in the middle. Our clustered EJB proxies don't allow failover in the middle of a transaction, so that means the client sees a failure. EJBTHREE-1116, consider the following session bean method: @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW) public void addUser(User user) { em.persist(user); } If the node is shutdown after a client has called addUser(), the transaction will indeed complete before the shutdown commences, but only as a side effect of waiting for the invocation to complete - the BlockContainerShutdownInterceptor sits in the front of the interceptor chain. Subsequent requests to addUser(...) (i.e. new transactions) will fail once shutdown is initiated. EJBTHREE-1116 doesn't cover transactions initiated from the client - nor invocations from one ejb to another (e.g. if addUser() tries to invoke a method on another ejb after shutdown is initiated). -- 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

17 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1537) Management messages should have expiry time configurable

by Tim Fox (JIRA)

Management messages should have expiry time configurable -------------------------------------------------------- Key: JBMESSAGING-1537 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1537 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.1.0.beta It should be configurable whether messages sent to management address have an expiry time set. -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6468) Update to XACML 2.0.3.CR1

by Jason T. Greene (JIRA)

Update to XACML 2.0.3.CR1 ------------------------- Key: JBAS-6468 URL: https://jira.jboss.org/jira/browse/JBAS-6468 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: Jason T. Greene Assignee: Anil Saldhana -- 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

17 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1534) JMS object message optimisation

by Tim Fox (JIRA)

JMS object message optimisation ------------------------------- Key: JBMESSAGING-1534 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1534 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.1.0.beta When sending an object message and the body is well known type like a List, Map, String etc, then we can avoid using Java serialization and encode the object in our own format for better performance. -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1532) Consider replicating buffer not packet

by Tim Fox (JIRA)

Consider replicating buffer not packet -------------------------------------- Key: JBMESSAGING-1532 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1532 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.1.0.beta Re-use the packet when replicating, to avoid needlessly decoding and re-encoding it. -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2282) JBossEntityResolver is not using schemaLocation URIs that are valid non-file URLs

by Jason T. Greene (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-2282?page=com.atlassian.jira.plug... ] Jason T. Greene updated JBAS-2282: ---------------------------------- Fix Version/s: JBossAS-5.1.0.CR1 (was: JBossAS-5.1.0.Beta1) > JBossEntityResolver is not using schemaLocation URIs that are valid non-file URLs > --------------------------------------------------------------------------------- > > Key: JBAS-2282 > URL: https://jira.jboss.org/jira/browse/JBAS-2282 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XML services > Affects Versions: JBossAS-4.0.3RC2 > Reporter: Scott M Stark > Assignee: Alexey Loubyansky > Fix For: JBossAS-5.1.0.CR1 > > Attachments: jboss-entity-resolver.zip > > > The org.jboss.util.xml.JBossEntityResolver is not dealing with systemIDs that are valid non-file URLs. For example, this xml fragment from a testcase which uses the jboss resource URL: > <?xml version="1.0" encoding="UTF-8"?> >  > <jaas:policy > xsi:schemaLocation="urn:jboss:security-config resource:security-config_4_1.xsd" > xmlns:jaas="urn:jboss:security-config" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > > > does map to a valid URL which can be loaded, but the parsing of this URL by the getLocalEntityName ends up throwing away the full path info to produce a resource name of schema/security-config_4_1.xsd. This would work inside the jboss server provided the security-config_4_1.xsd is bundled into a classpath location following the location conventions expected by the JBossEntityResolver, but does not work in the testsuite where this is not the case, and would not work for user defined schemas located elsewhere. It would seem we should try to load the schema from systemIDs that are valid URLs before defaulting to the jboss specific logic. -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1529) Spray messages at cluster

by Tim Fox (JIRA)

Spray messages at cluster ------------------------- Key: JBMESSAGING-1529 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1529 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.1.0.beta We should allow a clientsessionfactory to be configured so that messages are "sprayed" at the cluster message 0 on node 0, message 1 on node 1, round robin. This will only work with non transactional sending. -- 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

17 years, 4 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 March 2009