January 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-567) BAM-like capabilities within the core ESB

by Mark Little (JIRA)

BAM-like capabilities within the core ESB ----------------------------------------- Key: JBESB-567 URL: http://jira.jboss.com/jira/browse/JBESB-567 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: BPM, Tooling Reporter: Mark Little Assigned To: Kurt Stam Priority: Critical Fix For: 4.2 As we discussed, using something like Rules would be a great approach because it gives us the flexibility of dynamic updates to the system without requiring recompilations or redeployments. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1459) Services should be unique by node:esb:category:service

by Tom Cunningham (JIRA)

Services should be unique by node:esb:category:service ------------------------------------------------------ Key: JBESB-1459 URL: http://jira.jboss.com/jira/browse/JBESB-1459 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.3 Currently, services are unique by : node:esb:service They should be unique by : node:esb:category:service >From Kevin: The gateway generator enforces a unique service name within an esb but it does not take the category into account. It looks like you may have added this requirement into the code at some point, can you remember why the category was never used? -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1479) webservice_wsaddressing fails with NullPointerException due to failure to inject WebServiceContext

by Kevin Conner (JIRA)

webservice_wsaddressing fails with NullPointerException due to failure to inject WebServiceContext -------------------------------------------------------------------------------------------------- Key: JBESB-1479 URL: http://jira.jboss.com/jira/browse/JBESB-1479 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.3 -- 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, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-570) Configuration of JBoss AS installation directory in deployment.properties for ESB trailblazers fails if a relative path is used or the path name contains spaces

by Pete Bennett (JIRA)

Configuration of JBoss AS installation directory in deployment.properties for ESB trailblazers fails if a relative path is used or the path name contains spaces ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-570 URL: http://jira.jboss.com/jira/browse/JBESB-570 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 2 Environment: Fedora Core 6 J2SE 5 Ant 1.6.5 Reporter: Pete Bennett Assigned To: Mark Little Priority: Minor In the Quickstart guide and the Trailblazers, one needs to configure the deployment.properties file to point at an installation of JBoss AS with EJB3 enabled. If the path specified includes a space then things will seem to work, but when you try to start up the JBoss AS server for the Quickstart example, you get an error in the JBoss AS console Window when the ESB service tries to parse this pass as follows: 11:14:06,973 INFO [DatabaseInitializer] Initializing java:/juddiDB from listed sql files 11:14:07,166 INFO [JuddiRMIService] starting juddi RMI service 11:14:07,171 WARN [ServiceController] Problem starting service jboss.esb:service=JuddiRMI java.net.URISyntaxException: Illegal character in path at index 31: file:/home/pbennett/JBoss/JBoss ESB/4.2MR2/jbossesb-server/server/default/deploy/jbossesb.sar/esb.juddi.properties at java.net.URI$Parser.fail(URI.java:2816) at java.net.URI$Parser.checkChars(URI.java:2989) at java.net.URI$Parser.parseHierarchical(URI.java:3073) at java.net.URI$Parser.parse(URI.java:3021) at java.net.URI.<init>(URI.java:578) at org.jboss.internal.soa.esb.dependencies.JuddiRMIService.startService(JuddiRMIService.java:63) ... If you use a relative path rather than an absolute path, then the Quickstart example works when run from the original directory but the other Trailblazer examples fail to find the correct directory as they look relative to themselves rather than relative to the root. -- 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, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-1508) BPM quickstarts should use only JMS transports and they should be configured to participate in transactions

by Jiri Pechanec (JIRA)

BPM quickstarts should use only JMS transports and they should be configured to participate in transactions ----------------------------------------------------------------------------------------------------------- Key: JBESB-1508 URL: http://jira.jboss.com/jira/browse/JBESB-1508 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Environment: soa-4.2.0.CR1.zip standalone-soa-4.2.0.CR1.zip Reporter: Jiri Pechanec Assigned To: Kevin Conner Fix For: 4.2.1 CP1 It is good practice to show customer how the BPM should be used correctly - to avoid problems with message duplicates, callback responses coming before process is committed etc. -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1428) JbossRemotingGatewayListener sending hardcoded string as response

