Topic
3 replies Latest Post - ‏2013-03-05T20:18:50Z by DGawron
Munishsharma_in
Munishsharma_in
1 Post
ACCEPTED ANSWER

Pinned topic Access data from DB2 with WPF 6.x with WASCE

‏2012-01-17T14:10:10Z |
Please suggest the possible methods to access data from DB2 using WPF with WASCE.

1) We could add entry of DB2 as Datapool in WASCE (m stuck here because SQL Call builder cant fetch datasource)

2) We cant use any Java code via JDBC and then could use LJO (Please suggest if its optimum.)

3) ...any other suggestion
Updated on 2013-03-05T20:18:50Z at 2013-03-05T20:18:50Z by DGawron
  • DGawron
    DGawron
    250 Posts
    ACCEPTED ANSWER

    Re: Access data from DB2 with WPF 6.x with WASCE

    ‏2012-02-02T22:22:28Z  in response to Munishsharma_in
    You need to define a datasource and then correctly modify a few deployment descriptors for that datasource to be visible to your WPF WAR. Here's an article on the WPF wiki that covers the steps for WASCE.

    http://www-10.lotus.com/ldd/pfwiki.nsf/dx/how-do-i-configure-datasources-correctly-in-the-wasce-deployment-scenerio-
    • SystemAdmin
      SystemAdmin
      532 Posts
      ACCEPTED ANSWER

      Re: Access data from DB2 with WPF 6.x with WASCE

      ‏2013-03-01T19:42:08Z  in response to DGawron
      I already did the modifications on the geronimo-web.xml and wasce.web.xml files, but now i get this Error when I click the Fecth Datasource Names button

      "Error running processInputChange method on the following coordinator class: com.bowstreet.buidlers.webapp.ui.SqlCallCoordinator

      Reason:
      class.java.lang.ClassCastException:
      org.apache.xerces.parsers.XIncludeAwareParserConfiguration incompible with
      org.apache.xerces.xni.parser.XMLPArserConfiguration"

      And this is the Details >>

      class java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration incompatible with org.apache.xerces.xni.parser.XMLParserConfiguration
      org.apache.xerces.parsers.XIncludeAwareParserConfiguration incompatible with org.apache.xerces.xni.parser.XMLParserConfiguration
      Plug-in Provider: IBM
      Plug-in Name: Web Experience Factory Designer UI
      Plug-in ID: com.bowstreet.designer.ui
      Version: 8.0.0

      java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration incompatible with org.apache.xerces.xni.parser.XMLParserConfiguration
      at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
      at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
      at org.apache.xerces.jaxp.DocumentBuilderImpl.<init>(Unknown Source)
      at org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown Source)
      at org.eclipse.ui.internal.forms.widgets.FormTextModel.parseInputStream(FormTextModel.java:125)
      at org.eclipse.ui.internal.forms.widgets.FormTextModel.parseTaggedText(FormTextModel.java:111)
      at org.eclipse.ui.forms.widgets.FormText.setText(FormText.java:673)
      at org.eclipse.ui.internal.cheatsheets.views.ViewItem.addItem(ViewItem.java:212)
      at org.eclipse.ui.internal.cheatsheets.views.ViewItem.<init>(ViewItem.java:100)
      at org.eclipse.ui.internal.cheatsheets.views.CoreItem.<init>(CoreItem.java:60)
      at org.eclipse.ui.internal.cheatsheets.views.CheatSheetPage.createPart(CheatSheetPage.java:86)
      at org.eclipse.ui.internal.cheatsheets.views.CheatSheetViewer.initCheatSheetView(CheatSheetViewer.java:898)
      at org.eclipse.ui.internal.cheatsheets.views.CheatSheetViewer.setContent(CheatSheetViewer.java:1142)
      at org.eclipse.ui.internal.cheatsheets.views.CheatSheetViewer.setInput(CheatSheetViewer.java:1241)
      at org.eclipse.ui.internal.cheatsheets.views.CheatSheetViewer.setInput(CheatSheetViewer.java:1215)
      at org.eclipse.ui.internal.cheatsheets.views.CheatSheetView.setInput(CheatSheetView.java:217)
      at org.eclipse.ui.cheatsheets.OpenCheatSheetAction.run(OpenCheatSheetAction.java:147)
      at com.bowstreet.designer.eclipse.CoordinatorCallback.openCheatSheet(CoordinatorCallback.java:189)
      at com.bowstreet.builders.webapp.ui.SqlCallCoordinator.setDataSourceNameChoices(SqlCallCoordinator.java:167)
      at com.bowstreet.builders.webapp.ui.SqlCallCoordinator.handleFetchDataSourceNamesChange(SqlCallCoordinator.java:1106)
      at com.bowstreet.builders.webapp.ui.SqlCallCoordinator.processInputChange(SqlCallCoordinator.java:1284)
      at com.bowstreet.editor.uitools.coordinator.BuilderEditorCoordinatorController.processInputChange(BuilderEditorCoordinatorController.java:448)
      at com.bowstreet.designer.builders.CoordinatorRunner$CoordinatorContextInternal.processInputChange(CoordinatorRunner.java:666)
      at com.bowstreet.designer.builders.CoordinatorRunner.builderWidgetChanged(CoordinatorRunner.java:269)
      at com.bowstreet.designer.builders.widgets.AbstractBuilderWidget.notifyAllListeners(AbstractBuilderWidget.java:220)
      at com.bowstreet.designer.builders.widgets.AbstractButtonWidget.widgetSelected(AbstractButtonWidget.java:101)
      at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
      at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
      at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
      at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
      at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
      at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
      at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
      at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
      at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
      at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
      at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
      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:369)
      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:60)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
      at java.lang.reflect.Method.invoke(Method.java:611)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
      What should I do?
      • DGawron
        DGawron
        250 Posts
        ACCEPTED ANSWER

        Re: Access data from DB2 with WPF 6.x with WASCE

        ‏2013-03-05T20:18:50Z  in response to SystemAdmin
        This doesn't have anything to do with datasource config itself. You have a Xerces JAR somewhere in your Designer environment that is getting in the way of the one used in WEF. Search the WEF forums for the same error message and I think you'll find a few postings with possible solutions.