January 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6334) Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6334?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6334: ---------------------------------- Description: Task to track the work we've all been doing on expressions/transformers. See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem: 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute. 2) Basic transformation testing against 7.1.2 and 7.1.3 3) Reject-expression testing against 7.1.2 and 7.1.3 Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something. Please edit this description and put an OK after the subsystem name to indicate it's good to go. clustering cmp configadmin connector deployment-scanner ee ee-deployment ejb3 jacorb jaxr OK jaxrs jdr jmx jpa jsf jsr77 logging mail messaging modcluster naming osgi pojo remoting sar security threads transactions web webservices weld xts was: Task to track the work we've all been doing on expressions/transformers. See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem: 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute. 2) Basic transformation testing against 7.1.2 and 7.1.3 3) Reject-expression testing against 7.1.2 and 7.1.3 Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something. Please edit this description and put an OK after the subsystem name to indicate it's good to go. clustering cmp configadmin connector deployment-scanner ee ee-deployment ejb3 jacorb jaxr OK jaxrs jdr jmx jpa jsf jsr77 logging mail messaging modcluster naming osgi pojo remoting sar security server system-jmx threads transactions web webservices weld xts > Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems > -------------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-6334 > URL: https://issues.jboss.org/browse/AS7-6334 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 7.2.0.Alpha1 > > > Task to track the work we've all been doing on expressions/transformers. > See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem: > 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute. > 2) Basic transformation testing against 7.1.2 and 7.1.3 > 3) Reject-expression testing against 7.1.2 and 7.1.3 > Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something. > Please edit this description and put an OK after the subsystem name to indicate it's good to go. > clustering > cmp > configadmin > connector > deployment-scanner > ee > ee-deployment > ejb3 > jacorb > jaxr OK > jaxrs > jdr > jmx > jpa > jsf > jsr77 > logging > mail > messaging > modcluster > naming > osgi > pojo > remoting > sar > security > threads > transactions > web > webservices > weld > xts -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6334) Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6334?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6334: ---------------------------------- Description: Task to track the work we've all been doing on expressions/transformers. See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem: 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute. 2) Basic transformation testing against 7.1.2 and 7.1.3 3) Reject-expression testing against 7.1.2 and 7.1.3 Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something. Please edit this description and put an OK after the subsystem name to indicate it's good to go. clustering cmp configadmin connector deployment-scanner ee ee-deployment ejb3 jacorb jaxr OK jaxrs jdr jmx jpa jsf jsr77 logging mail messaging modcluster naming osgi pojo remoting sar security server system-jmx threads transactions web webservices weld xts was: Task to track the work we've all been doing on expressions/transformers. See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem: 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute. 2) Basic transformation testing against 7.1.2 and 7.1.3 3) Reject-expression testing against 7.1.2 and 7.1.3 Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something. Please edit this description and put an OK after the subsystem name to indicate it's good to go. clustering cmp configadmin connector deployment-scanner ee ee-deployment ejb3 jacorb jaxr jaxrs jdr jmx jpa jsf jsr77 logging mail messaging modcluster naming osgi pojo remoting sar security server system-jmx threads transactions web webservices weld xts > Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems > -------------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-6334 > URL: https://issues.jboss.org/browse/AS7-6334 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 7.2.0.Alpha1 > > > Task to track the work we've all been doing on expressions/transformers. > See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem: > 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute. > 2) Basic transformation testing against 7.1.2 and 7.1.3 > 3) Reject-expression testing against 7.1.2 and 7.1.3 > Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something. > Please edit this description and put an OK after the subsystem name to indicate it's good to go. > clustering > cmp > configadmin > connector > deployment-scanner > ee > ee-deployment > ejb3 > jacorb > jaxr OK > jaxrs > jdr > jmx > jpa > jsf > jsr77 > logging > mail > messaging > modcluster > naming > osgi > pojo > remoting > sar > security > server > system-jmx > threads > transactions > web > webservices > weld > xts -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6334) Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6334: ------------------------------------- Summary: Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems Key: AS7-6334 URL: https://issues.jboss.org/browse/AS7-6334 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 Task to track the work we've all been doing on expressions/transformers. See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem: 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute. 2) Basic transformation testing against 7.1.2 and 7.1.3 3) Reject-expression testing against 7.1.2 and 7.1.3 Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something. Please edit this description and put an OK after the subsystem name to indicate it's good to go. clustering cmp configadmin connector deployment-scanner ee ee-deployment ejb3 jacorb jaxr jaxrs jdr jmx jpa jsf jsr77 logging mail messaging modcluster naming osgi pojo remoting sar security server system-jmx threads transactions web webservices weld xts -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6333) Add an id xml attribute to resource-adpter containing DMR resource name

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/AS7-6333?page=com.atlassian.jira.plugin.s... ] Stefano Maestri commented on AS7-6333: -------------------------------------- We need to check also tests and dependency created on this generated name to try to remove as much complexity as possible, isolating name generation into the parser in case of id==null > Add an id xml attribute to resource-adpter containing DMR resource name > ----------------------------------------------------------------------- > > Key: AS7-6333 > URL: https://issues.jboss.org/browse/AS7-6333 > Project: Application Server 7 > Issue Type: Task > Components: JCA > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 7.2.0.CR1 > > > <xs:attribute name="id" type="xs:token" use="optional"><xs:annotation><xs:documentation>[ > An unique identifier for the resource adapter > </xs:documentation></xs:annotation></xs:attribute> > In case it is null resource name in DMR have to be generated (as now) and marshall in this attribute. > This way also generated name will be consistent after a server reload -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1317) BisocketClientInvoker waits for failed clients

