July 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2874) Deployers do not cleanly represent dependencies

by Kevin Conner (JIRA)

Deployers do not cleanly represent dependencies ----------------------------------------------- Key: JBESB-2874 URL: https://jira.jboss.org/jira/browse/JBESB-2874 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.8 The deployers create a separate object to represent the ESB deployment, expressing the contained dependencies, but any forced restart of this object (due to dependencies) does not redo any of the work contained in the deployer. We now have a lot of work which, as a consequence, misses out on this process. - ebws - http gateway - property substitution We need to move all this functionality into a separate object which can cleanly take part in the dependency process. -- 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

13 years, 9 months

3
13
0 / 0

[JBoss JIRA] Created: (JBESB-3365) StackOverflowError from WS Proxy with cyclic schema

by William DeCoste (JIRA)

StackOverflowError from WS Proxy with cyclic schema --------------------------------------------------- Key: JBESB-3365 URL: https://jira.jboss.org/browse/JBESB-3365 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.8 Reporter: William DeCoste Assignee: William DeCoste See attached ejb3 jar and esb files. Project also attached. Webservice via ejb3 deploys properly, but esb proxy causes StackOverflowError. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-3035) A one-way message that throws exception should not return HTTP code 500

by Kevin Conner (JIRA)

A one-way message that throws exception should not return HTTP code 500 ----------------------------------------------------------------------- Key: JBESB-3035 URL: https://jira.jboss.org/jira/browse/JBESB-3035 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.7 CP1 -- 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

13 years, 10 months

3
11
0 / 0

[JBoss JIRA] Created: (JBESB-3364) load_generator relies on auth.conf in server client directory

by Kevin Conner (JIRA)

load_generator relies on auth.conf in server client directory ------------------------------------------------------------- Key: JBESB-3364 URL: https://jira.jboss.org/browse/JBESB-3364 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.8 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Trivial Fix For: 4.9 When the auth.conf is missing, runtest-secure no longer works. The login is never executed (exception hidden) and the HTTP invocation eventually gives up after too many redirects (failure to authenticate). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3361) JBR listener drops HTTP headers

by Martin Vecera (JIRA)

JBR listener drops HTTP headers ------------------------------- Key: JBESB-3361 URL: https://jira.jboss.org/browse/JBESB-3361 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.7 CP2 Environment: SOA-5 5.0.2.CR3 Reporter: Martin Vecera In https_2way_ssl quickstart you can see that custom HTTP header is passed to the message (something like blah=blahval). If you run the QS you cannot see this header in the server output where all headers are printed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3363) Add documentation for jBPM JMS provider adapter

by Kevin Conner (JIRA)

Add documentation for jBPM JMS provider adapter ----------------------------------------------- Key: JBESB-3363 URL: https://jira.jboss.org/browse/JBESB-3363 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.7 CP2 Reporter: Kevin Conner Add the following text to the Administration Guide. Using Remote JMS Providers The JMS based Message and Scheduling services can reference remote JMS providers by allowing the configuration of a Provider Adapter within local JNDI. The Provider Adapter is an instance of the JMSProviderAdapter, as can be used within the standard application server JCA inflow configurations. The JMSProviderAdapter is configured through the addition of an MBean within a service.xml file. This can either be specific to the jBPM integration, for example added to the jbpm-service.xml, or can be shared with other JCA inflow configurations. The following example creates a provider adapter which references a remote JMS provider executing on the server located through the JNDI provider URL 192.168.1.1:1099, with the contents of the Properties attribute being used to create the JNDI InitialContext. <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=RemoteProviderLoader"> <attribute name="ProviderName">RemoteProviderAdapter</attribute> <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute> <attribute name="QueueFactoryRef">XAQueueConnectionFactory</attribute> <attribute name="TopicFactoryRef">XATopicConnectionFactory</attribute> <attribute name="Properties"> java.naming.provider.url=192.168.1.1:1099 </attribute> </mbean> The Provider Adapter is then be referenced within the JMSMessageServiceFactory and JMSSchedulerServiceFactory configurations by specifying the JNDI location through the providerAdapterJNDI field, an example of which is as follows. <service name="message"> <factory> <bean class="org.jboss.soa.esb.services.jbpm.integration.msg.JmsMessageServiceFactory"> <field name="providerAdapterJNDI"><string value="RemoteProviderAdapter"/></field> </bean> </factory> </service> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2862) Add support for XPath based routing using SXC

by Tom Fennelly (JIRA)

Add support for XPath based routing using SXC --------------------------------------------- Key: JBESB-2862 URL: https://jira.jboss.org/jira/browse/JBESB-2862 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Reporter: Tom Fennelly Fix For: 4.8 Use the existing XPathRouter and RegexRouter impls as a reference. -- 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

13 years, 10 months

1
8
0 / 0

[JBoss JIRA] Created: (JBESB-3328) Merge across JBESB_4_7_CP2_ER2 tag

by Kevin Conner (JIRA)

Merge across JBESB_4_7_CP2_ER2 tag ---------------------------------- Key: JBESB-3328 URL: https://jira.jboss.org/browse/JBESB-3328 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.8 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
8
0 / 0

[JBoss JIRA] Created: (JBESB-3292) Spring Integration needs to be updated to use SNOWDROP's VFSClassPathXmlApplicationContext

by Alex Deschapelles (JIRA)

Spring Integration needs to be updated to use SNOWDROP's VFSClassPathXmlApplicationContext ------------------------------------------------------------------------------------------ Key: JBESB-3292 URL: https://jira.jboss.org/jira/browse/JBESB-3292 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.7 Reporter: Alex Deschapelles The current AbstractSpringAction uses the standard ClassPathXmlApplicationContext (line 208 in the jboss-spring.jar) This does not work when the spring config searches for resources using the classpath*: notation. To fix, replace the ClassPathXmlApplicationContext with VFSClassPathXmlApplicationContext from SNOWDROP. -- 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

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-3275) SOAPClient may fail NTLM negotiations

by Kevin Conner (JIRA)

SOAPClient may fail NTLM negotiations ------------------------------------- Key: JBESB-3275 URL: https://jira.jboss.org/jira/browse/JBESB-3275 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 CP1 Reporter: Kevin Conner The soapui client may fail NTLM negotiations if no keep-alive is set on the connection. Some servers may respond with a directive to close each connection, which soapui honours. If this happens then each step of the NTLM negotiation will be handled over a separate connection and will fail. -- 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

13 years, 10 months

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2010