November 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3733) Allow enabling/disabling endpoint metrics

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3733: ------------------------------------- Summary: Allow enabling/disabling endpoint metrics Key: JBWS-3733 URL: https://issues.jboss.org/browse/JBWS-3733 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-4.3 We need to offer a mechanism for enabling/disabling endpoint metrics. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3732) Check for endpoint-config existence when processing @EndpointConfig

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3732: ------------------------------------- Summary: Check for endpoint-config existence when processing @EndpointConfig Key: JBWS-3732 URL: https://issues.jboss.org/browse/JBWS-3732 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-4.3 When processing endpoints required to use a given endpoint-config (coming either from the container or from a deployment descriptor), we should check if the specified config actually exists. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3731) Control and document behavior regarding thread default bus changes depending on client bus selection strategy

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3731?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3731: --------------------------------------- Updated https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration#ApacheC... section in the doc. > Control and document behavior regarding thread default bus changes depending on client bus selection strategy > ------------------------------------------------------------------------------------------------------------- > > Key: JBWS-3731 > URL: https://issues.jboss.org/browse/JBWS-3731 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2.3 > > > With the availability of different client bus selection strategies, we need to clarify if/what changes a client construction applies to the current thread default bus. > The enforced behavior should be the following: > * Thread default busses with THREAD_BUS strategy > |BEFORE client creation | USED for client | AFTER client creation > | NULL | NEW | NEW > | X | X | X > > * Thread default busses with NEW_BUS strategy: > |BEFORE client creation | USED for client | AFTER client creation > | NULL | NEW | NULL > | X | NEW | X > > * Thread default busses with TCCL_BUS strategy: > |BEFORE client creation | USED for client | AFTER client creation > | NULL | TCCL | NULL > | X | TCCL | X -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3706) JBossWS 4.2.1.Final errata

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3706?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3706: --------------------------------------- Same for JBossWS 4.2.3.Final > JBossWS 4.2.1.Final errata > --------------------------- > > Key: JBWS-3706 > URL: https://issues.jboss.org/browse/JBWS-3706 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2.1 > > -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3731) Control and document behavior regarding thread default bus changes depending on client bus selection strategy

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3731?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3731: --------------------------------------- Preliminary commit: https://source.jboss.org/changelog/JBossWS?cs=18058 > Control and document behavior regarding thread default bus changes depending on client bus selection strategy > ------------------------------------------------------------------------------------------------------------- > > Key: JBWS-3731 > URL: https://issues.jboss.org/browse/JBWS-3731 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > With the availability of different client bus selection strategies, we need to clarify if/what changes a client construction applies to the current thread default bus. > The enforced behavior should be the following: > * Thread default busses with THREAD_BUS strategy > |BEFORE client creation | USED for client | AFTER client creation > | NULL | NEW | NEW > | X | X | X > > * Thread default busses with NEW_BUS strategy: > |BEFORE client creation | USED for client | AFTER client creation > | NULL | NEW | NULL > | X | NEW | X > > * Thread default busses with TCCL_BUS strategy: > |BEFORE client creation | USED for client | AFTER client creation > | NULL | TCCL | NULL > | X | TCCL | X -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3731) Control and document behavior regarding thread default bus changes depending on client bus selection strategy

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3731?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3731: ---------------------------------- Description: With the availability of different client bus selection strategies, we need to clarify if/what changes a client construction applies to the current thread default bus. The enforced behavior should be the following: * Thread default busses with THREAD_BUS strategy ------------------------------------------------------------------ |BEFORE client creation | USED for client | AFTER client creation | NULL | NEW | NEW | X | X | X ------------------------------------------------------------------ * Thread default busses with NEW_BUS strategy: ------------------------------------------------------------------ |BEFORE client creation | USED for client | AFTER client creation ------------------------------------------------------------------ | NULL | NEW | NULL | X | NEW | X ------------------------------------------------------------------ * Thread default busses with TCCL_BUS strategy: ------------------------------------------------------------------ |BEFORE client creation | USED for client | AFTER client creation ------------------------------------------------------------------ | NULL | TCCL | NULL | X | TCCL | X ------------------------------------------------------------------ was: With the availability of different client bus selection strategies, we need to clarify if/what changes a client construction applies to the current thread default bus. The enforced behavior should be the following: * Thread default busses with THREAD_BUS strategy ------------------------------------------------------------------ |BEFORE client creation | USED for client | AFTER client creation ------------------------------------------------------------------ | NULL | NEW | NEW | X | X | X ------------------------------------------------------------------ * Thread default busses with NEW_BUS strategy: ------------------------------------------------------------------ |BEFORE client creation | USED for client | AFTER client creation ------------------------------------------------------------------ | NULL | NEW | NULL | X | NEW | X ------------------------------------------------------------------ * Thread default busses with TCCL_BUS strategy: ------------------------------------------------------------------ |BEFORE client creation | USED for client | AFTER client creation ------------------------------------------------------------------ | NULL | TCCL | NULL | X | TCCL | X ------------------------------------------------------------------ > Control and document behavior regarding thread default bus changes depending on client bus selection strategy > ------------------------------------------------------------------------------------------------------------- > > Key: JBWS-3731 > URL: https://issues.jboss.org/browse/JBWS-3731 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > With the availability of different client bus selection strategies, we need to clarify if/what changes a client construction applies to the current thread default bus. > The enforced behavior should be the following: > * Thread default busses with THREAD_BUS strategy > ------------------------------------------------------------------ > |BEFORE client creation | USED for client | AFTER client creation > | NULL | NEW | NEW > | X | X | X > ------------------------------------------------------------------ > > * Thread default busses with NEW_BUS strategy: > ------------------------------------------------------------------ > |BEFORE client creation | USED for client | AFTER client creation > ------------------------------------------------------------------ > | NULL | NEW | NULL > | X | NEW | X > ------------------------------------------------------------------ > > * Thread default busses with TCCL_BUS strategy: > ------------------------------------------------------------------ > |BEFORE client creation | USED for client | AFTER client creation > ------------------------------------------------------------------ > | NULL | TCCL | NULL > | X | TCCL | X > ------------------------------------------------------------------ -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3731) Control and document behavior regarding thread default bus changes depending on client bus selection strategy

