February 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1678) Style in ESB management console is invalid

by Jiri Pechanec (JIRA)

Style in ESB management console is invalid ------------------------------------------ Key: JBESB-1678 URL: http://jira.jboss.com/jira/browse/JBESB-1678 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2.1 CP2 Reporter: Jiri Pechanec Assigned To: Tom Cunningham Priority: Minor The file style_master.css in ESB console contains invalid style definition, see snippet TH { background-color : #000099; color: #DEB887; font-weight: bold; }.bg_table { background-color : #DEB887; } }.bg_cell{ background-color : #ffffff; } The bg_cell definition is orphaned. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1797) Repackage management console

by Kevin Conner (JIRA)

Repackage management console ---------------------------- Key: JBESB-1797 URL: http://jira.jboss.com/jira/browse/JBESB-1797 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.3 Reporter: Kevin Conner Fix For: 4.4 We need to revisit the packaging of the management console and come up with a solution that allows the modification of the database without recompiling the code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2185) Patch for [jUDDI retains invalid EPRs]

by Joakim Sandström (JIRA)

Patch for [jUDDI retains invalid EPRs] -------------------------------------- Key: JBESB-2185 URL: https://jira.jboss.org/jira/browse/JBESB-2185 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Joakim Sandström Patch for 'jUDDI retains invalid EPRs' issue (JBESB-866). Patch: The RegistryUtil.register method unregisters matching EPR's using unregister(category, name, epr) before (re)registering the same EPR. Not included in the patch: Registry.unRegisterEPR(serviceCategoryName, serviceName, epr) could return a boolean true/false and not raise a ServiceNotFoundException if the service isn't found - to avoid unneccesary stack traces in the log. -- 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, 1 month

3
13
0 / 0

[JBoss JIRA] Created: (JBESB-2401) FileGatewayListener: Does not support overwriting of processed files.

by Daniel Bevenius (JIRA)

FileGatewayListener: Does not support overwriting of processed files. --------------------------------------------------------------------- Key: JBESB-2401 URL: https://jira.jboss.org/jira/browse/JBESB-2401 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.6 In version 4.3 it was possible to have the processed file overwritten when a new file with the same name is later processed. This was possible as FileUtil previously first tried to rename the file but if it was unsuccessful it would copy the contents of the new file to the old replacing its content. Add a test that verifies that the file contents is overwritten and not only that the file was renamed so we can maintain this -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1646) Add support for making schedule-provider Jobs clusterable

by Tom Fennelly (JIRA)

Add support for making schedule-provider Jobs clusterable --------------------------------------------------------- Key: JBESB-1646 URL: http://jira.jboss.com/jira/browse/JBESB-1646 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly This should support "singleton" execution of a job in a clustered env, with fail-over etc. See http://java-x.blogspot.com/2006/12/using-quartz-scheduler-in-cluster.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-2203) Duplicate service names during cluster startup

by Joakim Sandström (JIRA)

Duplicate service names during cluster startup ---------------------------------------------- Key: JBESB-2203 URL: https://jira.jboss.org/jira/browse/JBESB-2203 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.4 Environment: jboss esb cluster, replicated mysql 5.1. Reporter: Joakim Sandström If I startup more than one cluster node at the same time when uddi is empty it will be populated as follows: -Service A -- node1 EPR -Service A -- node2 EPR Expected uddi content; -Service A --node1 EPR --node2 EPR The esb cluster nodes access the same mysq node (transaction READ_COMMITTED). -- 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, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2445) The update to the message context has broken serialisation with older versions

by Kevin Conner (JIRA)

The update to the message context has broken serialisation with older versions ------------------------------------------------------------------------------ Key: JBESB-2445 URL: https://jira.jboss.org/jira/browse/JBESB-2445 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 The message context was previously unused but was modified, by me I must admit, so that we could usefully distinguish between message context and message contents. Unfortunately this breaks when an old version of a serialized message is read by the new version. The fix is straight forward, add the following into the ContextImpl for the serialized format. /** * Deserialise the object, checking for old versions. * @param ois The object input stream. * @throws IOException For IO exceptions during object deserialisation. * @throws ClassNotFoundException If dependent classes cannot be found. */ private void readObject(final ObjectInputStream ois) throws IOException, ClassNotFoundException { ois.defaultReadObject() ; if (context == null) { context = new HashMap<String, Serializable>() ; } } The XML variant is correct. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2443) Merge JBESB-2025 : EBWS WS-Addressing does not work

by Tom Fennelly (JIRA)

