January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13381) ESB Editor removes "http-client-property" property (JBDS-2446)

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-13381: ----------------------------------------------- New pull request sent for 4.0.x https://github.com/jbosstools/jbosstools-esb/pull/13 > ESB Editor removes "http-client-property" property (JBDS-2446) > -------------------------------------------------------------- > > Key: JBIDE-13381 > URL: https://issues.jboss.org/browse/JBIDE-13381 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: esb > Affects Versions: 3.3.0.Final-SOA > Reporter: Brian Fitzpatrick > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 3.3.x, 4.0.x > > Attachments: jbide-13381.patch > > > When editing an ESB file (jboss-esb.xml), we have two ways which are using the native XML editor or the visual way. > When we want to use the property X. We created our service and our SOAPClient using the visual editor, then we have to add the "http-client-property" manually > <?xml version="1.0"?> > <jbossesb parameterReloadSecs="5" > xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."> > <services> > <service category="c1" description="d1" name="s1"> > <actions> > <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client"> > <property name="wsdl" value="someWsdl"/> > <property name="SOAPAction" value="noAction"/> > <property name="endpointUrl" value="http://host/servername"> > <http-client-property name="file" value="httpclient.properties" /> > </property> > </action> > </actions> > </service> > </services> > </jbossesb> > Notice the "http-client-property" in the action property element. The problem is that when using visual editor of this file and adding something new or editing existing thing, the code related to this property is deleted. In the example above, I have the following result, showing what the editor removed: (in this case I just changed the service name from service-test to service-test-edited) > <?xml version="1.0"?> > <jbossesb parameterReloadSecs="5" > xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."> > <services> > <service category="c1" description="d1" name="s1-edited"> > <actions> > <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client"> > <property name="wsdl" value="someWsdl"/> > <property name="SOAPAction" value="noAction"/> > <property name="endpointUrl" value="http://host/servername"/> > </action> > </actions> > </service> > </services> > </jbossesb> > One test we have done is change the XSD used by the JBDS(1.3.1 to the one used in quickstars (1.0.1). The http-client-property worked fine, but other things stopped working. So we need to know what's wrong with the schema and what should make it works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13381) ESB Editor removes "http-client-property" property (JBDS-2446)

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-13381: ----------------------------------------------- New pull request sent for 4.1.x https://github.com/jbosstools/jbosstools-esb/pull/12 > ESB Editor removes "http-client-property" property (JBDS-2446) > -------------------------------------------------------------- > > Key: JBIDE-13381 > URL: https://issues.jboss.org/browse/JBIDE-13381 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: esb > Affects Versions: 3.3.0.Final-SOA > Reporter: Brian Fitzpatrick > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 3.3.x, 4.0.x > > Attachments: jbide-13381.patch > > > When editing an ESB file (jboss-esb.xml), we have two ways which are using the native XML editor or the visual way. > When we want to use the property X. We created our service and our SOAPClient using the visual editor, then we have to add the "http-client-property" manually > <?xml version="1.0"?> > <jbossesb parameterReloadSecs="5" > xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."> > <services> > <service category="c1" description="d1" name="s1"> > <actions> > <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client"> > <property name="wsdl" value="someWsdl"/> > <property name="SOAPAction" value="noAction"/> > <property name="endpointUrl" value="http://host/servername"> > <http-client-property name="file" value="httpclient.properties" /> > </property> > </action> > </actions> > </service> > </services> > </jbossesb> > Notice the "http-client-property" in the action property element. The problem is that when using visual editor of this file and adding something new or editing existing thing, the code related to this property is deleted. In the example above, I have the following result, showing what the editor removed: (in this case I just changed the service name from service-test to service-test-edited) > <?xml version="1.0"?> > <jbossesb parameterReloadSecs="5" > xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."> > <services> > <service category="c1" description="d1" name="s1-edited"> > <actions> > <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client"> > <property name="wsdl" value="someWsdl"/> > <property name="SOAPAction" value="noAction"/> > <property name="endpointUrl" value="http://host/servername"/> > </action> > </actions> > </service> > </services> > </jbossesb> > One test we have done is change the XSD used by the JBDS(1.3.1 to the one used in quickstars (1.0.1). The http-client-property worked fine, but other things stopped working. So we need to know what's wrong with the schema and what should make it works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13397) remove upper limit on m2e requirements in org.eclipse.tools.maven.* MANIFEST.MF files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13397?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13397: ------------------------------------ Goal is to minimize the # of failed installs at Eclipse Marketplace. > remove upper limit on m2e requirements in org.eclipse.tools.maven.* MANIFEST.MF files > ------------------------------------------------------------------------------------- > > Key: JBIDE-13397 > URL: https://issues.jboss.org/browse/JBIDE-13397 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Marketplace, maven > Affects Versions: 3.3.2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 3.3.2 > > Attachments: JBIDE13397.patch.bundle-version-to-1.0.0.txt > > > Looks like we need another fix here to make installation of org.jboss.tools.maven.* plugins possible when m2e > 1.1 is installed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13385) Hibernate fails to build under kepler

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13385?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-13385: ----------------------------------- In the meantime I have eliminated all the compilation errors in org.jboss.tools.hibernate.jpt.core. 296 more to go in org.jboss.tools.hibernate.jpt.ui... > Hibernate fails to build under kepler > ------------------------------------- > > Key: JBIDE-13385 > URL: https://issues.jboss.org/browse/JBIDE-13385 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Main cause is changed Dali API (again) :( -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13382) 'Server Behaviour' title in Server Editor should use American spelling

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13382?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13382: ------------------------------------- i was not aware we had so many guidelines ;) very interesting to see. > 'Server Behaviour' title in Server Editor should use American spelling > ---------------------------------------------------------------------- > > Key: JBIDE-13382 > URL: https://issues.jboss.org/browse/JBIDE-13382 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Reporter: Michelle Murray > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.1.0.Alpha1 > > > One of the section titles on the Overview page of the Server Editor is misspelled: Server Behavi*our* should be Server Behavi*or* > American spellings should be followed, as you have with Application Reload Behavi*or* on the same page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ] Anonymous updated JBIDE-13263: ------------------------------ Attachment: astools api.png > Workspace metadata deployment does not work for AS 6 > ---------------------------------------------------- > > Key: JBIDE-13263 > URL: https://issues.jboss.org/browse/JBIDE-13263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: JBoss AS 6.1.0 > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.0.1.Final > > Attachments: astools api.gliffy, astools api.png > > > When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13263: -------------------------------- Attachment: astools api.png > Workspace metadata deployment does not work for AS 6 > ---------------------------------------------------- > > Key: JBIDE-13263 > URL: https://issues.jboss.org/browse/JBIDE-13263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: JBoss AS 6.1.0 > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.0.1.Final > > Attachments: astools api.gliffy, astools api.png > > > When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13381) ESB Editor removes "http-client-property" property (JBDS-2446)

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13381: ------------------------------------------- Slava, can you rebase those two streams and update your pull requests? They were out of sync before I did some recent changes and things have changed since then (including version #s). > ESB Editor removes "http-client-property" property (JBDS-2446) > -------------------------------------------------------------- > > Key: JBIDE-13381 > URL: https://issues.jboss.org/browse/JBIDE-13381 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: esb > Affects Versions: 3.3.0.Final-SOA > Reporter: Brian Fitzpatrick > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 3.3.x, 4.0.x > > Attachments: jbide-13381.patch > > > When editing an ESB file (jboss-esb.xml), we have two ways which are using the native XML editor or the visual way. > When we want to use the property X. We created our service and our SOAPClient using the visual editor, then we have to add the "http-client-property" manually > <?xml version="1.0"?> > <jbossesb parameterReloadSecs="5" > xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."> > <services> > <service category="c1" description="d1" name="s1"> > <actions> > <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client"> > <property name="wsdl" value="someWsdl"/> > <property name="SOAPAction" value="noAction"/> > <property name="endpointUrl" value="http://host/servername"> > <http-client-property name="file" value="httpclient.properties" /> > </property> > </action> > </actions> > </service> > </services> > </jbossesb> > Notice the "http-client-property" in the action property element. The problem is that when using visual editor of this file and adding something new or editing existing thing, the code related to this property is deleted. In the example above, I have the following result, showing what the editor removed: (in this case I just changed the service name from service-test to service-test-edited) > <?xml version="1.0"?> > <jbossesb parameterReloadSecs="5" > xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."> > <services> > <service category="c1" description="d1" name="s1-edited"> > <actions> > <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client"> > <property name="wsdl" value="someWsdl"/> > <property name="SOAPAction" value="noAction"/> > <property name="endpointUrl" value="http://host/servername"/> > </action> > </actions> > </service> > </services> > </jbossesb> > One test we have done is change the XSD used by the JBDS(1.3.1 to the one used in quickstars (1.0.1). The http-client-property worked fine, but other things stopped working. So we need to know what's wrong with the schema and what should make it works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13263: -------------------------------- Attachment: astools api.png > Workspace metadata deployment does not work for AS 6 > ---------------------------------------------------- > > Key: JBIDE-13263 > URL: https://issues.jboss.org/browse/JBIDE-13263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: JBoss AS 6.1.0 > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.0.1.Final > > Attachments: astools api.gliffy, astools api.png > > > When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13399) ESB Runtime - defaults to highest supported version - when creating a new ESB project

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-13399: ------------------------------------ Summary: ESB Runtime - defaults to highest supported version - when creating a new ESB project Key: JBIDE-13399 URL: https://issues.jboss.org/browse/JBIDE-13399 Project: Tools (JBoss Tools) Issue Type: Quality Risk Components: SOA Tooling Affects Versions: 3.2.2.Final Reporter: Len DiMaggio Assignee: Douglas Palmer Fix For: LATER Example scenario: New install of JBDS/JBossTools, install the ESB tooling, create a server runtime for SOA 5.2, and a corresponding ESB runtime of 4.10. Then, create a new ESB project - and the ESB runtime displayed in the wizard is 4.12, as this automatically defaults to the highest supported facet version on the runtime. For each version of ESB, we have declared an explicit facet. In org.jboss.tools.esb.project.core, we have facets defined (4.2,4.3,4.4,4.5,4.6,4.7,4.9,4.10,4.11,4.12) and assign them to EAP runtime components (4.3,5.0,6.0) (which are specified in the AS tools plug-ins). So every version of SOA-P based on EAP 4.3, 5.x, or 6.x supports every facet version we've defined thus far - up to 4.12 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2013