February 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1486) jUDDI using BRMS as repository

by Mark Little (JIRA)

jUDDI using BRMS as repository ------------------------------ Key: JBESB-1486 URL: http://jira.jboss.com/jira/browse/JBESB-1486 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Kurt Stam Fix For: 5.0 -- 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

16 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1460) jms-jca-provider doesn't read from queues on different node

by Martin Vecera (JIRA)

jms-jca-provider doesn't read from queues on different node ----------------------------------------------------------- Key: JBESB-1460 URL: http://jira.jboss.com/jira/browse/JBESB-1460 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters, Rosetta Affects Versions: 4.2.1 Environment: 2x RHEL5, SOA-P 4.2.0 beta 1, Oracle 10g Reporter: Martin Vecera Priority: Blocker While I was trying ESB load balancing and failover I found out the following issue... Scenario: 1. Two nodes (hostnames: jawa02, jawa04), sharing the same DB, different ServerPeerIDs but no JMS clustering. 2. I generated a message backlog on jawa02 queue/A (10,000 messages). 3. See my simple service configuration: <providers> <jms-jca-provider name="JBossMessaging" connection-factory="XAConnectionFactory" jndi-URL="jnp://jawa02:1099" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces" transacted="false"> <jms-bus busid="quickstartGwChannel"> <jms-message-filter dest-type="QUEUE" dest-name="queue/A" /> </jms-bus> </jms-jca-provider> <jms-jca-provider name="JBossMessaging" connection-factory="XAConnectionFactory" jndi-URL="jnp://jawa04:1099" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces" transacted="false"> <jms-bus busid="quickstartEsbChannel"> <jms-message-filter dest-type="QUEUE" dest-name="queue/C" /> </jms-bus> </jms-jca-provider> </providers> <services> <service category="FirstServiceESB" name="SimpleListener" description="Hello World"> <listeners> <jms-listener name="ESB-Gateway" busidref="quickstartGwChannel" maxThreads="4" is-gateway="true" /> <jms-listener name="helloWorld" busidref="quickstartEsbChannel" maxThreads="4" /> </listeners> <actions mep="OneWay"> <action name="notificationAction" class="org.jboss.soa.esb.actions.Notifier"> <property name="okMethod" value="notifyOK" /> <property name="notification-details"> <NotificationList type="OK"> <target class="NotifyConsole" /> </NotificationList> </property> </action> </actions> </service> </services> 4. I deployed the described service to jawa04 and expected it to start processing the messages from jawa02 queue/A but this didn't happen. 5. When I changed the GW provider from jms-jca-provider to jms-provider: <jms-provider name="JBossMessaging" connection-factory="XAConnectionFactory" jndi-URL="jnp://jawa02:1099" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces"> It worked as expected. Unfortunatelly jms-provider doesn't use ServiceInvoker and thus no load balancing/failover is possible. This makes the ESB failover impossible using JMS. Solution: 1) make jms-jca-provider read the messages from different nodes in the way jms-provider does it. or 2) make jms-provider use ServiceInvoker -- 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

16 years, 2 months

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-1412) Ability to send message payload as an attachment

by Kenneth Larsen (JIRA)

Ability to send message payload as an attachment ------------------------------------------------ Key: JBESB-1412 URL: http://jira.jboss.com/jira/browse/JBESB-1412 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Kenneth Larsen Attachments: NotifyEmailPatch.patch It would be nice to have the option of sending the message payload as an attachment when using the EMailNotifier instead of always having to include the message payload into the mail body. In some cases the payload might be binary content which is inappropriate in the mail body. By specifying an additional attribute for the target the payload should be attached to the mail: <target class="NotifyEmail" from="sender(a)domain.com" sendTo="recipient(a)anotherdomain.com" subject="subject for message" msgAttachmentName="attachmentname.ext"> In the example above a new attribute has been introduced (msgAttachmentName). If specified the payload is created as an attachment with the specified filename instead of being part of the mail body. -- 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

16 years, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-1391) NTLMConfigurator

by Faisal Azizullah (JIRA)

