January 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2235) Upgrade jBPM to version 3.3.0

by Kevin Conner (JIRA)

Upgrade jBPM to version 3.3.0 ----------------------------- Key: JBESB-2235 URL: https://jira.jboss.org/jira/browse/JBESB-2235 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 -- 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, 3 months

3
22
0 / 0

[JBoss JIRA] Created: (JBESB-2286) Remove esbwizard from the project

by Daniel Bevenius (JIRA)

Remove esbwizard from the project --------------------------------- Key: JBESB-2286 URL: https://jira.jboss.org/jira/browse/JBESB-2286 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Tooling Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.5 Is no longer needed as the JBoss Developers Studio now contains wizards that replace 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2280) EULA file name and contents should match http://www.redhat.com/licenses/jboss_eula.html (html or text)

by Jeff Yu (JIRA)

EULA file name and contents should match http://www.redhat.com/licenses/jboss_eula.html (html or text) ------------------------------------------------------------------------------------------------------ Key: JBESB-2280 URL: https://jira.jboss.org/jira/browse/JBESB-2280 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 CP1 Reporter: Jeff Yu Fix For: 4.4 CP2 we need to update following files. 1. Replace the JBossORG-EULA.txt with JBossEULA.txt (http://www.redhat.com/licenses/jboss_eula.html (html or text)) 2. Update the $JBossESB/product/samples/quickstarts/conf/base-build.xml by replacing the JBossORG-EULA.txt, JEMS-EULA.txt with JBossEULA.txt -- 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, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (JBESB-2285) Service Repository support not Servicen Registry cause it is provide by JUDDI

by Daniel F?rberg (JIRA)

Service Repository support not Servicen Registry cause it is provide by JUDDI ----------------------------------------------------------------------------- Key: JBESB-2285 URL: https://jira.jboss.org/jira/browse/JBESB-2285 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Environment: JBoss ESB 4.4 or SOA Platform 4.3 Reporter: Daniel F?rberg Fix For: 4.4 Attachments: techneutralsynchbus.jpg Actually i was at the partner talk about JBoss ESB at Devoxx 08 in Antwerp. And some questions about the support the ws-stack and Service Repositories which provides an Api that can fullfill som of our customers needs regarding implementation of SOA. I spoke to an representative in Exibition hall from France and got some information. It ended up here raising JIRA, as a feature request. The software Mark Little recomended was SOA Software which is a comercial product. We do only work with open source at the company i work for, so it's not an option. Mark mention little about the DNA project. I have been i contact with a local represnative here in Sweden at Redhat also. It ended up that i sucessfully created an overview architecture with WSO2 instead. But were a little bit late, they already started the dev with Mule. I wanted to continue with, as long as they are not satisfied with Mule. We can meet up, cause we have the trust. Anyhow back to require this customer have: Lockup support of servicecontracts both in design- and runtime Adminstarte service registry/repository containing servicecontract and other metadata of interest including user acess control and authorization(WS-policy based, XACML) WS-Policy or correspondant support for implicit autentication and authorization of systems or services Scheduled publising/unpublishing of wenbservices without need for restart Adjust opening hours for services(service activation) and i provide a sketch of the suggested solution: -- 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, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-2282) Properties for requestLocation, responseLocation is nöt yet supported and validate dosen't work it crashes

by Daniel F?rberg (JIRA)

Properties for requestLocation, responseLocation is nöt yet supported and validate dosen't work it crashes ---------------------------------------------------------------------------------------------------------- Key: JBESB-2282 URL: https://jira.jboss.org/jira/browse/JBESB-2282 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4 Environment: JBoss ESB 4.4 and/or JBoss SOA Platform Reporter: Daniel F?rberg Fix For: 4.4 Properties for requestLocation, responseLocation is not yet supported and validate dosen't work it crashes. Hence the description how to use these properties are provided in the documentation. -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2283) schemas specified in properties inXsd and outXsd, does not support xml import or includes, which results in that all types must be defined in the same namspace for the request and response

by Daniel F?rberg (JIRA)

