[JBoss JIRA] (JBIDE-13808) Test failures and timeouts in JSF tests
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13808?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-13808:
-------------------------------------------
Assignee: Konstantin Marmalyukov (was: Yahor Radtsevich)
> Test failures and timeouts in JSF tests
> ---------------------------------------
>
> Key: JBIDE-13808
> URL: https://issues.jboss.org/browse/JBIDE-13808
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf, visual-page-editor-core
> Affects Versions: 4.0.1.Final
> Reporter: Nick Boldt
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Fix For: 4.0.x
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--javaee/146/console}
> [INFO] org.jboss.tools.jsf.text.ext.test ................. FAILURE [1:20.290s]
> [INFO] org.jboss.tools.jsf.vpe.facelets.test ............. FAILURE [1:00:28.012s]
> [INFO] org.jboss.tools.jsf.vpe.jbpm.test ................. FAILURE [1:00:24.806s]
> [INFO] org.jboss.tools.jsf.vpe.jstl.test ................. FAILURE [1:00:25.978s]
> [INFO] org.jboss.tools.jsf.vpe.seam.test ................. FAILURE [1:00:28.143s]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.text.ext.test: An unexpected error occured (return code 134). See log for details. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.facelets.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.jbpm.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.jstl.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.seam.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-13364) Consider changing the way in which BrowserSim uses WebKit engine
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13364?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-13364:
-------------------------------------------
Assignee: Konstantin Marmalyukov (was: Yahor Radtsevich)
> 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: browsersim
> Reporter: Yahor Radtsevich
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.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]
> * Support debugging protocol or ability to launch Web Inspector/Chrome Developer Tools [for 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
> ** - Do not support Web Inspector/Chrome Developer Tools
> *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
12 years, 5 months
[JBoss JIRA] (JBIDE-3287) rich:messages bugs
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3287?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-3287:
------------------------------------------
Assignee: Konstantin Marmalyukov (was: Yahor Radtsevich)
> rich:messages bugs
> ------------------
>
> Key: JBIDE-3287
> URL: https://issues.jboss.org/browse/JBIDE-3287
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-templates
> Affects Versions: 3.0.0.beta1
> Reporter: Yura Zhishko
> Assignee: Konstantin Marmalyukov
> Fix For: LATER
>
> Attachments: screenshot-1.jpg, screenshot-2.jpg, xh.zip
>
>
> 1) Incorrect behavior of labelClass attribute (screenshot-1):
> STEP 1. Use attached file
> STEP 2. Find rich:messages component
> STEP 3. Set labelClass attribute with the name value of non-existing class
> RESULT: Styles of *Class attributes are not overriding by styles from *LableClass attributes, but they have to do it
> 2) Text-align isn't applyed correctly (screenshot-1), because we use representation of the component as a table with two collumns (for markers, and for labels), something like that:
> <TABLE>
> <TR>
> <TD>
> <DIV>
> <SPAN>
> Warning
> </SPAN>
> </DIV>
> </TD>
> <TD>
> Warning message
> </TD>
> </TR>
> ......
> </TABLE>
> But mozilla browser build only one collumn, something like that:
> <TABLE>
> <TR>
> <TD>
> <SPAN>Warning</SPAN>
> <SPAN>Warning message</SPAN>
> </TD>
> <TR>
> ......
> </TABLE>
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-3382) f:verbatim interaction with JSF tags
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3382?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-3382:
------------------------------------------
Assignee: Konstantin Marmalyukov (was: Yahor Radtsevich)
> f:verbatim interaction with JSF tags
> ------------------------------------
>
> Key: JBIDE-3382
> URL: https://issues.jboss.org/browse/JBIDE-3382
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-templates
> Affects Versions: 3.0.0.CR2
> Reporter: Yura Zhishko
> Assignee: Konstantin Marmalyukov
> Fix For: 4.0.x
>
> Attachments: richT1.zip, screenshot-1.jpg, testT1_noVerbatim.zip
>
>
> 1) Import attached project
> 2) Open emptyTags.jsp page
> 3) You'll see a full list of jsf components with f:verbatim tag inside
> 4) Run this project on server
> RESULT: VPE reflection and browser reflection are different (see screen shot)
> Every tag has a label opposite itself with instruction how it processes f:verbatim tag.
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-9248) Add JSP 2.0 Tag Files support (<jsp:doBody> should be displayed correctly)
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9248?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-9248:
------------------------------------------
Assignee: Konstantin Marmalyukov (was: Yahor Radtsevich)
> Add JSP 2.0 Tag Files support (<jsp:doBody> should be displayed correctly)
> --------------------------------------------------------------------------
>
> Key: JBIDE-9248
> URL: https://issues.jboss.org/browse/JBIDE-9248
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-templates
> Affects Versions: 3.3.0.M1
> Reporter: Maxim Areshkau
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.x
>
> Attachments: greeting.jsp, greeting.png, jspDoBody.zip, response.png, response.tag
>
>
> Currently custom JSP tags from *.tag files are not properly displayed in VPE.
> As well as <jsp:doBody> tag from within such tags.
> The requirements are:
> 1) Add to VPE the ability to recognize JSP 2.0 custom tags files (*.[tag|tagx])
> 2) VPE should CORRECTLY display the content of the JSP 2.0 Tag Files.
> 3) The content(children) of the custom tag should be plased into its template from *.[tag|tagx] files to the place where <jsp:doBody> is specified.
--
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
12 years, 5 months