by Doug Grove (JIRA)

[ https://issues.jboss.org/browse/JBREM-1317?page=com.atlassian.jira.plugin... ] Doug Grove updated JBREM-1317: ------------------------------ Description: When a client dies or is killed, the failure is actually detected in org.jboss.remoting.transport.socket.MicroSocketClientInvoker: (NEW ClientSocketWrapper[Socket[addr=/10.0.0.212,port=36600,localport=4458].d3e837]) got Exception: java.io.IOException: Broken pipe The "Broken pipe" exception means that the client has disconnected and can not return. This exception is treated in the code a retry-able, however. The code carries on, finally calling BisocketClientInvoker.createSocket(). This code then waits for a socket to appear in a list. I can see no way for a new socket to ever appear in the list. This results in the code waiting for the full duration of the configured timeout. was: When a client dies or is killed, the failure is actually detected in org.jboss.remoting.transport.socket.MicroSocketClientInvoker: (NEW ClientSocketWrapper[Socket[addr=/10.0.0.212,port=36600,localport=4458].d3e837]) got Exception: java.io.IOException: Broken pipe The "Broken pipe" exception means that the client has disconnected and can not return. This exception is treated in the code a retry-able, however. This is ignored, however, and the code carries on, finally calling BisocketClientInvoker.createSocket(). This code then waits for a socket to appear in a list. I can see no way for a new socket to ever appear in the list. This results in the code waiting for the full duration of the configured timeout. > BisocketClientInvoker waits for failed clients > ---------------------------------------------- > > Key: JBREM-1317 > URL: https://issues.jboss.org/browse/JBREM-1317 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: callbacks > Affects Versions: 2.5.4.SP3 > Environment: JBoss EAP 5.1.2 > Reporter: Doug Grove > Assignee: Ron Sigal > Priority: Minor > > When a client dies or is killed, the failure is actually detected in org.jboss.remoting.transport.socket.MicroSocketClientInvoker: > (NEW ClientSocketWrapper[Socket[addr=/10.0.0.212,port=36600,localport=4458].d3e837]) got Exception: java.io.IOException: Broken pipe > The "Broken pipe" exception means that the client has disconnected and can not return. This exception is treated in the code a retry-able, however. > The code carries on, finally calling BisocketClientInvoker.createSocket(). This code then waits for a socket to appear in a list. I can see no way for a new socket to ever appear in the list. > This results in the code waiting for the full duration of the configured timeout. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6333) Add an id xml attribute to resource-adpter containing DMR resource name

by Stefano Maestri (JIRA)

Stefano Maestri created AS7-6333: ------------------------------------ Summary: Add an id xml attribute to resource-adpter containing DMR resource name Key: AS7-6333 URL: https://issues.jboss.org/browse/AS7-6333 Project: Application Server 7 Issue Type: Task Reporter: Stefano Maestri Assignee: Stefano Maestri <xs:attribute name="id" type="xs:token" use="optional"><xs:annotation><xs:documentation>[ An unique identifier for the resource adapter </xs:documentation></xs:annotation></xs:attribute> In case it is null resource name in DMR have to be generated (as now) and marshall in this attribute. This way also generated name will be consistent after a server reload -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6333) Add an id xml attribute to resource-adpter containing DMR resource name

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/AS7-6333?page=com.atlassian.jira.plugin.s... ] Stefano Maestri updated AS7-6333: --------------------------------- Fix Version/s: 7.2.0.CR1 > Add an id xml attribute to resource-adpter containing DMR resource name > ----------------------------------------------------------------------- > > Key: AS7-6333 > URL: https://issues.jboss.org/browse/AS7-6333 > Project: Application Server 7 > Issue Type: Task > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 7.2.0.CR1 > > > <xs:attribute name="id" type="xs:token" use="optional"><xs:annotation><xs:documentation>[ > An unique identifier for the resource adapter > </xs:documentation></xs:annotation></xs:attribute> > In case it is null resource name in DMR have to be generated (as now) and marshall in this attribute. > This way also generated name will be consistent after a server reload -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6333) Add an id xml attribute to resource-adpter containing DMR resource name

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/AS7-6333?page=com.atlassian.jira.plugin.s... ] Stefano Maestri updated AS7-6333: --------------------------------- Component/s: JCA > Add an id xml attribute to resource-adpter containing DMR resource name > ----------------------------------------------------------------------- > > Key: AS7-6333 > URL: https://issues.jboss.org/browse/AS7-6333 > Project: Application Server 7 > Issue Type: Task > Components: JCA > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 7.2.0.CR1 > > > <xs:attribute name="id" type="xs:token" use="optional"><xs:annotation><xs:documentation>[ > An unique identifier for the resource adapter > </xs:documentation></xs:annotation></xs:attribute> > In case it is null resource name in DMR have to be generated (as now) and marshall in this attribute. > This way also generated name will be consistent after a server reload -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1317) BisocketClientInvoker waits for failed clients