Merge JBESB-2025 : EBWS WS-Addressing does not work --------------------------------------------------- Key: JBESB-2443 URL: https://jira.jboss.org/jira/browse/JBESB-2443 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Web Services Affects Versions: 4.4 Reporter: Tom Fennelly Assignee: Kevin Conner Fix For: 4.5 I tried to sent this WS-A enabled message to EBWS service <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:say="http://www.jboss.org/sayHi"> <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"> <wsa:MessageID>urn:esb:1234567</wsa:MessageID> <wsa:To>http://example.com/To</wsa:To> <wsa:Action>http://example.com/Action</wsa:Action> </soapenv:Header> <soapenv:Body> <say:sayHi xmlns:say="http://www.jboss.org/sayHi"> <say:arg0>This is real QA message</say:arg0> </say:sayHi> </soapenv:Body> </soapenv:Envelope> and the server generates exception 2008-09-11 13:43:48,094 WARN [org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler] Unable to resolve replyAction for {http://soa.jboss.org/Unsecured}invoke 2008-09-11 13:43:48,094 ERROR [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Exception during handler processing javax.xml.ws.addressing.AddressingException: Required addressing property missing: {http://www.w3.org/2005/08/addressing}Action at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.appendRequiredHeader(SOAPAddressingPropertiesImpl.java:304) at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.writeHeaders(SOAPAddressingPropertiesImpl.java:257) at org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler.handleResponseOrFault(WSAddressingServerHandler.java:156) at org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler.handleOutbound(WSAddressingServerHandler.java:92) at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140) at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callResponseHandlerChain(HandlerDelegateJAXWS.java:95) at org.jboss.ws.core.server.ServiceEndpointInvoker.callResponseHandlerChain(ServiceEndpointInvoker.java:131) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:263) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:410) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:273) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:190) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:123) at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) 2008-09-11 13:43:48,094 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception javax.xml.ws.addressing.AddressingException: Required addressing property missing: {http://www.w3.org/2005/08/addressing}Action at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.appendRequiredHeader(SOAPAddressingPropertiesImpl.java:304) at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.writeHeaders(SOAPAddressingPropertiesImpl.java:257) at org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler.handleResponseOrFault(WSAddressingServerHandler.java:156) at org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler.handleOutbound(WSAddressingServerHandler.java:92) at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140) at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callResponseHandlerChain(HandlerDelegateJAXWS.java:95) at org.jboss.ws.core.server.ServiceEndpointInvoker.callResponseHandlerChain(ServiceEndpointInvoker.java:131) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:263) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:410) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:273) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:190) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:123) at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) 2008-09-11 13:43:48,096 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception javax.xml.ws.addressing.AddressingException: Required addressing property missing: {http://www.w3.org/2005/08/addressing}Action at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.appendRequiredHeader(SOAPAddressingPropertiesImpl.java:304) at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.writeHeaders(SOAPAddressingPropertiesImpl.java:257) at org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler.handleResponseOrFault(WSAddressingServerHandler.java:156) at org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler.handleOutbound(WSAddressingServerHandler.java:92) at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140) at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callResponseHandlerChain(HandlerDelegateJAXWS.java:95) at org.jboss.ws.core.server.ServiceEndpointInvoker.callResponseHandlerChain(ServiceEndpointInvoker.java:131) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:263) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:410) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:273) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:190) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:123) at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) The same happens even if wsa:replyTo header is present. Moreover if replyTo is not used the fault is returned <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header></env:Header><env:Body><env:Fault xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><faultcode>env:Server</faultcode><faultstring>Required addressing property missing: {http://www.w3.org/2005/08/addressing}Action</faultstring></env:Fault></env:Body></env:Envelope> but if replyTo is used then it returns empty string -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2441) Merge JBESB-1984: XSD validation in AbstractProcessingPipeline can fail in legacy environments

by Tom Fennelly (JIRA)

Merge JBESB-1984: XSD validation in AbstractProcessingPipeline can fail in legacy environments ---------------------------------------------------------------------------------------------- Key: JBESB-2441 URL: https://jira.jboss.org/jira/browse/JBESB-2441 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Tom Fennelly Assignee: Kevin Conner Priority: Critical Fix For: 4.5 In AbstractProcessingPipeline the message payload is accessed by direct call of message.get() for purpose of XSD validations. I thing the access should be via MessagePayloadProxy class as in other parts of the codebase to work correctly in legacy environment. -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2429) Merge JBESB-2179 - Add Tomcat support for HTTP Gateway

by Tom Fennelly (JIRA)

Merge JBESB-2179 - Add Tomcat support for HTTP Gateway ------------------------------------------------------ Key: JBESB-2429 URL: https://jira.jboss.org/jira/browse/JBESB-2429 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Reporter: Tom Fennelly Assignee: Kevin Conner Fix For: 4.5 >From the LegStar work. -- 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, 2 months

2
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2009