5:34 a.m.
Unusual bean mapping warnings
-----------------------------
Key: JBIDE-5254
URL: https://jira.jboss.org/jira/browse/JBIDE-5254
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Reporter: Tom Fennelly
Fix For: 3.1.0.CR1
When I
1. Open the "json-to-java" example (Smooks project examples),
2. Configure the input (using the input-message.jsn)
3. Open the "Java Mapping" process node.
All the bean bindings have warnings on them saying "- Selector 'XXXX'
isn't available".
What's this about? The Smooks config in question is totally valid, but in any case,
can we do something here to help the user make sense of this?
Image attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:34 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5254) Unusual bean mapping warnings
[
https://jira.jboss.org/jira/browse/JBIDE-5254?page=com.atlassian.jira.plu...
]
Tom Fennelly updated JBIDE-5254:
--------------------------------
Description:
When I:
1. Open the "json-to-java" example (Smooks project examples),
2. Configure the input (using the input-message.jsn)
3. Open the "Java Mapping" process node.
All the bean bindings have warnings on them saying "- Selector 'XXXX'
isn't available".
What's this about? The Smooks config in question is totally valid, but in any case,
can we do something here to help the user make sense of this?
Image attached.
was:
When I
1. Open the "json-to-java" example (Smooks project examples),
2. Configure the input (using the input-message.jsn)
3. Open the "Java Mapping" process node.
All the bean bindings have warnings on them saying "- Selector 'XXXX'
isn't available".
What's this about? The Smooks config in question is totally valid, but in any case,
can we do something here to help the user make sense of this?
Image attached.
Unusual bean mapping warnings
-----------------------------
Key: JBIDE-5254
URL: https://jira.jboss.org/jira/browse/JBIDE-5254
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Reporter: Tom Fennelly
Fix For: 3.1.0.CR1
When I:
1. Open the "json-to-java" example (Smooks project examples),
2. Configure the input (using the input-message.jsn)
3. Open the "Java Mapping" process node.
All the bean bindings have warnings on them saying "- Selector 'XXXX'
isn't available".
What's this about? The Smooks config in question is totally valid, but in any case,
can we do something here to help the user make sense of this?
Image attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:36 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5254) Unusual bean mapping warnings
[
https://jira.jboss.org/jira/browse/JBIDE-5254?page=com.atlassian.jira.plu...
]
Tom Fennelly updated JBIDE-5254:
--------------------------------
Attachment: Screen shot 2009-11-24 at 11.21.55.png
Unusual bean mapping warnings
-----------------------------
Key: JBIDE-5254
URL: https://jira.jboss.org/jira/browse/JBIDE-5254
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Reporter: Tom Fennelly
Fix For: 3.1.0.CR1
Attachments: Screen shot 2009-11-24 at 11.21.55.png
When I:
1. Open the "json-to-java" example (Smooks project examples),
2. Configure the input (using the input-message.jsn)
3. Open the "Java Mapping" process node.
All the bean bindings have warnings on them saying "- Selector 'XXXX'
isn't available".
What's this about? The Smooks config in question is totally valid, but in any case,
can we do something here to help the user make sense of this?
Image attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:19 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5254) Unusual bean mapping warnings
[
https://jira.jboss.org/jira/browse/JBIDE-5254?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick updated JBIDE-5254:
-------------------------------------
Assignee: Xue Peng
Unusual bean mapping warnings
-----------------------------
Key: JBIDE-5254
URL: https://jira.jboss.org/jira/browse/JBIDE-5254
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Reporter: Tom Fennelly
Assignee: Xue Peng
Fix For: 3.1.0.CR1
Attachments: Screen shot 2009-11-24 at 11.21.55.png
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
When I:
1. Open the "json-to-java" example (Smooks project examples),
2. Configure the input (using the input-message.jsn)
3. Open the "Java Mapping" process node.
All the bean bindings have warnings on them saying "- Selector 'XXXX'
isn't available".
What's this about? The Smooks config in question is totally valid, but in any case,
can we do something here to help the user make sense of this?
Image attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:19 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5254) Unusual bean mapping warnings
[
https://jira.jboss.org/jira/browse/JBIDE-5254?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick updated JBIDE-5254:
-------------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
I'm having even more issues here. If I create a collection class (People) and an
object class (Person) and try to add either of these classes to the Java Mapping task,
I'm getting all kinds of exceptions. I'm attaching this one here... Anybody have
any ideas why? I've checked the Java compiler & JRE versions for the runtime and
they match.
!ENTRY org.eclipse.ui 4 0 2009-11-23 16:26:22.758
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.jboss.tools.smooks.graphical.wizards.JavaBeanCreationWizardPage.refreshJavaBeanModel(JavaBeanCreationWizardPage.java:398)
at
org.jboss.tools.smooks.graphical.wizards.JavaBeanCreationWizardPage$4.modifyText(JavaBeanCreationWizardPage.java:293)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1200)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1181)
at org.eclipse.swt.widgets.Text.setText(Text.java:2014)
at
org.jboss.tools.smooks.graphical.wizards.JavaBeanCreationWizardPage$8.modifyText(JavaBeanCreationWizardPage.java:457)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1200)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1181)
at org.eclipse.swt.widgets.Text.setText(Text.java:2014)
at
org.jboss.tools.smooks.graphical.wizards.JavaBeanCreationWizardPage$9.widgetSelected(JavaBeanCreationWizardPage.java:480)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at
org.jboss.tools.smooks.graphical.editors.commands.CreateJavaBeanModelCommand.execute(CreateJavaBeanModelCommand.java:75)
at org.eclipse.gef.commands.CompoundCommand.execute(CompoundCommand.java:107)
at org.eclipse.gef.commands.CommandStack.execute(CommandStack.java:170)
at
org.jboss.tools.smooks.graphical.editors.SmooksGraphicalEditorPart$1.execute(SmooksGraphicalEditorPart.java:154)
at org.eclipse.gef.ui.actions.WorkbenchPartAction.execute(WorkbenchPartAction.java:76)
at
org.jboss.tools.smooks.graphical.actions.AddSmooksModelAction.run(AddSmooksModelAction.java:99)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Unusual bean mapping warnings
-----------------------------
Key: JBIDE-5254
URL: https://jira.jboss.org/jira/browse/JBIDE-5254
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Reporter: Tom Fennelly
Fix For: 3.1.0.CR1
Attachments: Screen shot 2009-11-24 at 11.21.55.png
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
When I:
1. Open the "json-to-java" example (Smooks project examples),
2. Configure the input (using the input-message.jsn)
3. Open the "Java Mapping" process node.
All the bean bindings have warnings on them saying "- Selector 'XXXX'
isn't available".
What's this about? The Smooks config in question is totally valid, but in any case,
can we do something here to help the user make sense of this?
Image attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:57 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5254) Unusual bean mapping warnings
[
https://jira.jboss.org/jira/browse/JBIDE-5254?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBIDE-5254:
-------------------------------------
I had a little play with this.
The problem, as I see it is that, is with how the JsonInputDataParser class constructs the
tagList (IXMLStructuredObject) for the SelectorCreationDialog dialog. It uses the
XMLObjectAnalyzer class to build up the TagList instance. This instance gets set as the
rootList on the IXMLStructuredObject returned to SelectorCreationDialog, but
SelectorCreationDialog attempts to get the list from the IXMLStructuredObject's child
list (yes... IXMLStructuredObject has 2 lists).
After modifying that locally, it gets rid of the warnings, but only temporarily :) If I
mod something, the List<Object> held by the SelectorValidator gets cleared and a
thread is kicked off to async repopulate it. Meantime (in a separate thread I assume),
the SelectorValidator is called to validate the selectors against the internal
List<Object>, but it hasn't been populated yet by the async thread.... more
warnings.... when the List does get repopulated, the warnings are not getting removed
because the validation doesn't seem to happen again.
Sooooo...... seems to be at least 2 issues here... how the tagList is being added to
IXMLStructuredObject, and how the validation is synchronized.
Hope that's of some help.
Unusual bean mapping warnings
-----------------------------
Key: JBIDE-5254
URL: https://jira.jboss.org/jira/browse/JBIDE-5254
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Reporter: Tom Fennelly
Assignee: Xue Peng
Fix For: 3.1.0.CR1
Attachments: Screen shot 2009-11-24 at 11.21.55.png
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
When I:
1. Open the "json-to-java" example (Smooks project examples),
2. Configure the input (using the input-message.jsn)
3. Open the "Java Mapping" process node.
All the bean bindings have warnings on them saying "- Selector 'XXXX'
isn't available".
What's this about? The Smooks config in question is totally valid, but in any case,
can we do something here to help the user make sense of this?
Image attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:32 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5254) Unusual bean mapping warnings
[
https://jira.jboss.org/jira/browse/JBIDE-5254?page=com.atlassian.jira.plu...
]
Xue Peng commented on JBIDE-5254:
---------------------------------
To Brian :
I have no idea with your problems , maybe you need to refresh them ....
To Tom :
As you said , because the List was filled in async thread , so when validated the selector
string , the List is empty sometimes. I have change it to fill the List in the sync thread
.
Unusual bean mapping warnings
-----------------------------
Key: JBIDE-5254
URL: https://jira.jboss.org/jira/browse/JBIDE-5254
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Reporter: Tom Fennelly
Assignee: Xue Peng
Fix For: 3.1.0.CR1
Attachments: Screen shot 2009-11-24 at 11.21.55.png
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
When I:
1. Open the "json-to-java" example (Smooks project examples),
2. Configure the input (using the input-message.jsn)
3. Open the "Java Mapping" process node.
All the bean bindings have warnings on them saying "- Selector 'XXXX'
isn't available".
What's this about? The Smooks config in question is totally valid, but in any case,
can we do something here to help the user make sense of this?
Image attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:08 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-5254) Unusual bean mapping warnings
[
https://jira.jboss.org/jira/browse/JBIDE-5254?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick resolved JBIDE-5254.
--------------------------------------
Resolution: Done
Unusual bean mapping warnings
-----------------------------
Key: JBIDE-5254
URL: https://jira.jboss.org/jira/browse/JBIDE-5254
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Reporter: Tom Fennelly
Assignee: Xue Peng
Fix For: 3.1.0.CR1
Attachments: Screen shot 2009-11-24 at 11.21.55.png
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
When I:
1. Open the "json-to-java" example (Smooks project examples),
2. Configure the input (using the input-message.jsn)
3. Open the "Java Mapping" process node.
All the bean bindings have warnings on them saying "- Selector 'XXXX'
isn't available".
What's this about? The Smooks config in question is totally valid, but in any case,
can we do something here to help the user make sense of this?
Image attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5976
days inactive
5977
days old
jbosstools-issues@lists.jboss.org
7 comments
3 participants
participants (3)
-
Brian Fitzpatrick (JIRA) -
Tom Fennelly (JIRA)
-
Xue Peng (JIRA)