July 2008 - 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

15 years, 9 months

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

15 years, 9 months

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

15 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination

by Daniel Bevenius (JIRA)

JBossRemotingGateway listener should support multiple listeners for the same host port combination -------------------------------------------------------------------------------------------------- Key: JBESB-1557 URL: http://jira.jboss.com/jira/browse/JBESB-1557 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.3 Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Fix For: 4.3 Add support for having multiple jbr listeners listen to the same host port combination: <jbr-provider name="JBR-Http" protocol="http" host="localhost" path="service1"> <jbr-bus busid="Http-1" port="8765" /> </jbr-provider> <jbr-provider name="JBR-Http2" protocol="http" host="localhost" path="service2"> <jbr-bus busid="Http-2" port="8765"/> </jbr-provider> Also notice the addition of the path configuration parameter. This is intended to identify the path that will be used by a ws client that calls the service. Talked to Tom and he suggested placing the path property on the jbr-bus element so I'll change that. The attached example uses this way just as a proof-of-concept (too lazy to change it right now) The path is used by the JBossRemoteGatewayListener as the subsystem when adding InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting Connectors that share the same host/port combination, and adding InvokationHandlers to them with the above specifed path as their subsystem. This solution requires that the JBoss Remoting ServerInvoker be modified and adding something like this: String subsystem = invocation.getSubsystem(); String clientId = invocation.getSessionId(); Map requestPayload = invocation.getRequestPayload(); if ( subsystem == null && requestPayload != null ) { String path = (String) requestPayload.get( HTTPMetadataConstants.PATH ); subsystem = path.substring( path.indexOf( '/' ) + 1 ); } log.info( "subsystem : " + subsystem ); This is needed so it can set the incoming path as the target subsystem. I'm not sure if this is the best way to do this but I'll ask in the Remoting forum if they have a better suggestion. Really, the gain with this is that we can have multiple webservice running in a ESB instance using the same port. This is important because we it becomes difficult opening a separate port for every web service. This is the issue we are facing at the moment. Note that this solution does not work when running multiple ESB instances on the same machine, as this would still cause a port conflict. The solution is specific to a single JVM. Any thought or comments on this? -- 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

15 years, 10 months

3
15
0 / 0

[JBoss JIRA] Created: (JBESB-1780) Generate wsdl for the ESB service when the in/out schema file is defined.

by Jim Ma (JIRA)

Generate wsdl for the ESB service when the in/out schema file is defined. ------------------------------------------------------------------------- Key: JBESB-1780 URL: http://jira.jboss.com/jira/browse/JBESB-1780 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Jim Ma -- 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

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1575) create unit test for freemarker smooks transformation in soapui-client

by Stefano Maestri (JIRA)

create unit test for freemarker smooks transformation in soapui-client ---------------------------------------------------------------------- Key: JBESB-1575 URL: http://jira.jboss.com/jira/browse/JBESB-1575 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Stefano Maestri Assigned To: Stefano Maestri -- 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

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-651) Update PackageJmsMessageContents to set the JMS header field JMSCorreletionID on the ESB Message Object body

by Daniel Bevenius (JIRA)

Update PackageJmsMessageContents to set the JMS header field JMSCorreletionID on the ESB Message Object body ------------------------------------------------------------------------------------------------------------ Key: JBESB-651 URL: http://jira.jboss.com/jira/browse/JBESB-651 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Daniel Bevenius Assigned To: Mark Little Priority: Minor PackageJmsMessageContents currently adds the JMS header field JMSMessageID to the body of the ESB Message Object: if (jmsMsg.getJMSMessageID()!=null) { message.getBody().add("MessageId", jmsMsg.getJMSMessageID()); } It would be nice to add the JMSCorrelationID aswell, and perhaps other JMSHeader fields that can be set by an application. As far as I know the only others one besides the correlation id that can be set by an application are JMSType and JMSReplyTo. -- 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

15 years, 10 months

2
12
0 / 0

[JBoss JIRA] Created: (JBESB-652) Refactory JMSRouter to simplfy setting properties on JMSMessage from ESB Message object

by Daniel Bevenius (JIRA)

Refactory JMSRouter to simplfy setting properties on JMSMessage from ESB Message object --------------------------------------------------------------------------------------- Key: JBESB-652 URL: http://jira.jboss.com/jira/browse/JBESB-652 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Assigned To: Mark Little Priority: Minor The use case for this is that we need to set the correlation id of the JMSMessage before it is sent by the JMSRouter. We have previously subclassed JMSRouter but this was not the best solution as we needed to override the route method and duplicate most of the code. I would be nice to have a method that would be called from the route method that looked something like this: setJMSProperties ( jmsMessage, esbMsg ); The default implementation could do nothing but would let subclasses only override this method. -- 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

15 years, 10 months

2
10
0 / 0

[JBoss JIRA] Created: (JBESB-1697) Docs refer to bossesb-listener.xml and jbossesb-gateway.xml

by Len DiMaggio (JIRA)

Docs refer to bossesb-listener.xml and jbossesb-gateway.xml ----------------------------------------------------------- Key: JBESB-1697 URL: http://jira.jboss.com/jira/browse/JBESB-1697 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 CP2 Reporter: Len DiMaggio Assigned To: Joshua Wulf Project JIRA for SOA-534 -- 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

15 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1574) Add freemarker support to soapui-client smook transoformation

by Stefano Maestri (JIRA)

Add freemarker support to soapui-client smook transoformation ------------------------------------------------------------- Key: JBESB-1574 URL: http://jira.jboss.com/jira/browse/JBESB-1574 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Stefano Maestri Assigned To: Stefano Maestri Tom fennely says: <tfennelly> I just had a quick look at that soapclient stuff and it doesn't support dynamic values going into the transforms, but it wouldn't be difficult to add it <maeste> ok, perfect, I can take a look if is fine for you. Any hints? <tfennelly> sure <maeste> I'm going to open a Jira issue <tfennelly> so look at the SoapUIClientService class in the soapui-client service <tfennelly> sure <tfennelly> it receives a parameter map that contains the params to be mapped into the SOAP request template <tfennelly> you could also use this map to carry the params that are to be used in the transformation <tfennelly> e.g. a value to be inserted as a header <maeste> ok I see <tfennelly> just push this map into the applySmooksTransform and set it into the BeanAccessor context <tfennelly> Ithis will make this map available to e.g. freemarker templates <tfennelly> then you just write a freemarker template that uses the dynamic value... <tfennelly> smooks will add the result of the templating op to the SOAP header -- 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

15 years, 10 months

3
15
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2008