September 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1020) JmsGatewayListener contains System.out.err logging.

by Daniel Bevenius (JIRA)

JmsGatewayListener contains System.out.err logging. --------------------------------------------------- Key: JBESB-1020 URL: http://jira.jboss.com/jira/browse/JBESB-1020 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Trivial Fix For: 4.2.1 JmsGatewayListener line 143 looks like this: System.err.println("**RUNNING JMS GATEWAY RECEIVED MESSAGE**"); This line should simply be removed. -- 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, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-1039) ERROR [STDERR] **RUNNING JMS GATEWAY RECEIVED MESSAGE** generated by HelloWorld quickstart

by Len DiMaggio (JIRA)

ERROR [STDERR] **RUNNING JMS GATEWAY RECEIVED MESSAGE** generated by HelloWorld quickstart ------------------------------------------------------------------------------------------ Key: JBESB-1039 URL: http://jira.jboss.com/jira/browse/JBESB-1039 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR1 Environment: RHEL5 java version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode) JBoss ESB as downloaded from svn Sept 13, 2007 Reporter: Len DiMaggio Assigned To: Mark Little I'm seeing this ERROR written to the server log in running the HelloWorld quickstart - the logging level is ERROR, but I'm guessing that it's really just a DEBUG statement left behind... 11:35:27,814 ERROR [STDERR] **RUNNING JMS GATEWAY RECEIVED MESSAGE** 11:35:27,836 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 11:35:27,836 INFO [STDOUT] Message = Hello World 11:35:27,836 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 11:35:27,836 INFO [STDOUT] Message structure: 11:35:27,836 INFO [STDOUT] [Hello World]. -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-815) JAXB-Intros @XmlAttribute annotation handling issue

by Sylvia Isler (JIRA)

JAXB-Intros @XmlAttribute annotation handling issue --------------------------------------------------- Key: JBESB-815 URL: http://jira.jboss.com/jira/browse/JBESB-815 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports, Web Services Affects Versions: 4.2 Milestone Release 3 Environment: Windows XP v2002 sp2, JAVA 1.5_02 Reporter: Sylvia Isler Assigned To: Mark Little JAXB with JAXB-introductions fails to Marshall @XmlAttribute annotations in the following example: The following class contains a simple double for an attribute: public class UnitPrice { public double value; UnitPrice(double value){ this.value=value; } UnitPrice() { } public double getValue() { return this.value; } } The following JAXB-intros config file was used <?xml version = "1.0" encoding = "UTF-8"?> <jaxb-intros xmlns="http://www.jboss.org/xsd/jaxb/intros"> <Class name="junit.prices.UnitPrice"> <XmlType name = "UnitPrice"/> <Field name="value"> <XmlAttribute name="value" required="true" /> </Field> </Class> </jaxb-intros> along with the following schema file: <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="UnitPrice"> <xs:complexType> <xs:attribute name="value" type=xs:double use="required"/> <xs:attribute name="currency" use="optional"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="USD"/> <xs:enumeration value="Euro"/> <xs:enumeration value="JPY"/> </xs:restriction> </xs:simpleType> </xs:attribute> </xs:complexType> </xs:element> </xs:schema> To unmarshall this XML file: <?xml version="1.0" encoding="UTF-8"?> <UnitPrice value="40.0" xsi:noNamespaceSchemaLocation="C:\UnitPrice.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/> I then used the following code to test the unmarshalling of the above XML. JaxbIntros config = IntroductionsConfigParser.parseConfig(getClass().getResourceAsStream("UnitConfig.xml")); ClassIntroConfig classIntroConfig = config.getClazz().get(0); assertEquals(UnitPrice.class.getName(), classIntroConfig.getName()); IntroductionsAnnotationReader reader = new IntroductionsAnnotationReader(config); Map<String, Object> jaxbConfig= new HashMap<String, Object>(); jaxbConfig.put(JAXBRIContext.ANNOTATION_READER, reader); JAXBContext jaxbContext = JAXBContext.newInstance(new Class[] {UnitPrice.class}, jaxbConfig); Unmarshaller unmarshaller = jaxbContext.createUnmarshaller(); JAXBElement jbe = null; UnitPrice order =null; StreamSource ss = new StreamSource(getClass().getResourceAsStream("UsdUnitPrice1.xml")); jbe = unmarshaller.unmarshal(ss, UnitPrice.class); order =(UnitPrice)jbe.getValue(); try{ assertEquals("get double value error", 40.0, order.getValue()); } catch (Exception e) { fail(e.getMessage()); } a UnitPrice instance is instantiated. However, the above test code fails because the value attribute of the unmarshalled UnitPrice instance is 0.0 instead of 40.0.. After some discussion on the forums, I decided to try using <Method> tag instead of the <Field> in the config file above. When this yielded the same result, -- 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, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-1038) NotifyEmail inserts message content two times into the email

