[JBoss JIRA] (JBIDE-14652) CordovaSim: cross-origin requests send default user agent string in headers
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14652?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-14652:
--------------------------------
Attachment: userAgent.png
> CordovaSim: cross-origin requests send default user agent string in headers
> ---------------------------------------------------------------------------
>
> Key: JBIDE-14652
> URL: https://issues.jboss.org/browse/JBIDE-14652
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Affects Versions: 4.1.0.Beta1
> Reporter: Yahor Radtsevich
> Assignee: Ilya Buziuk
> Fix For: 4.1.0.Beta2
>
> Attachments: ua-actual-result.png, userAgent.png
>
>
> Cross-origin XMLHttpRequest send browser's default User Agent string in the request headers.
> *Steps to reproduce:*
> Create the following page in a hybrid project and open it with CordovaSim:
> {code:xml|title=ua-test.html}
> <script>
> var client = new XMLHttpRequest();
> client.onreadystatechange = function() {
> if(client.readyState == client.DONE) {
> if (client.status == 200) {
> alert(/<span id="body_lbUserAgent">([^>]*)<\/span>/ig.exec(client.responseText)[1]);
> } else {
> alert("Error code: " + client.status);
> }
> }
> }
> client.open("GET", "http://www.whatsmyuseragent.com/");
> client.send();
> </script>
> {code}
> *Actual result:*
> A desktop User Agent is shown:
> !ua-actual-result.png|thumbnail!
> *Expected result:*
> An iPhone User Agent is shown.
--
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, 10 months
[JBoss JIRA] (JBDS-2653) Can't update m2e-wtp to latest version in JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2653?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2653:
----------------------------------
This usecase is not supported. JBDS via the installer is a "you use what we give you, because that's what is 100% supported."
If you would like a "colour outside the lines" version of JBDS, where things like m2e and m2e-wtp can be upgraded to newer, more bleeding edge versions, then you want this:
http://marketplace.eclipse.org/content/jboss-developer-studio-kepler
... Or maybe we need to fix this so that both BYOE-via-Marketplace and Product-from-installer work the same way?
> Can't update m2e-wtp to latest version in JBDS
> ----------------------------------------------
>
> Key: JBDS-2653
> URL: https://issues.jboss.org/browse/JBDS-2653
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build, maven
> Affects Versions: 7.0.0.Beta1
> Reporter: Fred Bricon
> Fix For: 7.0.0.Beta2
>
>
> {quote}
> [19:26] <@fbricon> using latest JBDS beta1, I can't upgrade m2e-wtp to the version sitting in http://download.eclipse.org/m2e-wtp/milestones/kepler/1.0.0/1.0.0.2013060...
> [19:26] <@fbricon> though it seems JPA, JAXRS and JSF features can be updated
> [19:27] <@fbricon> nboldt: that can't be a range restriction from the features/plugins in central, otherwise m2e-wtp 1.0.0 wouldn't be installed in JBDS at all
> [19:28] <@fbricon> nboldt: m2e itself can be updated
> {quote}
> I can see the remediation screen and some option seems to be to uninstall JBDS to fix the issue. I also found the original error message buried in the UI :
> {noformat}
> Your original request has been modified.
> "m2e-wtp - Maven Integration for WTP (Incubation)" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130604-1618)
> Software currently installed: JBoss Developer Studio (Branded Product) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.all 7.0.0.Beta1-v20130529-0631-B257)
> Only one of the following can be installed at once:
> Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130507-1357 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130507-1357)
> Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130528-1157 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130528-1157)
> Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130604-1618)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.all 7.0.0.Beta1-v20130529-0631-B257)
> To: com.jboss.jbds.product.feature.feature.group [7.0.0.Beta1-v20130529-0631-B257]
> Cannot satisfy dependency:
> From: Maven Integration (Selected) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.m2e.feature.feature.group 7.0.0.Beta1-v20130529-0631-B257)
> To: org.eclipse.m2e.wtp.feature.feature.group [1.0.0.20130507-1357]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.product.feature.feature.group 7.0.0.Beta1-v20130529-0631-B257)
> To: com.jboss.jbds.m2e.feature.feature.group [7.0.0.Beta1-v20130529-0631-B257]
> Cannot satisfy dependency:
> From: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130507-1357 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130507-1357)
> To: org.eclipse.m2e.wtp.overlay.ui [1.0.0.20130507-1357]
> Cannot satisfy dependency:
> From: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130604-1618)
> To: org.eclipse.m2e.wtp.overlay.ui [1.0.0.20130604-1618]
> {noformat}
--
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, 10 months
[JBoss JIRA] (JBIDE-14769) Solutions not available reported by Marketplace
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14769?page=com.atlassian.jira.plugi... ]
Jiri Peterka commented on JBIDE-14769:
--------------------------------------
I was trying to replicate it to get better screenshot but it is gone now and I cannot see any warning anymore. Feel free to set it resolved. Not sure if it was related to JBIDE-14762 not not.
> Solutions not available reported by Marketplace
> -----------------------------------------------
>
> Key: JBIDE-14769
> URL: https://issues.jboss.org/browse/JBIDE-14769
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 4.1.0.Beta1
> Environment: JBT 4.1.Beta2, L64
> Reporter: Jiri Peterka
> Assignee: Jiri Peterka
> Fix For: 4.1.0.Beta2
>
> Attachments: solutions-not-available.png
>
>
> Not sure what it means but while installing JBT from Marketplace, there is this message. Installation seems ok. Can we avoid this meessage?
--
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, 10 months
[JBoss JIRA] (JBDS-2655) Using Database Developer, requires running server in order to connect using Teiid JDBC driver
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/JBDS-2655?page=com.atlassian.jira.plugin.... ]
Van Halbert updated JBDS-2655:
------------------------------
Description: When using Database Developer, created a new datasource (added Teiid JDBC driver from the file system) to connect to a EAP server running Teiid. I would have expected the connection to Teiid to operate as any other jdbc driver and other SQL tools, but in order to connect, I was required to setup a server in JBDS and start it. Which shouldn't be needed in order to make a jdbc connection to an external database. (was: When using Database Developer, created a new datasource (added Teiid JDBC driver from the file system) to connect to a EAP server running Teiid. I would have expected the connection to Teiid to operate as any other jdbc driver and other SQL tools, but in order to connect, I was required to setup a server in JBDS and start it (which shouldn't be required, IMO).)
> Using Database Developer, requires running server in order to connect using Teiid JDBC driver
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-2655
> URL: https://issues.jboss.org/browse/JBDS-2655
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: teiid
> Reporter: Van Halbert
>
> When using Database Developer, created a new datasource (added Teiid JDBC driver from the file system) to connect to a EAP server running Teiid. I would have expected the connection to Teiid to operate as any other jdbc driver and other SQL tools, but in order to connect, I was required to setup a server in JBDS and start it. Which shouldn't be needed in order to make a jdbc connection to an external database.
--
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, 10 months
[JBoss JIRA] (JBDS-2655) Using Database Developer, requires running server in order to connect using Teiid JDBC driver
by Van Halbert (JIRA)
Van Halbert created JBDS-2655:
---------------------------------
Summary: Using Database Developer, requires running server in order to connect using Teiid JDBC driver
Key: JBDS-2655
URL: https://issues.jboss.org/browse/JBDS-2655
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: teiid
Reporter: Van Halbert
When using Database Developer, created a new datasource (added Teiid JDBC driver from the file system) to connect to a EAP server running Teiid. I would have expected the connection to Teiid to operate as any other jdbc driver and other SQL tools, but in order to connect, I was required to setup a server in JBDS and start it (which shouldn't be required, IMO).
--
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, 10 months
[JBoss JIRA] (JBIDE-14770) Missing components when JBT 4.1.Beta1 is installed via Marketplace
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14770?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-14770:
------------------------------------
The aforementioned fix was to remove the trailing commas on the config, as I said in the previous (hence aforementioned) comment.
Screenshot for those who can't (or won't) scroll up: http://snag.gy/fx0h9.jpg
> Missing components when JBT 4.1.Beta1 is installed via Marketplace
> ------------------------------------------------------------------
>
> Key: JBIDE-14770
> URL: https://issues.jboss.org/browse/JBIDE-14770
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 4.1.0.Beta1
> Reporter: Jiri Peterka
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.1.0.Beta1
>
> Attachments: jbide14770.png
>
>
> Missing components when JBT 4.1.Beta1 is installed via Marketplace, specifially:
> Some of them might be intentional:
> - Arquillian support (Experimental) 1.0.4.Beta1-v20130518-2210-B3
> - Forge Tools Extensions (Forge 2.0 Support - Experimental) 1.0.0.Beta1-v20130524-1739-B66
> - JBoss BIRT Integration 1.5.0.Beta1-v20130518-0411-B36
> - JBoss Central - UI Themes for Eclipse 1.2.0.Beta1-v20130523-1233-B39
> - JBoss GWT Integration (Experimental) 1.1.0.Final-v20130205-2223-B78
> - JBoss Maven GWT Configurator 1.5.0.Beta1-v20130523-1233-B39
> - JBoss Mobile Hybrid Application Development Tools (Experimental) 1.0.0.Beta1-v20130523-2211-B7
> - JBoss Tools Apache Cordova Simulator 3.5.0.Beta1-v20130525-0825-B60
> - JBoss Tools Common - Mylyn 3.5.0.Beta1-v20130525-0108-B68
> - JBoss Tools LiveReload 1.0.0.Beta1-v20130524-1307-B28
> - Maven Integration for Eclipse JDT APT 1.0.1.201209200721
--
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, 10 months
[JBoss JIRA] (JBIDE-14770) Missing components when JBT 4.1.Beta1 is installed via Marketplace
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14770?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-14770.
-----------------------------------------
Resolution: Done
I dont know what "after the aforementioned fix" refers to - [~nickboldt]
but for me livereload and eclipse JDT are expected to be on marketplace and they seem to be based on my own and nicks test thus resolving. back to [~jpeterka]
> Missing components when JBT 4.1.Beta1 is installed via Marketplace
> ------------------------------------------------------------------
>
> Key: JBIDE-14770
> URL: https://issues.jboss.org/browse/JBIDE-14770
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 4.1.0.Beta1
> Reporter: Jiri Peterka
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.1.0.Beta1
>
> Attachments: jbide14770.png
>
>
> Missing components when JBT 4.1.Beta1 is installed via Marketplace, specifially:
> Some of them might be intentional:
> - Arquillian support (Experimental) 1.0.4.Beta1-v20130518-2210-B3
> - Forge Tools Extensions (Forge 2.0 Support - Experimental) 1.0.0.Beta1-v20130524-1739-B66
> - JBoss BIRT Integration 1.5.0.Beta1-v20130518-0411-B36
> - JBoss Central - UI Themes for Eclipse 1.2.0.Beta1-v20130523-1233-B39
> - JBoss GWT Integration (Experimental) 1.1.0.Final-v20130205-2223-B78
> - JBoss Maven GWT Configurator 1.5.0.Beta1-v20130523-1233-B39
> - JBoss Mobile Hybrid Application Development Tools (Experimental) 1.0.0.Beta1-v20130523-2211-B7
> - JBoss Tools Apache Cordova Simulator 3.5.0.Beta1-v20130525-0825-B60
> - JBoss Tools Common - Mylyn 3.5.0.Beta1-v20130525-0108-B68
> - JBoss Tools LiveReload 1.0.0.Beta1-v20130524-1307-B28
> - Maven Integration for Eclipse JDT APT 1.0.1.201209200721
--
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, 10 months
[JBoss JIRA] (JBIDE-14770) Missing components when JBT 4.1.Beta1 is installed via Marketplace
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14770?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-14770:
----------------------------------
Assignee: Max Rydahl Andersen (was: Nick Boldt)
I think this is fixed, but you might want to have more features added to the CoreTools category from which Marketplace config is derived, so I'm assigning this to you for comment, [~maxandersen].
I can add more features to Marketplace's Beta1 entry easily, but we should also ensure if we want to do that that the same is done in the update site's category.xml so that the category contents match what's put in Marketplace.
> Missing components when JBT 4.1.Beta1 is installed via Marketplace
> ------------------------------------------------------------------
>
> Key: JBIDE-14770
> URL: https://issues.jboss.org/browse/JBIDE-14770
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 4.1.0.Beta1
> Reporter: Jiri Peterka
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.1.0.Beta1
>
> Attachments: jbide14770.png
>
>
> Missing components when JBT 4.1.Beta1 is installed via Marketplace, specifially:
> Some of them might be intentional:
> - Arquillian support (Experimental) 1.0.4.Beta1-v20130518-2210-B3
> - Forge Tools Extensions (Forge 2.0 Support - Experimental) 1.0.0.Beta1-v20130524-1739-B66
> - JBoss BIRT Integration 1.5.0.Beta1-v20130518-0411-B36
> - JBoss Central - UI Themes for Eclipse 1.2.0.Beta1-v20130523-1233-B39
> - JBoss GWT Integration (Experimental) 1.1.0.Final-v20130205-2223-B78
> - JBoss Maven GWT Configurator 1.5.0.Beta1-v20130523-1233-B39
> - JBoss Mobile Hybrid Application Development Tools (Experimental) 1.0.0.Beta1-v20130523-2211-B7
> - JBoss Tools Apache Cordova Simulator 3.5.0.Beta1-v20130525-0825-B60
> - JBoss Tools Common - Mylyn 3.5.0.Beta1-v20130525-0108-B68
> - JBoss Tools LiveReload 1.0.0.Beta1-v20130524-1307-B28
> - Maven Integration for Eclipse JDT APT 1.0.1.201209200721
--
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, 10 months
