February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13462) Given a .target file materialize it with sources for use for dev

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13462?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13462: ----------------------------------- Fix Version/s: 4.1.0.Alpha1 > Given a .target file materialize it with sources for use for dev > ---------------------------------------------------------------- > > Key: JBIDE-13462 > URL: https://issues.jboss.org/browse/JBIDE-13462 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > 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

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13381: ---------------------------------- Fix Version/s: 4.0.1.Final (was: 4.0.x) > 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: Brian Fitzpatrick > Priority: Critical > Fix For: 3.3.x, 4.0.1.Final > > Attachments: JBIDE-13381-3.3.x.patch, jbide-13381.patch, JBIDE-13381_error.png, JBIDE-13381_error_source.png, JBIDE-13381_resolved.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 Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13381: ---------------------------------- Assignee: Brian Fitzpatrick (was: Viacheslav Kabanovich) > 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: Brian Fitzpatrick > 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, JBIDE-13381_resolved.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-13400) PageContextFactory.ExtendedLinkElementAdapter is leaked

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13400?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13400: --------------------------------------- Victor, PageContextFactory.ExtendedLinkElementAdapter isn't leaked when building a Java EE Web quickstart. > PageContextFactory.ExtendedLinkElementAdapter is leaked > ------------------------------------------------------- > > Key: JBIDE-13400 > URL: https://issues.jboss.org/browse/JBIDE-13400 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.0.0.Final > Reporter: Snjezana Peco > Assignee: Victor Rubezhny > Fix For: 4.1.0.Alpha1 > > Attachments: jbide13400.patch > > > Steps to reproduce: > Call a full rebuild of a Java EE Web project. > An object of the PageContextFactory.ExtendedLinkElementAdapter type is leaked. That object leaks a lot of org.eclipse.wst.* objects. -- 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-13492) org.eclipse.zest (nedded for ESB) is missing in TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13492?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-13492: ---------------------------------- Assignee: Paul Leacu (was: Nick Boldt) Paul, can you explain to Alexy how to build ESB using your new JBTIS target platform? Thanks! > org.eclipse.zest (nedded for ESB) is missing in TP > -------------------------------------------------- > > Key: JBIDE-13492 > URL: https://issues.jboss.org/browse/JBIDE-13492 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: esb, target-platform > Environment: Eclipse 4.3.0.M5 > Reporter: Alexey Kazakov > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > {code} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.esb.project.ui 1.5.300.qualifier > [ERROR] Missing requirement: org.jboss.tools.esb.project.ui 1.5.300.qualifier requires 'bundle org.eclipse.zest.core 0.0.0' but it could not be found > [ERROR] > [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.qualifier to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.qualifier to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.qualifier to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.qualifier to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."] > {code} -- 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-13413) jQuery Mobile Widget Palette

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13413?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-13413: ---------------------------------- Attachment: PaletteThinLines.png > jQuery Mobile Widget Palette > ---------------------------- > > Key: JBIDE-13413 > URL: https://issues.jboss.org/browse/JBIDE-13413 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.1.x > > Attachments: CSS-Preview.png, NewBlock.bmml, NewBlock.bmml, NewBlock.png, NewButton.bmml, NewButton.png, NewCheckBox.bmml, NewCheckBox.png, NewCheckboxWizard.png, NewCheckboxWizard.png, NewDialog.bmml, NewDialog.bmml, NewDialog.png, NewFlip.bmml, NewFlip.png, NewGrid.bmml, NewGrid.png, NewGroupedCheckBoxes.bmml, NewGroupedCheckBoxes.png, NewHeaderBar.bmml, NewHeaderBar.png, NewListview.bmml, NewListview.png, NewNavbar.bmml, NewNavbar.png, NewPage.bmml, NewPage.png, NewPopup.bmml, NewPopup.png, NewRadioButton.bmml, NewRadioButton.png, PaletteThinLines.png, Palette_1.png, Palette_2.png, Palette_3.png, withwithoutpreview.bmml, withwithoutpreview.png > > > http://jquerymobile.com/test/ > See my proposal regarding the content of jQuery Mobile palette below. > Also I have an idea to add a live preview into each wizard. > We could try to add a browser to the wizard which will show how the widget is going to look. -- 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-13493) Filter by name of components for new HTML5 Widget Palette

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13493?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13493: ----------------------------------- Fix Version/s: 4.1.0.Alpha1 (was: 4.1.x) > Filter by name of components for new HTML5 Widget Palette > --------------------------------------------------------- > > Key: JBIDE-13493 > URL: https://issues.jboss.org/browse/JBIDE-13493 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > 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

[JBoss JIRA] (JBIDE-13493) Filter by name of components for new HTML5 Widget Palette

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13493?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13493: ----------------------------------- Fix Version/s: 4.1.0.Alpha2 (was: 4.1.0.Alpha1) > Filter by name of components for new HTML5 Widget Palette > --------------------------------------------------------- > > Key: JBIDE-13493 > URL: https://issues.jboss.org/browse/JBIDE-13493 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 4.1.0.Alpha2 > > -- 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-13493) Filter by name of components for new HTML5 Widget Palette

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-13493: -------------------------------------- Summary: Filter by name of components for new HTML5 Widget Palette Key: JBIDE-13493 URL: https://issues.jboss.org/browse/JBIDE-13493 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml/html source editing Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 4.1.x -- 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-13492) org.eclipse.zest (nedded for ESB) is missing in TP

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-13492: -------------------------------------- Summary: org.eclipse.zest (nedded for ESB) is missing in TP Key: JBIDE-13492 URL: https://issues.jboss.org/browse/JBIDE-13492 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb, target-platform Environment: Eclipse 4.3.0.M5 Reporter: Alexey Kazakov Assignee: Nick Boldt Priority: Blocker Fix For: 4.1.0.Alpha1 {code} [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.jboss.tools.esb.project.ui 1.5.300.qualifier [ERROR] Missing requirement: org.jboss.tools.esb.project.ui 1.5.300.qualifier requires 'bundle org.eclipse.zest.core 0.0.0' but it could not be found [ERROR] [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.qualifier to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.qualifier to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.qualifier to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.qualifier to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."] {code} -- 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