October 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2135) clob usage should check for null too.

by Mark Little (JIRA)

clob usage should check for null too. ------------------------------------- Key: JBESB-2135 URL: https://jira.jboss.org/jira/browse/JBESB-2135 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP1 Reporter: Mark Little Assignee: Mark Little Fix For: 4.4 CP1 -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2136) Security context not passed to EJB in a way that EJB understands

by Martin Vecera (JIRA)

Security context not passed to EJB in a way that EJB understands ---------------------------------------------------------------- Key: JBESB-2136 URL: https://jira.jboss.org/jira/browse/JBESB-2136 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Martin Vecera Attachments: security_ejb.tar.bz2 It is not possible to call secured EJB (secured with annotations, see attached file) from secured ESB service. The ESB's security context is passed - comment out security annotations @SecurityDomain and @RolesAllowed in ejb3/src/org/jboss/soa/esb/samples/quickstart/servicecaller/ServiceCallerBean.java and rerun the test. You'll see the Subject passed which is correct. You can run this example by copying it to quickstarts and running: ant deploy-ejb ant deploy ant runtest -- 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, 5 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-2126) JBoss security credentials not always initialised

by Kevin Conner (JIRA)

JBoss security credentials not always initialised ------------------------------------------------- Key: JBESB-2126 URL: https://jira.jboss.org/jira/browse/JBESB-2126 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Fix For: 4.4 CP1 The JBoss security credentials are not always propagated. The current code is pushing the context within the authentication but there are a couple of issues with this. - authentication is not always performed (if a security context exists) - there is not attempt to 'pop' these credentials when finished. This functionality should be pushed into the pipeline, through an implementation(s) configured from jbossesb-properties.xml, and wrap the execution. -- 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, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-2143) Add SOA Software Integration Document

by Tom Cunningham (JIRA)

Add SOA Software Integration Document ------------------------------------- Key: JBESB-2143 URL: https://jira.jboss.org/jira/browse/JBESB-2143 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.4 CP1 Add a document on the SOA Software Integration. -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2139) Remove State from ESB level of ESB JON plugin

by Tom Cunningham (JIRA)

Remove State from ESB level of ESB JON plugin --------------------------------------------- Key: JBESB-2139 URL: https://jira.jboss.org/jira/browse/JBESB-2139 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.4 CP1 Remove state from the ESB node of the JBoss ESB plugin. State is not a MessageCounter attribute. -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-2108) InVM issues

by Kevin Conner (JIRA)

InVM issues ----------- Key: JBESB-2108 URL: https://jira.jboss.org/jira/browse/JBESB-2108 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Kevin Conner The InVMCourier contains a notion of active state but the handling of this is inconsistent and error prone. The courier is created in the active state and can only be disabled when the associated service is unregistered. Unfortunately the courier is *always* enabled when it is retrieved from the CourierFactory. This can lead to inconsistent behaviour on behalf of the users of the courier as the disabled courier can be enabled when anyone retrieves a new courier for the service. This is further compounded by the fact that the courier names are not unique. The name is derived from a concatenation of the category/name but this can clash when multiple ESBs expose the same service in the same VM. It can also clash with other services that happen to generate the same concatenation. -- 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, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-2113) Access to message data not thread safe

by Kevin Conner (JIRA)

Access to message data not thread safe -------------------------------------- Key: JBESB-2113 URL: https://jira.jboss.org/jira/browse/JBESB-2113 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.4 CP1 The message implementations are not designed to be used in a thread safe manner but, as a consequence of InVM pass by reference, this is now possible. The Header/Context sections are never passed by reference but the other sections are. We need to go through the other sections and tidy this up given the new requirements. -- 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, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-2144) EBWS test failure under jdk1.6

by Kevin Conner (JIRA)

EBWS test failure under jdk1.6 ------------------------------ Key: JBESB-2144 URL: https://jira.jboss.org/jira/browse/JBESB-2144 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 The EBWS unit test is failing under jdk 1.6 because of the following server side exception 2008-10-22 10:38:11,258 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441) at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:67) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:207) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:185) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:389) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122) at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) -- 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, 5 months

1
6
0 / 0

[JBoss JIRA] Created: (JBESB-2107) Service/action metric changes

by Kevin Conner (JIRA)

Service/action metric changes ----------------------------- Key: JBESB-2107 URL: https://jira.jboss.org/jira/browse/JBESB-2107 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 Reporter: Kevin Conner All the byte total metrics in ServiceMessageCounter are measured in integer values which is not sufficient. Moving these to long is currently prevented by the DataFiler, which is unable to handle long values. The DataFiler appears to coalesce long/double values down to integer/float. We need to fix the DataFiler so that it accepts these types without losing precision and address the metrics. -- 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, 5 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-2089) EBWS One way MEP does not conform to standard

by Jiri Pechanec (JIRA)

EBWS One way MEP does not conform to standard --------------------------------------------- Key: JBESB-2089 URL: https://jira.jboss.org/jira/browse/JBESB-2089 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Web Services Reporter: Jiri Pechanec Fix For: 4.4 CP1 When one way service for EBWS is used it returns <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header></env:Header><env:Body></env:Body></env:Envelope> in response. This is wrong ccording to WS-I Basic profile R2714 - http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement1... R2714 For one-way operations, an INSTANCE MUST NOT return a HTTP response that contains a SOAP envelope. Specifically, the HTTP response entity-body must be empty. -- 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, 5 months

3
9
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2008