February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13431) BrowserSim: create galaxy S III skin

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13431?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-13431: -------------------------------- Summary: BrowserSim: create galaxy S III skin (was: BrowserSim: remake galaxy S III skin) > BrowserSim: create galaxy S III skin > ------------------------------------ > > Key: JBIDE-13431 > URL: https://issues.jboss.org/browse/JBIDE-13431 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Reporter: Ilya Buziuk > Assignee: Daniel Azarov > Attachments: attributes.png, Buttons.png, buttons.png, Camera.png, Camera.png, Clear skin.png, Clear skin.png, Compressed.png, Compressed.png, Compressed.png, Compressed.png, Compressed.png, Example.png, forward-disabled.png, forward-selected.png, forward.png, Home.png, Home.png, Menu Button.png, port_back.xcf, refresh-horizontal-selected.png, refresh-horizontal.png, refresh-selected.png, refresh.png, refresh.png, refresh_replacement.png, Refresh_Transparent.png, Refresh_Transparent.png, Return Disabled.png, Return Disabled.png, Return Enabled.png, Return Enabled.png, Return Selected.png, Return Selected.png, Samsung Logo.png, Samsung Logo.png, screen_size.png, Speaker.png, Speaker.png, Two Sensors.png, Two Sensors.png, uneven_edge.png, uneven_edge_max.png > > > Need to remake galaxy S III skin, which is generated by Android Asset Studio: [http://android-ui-utils.googlecode.com/hg/asset-studio/dist/device-frames...] > * while compressing the mockup the edge of the device is becoming uneven: !uneven_edge.png|thumbnail! , !uneven_edge_max.png|thumbnail! - the edges should be even; > * the mockup should be vertically compressed until the screen size of the device will be no more than 800px - !screen_size.png|thumbnail!; > * mikrofon, 3 cameras, "sumsung" symbolism, *side buttons*: every item should be settled on the new layer: !attributes.png|thumbnail!; > * "menu" button should be replaced with the "refresh" !refresh.png|thumbnail! button: !refresh_replacement.png|thumbnail!; > * 3 buttons at the bottom of the device !refresh_replacement.png|thumbnail! should have 3 states: enable !forward.png|thumbnail!, disable !forward-disabled.png|thumbnail!, selected !forward-selected.png|thumbnail! - each item on the new layer; > Link to the source images: [http://code.google.com/p/android-ui-utils/source/browse/#hg%2Fasset-studi...] -- 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 closed JBIDE-13381. -------------------------------- Sorry - meant to close this yesterday. Verified in the 5.0.3 tooling > 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 Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick resolved JBIDE-13381. --------------------------------------- Resolution: Done Yes, this has been resolved. Len will close shortly. > 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-13400) PageContextFactory.ExtendedLinkElementAdapter is leaked

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13400?page=com.atlassian.jira.plugi... ] Victor Rubezhny reassigned JBIDE-13400: --------------------------------------- Assignee: Alexey Kazakov (was: Victor Rubezhny) Please verify. > 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: Alexey Kazakov > 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-13313) Upgrade JBoss archetypes to 7.1.2.Final

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13313?page=com.atlassian.jira.plugi... ] Juergen Zimmermann updated JBIDE-13313: --------------------------------------- Summary: Upgrade JBoss archetypes to 7.1.2.Final (was: Upgrade JBoss archetypes to 7.1.2.CR1) > Upgrade JBoss archetypes to 7.1.2.Final > --------------------------------------- > > Key: JBIDE-13313 > URL: https://issues.jboss.org/browse/JBIDE-13313 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.0.0.Final > Reporter: Juergen Zimmermann > Assignee: Fred Bricon > > There is a new version of JBoss archetypes at e.g. https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/a... -- 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-13313) Upgrade JBoss archetypes to 7.1.2.CR1

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13313?page=com.atlassian.jira.plugi... ] Juergen Zimmermann commented on JBIDE-13313: -------------------------------------------- Meanwhile there is 7.1.2.Final. > Upgrade JBoss archetypes to 7.1.2.CR1 > ------------------------------------- > > Key: JBIDE-13313 > URL: https://issues.jboss.org/browse/JBIDE-13313 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.0.0.Final > Reporter: Juergen Zimmermann > Assignee: Fred Bricon > > There is a new version of JBoss archetypes at e.g. https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/a... -- 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-13476) Get rid of bootstrap profiles in root poms for JBT projects (no longer needed)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13476?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13476: ---------------------------------------- [~kmarmaliykov]: In order to find a better naming and configruation for the bootstrap profile your use. can you please descibe * What does "building BrowserSim standalone" mean? Which bundles/features must be built? What is the expected output? How do you use the output of the build? * How do you run the browsersim only build? Only "mvn verify -P bootstrap" ? * Why do you need this profile to build BrowserSim ? > Get rid of bootstrap profiles in root poms for JBT projects (no longer needed) > ------------------------------------------------------------------------------ > > Key: JBIDE-13476 > URL: https://issues.jboss.org/browse/JBIDE-13476 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng, Visual Page Editor core > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > It seens like the bootstrap profiles are not used by developers. > The only exceptuin is the BrowserSim pieces that use those profiles to have BrowserSim built standalone. > We should review the profiles for BrowserSim to make it more adapted to use cases (create a "browsersim-standalone" profile for example); and remove bootstrap profiles from other poms. > Those bootstrap profile cause issue with the set-version plugin, and may cause issue with plugins that look at modules in general -- 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-10207) Add support for JAX-RS Providers

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10207?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-10207: ---------------------------------- Fix Version/s: 4.1.0.Alpha2 (was: 4.1.0.Alpha1) > Add support for JAX-RS Providers > -------------------------------- > > Key: JBIDE-10207 > URL: https://issues.jboss.org/browse/JBIDE-10207 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Webservices > Affects Versions: 3.3.0.M4 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.1.0.Alpha2 > > > Add support for JAX-RS @Provider elements -- 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-12190) enable API Tooling for JBoss Tools components

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12190?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-12190: ---------------------------------------- Just got access to a repository where we can make some experiments on the best way to deploy the plugin and its dependencies: https://repository.jboss.org/nexus/content/repositories/jbosstools-experi... When we have something satisfying, I'll report it to the Eclipse CBI people who are dealing with Nexus usage at Eclipse.org since they'll for sure be interested in our approach. > enable API Tooling for JBoss Tools components > --------------------------------------------- > > Key: JBIDE-12190 > URL: https://issues.jboss.org/browse/JBIDE-12190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: LATER > > Attachments: JBIDE12190-1.png, JBIDE12190-2.png, JBIDE12190-3.png > > > We should enable API Tooling support in projects so that we can get immediate feedback when someone forgets to upversion their plugins or breaks API. > http://wiki.eclipse.org/Version_Numbering > http://www.eclipse.org/pde/pde-api-tools/ > http://wiki.eclipse.org/PDE/API_Tools/User_Guide > http://www.ibm.com/developerworks/opensource/library/os-eclipse-api-tools > http://grepcode.com/file/repository.grepcode.com/java/eclipse.org/3.7/org... -- 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-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 resolved JBIDE-13462. ------------------------------------ Resolution: Done In order to have a local mirror of that contains sources, so it can be used in several workspaces without redownloading everything, people have to run this command locally, for the jbosstools-target-platfroms repo: {code} cd jbosstools/multiple mvn clean verify -Dmirror-target-to-repo.includeSources=true {code} > 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 > -- 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