January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13322) Add JBossAS 7.x configuration schemas to eclipse xml catalog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13322?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-13322: ----------------------------------- Assignee: Max Rydahl Andersen (was: Rob Stryker) This isn't a difficult thing to do now that I've found the proper URL where all the schemas are held. Max, should I include ALL of the xsd's found in the schema folder? Is there any chance of conflicts? Do you know of any bad ramifications if I were to add ALL files in that folder to the catalog entries? If it's safe, I'd sooner add all, and check once each major app server release that there are no new ones. I could even make a unit test (somehow) to do that ;) > Add JBossAS 7.x configuration schemas to eclipse xml catalog > ------------------------------------------------------------ > > Key: JBIDE-13322 > URL: https://issues.jboss.org/browse/JBIDE-13322 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JBossAS/Servers > Reporter: Samuli Saarinen > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Alpha1 > > > JBAS7 configuration schemas could be added to Eclipse XML catalog. This way developer wanting to edit eg. standalone.xml could get auto-complete without the need to import all the schemas by hand. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13364) Consider changing the way in which BrowserSim uses WebKit engine

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13364?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-13364: -------------------------------------- I think the ability to launch the WebKit web Inspector[1] UI should also be a requirement. I think web inspector is a good way to provide debugging on BrowserSim. This is one case where the current SWT bindings fail to satisfy. When I look at the studied alternates other than Google Chrome Frame others are either already able to have the inspector or can be enabled easily. [1]http://trac.webkit.org/wiki/WebInspector > Consider changing the way in which BrowserSim uses WebKit engine > ---------------------------------------------------------------- > > Key: JBIDE-13364 > URL: https://issues.jboss.org/browse/JBIDE-13364 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Fix For: 4.1.x > > > A perfect solution for BrowserSim must match the following criteria: > * Be Java-based > * Allow to fully customize the application window [skinning] > * Work on every supported platform (Windows, Mac and Linux) > * Use browser already installed in the system [to avoid library conflicts and reduce the size of our plugins] > * Allow to execute JavaScript and/or modify DOM [to simulate some mobile * JavaScript events and Cordova API] > * Allow to change User-Agent header > * Allow to disable web security or support extensions [for Cordova cross-domain requests] > * Support debugging protocol or support extensions [for better LiveEdit/LiveReload and JavaScript debugging capabilities] > Unfortunately, there is no perfect solution, at least I do not know any. > This is the list of the libraries I consider for BrowserSim (+=Pros, -=Cons, ?=questionable): > * Java wrapper for [Chromium Embedded Framework|http://code.google.com/p/javachromiumembedded/] > ** + I was able to run it on Windows > ** - It failed in a half of a minute :) > ** - Not supported since 2010 > ** ? probably will work better with the most recent version of CEF > ** ? looks like there is no Linux support > * [Qt WebKit bindings for SWT|http://code.google.com/p/qtwidgetsinswt/] > ** + I was able successfully run on Windows (32-bit) with Qt 4.8 and MinGW > ** + At least during my smoketesting it did not fail > ** - The plugin page claims that only win32 and cocoa32 are supported > ** - requires Qt (and MSVC or MinGW for Windows) libraries to be bundled with it > ** - Does not have existing API for invoking JavaScript. > ** - Not supported since 2010 > ** ? I do not know how easy it would be to run it on Linux > ** ? I do not know if it will work with Qt 5 > * [AppJS|http://appjs.org/] - a JavaScript SDK for creating Chromium based desktop applications > ** + Supports Windows, Mac and Linux! > ** + Allows to disable web security > ** + Has active community > ** + Did not fail at my smoketest > ** ? need to ensure that applications may be run without borders > * [node-webkit|https://github.com/rogerwang/node-webkit#readme] - the idea is the same as with AppJS - allows to create desktop apps with JavaScript > ** + supported by Intel in some way > ** ? I did not try it yet > * [Google Chrome Frame|http://www.google.com/chromeframe] > ** + the only way to embed _already installed_ Chrome into our application (all other require libraries to be bundled) > ** - Windows only > ** - [no success to use it as Ole object|http://code.google.com/p/chromium/issues/attachmentText?id=25448&a...] > ** ? Probably will work if use it with Browser(SWT.NONE) > * Stay with existing SWT bindings for WebKit > ** + We already use it > ** + Support all platforms > ** + Allow JavaScript to be executed > ** + Do not require to be bundled with our plugins > ** + Allow skinning > ** - Require Safari on Windows [no updates since May 9, 2012] > ** - Web security cannot be disabled > ** - Do not support extensions > ** - Do not support remote debugging protocol > *To conclude:* > * Firstly, moving to a JavaScript SDK potentially could resolve all our problems, but now I do not think it is worth it. > * Secondly, it would be great if we had good SWT bindings for Chromium, but they do not exist. The only way to get them is to implement them by ourself. > * Thirdly, the last option does not look too bad. And probably it does not worth it to create Chromium bindings or to move to another non-Java language. Especially, if we would be able to create a good workaround for cross-domain requests for Cordova, then almost everything else is ok. > * Fourthly, the biggest issue with existing SWT bindings is that Safari is not supported anymore on Windows. It is an OS specific issue and we could consider a replacement of SWT bindings on Windows only (e.g. use Chrome Frame or Qt on Windows). -- 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, 5 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 reassigned JBIDE-13382: ----------------------------------- Assignee: Max Rydahl Andersen (was: Rob Stryker) just a ping on this... i realize we should use one spelling, not two. Do we as a company prefer American spelling? Is this policy? sorry if this is an annoying quibble... just curious ;) > '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: Max Rydahl Andersen > > 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, 5 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 updated JBIDE-13382: -------------------------------- Fix Version/s: 4.1.0.Alpha1 > '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: Max Rydahl Andersen > 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, 5 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 updated JBIDE-13382: -------------------------------- Priority: Minor (was: Major) > '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: Max Rydahl Andersen > 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, 5 months

1
0
0 / 0

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

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13382?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-13382: ------------------------------------ Description: 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. was: 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. > '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 > > 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, 5 months

1
0
0 / 0

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

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13382?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-13382: ------------------------------------ Description: 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. was: 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. > '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 > > 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, 5 months

1
0
0 / 0

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

by Michelle Murray (JIRA)

Michelle Murray created JBIDE-13382: --------------------------------------- Summary: '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 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, 5 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 updated JBIDE-13381: ------------------------------------------ Attachment: jbide-13381.patch > 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, 5 months

1
0
0 / 0

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

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBDS-2446?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBDS-2446: ----------------------------------------- It's definitely SOA-P tooling that you're bumping up against. We're in the process of getting a better handle on some of the SOA-P tools again now that we have a few more folks to work on it. But Slava is still our best hope in the short term. :) He's been helping us out when we've needed tweaks to the ESB editor. > 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 > > 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, 5 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