May 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3200) esb.juddi.xml contains juddi.keygeneratorr

by Ryan Hochstetler (JIRA)

esb.juddi.xml contains juddi.keygeneratorr ------------------------------------------ Key: JBESB-3200 URL: https://jira.jboss.org/jira/browse/JBESB-3200 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.7 Environment: ESB 4.7 installed via packaged installer to JBoss AS 5.1 Reporter: Ryan Hochstetler jbossesb-4.7\lib\jbossesb-registry.sar\esb.juddi.xml contains a typo as packaged in the 4.7 AS installation zip. <entry key="juddi.keygeneratorr">org.apache.juddi.keygen.KeyGenerator</entry> Note the extra trailing 'R' in the key. Eliminating the typo prevents system boot because the value of this entry must be a concrete class. The correct value is org.apache.juddi.keygen.DefaultKeyGenerator The reason this works with the typo in place is because org.apache.juddi.keygen.KeyGeneratorFactory is coded to provide an instance of DefaultKeyGenerator when no value has been set for the property juddi.keygenerator -- 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

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3164) Deprecated HttpResponse and HttpHeader cannot be used

by Kevin Conner (JIRA)

Deprecated HttpResponse and HttpHeader cannot be used ----------------------------------------------------- Key: JBESB-3164 URL: https://jira.jboss.org/jira/browse/JBESB-3164 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 Reporter: Kevin Conner While these are compatible with the signature they cannot be used at runtime. The HttpResponse created by HttpRouter creates an instance of the new subclass. Also, the new HttpHeader subclass is created which means that the getHeaders method will not return any values. -- 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

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3091) Merge Programmers and Services Guide

by Fernando Ribeiro (JIRA)

Merge Programmers and Services Guide ------------------------------------ Key: JBESB-3091 URL: https://jira.jboss.org/jira/browse/JBESB-3091 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.7 Reporter: Fernando Ribeiro It would be a good idea to merge these two guides, which are really targeted at the same audience, and lower the number of documents that need to be maintained across changes. -- 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

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1912) There are two HttpRouter actions in codebase

by Jiri Pechanec (JIRA)

There are two HttpRouter actions in codebase -------------------------------------------- Key: JBESB-1912 URL: https://jira.jboss.org/jira/browse/JBESB-1912 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Jiri Pechanec Fix For: 4.4 CP1 There is org.jboss.soa.esb.actions.routing.HttpRouter action. This action does not support standard router features and should be removed. -- 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

14 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-2748) Statistics in JBossESB console contains null values

by Jiri Pechanec (JIRA)

Statistics in JBossESB console contains null values --------------------------------------------------- Key: JBESB-2748 URL: https://jira.jboss.org/jira/browse/JBESB-2748 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management, Tooling Affects Versions: 4.4 CP3 Environment: SOA-P 4.3 CP02 ER3 - plain all config Reporter: Jiri Pechanec Whenever the statisccs are collected and recorded the management console displays two values - one with real data and second with null value 07-16 13:35:29 0 07-16 13:35:29 null It is enough just to start server and hit Collect statistics button in console -- 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

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2974) No documentation for how to include .jar files or .class files in an ESB archive (like for a custom action, etc.)

by Aaron Pestel (JIRA)

No documentation for how to include .jar files or .class files in an ESB archive (like for a custom action, etc.) ----------------------------------------------------------------------------------------------------------------- Key: JBESB-2974 URL: https://jira.jboss.org/jira/browse/JBESB-2974 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.6 Reporter: Aaron Pestel There is currently no product documentation that I can find for how to include .jar files or .class files in an ESB archive. It appears that in ESB 4.6 and earlier, you can put jars in any folder of the .esb archive. In ESB 4.7, that seems to be changing because of the move to AS 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

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2800) SOAPClient does not allow specification of content type in the http header

by Pavel Drozd (JIRA)

SOAPClient does not allow specification of content type in the http header -------------------------------------------------------------------------- Key: JBESB-2800 URL: https://jira.jboss.org/jira/browse/JBESB-2800 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.3 Reporter: Pavel Drozd SOAPClient does not allow communication in SOAP 1.2 with Axis Webservice. Axis requires (in SOAP1.2) specific content type in the http header (application/soap+xml). The SOAPClient does not allow to change this and allways fills the content type by the string "text/xml", which is specific for SOAP1.1. -- 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

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2798) QS: transfrorm_XML2XML_simple - org.jboss.soa.esb.testutils.JMSUtil class missing

by Boris Belovic (JIRA)

QS: transfrorm_XML2XML_simple - org.jboss.soa.esb.testutils.JMSUtil class missing --------------------------------------------------------------------------------- Key: JBESB-2798 URL: https://jira.jboss.org/jira/browse/JBESB-2798 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 Reporter: Boris Belovic In build.xml ( on line 22) in transform_XML2XML_simple quickstart is notifyUpdate target which depends on org.jboss.soa.esb.testutils.JMSUtil class. This target fails because this class is no more part of ESB, other targets work fine for this quickstart. Target with missing class: <target name="notifyUpdate" depends="compile" description="Send a notification message to the JMS Topic"> <echo>Sending transformation update notification for transform "simple-transform" to deployed ESB.</echo> <java fork="yes" classname="org.jboss.soa.esb.testutils.JMSUtil" failonerror="true" classpathref="exec-classpath"> <arg value="topic/org.jboss.soa.esb.transformation.Update"/> <arg value="topic"/> <arg value="simple-transform"/> </java> </target> and the exception which this target throws: Caused by: java.lang.ClassNotFoundException: org.jboss.soa.esb.testutils.JMSUtil [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:200) [java] at java.security.AccessController.doPrivileged(Native Method) [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:307) [java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:252) [java] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) [java] Could not find the main class: org.jboss.soa.esb.testutils.JMSUtil. Program will exit. -- 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

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2634) Can not use mode=OUT in @WebParam

by Lan Chen (JIRA)

Can not use mode=OUT in @WebParam --------------------------------- Key: JBESB-2634 URL: https://jira.jboss.org/jira/browse/JBESB-2634 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Affects Versions: 4.5 Environment: jbossesb-server-4.5.GA Reporter: Lan Chen I tried to add company required response header information (bottom up design, generate wsdl file by annotations) 1. By @WebResult (header=true) The header part published correctly in wsdl file but transfered in SOAP:body instead of SOAP:header 2. By @WebParam(mode=OUT) This cause deploy error. Any suggestions? Thanks. Lan -- 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

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2624) Error running bpm_orchestration3

by Marek Baluch (JIRA)

Error running bpm_orchestration3 -------------------------------- Key: JBESB-2624 URL: https://jira.jboss.org/jira/browse/JBESB-2624 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 CP2 Reporter: Marek Baluch Running this step of the quickstart: 5. In Window1, if the Instance ID you found in Step 4 was 1, type 'ant -Dtoken=1 signalProcess' produces the following error: Buildfile: build.xml BUILD FAILED Target "signalProcess" does not exist in the project "Quickstart_bpm_orchestration3". The signalProcess targer in the ant build file is needed in order to continue with the quickstart. -- 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

14 years, 9 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2010