by Doug Grove (JIRA)

[ https://issues.jboss.org/browse/JBREM-1317?page=com.atlassian.jira.plugin... ] Doug Grove updated JBREM-1317: ------------------------------ Issue Type: Bug (was: Feature Request) > BisocketClientInvoker waits for failed clients > ---------------------------------------------- > > Key: JBREM-1317 > URL: https://issues.jboss.org/browse/JBREM-1317 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: callbacks > Affects Versions: 2.5.4.SP3 > Environment: JBoss EAP 5.1.2 > Reporter: Doug Grove > Assignee: Ron Sigal > Priority: Minor > > When a client dies or is killed, the failure is actually detected in org.jboss.remoting.transport.socket.MicroSocketClientInvoker: > (NEW ClientSocketWrapper[Socket[addr=/10.0.0.212,port=36600,localport=4458].d3e837]) got Exception: java.io.IOException: Broken pipe > The "Broken pipe" exception means that the client has disconnected and can not return. This exception is treated in the code a retry-able, however. > This is ignored, however, and the code carries on, finally calling BisocketClientInvoker.createSocket(). This code then waits for a socket to appear in a list. I can see no way for a new socket to ever appear in the list. > This results in the code waiting for the full duration of the configured timeout. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-720) Generate JAR with test-sources in picketbox-ldap project

by Marek Posolda (JIRA)

[ https://issues.jboss.org/browse/SECURITY-720?page=com.atlassian.jira.plug... ] Marek Posolda commented on SECURITY-720: ---------------------------------------- Pull request sent to fix this: https://github.com/picketbox/picketbox-ldap/pull/2 > Generate JAR with test-sources in picketbox-ldap project > -------------------------------------------------------- > > Key: SECURITY-720 > URL: https://issues.jboss.org/browse/SECURITY-720 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: PicketBox > Environment: Affects version: picketbox-ldap 1.0.2.Final > Fixed version: picketbox-ldap 1.0.3.Final > Reporter: Marek Posolda > Assignee: Anil Saldhana > Priority: Minor > > It would be useful if JAR with test-sources will be attached under https://repository.jboss.org/nexus/content/groups/public/org/picketbox/pi... because currently test sources are not seen from dependent projects (like source of class org.picketbox.test.ldap.AbstractLDAPTest is not automatically seen from picketlink) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 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 January 2013