by Vinicius Carvalho (JIRA)

JbossRemotingGatewayListener sending hardcoded string as response ----------------------------------------------------------------- Key: JBESB-1428 URL: http://jira.jboss.com/jira/browse/JBESB-1428 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 Reporter: Vinicius Carvalho The class sends an "<ack/>" as a response when it's used in asynchronous way. One should be able to set the response contents (for instance, for oneway operations on WS called by the SOAPProcessor) -- 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, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (JBESB-467) Reducing registry lookup overhead

by Mark Little (JIRA)

Reducing registry lookup overhead --------------------------------- Key: JBESB-467 URL: http://jira.jboss.com/jira/browse/JBESB-467 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository, Rosetta Affects Versions: 4.0 Reporter: Mark Little Assigned To: Kurt Stam Priority: Critical Fix For: 4.2, 5.0 >From our previous discussion on reducing registry lookup overhead (currently lookup per message send): There are a number of solutions to this and we should try to support them all eventually: (i) EPR lifetime: service deployers can register a lifetime associated with the EPR in the registry and when something reads the EPR it also receives information on how long the EPR will remain valid for. After that time elapses, clients must go back to the registry to get a new copy. (ii) building on (i), EPRs can be marked as persistent - they never change so one lookup will always be enough. (iii) interactions with services are scoped by sessions and the EPR is assumed to remain valid for the duration of the session. The service can be marked as useable within such a session. (iv) EPRs are looked up once per client lifecycle and only rebound if the service fails. If you recall from the original ESB architecture document, service migration is something that is on the roadmap (5.0) and if a service moves it can leave a forwarding address (EPR) and the architecture allows messages to be redirected and eventually short-cut, i.e., the client EPR is updated with the new EPR transparently as a result of receiving a response from a different endpoint. (iii) and (iv) are really for the 5.0 architecture. However, it should be possible to add something along (i) and (ii) for 4.0. What do you think? -- 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, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-1519) NotifyJMS creates sessions array but never uses anything other than element 0

by Mark Little (JIRA)

NotifyJMS creates sessions array but never uses anything other than element 0 ----------------------------------------------------------------------------- Key: JBESB-1519 URL: http://jira.jboss.com/jira/browse/JBESB-1519 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Mark Little Fix For: 4.3 In the code ... /** * The javax.jms.Session instance used to talk to JMS */ protected Session[] sessions; then ... if(obj == null) { // create a null payload message... jmsMessage = sessions[0].createObjectMessage(null); } else if(obj instanceof byte[]) { jmsMessage = sessions[0].createObjectMessage((byte[]) obj); but ... final int nrQueuesOrTopics = configTrees.length; producers = new MessageProducer[nrQueuesOrTopics]; connectionPools = new JmsConnectionPool[nrQueuesOrTopics]; sessions = new Session[nrQueuesOrTopics]; -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1342) 30 character limit of tablenames in Oracle

by Kurt Stam (JIRA)

30 character limit of tablenames in Oracle ------------------------------------------ Key: JBESB-1342 URL: http://jira.jboss.com/jira/browse/JBESB-1342 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Reporter: Kurt Stam Fix For: 4.2.1 CP1 The JBossESB console needs transformationresourceparameter and transformationresourceparameterspec tables, whos names are too long (tablename length limited into 30 characters in Oracle). -- 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, 9 months

5
6
0 / 0

[JBoss JIRA] Created: (JBESB-1365) Make an Eclipse plugin for ESB configuration editor

by Mark Little (JIRA)

Make an Eclipse plugin for ESB configuration editor ---------------------------------------------------- Key: JBESB-1365 URL: http://jira.jboss.com/jira/browse/JBESB-1365 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Daniel Bevenius Fix For: 4.3 -- 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, 9 months

4
16
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2008