by Alessio Soldano (JIRA)

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3731) Control and document behavior regarding thread default bus changes depending on client bus selection strategy

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3731: ------------------------------------- Summary: Control and document behavior regarding thread default bus changes depending on client bus selection strategy Key: JBWS-3731 URL: https://issues.jboss.org/browse/JBWS-3731 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, productization Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 With the availability of different client bus selection strategies, we need to clarify if/what changes a client construction applies to the current thread default bus. The enforced behavior should be the following: * Thread default busses with THREAD_BUS strategy ------------------------------------------------------------------ |BEFORE client creation | USED for client | AFTER client creation ------------------------------------------------------------------ | NULL | NEW | NEW | X | X | X ------------------------------------------------------------------ * Thread default busses with NEW_BUS strategy: ------------------------------------------------------------------ |BEFORE client creation | USED for client | AFTER client creation ------------------------------------------------------------------ | NULL | NEW | NULL | X | NEW | X ------------------------------------------------------------------ * Thread default busses with TCCL_BUS strategy: ------------------------------------------------------------------ |BEFORE client creation | USED for client | AFTER client creation ------------------------------------------------------------------ | NULL | TCCL | NULL | X | TCCL | X ------------------------------------------------------------------ -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3730) Allow disabling JAXWS handler authorization for EJB3 endpoints

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3730: ------------------------------------- Summary: Allow disabling JAXWS handler authorization for EJB3 endpoints Key: JBWS-3730 URL: https://issues.jboss.org/browse/JBWS-3730 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 For compatibility reasons with PicketLink, we need a mechanism for disabling the explicit JAXWS handler authorization for EJB3 endpoints introduced in https://issues.jboss.org/browse/JBWS-3378. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3569) WSDL produced for a multi-port service contains invalid port addresses in clustered configuration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3569?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3569: ----------------------------------------------- Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 905410|https://bugzilla.redhat.com/show_bug.cgi?id=905410] from VERIFIED to CLOSED > WSDL produced for a multi-port service contains invalid port addresses in clustered configuration > ------------------------------------------------------------------------------------------------- > > Key: JBWS-3569 > URL: https://issues.jboss.org/browse/JBWS-3569 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Chris Laprun > Assignee: Alessio Soldano > Priority: Critical > Fix For: jbossws-cxf-4.1.1 > > > Using a loadbalancer fronted cluster and the loadbalancer URL for the WSDL results in ports containing the node URLs instead of the loadbalancer's. > I've tried using the dynamic WSDL rewriting as described in https://docs.jboss.org/author/display/AS71/Advanced+User+Guide but this results in invalid URLs for the ports (with {{jbossws.undefined.host}} as the host name *and* the cluster node port) that haven't been used to access the WSDL, the port used to access the WSDL has the proper address though. -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2013