February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13336) create target platform using Kepler dependencies

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13336?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13336: ------------------------------- Comment: was deleted (was: Closing assigned to bad fixVersion to test jiralint.) > create target platform using Kepler dependencies > ------------------------------------------------ > > Key: JBIDE-13336 > URL: https://issues.jboss.org/browse/JBIDE-13336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > Attachments: multiple.target, multiple.target_update_hints.txt > > > Along with the refactoring we talked about doing in JBIDE-13232, it's time to create a new Kepler M4 target platform. > I've pulled mirrors for the three largest pieces: Kepler M4, Eclipse 4.3M4, WTP 3.5M4: > http://download.jboss.org/jbosstools/updates/requirements/kepler/20121221... > http://download.jboss.org/jbosstools/updates/requirements/eclipse/S-4.3M4... > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5.... > Do you need anything else mirrored? If so bounce this to me and I'll get the bits copied to download.jboss.org for you. -- 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, 2 months

1
0
0 / 0

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

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2446?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2446: ------------------------------- Priority: Critical (was: Major) > ESB Editor removes "http-client-property" property > -------------------------------------------------- > > Key: JBDS-2446 > URL: https://issues.jboss.org/browse/JBDS-2446 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.0.GA-SOA > Environment: RHEL 6.1 > java version "1.6.0_25" > SOA-P 5.0 > Reporter: William Siqueira > Assignee: Douglas Palmer > Priority: Critical > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13336) create target platform using Kepler dependencies

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13336?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-13336. ------------------------------ Closing assigned to bad fixVersion to test jiralint. > create target platform using Kepler dependencies > ------------------------------------------------ > > Key: JBIDE-13336 > URL: https://issues.jboss.org/browse/JBIDE-13336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.x > > Attachments: multiple.target, multiple.target_update_hints.txt > > > Along with the refactoring we talked about doing in JBIDE-13232, it's time to create a new Kepler M4 target platform. > I've pulled mirrors for the three largest pieces: Kepler M4, Eclipse 4.3M4, WTP 3.5M4: > http://download.jboss.org/jbosstools/updates/requirements/kepler/20121221... > http://download.jboss.org/jbosstools/updates/requirements/eclipse/S-4.3M4... > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5.... > Do you need anything else mirrored? If so bounce this to me and I'll get the bits copied to download.jboss.org for you. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13381) ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-13381: --------------------------------- Summary: ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS (was: ESB Editor removes "http-client-property" property (JBDS-2446)) > ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS > ----------------------------------------------------------------------------------------------------------------------- > > 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-3.3.x.patch, jbide-13381.patch, JBIDE-13381_error.png, JBIDE-13381_error_source.png > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13381) ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-13381: -------------------------------------- And - the resulting .esb cannot be deployed as vaildation fails: DEPLOYMENTS IN ERROR: Deployment "jboss.esb.vfsfile:/jboss/local/SOA_servers/53_GA/jboss-soa-p-5/jboss-as/server/default/deploy/TestESB.esb/" is in error due to the following reason(s): java.lang.IllegalStateException: ESB file had validation errors. > ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS > ----------------------------------------------------------------------------------------------------------------------- > > 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-3.3.x.patch, jbide-13381.patch, JBIDE-13381_error.png, JBIDE-13381_error_source.png > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13336) create target platform using Kepler dependencies

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13336?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13336: ------------------------------- Fix Version/s: (was: 4.1.0.Alpha1) > create target platform using Kepler dependencies > ------------------------------------------------ > > Key: JBIDE-13336 > URL: https://issues.jboss.org/browse/JBIDE-13336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.x > > Attachments: multiple.target, multiple.target_update_hints.txt > > > Along with the refactoring we talked about doing in JBIDE-13232, it's time to create a new Kepler M4 target platform. > I've pulled mirrors for the three largest pieces: Kepler M4, Eclipse 4.3M4, WTP 3.5M4: > http://download.jboss.org/jbosstools/updates/requirements/kepler/20121221... > http://download.jboss.org/jbosstools/updates/requirements/eclipse/S-4.3M4... > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5.... > Do you need anything else mirrored? If so bounce this to me and I'll get the bits copied to download.jboss.org for you. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13336) create target platform using Kepler dependencies

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13336?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13336: ------------------------------- Fix Version/s: 4.1.x > create target platform using Kepler dependencies > ------------------------------------------------ > > Key: JBIDE-13336 > URL: https://issues.jboss.org/browse/JBIDE-13336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1, 4.1.x > > Attachments: multiple.target, multiple.target_update_hints.txt > > > Along with the refactoring we talked about doing in JBIDE-13232, it's time to create a new Kepler M4 target platform. > I've pulled mirrors for the three largest pieces: Kepler M4, Eclipse 4.3M4, WTP 3.5M4: > http://download.jboss.org/jbosstools/updates/requirements/kepler/20121221... > http://download.jboss.org/jbosstools/updates/requirements/eclipse/S-4.3M4... > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5.... > Do you need anything else mirrored? If so bounce this to me and I'll get the bits copied to download.jboss.org for you. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2348) JBDS product page on redhat.com is out of date

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2348?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2348: ---------------------------------- Feb 6: http://www.redhat.com/resourcelibrary/datasheets/JBoss-Developer-Studio-P... is *STILL* out of date – refers to Eclipse 3.7 Indigo and WTP 3.2 rather than Eclipse 4.2 and WTP 3.4. > JBDS product page on redhat.com is out of date > ---------------------------------------------- > > Key: JBDS-2348 > URL: https://issues.jboss.org/browse/JBDS-2348 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, documentation > Affects Versions: 5.0.1.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 6.0.1.GA > > > This page [1] mentions Eclipse 3.6 and JBoss Tools 3, but JBDS 6 uses Eclipse 4.2 and JBoss Tools 4. > [1] https://www.redhat.com/apps/store/developers/jboss_developer_studio.html > Can we get that page updated? -- 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, 2 months

1
0
0 / 0

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

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-13381: --------------------------------- Attachment: JBIDE-13381_error_source.png JBIDE-13381_error.png The January 28 build available here: http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.3.GA.soa-to... Results in the <http-client-property name="file" value="httpclient.properties" /> no longer being automatically deleted by the editor. However, the editor is flagging this as an error with this error message: ERROR: Editor model does not support child element http-client-property of action See screnshots > 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-3.3.x.patch, jbide-13381.patch, JBIDE-13381_error.png, JBIDE-13381_error_source.png > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13479) Update minor version for common, jst, jsf, seam, cdi components

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-13479: -------------------------------------- Summary: Update minor version for common, jst, jsf, seam, cdi components Key: JBIDE-13479 URL: https://issues.jboss.org/browse/JBIDE-13479 Project: Tools (JBoss Tools) Issue Type: Task Components: CDI, common/jst/core, JSF, Seam 2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.1.0.Alpha1 -- 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, 2 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 February 2013