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)
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)
I think the correct place to file this is https://issues.jboss.org/browse/JBIDE. I've CC'd someone who will likely know.
This has been moved to Jira.
@Sepastian Faulhaber: I tried to replicate the bug but failed to do so. I can create an application which is using a special character '\u00ae' in the manifest (cartridge name or description for instance). Could your issue be caused by something different than the tooling itself or do I miss something?
It would be especially helpful if you could provide your Eclipse log if there's anything relevant in it.
ok...please try the following steps to reproduce:
1. Modify the official EAP Cartridge by adding a '®' to the description: (I've attached my manifest.yml)
2. Reinstall cartridge with the following commands:
oo-admin-cartridge --action install --recursive --source /usr/libexec/openshift/cartridges
oo-admin-ctl-cartridge --activate -c import-node --obsolete
oo-admin-broker-cache --clear && oo-admin-console-cache --clear
3. Create a new gear based on EAP cartridge.
4. Start JBDS and connect to OSE instance via OpenShiftExplorer Plugin. The first rest call against OSE should lead to the error.
My .log shows the following error:
!ENTRY org.eclipse.core.jobs 4 2 2014-08-28 03:02:54.101
!MESSAGE An internal error occurred during: "Loading OpenShift information...".
java.lang.NumberFormatException: For input string: "00ae"
Software Versions (I use the official VMDK OSE image from our customer portal):
OpenShift Enterprise 2.1.0
JBoss Developer Studio
Build id: GA-v20140314-2145-B688
Build date: 20140314-2145
Created attachment 931751 [details]
manifest.yml with ® character that can be used to reproduce the issue.
@Sepastian Faulhaber: thanks, that helps a lot! Nevertheless after Brenton changed the manifests in our dev instance I still cannot reproduce the issue. I can create the app (with the invalid character in manfiest aka "description") and have it listed in OpenShift Explorer. See the screenshot here: https://issues.jboss.org/browse/JBIDE-18093?focusedCommentId=12996495&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12996495
looking more closely at your stacktrace I have the impression that you have an illegal character in some domain name:
is in java code
Is that the case?
I did not use a special character in the domain name; just alphanumeric characters.
Are you also trying to reproduce it on the OSE VMDK 2.1.0 ? Can I provide you any more logs or shall I share my screen for you?
The VM we're using is very slightly newer than OSE VMDK 2.1.0.
@Sepastian: could I also ask you to test our latest Milestone in order to verify that the latest (JBDS 8.0.0.Beta3) would have this fixed?
it works smoothly with JBDS 8.0.0.Beta3. So maybe the issue is JBDS related?!
Andre Dietisheim <email@example.com> updated the status of jira JBIDE-18093 to Resolved
I could finally reproduce this in JBDS 7.1.1 while I cant in JBDS 8 so the issue is fixed in upcoming JBDS 8 which will become GA in October.
@Sebastian Faulhaber: the root cause of this error is in the json parser that we us in openshift-java-client which JBDS relies on. I vaguely remember that we upgraded the parser at some point in the JBDS 8 dev cycle. I bet this fixed this for JBDS 8.
Marián Labuda <firstname.lastname@example.org> updated the status of jira JBIDE-18093 to Closed