[JBoss JIRA] (JBIDE-18093) Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS
by Brenton Leanhardt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
Brenton Leanhardt commented on JBIDE-18093:
-------------------------------------------
Crazy. It might be worth following up with the reporter of the original bug: https://bugzilla.redhat.com/show_bug.cgi?id=1122089
> Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18093
> URL: https://issues.jboss.org/browse/JBIDE-18093
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.CR1
>
> Attachments: special-character-mock-cartridges.png
>
>
> Description of problem:
> I have developed a custom cartridge for OSE and placed the special character "®" (registered trademark) in the description field within my "manifest.yml". The cartridge could be installed correctly via WebUI and was also working fine from a technical point of view.
> However, when trying to access the OSE instance from JBDS via the Openshift Explorer plugin, I always got the following error:
> Invalid value for input string: "00ae"
> The string "00ae" is the unicode representation of my special character. After removing everything worked fine again. The OpenShift Explorer was completely unusable in this scenario! So only one installed cartridge with this special character can poison a whole installation and affect ALL users!!!
> Version-Release number of selected component (if applicable):
> OSE 2.2 (Developer Image)
> How reproducible:
> Yes.
> Steps to Reproduce:
> 1. Create a custom cartridge and add a "®" to the description field of your manifest.yml.
> 2. Install the cartridge according to doc.
> 3. Start JBDS and try to work with your OSE instance via the OpenShift Explorer plugin (e.g. try to add an application)
> Actual results:
> Expected results:
> Additional info:
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen commented on JBIDE-2720:
--------------------------------------------
xulrunner one wont support much html5 content - especially pages with heavy javascript. the html5 preview does. thats the main benefit.
the "loss" is that you can't edit in the preview but for now users feedback have generally been they dont care/need the visual edit - more important is the visual selection/navigation. Which html5 preview does provide.
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, screenshot-1.png, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17656:
---------------------------------------------
i'm marking this as critical since this is on the most used OS.
> Forge crashed Eclipse
> ---------------------
>
> Key: JBIDE-17656
> URL: https://issues.jboss.org/browse/JBIDE-17656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2
> Reporter: Fred Bricon
> Assignee: Vineet Reynolds
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log, hs_err_pid640.log, JVM-GCactivity-heap.png, JVM-GCactivity-Linux.png, JVM-GCactivity.png
>
>
> I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17656:
----------------------------------------
Priority: Critical (was: Major)
> Forge crashed Eclipse
> ---------------------
>
> Key: JBIDE-17656
> URL: https://issues.jboss.org/browse/JBIDE-17656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2
> Reporter: Fred Bricon
> Assignee: Vineet Reynolds
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log, hs_err_pid640.log, JVM-GCactivity-heap.png, JVM-GCactivity-Linux.png, JVM-GCactivity.png
>
>
> I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18093) Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18093:
------------------------------------------
I tried this and it worked for me, I cant reproduce this:
!special-character-mock-cartridges.png!
Maybe I'm missing something?
> Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18093
> URL: https://issues.jboss.org/browse/JBIDE-18093
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.CR1
>
> Attachments: special-character-mock-cartridges.png
>
>
> Description of problem:
> I have developed a custom cartridge for OSE and placed the special character "®" (registered trademark) in the description field within my "manifest.yml". The cartridge could be installed correctly via WebUI and was also working fine from a technical point of view.
> However, when trying to access the OSE instance from JBDS via the Openshift Explorer plugin, I always got the following error:
> Invalid value for input string: "00ae"
> The string "00ae" is the unicode representation of my special character. After removing everything worked fine again. The OpenShift Explorer was completely unusable in this scenario! So only one installed cartridge with this special character can poison a whole installation and affect ALL users!!!
> Version-Release number of selected component (if applicable):
> OSE 2.2 (Developer Image)
> How reproducible:
> Yes.
> Steps to Reproduce:
> 1. Create a custom cartridge and add a "®" to the description field of your manifest.yml.
> 2. Install the cartridge according to doc.
> 3. Start JBDS and try to work with your OSE instance via the OpenShift Explorer plugin (e.g. try to add an application)
> Actual results:
> Expected results:
> Additional info:
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18093) Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18093:
-------------------------------------
Attachment: special-character-mock-cartridges.png
> Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18093
> URL: https://issues.jboss.org/browse/JBIDE-18093
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.CR1
>
> Attachments: special-character-mock-cartridges.png
>
>
> Description of problem:
> I have developed a custom cartridge for OSE and placed the special character "®" (registered trademark) in the description field within my "manifest.yml". The cartridge could be installed correctly via WebUI and was also working fine from a technical point of view.
> However, when trying to access the OSE instance from JBDS via the Openshift Explorer plugin, I always got the following error:
> Invalid value for input string: "00ae"
> The string "00ae" is the unicode representation of my special character. After removing everything worked fine again. The OpenShift Explorer was completely unusable in this scenario! So only one installed cartridge with this special character can poison a whole installation and affect ALL users!!!
> Version-Release number of selected component (if applicable):
> OSE 2.2 (Developer Image)
> How reproducible:
> Yes.
> Steps to Reproduce:
> 1. Create a custom cartridge and add a "®" to the description field of your manifest.yml.
> 2. Install the cartridge according to doc.
> 3. Start JBDS and try to work with your OSE instance via the OpenShift Explorer plugin (e.g. try to add an application)
> Actual results:
> Expected results:
> Additional info:
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-15577) Hibernate Console problem while creating session factory
by Guillaume JOUVELOT (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15577?page=com.atlassian.jira.plugi... ]
Guillaume JOUVELOT commented on JBIDE-15577:
--------------------------------------------
I think I've found the root cause. In fact into my projects I'm using JPA annotations and Hibernate annotations at the same time and hibernate tools may not be able to manage the to types together.
Can you confirm it ?
> Hibernate Console problem while creating session factory
> --------------------------------------------------------
>
> Key: JBIDE-15577
> URL: https://issues.jboss.org/browse/JBIDE-15577
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.x
> Environment: Eclipse 4.3 (kepler), hibernate tools 3.7.0, Hibernate 4.2.2, jdk1.6.0.38
> Reporter: Guillaume JOUVELOT
> Assignee: Koen Aers
> Fix For: 4.2.x
>
>
> When I try to use hibernate console in order to test HQL queries I've the following error message from eclipse :
> {color:red}java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;{color}
> And the eclipse log file :
> !ENTRY org.hibernate.eclipse.console 4 4 2013-09-27 15:57:20.198
> !MESSAGE Problems while creating sessionfactory
> !SUBENTRY 1 org.hibernate.eclipse.console 4 150 2013-09-27 15:57:20.198
> !MESSAGE java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;
> !STACK 0
> java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;
> at org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider.<clinit>(C3P0ConnectionProvider.java:58)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at java.lang.Class.newInstance0(Unknown Source)
> at java.lang.Class.newInstance(Unknown Source)
> at org.hibernate.connection.ConnectionProviderFactory.initializeConnectionProviderFromConfig(ConnectionProviderFactory.java:174)
> at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:102)
> at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:84)
> at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:438)
> at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:91)
> at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2163)
> at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2159)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1383)
> at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954)
> at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:278)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107)
> at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:273)
> at org.hibernate.eclipse.console.workbench.LazySessionFactoryAdapter.getChildren(LazySessionFactoryAdapter.java:43)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> !SUBENTRY 2 org.hibernate.eclipse.console 4 150 2013-09-27 15:57:20.198
> !MESSAGE java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;
> !STACK 0
> java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;
> at org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider.<clinit>(C3P0ConnectionProvider.java:58)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at java.lang.Class.newInstance0(Unknown Source)
> at java.lang.Class.newInstance(Unknown Source)
> at org.hibernate.connection.ConnectionProviderFactory.initializeConnectionProviderFromConfig(ConnectionProviderFactory.java:174)
> at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:102)
> at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:84)
> at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:438)
> at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:91)
> at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2163)
> at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2159)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1383)
> at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954)
> at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:278)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107)
> at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:273)
> at org.hibernate.eclipse.console.workbench.LazySessionFactoryAdapter.getChildren(LazySessionFactoryAdapter.java:43)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> I've well configured my session factory.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months