November 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3004) Override juddi access_point_url in BindingTemplate

by Kevin Conner (JIRA)

Override juddi access_point_url in BindingTemplate -------------------------------------------------- Key: JBESB-3004 URL: https://jira.jboss.org/jira/browse/JBESB-3004 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP1 Currently set to 2000 but we need 4000. -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2997) security_saml quickstart: Remove the need to manually update the servers login-config.xml

by Daniel Bevenius (JIRA)

security_saml quickstart: Remove the need to manually update the servers login-config.xml ----------------------------------------------------------------------------------------- Key: JBESB-2997 URL: https://jira.jboss.org/jira/browse/JBESB-2997 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Minor Fix For: 4.7 CP1 Add a jboss-service.xml that deploys the login configuration with the .esb archive. -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2995) ivysetting for ejb3-persistence is incorrect

by Kevin Conner (JIRA)

ivysetting for ejb3-persistence is incorrect -------------------------------------------- Key: JBESB-2995 URL: https://jira.jboss.org/jira/browse/JBESB-2995 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP1 If you start with a clean ivy cache then you see the following. [ivy:retrieve] ==== ejb3: tried [ivy:retrieve] -- artifact org.hibernate#ejb3-persistence;1.0.2.GA!ejb3-persistence.jar: [ivy:retrieve] http://repository.jboss.org/maven2/org.hibernate/ejb3-persistence/1.0.2.G... The mistake is in the ivysettings.xml file. -- 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

16 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2996) ivysetting for ejb3-persistence is incorrect

by Kevin Conner (JIRA)

ivysetting for ejb3-persistence is incorrect -------------------------------------------- Key: JBESB-2996 URL: https://jira.jboss.org/jira/browse/JBESB-2996 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP1 If you start with a clean ivy cache then you see the following. [ivy:retrieve] ==== ejb3: tried [ivy:retrieve] -- artifact org.hibernate#ejb3-persistence;1.0.2.GA!ejb3-persistence.jar: [ivy:retrieve] http://repository.jboss.org/maven2/org.hibernate/ejb3-persistence/1.0.2.G... The mistake is in the ivysettings.xml file. -- 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

16 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2987) Upgrade JBoss-Identity to 1.0.0.GA

by Daniel Bevenius (JIRA)

Upgrade JBoss-Identity to 1.0.0.GA ---------------------------------- Key: JBESB-2987 URL: https://jira.jboss.org/jira/browse/JBESB-2987 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Examples, Security Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.7 CP1 The project is currently using version 1.0.0.beta3 of JBoss-Identity and we should upgrade this to 1.0.0.GA when it is available. This task should also update the login modules configuration in the security_saml quickstart to reflect changes that differ from the beta3. -- 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

16 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2988) Missing classes in juddi persistence.xml

by Kevin Conner (JIRA)

Missing classes in juddi persistence.xml ---------------------------------------- Key: JBESB-2988 URL: https://jira.jboss.org/jira/browse/JBESB-2988 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 While investigating the juddi webservices I noticed that our persistence.xml does not contain the following classes org.apache.juddi.model.Clerk, org.apache.juddi.model.ClientSubscriptionInfo and org.apache.juddi.model.Node. I believe these have been added for subscription support. -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2984) web port substitution not working in as5 bindings

by Kevin Conner (JIRA)

web port substitution not working in as5 bindings ------------------------------------------------- Key: JBESB-2984 URL: https://jira.jboss.org/jira/browse/JBESB-2984 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.7 CP1 We do not need this at present, but may do for supporting juddi webservice endpoints. At present the value remains at 8080 when using alternative bindings. -- 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

16 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2986) JbpmService assumes existence of JobExecutor

by Kevin Conner (JIRA)

JbpmService assumes existence of JobExecutor -------------------------------------------- Key: JBESB-2986 URL: https://jira.jboss.org/jira/browse/JBESB-2986 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 Check for existence of JobExecutor and force start/stop of services through JbpmConfiguration/JbpmContext. -- 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

16 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2982) juddi fails to start when ports ofther than default are specified in Service Binding Manager

by Brad Maxwell (JIRA)

juddi fails to start when ports ofther than default are specified in Service Binding Manager -------------------------------------------------------------------------------------------- Key: JBESB-2982 URL: https://jira.jboss.org/jira/browse/JBESB-2982 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.6 Environment: Tested in EAP 5 and AS 5.1, the problem occurs in both when the Service Binding Manager is used with configuration ports-01 Reporter: Brad Maxwell juddi fails to start when ports other than default are specified such as using the ports-01 configuration in the Service Binding Manager. It appears to just be the JNDI port which is hard coded to 1099 in $JBOSS_HOME/server/$SERVER_CONF/deployers/esb.deployer/esb.juddi.xml. This should be changed to use the port injection or some other method such that the Service Binding Manager can be used. ERROR [STDERR] (main) javax.naming.CommunicationException: Could not obtain connection to any of these urls: hostname:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server hostname/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server hostname/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]]] ERROR [STDERR] (main) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763) ERROR [STDERR] (main) at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:547) ... ERROR [STDERR] (main) Caused by: javax.naming.CommunicationException: Failed to connect to server hostname/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server hostname/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]] ERROR [STDERR] (main) at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335) ... ERROR [STDERR] (main) Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server hostname/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused] ERROR [STDERR] (main) at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305) ERROR [STDERR] (main) ... 69 more ERROR [STDERR] (main) Caused by: java.net.ConnectException: Connection refused ERROR [STDERR] (main) at java.net.PlainSocketImpl.socketConnect(Native Method) -- 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

16 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2980) Update remaining quickstart configurations for juddiv3

by Kevin Conner (JIRA)

Update remaining quickstart configurations for juddiv3 ------------------------------------------------------ Key: JBESB-2980 URL: https://jira.jboss.org/jira/browse/JBESB-2980 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 A number of quickstarts have not had their configuration updated for the juddi v3 release and some of the merged ones do not look correct.. -- 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

16 years, 5 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2009