schemas specified in properties inXsd and outXsd, does not support xml import or includes, which results in that all types must be defined in the same namspace for the request and response -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-2283 URL: https://jira.jboss.org/jira/browse/JBESB-2283 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.4 Reporter: Daniel F?rberg Priority: Critical Fix For: 4.4 schemas specified in properties inXsd and outXsd, does not support xml import or includes, which results in that all types must be defined in the same namspace for the request and response. It works fine until deployment, during deployment the wsdl is generated as expected. But when running the service the xsds imported can not be found, cause they are not copied to the expanded archive for deployment procedures. -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-2227) Asynchronous sending of a fault message causes the fault to be raised

by Kevin Conner (JIRA)

Asynchronous sending of a fault message causes the fault to be raised --------------------------------------------------------------------- Key: JBESB-2227 URL: https://jira.jboss.org/jira/browse/JBESB-2227 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 CP1, 4.4 Reporter: Kevin Conner Fix For: 4.5, 4.4 CP2 -- 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, 3 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-1711) ESB unit test suite hangs when run against SOA-P CP1

by Aleksandar Kostadinov (JIRA)

ESB unit test suite hangs when run against SOA-P CP1 ---------------------------------------------------- Key: JBESB-1711 URL: http://jira.jboss.com/jira/browse/JBESB-1711 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Reporter: Aleksandar Kostadinov Assigned To: Aleksandar Kostadinov unzip SOA-P distribution in $WORKSPACE/jbosssoa chprop product.properties org.jboss.esb.server.home "$WORKSPACE/jbosssoa/jboss-as" chprop product.properties org.jboss.esb.server.config $SERVER_NAME chprop product.properties org.jboss.esb.test.ftp.hostname dev39.qa.atl.jboss.com chprop product.properties org.jboss.esb.test.ftp.user user chprop product.properties org.jboss.esb.test.ftp.pwd pass chprop product.properties org.jboss.esb.test.ftp.dir /esb-in-soa then: cd product ant org.jboss.esb.integration.test Test suite hangs after first few tests. -- 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, 3 months

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-2269) Action instantiation - configuration injection using BeanConfiguredAction or annotations

by Morten Hattesen (JIRA)

Action instantiation - configuration injection using BeanConfiguredAction or annotations ---------------------------------------------------------------------------------------- Key: JBESB-2269 URL: https://jira.jboss.org/jira/browse/JBESB-2269 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4 CP1 Reporter: Morten Hattesen Priority: Minor Change the way ESB actions are configured/instantiated, to allow Actions that implement ActionPipelineProcessor (subclasses of AbstractActionPipelineProcessor) automatically have action properties injected directly by simply implementing BeanConfiguredAction. Alternatively, property injection could be performed by adding runtime-retained annotations to the actions. Any of the above changes would make creating custom actions easier, since action properties would be directly injected into the action bean using setter-style injection. As a consequence of implementing (either of) the above change, out-of-the-box actions should be updated, where relevant. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2268) Actions that implement BeanConfiguredAction are instantiated for every process() invocation

by Morten Hattesen (JIRA)

Actions that implement BeanConfiguredAction are instantiated for every process() invocation ------------------------------------------------------------------------------------------- Key: JBESB-2268 URL: https://jira.jboss.org/jira/browse/JBESB-2268 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4 CP1 Reporter: Morten Hattesen Priority: Minor Whereas actions that extend ActionPipelineProcessor are instantiated once per action, and the process() method called on this instance, the lifecycle of actions that implement BeanConfiguredAction is entirely different, which is NOT clear from documentation or JavaDoc. An action that implements BeanConfiguredAction is instantiated on every call to the process() method, making it impossible to maintain state across invocations. This effectively renders this way of configuring Actions useless for anything but the most simple actions, since lazy-initialization is made impossible (unless static scope is employed). I see absolutely no argument for retaining the current instance-per-invocation lifecycle at all. I propose to change org.jboss.soa.esb.listeners.message.BeanConfigActionProcessor to maintain a single processor instance variable on which the process method is invoked, in the same way it is done by the org.jboss.soa.esb.listeners.message.OverriddenActionPipelineProcessor (used when an action implements ActionPipelineProcessor, which is the case on AbstractActionPipelineProcessor). Alternatively, it should be made absolutely clear in the ESB documentation, that actions that implement BeanConfiguredAction have an instance-per-invocation lifecycle, which will typically have serious performance-implications since no action-state can be maintained. -- 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, 3 months

2
2
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 2009