[JBoss JIRA] (JBIDE-22464) Jax-RS validation and browser doesn't understand mulitple jax-rs applicaitons in same project
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22464?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22464:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Jax-RS validation and browser doesn't understand mulitple jax-rs applicaitons in same project
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-22464
> URL: https://issues.jboss.org/browse/JBIDE-22464
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.4.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Xavier Coulon
> Fix For: 4.5.x
>
>
> I'm testing an application with 2 Jax-RS application servlets. I've defined then in the web.xml as follows (I'm not using annotations):
> {code:xml}
> <servlet-mapping>
> <servlet-name>my.app.services.RestServices</servlet-name>
> <url-pattern>/api/*</url-pattern>
> </servlet-mapping>
> <servlet-mapping>
> <servlet-name>my.app.pages.WebPages</servlet-name>
> <url-pattern>/pages/*</url-pattern>
> </servlet-mapping>
> {code}
> This cause a few issues:
> * in web.xml "Multiple JAX-RS Activators are defined for the project." (error by default, I set it to warning)
> * in the RestfulServices class, "The Application Path should be configured with an @ApplicationPath annotation or in the web deployment descriptor." error. It seems like the validator ignores a part of the web.xml
> * In Project Explorer, the "Jax-RS Services" node shows incorrect children: it shows api/ endpoints under pages/api/... whereas pages and api are "siblings".
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-16575) Tests for BrowserSim
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16575?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-16575:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Tests for BrowserSim
> --------------------
>
> Key: JBIDE-16575
> URL: https://issues.jboss.org/browse/JBIDE-16575
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: browsersim
> Reporter: Alexey Kazakov
> Assignee: Ilya Buziuk
> Priority: Critical
> Fix For: 4.5.x
>
>
> We should create JUnit tests which will run BrowserSim on both Java platforms: with JavaFX and w/o it. Those tests should check if webkit BS can be run on both platforms and if JavaFX BS can be run on the platform with JavaFX.
> It's probably imposible to have such tests without special Jenkins settings.
> So [~nickboldt]'s help is needed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22952) 3rd party caused HIDDEN below CordovaSimLaunchParametersUtil.getCordovaEngineLocation
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22952?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22952:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> 3rd party caused HIDDEN below CordovaSimLaunchParametersUtil.getCordovaEngineLocation
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-22952
> URL: https://issues.jboss.org/browse/JBIDE-22952
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: An internal error occurred during: "Launching kitchensink-cordova".
> {noformat}
> HIDDEN: Numeric identifier MUST NOT contain leading zeroes
> at EXTERNAL.EXTERNAL(null:-1)
> at org.eclipse.thym.android.core.adt.AndroidLibraryResolver.initFiles(AndroidLibraryResolver.java:56)
> at org.eclipse.thym.android.core.adt.AndroidLibraryResolver.isLibraryConsistent(AndroidLibraryResolver.java:88)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.searchDir(CordovaEngineProvider.java:246)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.searchDir(CordovaEngineProvider.java:271)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.searchDir(CordovaEngineProvider.java:271)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.searchDir(CordovaEngineProvider.java:271)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.searchDir(CordovaEngineProvider.java:271)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.searchForRuntimes(CordovaEngineProvider.java:233)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.initEngineList(CordovaEngineProvider.java:83)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.getAvailableEngines(CordovaEngineProvider.java:63)
> at org.eclipse.thym.core.engine.HybridMobileEngineManager.defaultEngines(HybridMobileEngineManager.java:112)
> at org.eclipse.thym.core.engine.HybridMobileEngineManager.getActiveEngines(HybridMobileEngineManager.java:78)
> at org.eclipse.thym.core.HybridProject.getActiveEngines(HybridProject.java:163)
> at org.jboss.tools.cordovasim.eclipse.launch.CordovaSimLaunchParametersUtil.getCordovaEngineLocation(CordovaSimLaunchParametersUtil.java:204)
> at org.jboss.tools.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:79)
> at org.jboss.tools.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationDelegate.launch(CordovaSimLaunchConfigurationDelegate.java:25)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.8.0.v20160509-0411 |
> | org.eclipse.debug.core | 3.10.100.v20160419-1720 | 3.10.100.v20160419-1720 |
> | org.eclipse.debug.ui | 3.11.200.v20160518-1858 | 3.11.200.v20160518-1858 |
> | org.eclipse.thym.android.core | 2.0.0.201605071736 | 2.0.0.201605071736 |
> | org.eclipse.thym.core | 2.0.0.201605071736 | 2.0.0.201605071736 |
> | org.jboss.tools.cordovasim.eclipse | 3.8.0.Final-v20160609-2302-B3 | 3.8.0.Final-v20160609-2302-B3 |
> Operating Systems:
> | MacOSX | 10.9.5 | 10.9.5 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57988311e4b0300861...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-20935:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Central doesn't scale back after being enlarged on Windows
> ----------------------------------------------------------
>
> Key: JBIDE-20935
> URL: https://issues.jboss.org/browse/JBIDE-20935
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Environment: Windows 10
> 250% UI scale
> Reporter: Jan Richter
> Assignee: Ilya Buziuk
> Labels: ui-scaling
> Fix For: 4.5.x
>
> Attachments: JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4, central.png, screenshot-1.png
>
>
> When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars.
> Like so:
> !central.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-13364) Consider changing the way in which BrowserSim uses WebKit engine
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13364?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-13364:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> 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: Ilya Buziuk
> Fix For: 4.5.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 was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-23376) Deploy Docker Wizard: Wizard is streched to display height
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23376?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-23376:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Deploy Docker Wizard: Wizard is streched to display height
> ----------------------------------------------------------
>
> Key: JBIDE-23376
> URL: https://issues.jboss.org/browse/JBIDE-23376
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Assignee: Snjezana Peco
> Priority: Minor
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.5.x
>
>
> When opening a Deploy Image to OpenShift from context menu of a docker image in Docker Explorer and I don't have selected any OpenShift connection, first wizard page contains selection of an OpenShift connection. Upon clicking on Next button, the next wizard page Deploy an Image is stretched to whole height of a display. I think it could be caused by changes in JBIDE-22912.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-19536:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Infinite job loop when creating project
> ---------------------------------------
>
> Key: JBIDE-19536
> URL: https://issues.jboss.org/browse/JBIDE-19536
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Rastislav Wagner
> Priority: Critical
> Fix For: 4.5.x
>
> Attachments: building.png, cdi_jstack, jstack.out, threaddump-1440009974151.tdump, threaddump-1440009999047.tdump, threaddump-1440010035476.tdump, workspace_jbds9_endless_building_loop.rar
>
>
> Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974
> I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months