NTLMConfigurator ---------------- Key: JBESB-1391 URL: http://jira.jboss.com/jira/browse/JBESB-1391 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Environment: JBOSS ESB 4.2.1 GA Reporter: Faisal Azizullah Fix For: 4.2.1 package org.jboss.soa.esb.http.configurators; /* * *@ author: Faisal Azizullah *@ company : Lewisville ISD * */ import org.apache.commons.httpclient.HttpClient; import org.apache.commons.httpclient.Credentials; import org.apache.commons.httpclient.NTCredentials; import org.apache.commons.httpclient.auth.AuthScope; import org.jboss.soa.esb.ConfigurationException; import org.jboss.soa.esb.http.Configurator; import java.util.Properties; /** * HTTP NTLM Authentication Configurator. * * Properties: * <ul> * <li>username: See {@link NTCredentials}. (Required)</li> * <li>password: See {@link NTCredentials}. (Required)</li> * <li>authscope-host: See {@link AuthScope}. (Required)</li> * <li>authscope-port: See {@link AuthScope}. (Required)</li> * <li>authscope-domain: See {@link AuthScope}. (Required)</li> * <li>authscope-realm: See {@link AuthScope}. (Optional)</li> * </ul> * * See <a href="http://jakarta.apache.org/commons/httpclient/authentication.html">HttpClient Authentication Guide</a>. * * */ public class AuthNTLM extends Configurator { public void configure(HttpClient httpClient, Properties properties) throws ConfigurationException { String username = properties.getProperty("ntauth-username"); String password = properties.getProperty("ntauth-password"); String authScopeHost = properties.getProperty("ntauthscope-host"); String authScopePort = properties.getProperty("ntauthscope-port"); String authScopeRealm = properties.getProperty("ntauthscope-realm"); String authScopeDomain = properties.getProperty("ntauthscope-domain"); assertPropertySetAndNotBlank(username, "ntauth-username"); assertPropertySetAndNotBlank(password, "ntauth-password"); assertPropertySetAndNotBlank(authScopeHost, "ntauthscope-host"); assertPropertyIsInteger(authScopePort, "ntauthscope-port"); assertPropertySetAndNotBlank(authScopeDomain, "ntauthscope-domain"); Credentials creds = new NTCredentials(username, password,authScopeHost,authScopeDomain); AuthScope authScope; if(authScopeRealm != null && !authScopeRealm.trim().equals("")) { authScope = new AuthScope(authScopeHost, Integer.parseInt(authScopePort), authScopeRealm); } else { authScope = new AuthScope(authScopeHost, Integer.parseInt(authScopePort)); } httpClient.getState().setCredentials(authScope, creds); } } -- 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

16 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1350) Action for invoking SLSB methods

by Dominik Kunz (JIRA)

Action for invoking SLSB methods -------------------------------- Key: JBESB-1350 URL: http://jira.jboss.com/jira/browse/JBESB-1350 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Dominik Kunz Attachments: EJBProcessor.java Action for invoking SLSB methods using the reflection API. Configurable through jboss-esb.xml. -- 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

16 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-1143) NotifySocket needed

by Jarek Pekala (JIRA)

NotifySocket needed ------------------- Key: JBESB-1143 URL: http://jira.jboss.com/jira/browse/JBESB-1143 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Jarek Pekala Assigned To: Mark Little I need new Notify class (NotifySocket) to send notification over TCP/IP -- 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

16 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-1376) Message copy capability

by Mark Little (JIRA)

Message copy capability ----------------------- Key: JBESB-1376 URL: http://jira.jboss.com/jira/browse/JBESB-1376 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1375) Revisit ResponseHeader location

by Mark Little (JIRA)

Revisit ResponseHeader location ------------------------------- Key: JBESB-1375 URL: http://jira.jboss.com/jira/browse/JBESB-1375 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Fix For: 4.3 Need to discuss with TomF about package (and reason for) ResponseHeader. -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1385) Upgrade Smooks to version 1.0

by Daniel Bevenius (JIRA)

Upgrade Smooks to version 1.0 ----------------------------- Key: JBESB-1385 URL: http://jira.jboss.com/jira/browse/JBESB-1385 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.3 Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Minor Fix For: 4.3 Update the Smooks jars to version 1.0 (when released). Clean up code where needed and remove imports that are no longer being used. We have already upgraded our ESB server as we needed som new of the new features. -- 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

16 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-1513) ESB test suite against external binaries

by Aleksandar Kostadinov (JIRA)

ESB test suite against external binaries ---------------------------------------- Key: JBESB-1513 URL: http://jira.jboss.com/jira/browse/JBESB-1513 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build and Release, Testing Affects Versions: 4.2.1 CP1 Reporter: Aleksandar Kostadinov Assigned To: Kevin Conner Fix For: 4.2.1 CP1 Kevin, many thanks for your offer to go through the build files and to make sure it runs against external binaries. I'm creating that issue so this can be tracked. Please let me know any estimate based on your schedule on how soon would you be able to look at that. -- 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

16 years, 2 months

5
19
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2008