by Pavel Kadlec (JIRA)

NotifyEmail inserts message content two times into the email ------------------------------------------------------------ Key: JBESB-1038 URL: http://jira.jboss.com/jira/browse/JBESB-1038 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Reporter: Pavel Kadlec Assigned To: Mark Little NotifyEmail inserts message content two times into the email. Bug is in NotifyEmail.java, the line number 100 sMsg = ((null == sMsg) ? content : sMsg + "\n") + content; -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1022) esb fails to install cleanly into EAP production environment

by Trevor Kirby (JIRA)

esb fails to install cleanly into EAP production environment ------------------------------------------------------------ Key: JBESB-1022 URL: http://jira.jboss.com/jira/browse/JBESB-1022 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.2 Reporter: Trevor Kirby Assigned To: Kevin Conner Ant deploy generates the following error because none of the three checks match what is in the production environment :- jms.config.check: [available] Unable to find /home/trev/workspace/esbGA/jboss-eap-4.2/jboss-as/server/production/deploy/jboss-messaging to set property jbm.present [available] Unable to find /home/trev/workspace/esbGA/jboss-eap-4.2/jboss-as/server/production/deploy/jboss-messaging.sar to set property jbm.present [available] Unable to find /home/trev/workspace/esbGA/jboss-eap-4.2/jboss-as/server/production/deploy/jms/jbossmq-service.xml to set property jbmq.present [ant] Exiting /home/trev/workspace/esbGA/jbossesb-4.2GA/install/build.xml. BUILD FAILED /home/trev/workspace/esbGA/build.xml:36: The following error occurred while executing this line: /home/trev/workspace/esbGA/jbossesb-4.2GA/install/build.xml:64: Could not determine JMS provider at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:541) ================== jms in production is as follows: - ls server/production/deploy/jms hajndi-jms-ds.xml jms-ra.rar -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1036) Action documentation inappropriate

by Mark Little (JIRA)

Action documentation inappropriate ---------------------------------- Key: JBESB-1036 URL: http://jira.jboss.com/jira/browse/JBESB-1036 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 We don't have any good documentation within the docs about Action and Message relationship. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1033) Make sure wiki WS docs are in shipped docs

by Mark Little (JIRA)

Make sure wiki WS docs are in shipped docs ------------------------------------------ Key: JBESB-1033 URL: http://jira.jboss.com/jira/browse/JBESB-1033 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 http://wiki.jboss.org/wiki/Wiki.jsp?page=WebservicesSupport -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-791) Document gateway transformation mapping

by Mark Little (JIRA)

Document gateway transformation mapping --------------------------------------- Key: JBESB-791 URL: http://jira.jboss.com/jira/browse/JBESB-791 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Len: The "Transport Protocol Mediation: Gateways & Listeners" section - in the description of gateways - says '...Specific mappings of the message body/contents from its native type to the ESB type need to still be documented. Especially in the area of properties and header information...' -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1032) Add reminder comment into JMS Gateway code concerning removal of byte array

by Mark Little (JIRA)

Add reminder comment into JMS Gateway code concerning removal of byte array --------------------------------------------------------------------------- Key: JBESB-1032 URL: http://jira.jboss.com/jira/browse/JBESB-1032 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Mark Little Assigned To: Mark Little Currently JMS Gateways add the data type into the Body but also into the byte array EXCEPT where the input JMS message was a BytesMessage where it only goes into the byte array. The comment in the code currently mentions that the byte array use needs to go, which is fine as long as whoever removes it later remembers to make the BytesMessage the explicitly set the content itself. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-722) Hibernate interceptor unLoad event reports empty object

by Kevin Conner (JIRA)

Hibernate interceptor unLoad event reports empty object ------------------------------------------------------- Key: JBESB-722 URL: http://jira.jboss.com/jira/browse/JBESB-722 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Mark Little Fix For: 4.2 The hibernate interceptor catches the preLoad event and uses the entity to create the message. Unfortunately, at this point, the entity is uninitialised with the exception of any primary keys. The entity state is located in the state/propertyNames/types arrays. We need to revisit this event to pass in meaningful information. -- 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, 5 months

3
12
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2007