Hallo allerseits!
Ich habe einen Web Service auf meinem JBoss Server (Jboss-WS CXF Stack) aufgesetzt. Dafür habe ich mir bereits über diverse Tools Client Stubs generieren lassen (Axis2, CFX, JDK-Variante, JBoss-spezifisch).
Diese funktionieren auch soweit ich feststellen konnte. Mit SoapUI kann ich auch herrlich mit dem WS umgehen. Aber sobald ich das Ganze in meinem RCP Client ausführen möchte, geht gar nichts mehr.
Vorweg: Mit einem Dummy-Modell funktioniert die RCP-Anwendung tadellos.
Wenn ich nu die ausgetauschten Daten mit Wireshark mitschneide (Server löppt auf VM), dann erkenne ich lesbaren (wenn auch nicht schönen) XML-Inhalt. Und alle Java SE Implementierungen können damit anscheinend umgehen.
[XML]
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:getAllNewsResponse xmlns:ns2="http://facade.news.wsServe.mmoell.de/">
<allNews>
<id>2</id>
<title>Messi: Auf dem Weg zum bestbezahlten Fuballer der Welt</title>
<author>matthias</author>
<created>2012-10-02T11:27:59+02:00</created>
<text>Lionel Messi trifft derzeit nach Belieben und hat den FC Barcelona im Alter von 25 Jahren schon zu zahlreichen Titeln geschossen. Durch seine starken Leistungen katapultiert sich der Argentinier auch in der weltweiten Gehaltsliste fast ganz nach oben. Nur ein ehemaliger Teamkollege kassiert noch mehr.</text>
</allNews>
<allNews>
...
</allNews>
</ns2:getAllNewsResponse>
</soap:Body>
</soap:Envelope>
[/XML]
Nur innerhalb meines RCP Clients will nichts funktionieren. Nur, das verstehe ich nicht:
Aus dem Stacktrace erahne ich, dass es was mit dem JAXB-Mapping zu tun hat. Aber eigentlich macht es doch keinen Sinn, wenn ich diesen Web Service und diese Client Stubs in einem normalen Java Programm verwenden kann oder?
[WR]
javax.xml.ws.WebServiceException: Unable to create JAXBContext
at com.sun.xml.internal.ws.model.AbstractSEIModelImpl.createJAXBContext(Unknown Source)
at com.sun.xml.internal.ws.model.AbstractSEIModelImpl.postProcess(Unknown Source)
at com.sun.xml.internal.ws.model.RuntimeModeler.buildRuntimeModel(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.createSEIPortInfo(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.addSEI(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(Unknown Source)
at javax.xml.ws.Service.getPort(Unknown Source)
at de.mmoell.wsclient.news.model.NewsInputProvider.getNewsContents(NewsInputProvider.java:55)
at de.mmoell.wsclient.news.view.NewsNavigationView.createPartControl(NewsNavigationView.java:51)
at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:375)
at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:229)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313)
at org.eclipse.ui.internal.ViewPane.setVisible(ViewPane.java:534)
at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180)
at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270)
at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473)
at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1245)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1198)
at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1597)
at org.eclipse.ui.internal.PartStack.createControl(PartStack.java:643)
at org.eclipse.ui.internal.PartStack.createControl(PartStack.java:570)
at org.eclipse.ui.internal.PartSashContainer.createControl(PartSashContainer.java:568)
at org.eclipse.ui.internal.PerspectiveHelper.activate(PerspectiveHelper.java:272)
at org.eclipse.ui.internal.Perspective.onActivate(Perspective.java:981)
at org.eclipse.ui.internal.WorkbenchPage.onActivate(WorkbenchPage.java:2714)
at org.eclipse.ui.internal.WorkbenchWindow$28.run(WorkbenchWindow.java:3030)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchWindow.setActivePage(WorkbenchWindow.java:3011)
at org.eclipse.ui.internal.WorkbenchWindow.busyOpenPage(WorkbenchWindow.java:799)
at org.eclipse.ui.internal.Workbench$23.runWithException(Workbench.java:1229)
at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757)
at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803)
at org.eclipse.ui.internal.Workbench$33.runWithException(Workbench.java:1600)
at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2609)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at de.mmoell.wsclient.Application.start(Application.java:20)
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:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: java.security.PrivilegedActionException: com.sun.xml.internal.bind.v2.runtime.IllegalAnnotationsException: 26 counts of IllegalAnnotationExceptions
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getOwningNewsOfCommentById". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetOwningNewsOfCommentById
at public de.mmoell.wsclient.ws.news.GetOwningNewsOfCommentById de.mmoell.wsclient.ws.news.ObjectFactory.createGetOwningNewsOfCommentById()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetOwningNewsOfCommentById
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getOwningNewsOfCommentByIdResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetOwningNewsOfCommentByIdResponse
at public de.mmoell.wsclient.ws.news.GetOwningNewsOfCommentByIdResponse de.mmoell.wsclient.ws.news.ObjectFactory.createGetOwningNewsOfCommentByIdResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetOwningNewsOfCommentByIdResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}removeNewsById". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.RemoveNewsById
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createRemoveNewsById(de.mmoell.wsclient.ws.news.RemoveNewsById)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.RemoveNewsById
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}removeNewsByIdResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.RemoveNewsByIdResponse
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createRemoveNewsByIdResponse(de.mmoell.wsclient.ws.news.RemoveNewsByIdResponse)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.RemoveNewsByIdResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}removeComment". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.RemoveComment
at public de.mmoell.wsclient.ws.news.RemoveComment de.mmoell.wsclient.ws.news.ObjectFactory.createRemoveComment()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.RemoveComment
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}removeCommentResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.RemoveCommentResponse
at public de.mmoell.wsclient.ws.news.RemoveCommentResponse de.mmoell.wsclient.ws.news.ObjectFactory.createRemoveCommentResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.RemoveCommentResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}persistNews". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.PersistNews
at public de.mmoell.wsclient.ws.news.PersistNews de.mmoell.wsclient.ws.news.ObjectFactory.createPersistNews()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.PersistNews
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}persistNewsResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.PersistNewsResponse
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createPersistNewsResponse(de.mmoell.wsclient.ws.news.PersistNewsResponse)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.PersistNewsResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}createNews". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.CreateNews
at public de.mmoell.wsclient.ws.news.CreateNews de.mmoell.wsclient.ws.news.ObjectFactory.createCreateNews()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.CreateNews
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}createNewsResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.CreateNewsResponse
at public de.mmoell.wsclient.ws.news.CreateNewsResponse de.mmoell.wsclient.ws.news.ObjectFactory.createCreateNewsResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.CreateNewsResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getCommentById". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetCommentById
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createGetCommentById(de.mmoell.wsclient.ws.news.GetCommentById)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetCommentById
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getCommentByIdResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetCommentByIdResponse
at public de.mmoell.wsclient.ws.news.GetCommentByIdResponse de.mmoell.wsclient.ws.news.ObjectFactory.createGetCommentByIdResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetCommentByIdResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getIdOfOwningNewsOfCommentById". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetIdOfOwningNewsOfCommentById
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createGetIdOfOwningNewsOfCommentById(de.mmoell.wsclient.ws.news.GetIdOfOwningNewsOfCommentById)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetIdOfOwningNewsOfCommentById
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getIdOfOwningNewsOfCommentByIdResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetIdOfOwningNewsOfCommentByIdResponse
at public de.mmoell.wsclient.ws.news.GetIdOfOwningNewsOfCommentByIdResponse de.mmoell.wsclient.ws.news.ObjectFactory.createGetIdOfOwningNewsOfCommentByIdResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetIdOfOwningNewsOfCommentByIdResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getCommentsOfNewsById". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetCommentsOfNewsById
at public de.mmoell.wsclient.ws.news.GetCommentsOfNewsById de.mmoell.wsclient.ws.news.ObjectFactory.createGetCommentsOfNewsById()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetCommentsOfNewsById
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getCommentsOfNewsByIdResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetCommentsOfNewsByIdResponse
at public de.mmoell.wsclient.ws.news.GetCommentsOfNewsByIdResponse de.mmoell.wsclient.ws.news.ObjectFactory.createGetCommentsOfNewsByIdResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetCommentsOfNewsByIdResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getAllNews". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetAllNews
at public de.mmoell.wsclient.ws.news.GetAllNews de.mmoell.wsclient.ws.news.ObjectFactory.createGetAllNews()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetAllNews
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getAllNewsResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetAllNewsResponse
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createGetAllNewsResponse(de.mmoell.wsclient.ws.news.GetAllNewsResponse)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetAllNewsResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}editNews". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.EditNews
at public de.mmoell.wsclient.ws.news.EditNews de.mmoell.wsclient.ws.news.ObjectFactory.createEditNews()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.EditNews
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}editNewsResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.EditNewsResponse
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createEditNewsResponse(de.mmoell.wsclient.ws.news.EditNewsResponse)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.EditNewsResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}editComment". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.EditComment
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createEditComment(de.mmoell.wsclient.ws.news.EditComment)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.EditComment
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}editCommentResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.EditCommentResponse
at public de.mmoell.wsclient.ws.news.EditCommentResponse de.mmoell.wsclient.ws.news.ObjectFactory.createEditCommentResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.EditCommentResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}addComment". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.AddComment
at public de.mmoell.wsclient.ws.news.AddComment de.mmoell.wsclient.ws.news.ObjectFactory.createAddComment()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.AddComment
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}addCommentResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.AddCommentResponse
at public de.mmoell.wsclient.ws.news.AddCommentResponse de.mmoell.wsclient.ws.news.ObjectFactory.createAddCommentResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.AddCommentResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getNewsById". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetNewsById
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createGetNewsById(de.mmoell.wsclient.ws.news.GetNewsById)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetNewsById
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getNewsByIdResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetNewsByIdResponse
at public de.mmoell.wsclient.ws.news.GetNewsByIdResponse de.mmoell.wsclient.ws.news.ObjectFactory.createGetNewsByIdResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetNewsByIdResponse
[/WR]
Ich hole mir einfach nur eine Liste von Modellobjekten, welche ich im Programm kurz darstellen möchte.
Es wäre echt schön, wenn jemand eine Idee hätte. Ich kann natürlich auch gerne noch was nachreichen, wenn ihr zum Beispiel gern das Model sehen würdet. Aber ich hoffe drauf, dass ich irgendwas Triviales bei meinem RCP Projekt vergessen hab...
Ich habe einen Web Service auf meinem JBoss Server (Jboss-WS CXF Stack) aufgesetzt. Dafür habe ich mir bereits über diverse Tools Client Stubs generieren lassen (Axis2, CFX, JDK-Variante, JBoss-spezifisch).
Diese funktionieren auch soweit ich feststellen konnte. Mit SoapUI kann ich auch herrlich mit dem WS umgehen. Aber sobald ich das Ganze in meinem RCP Client ausführen möchte, geht gar nichts mehr.
Vorweg: Mit einem Dummy-Modell funktioniert die RCP-Anwendung tadellos.
Wenn ich nu die ausgetauschten Daten mit Wireshark mitschneide (Server löppt auf VM), dann erkenne ich lesbaren (wenn auch nicht schönen) XML-Inhalt. Und alle Java SE Implementierungen können damit anscheinend umgehen.
[XML]
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:getAllNewsResponse xmlns:ns2="http://facade.news.wsServe.mmoell.de/">
<allNews>
<id>2</id>
<title>Messi: Auf dem Weg zum bestbezahlten Fuballer der Welt</title>
<author>matthias</author>
<created>2012-10-02T11:27:59+02:00</created>
<text>Lionel Messi trifft derzeit nach Belieben und hat den FC Barcelona im Alter von 25 Jahren schon zu zahlreichen Titeln geschossen. Durch seine starken Leistungen katapultiert sich der Argentinier auch in der weltweiten Gehaltsliste fast ganz nach oben. Nur ein ehemaliger Teamkollege kassiert noch mehr.</text>
</allNews>
<allNews>
...
</allNews>
</ns2:getAllNewsResponse>
</soap:Body>
</soap:Envelope>
[/XML]
Nur innerhalb meines RCP Clients will nichts funktionieren. Nur, das verstehe ich nicht:
- Es sind die selben generierten Klassen verwendet
- Es ist derselbe "Session-Aufbau"
- Es wurde keinerlei libraries eingebunden
Aus dem Stacktrace erahne ich, dass es was mit dem JAXB-Mapping zu tun hat. Aber eigentlich macht es doch keinen Sinn, wenn ich diesen Web Service und diese Client Stubs in einem normalen Java Programm verwenden kann oder?
[WR]
javax.xml.ws.WebServiceException: Unable to create JAXBContext
at com.sun.xml.internal.ws.model.AbstractSEIModelImpl.createJAXBContext(Unknown Source)
at com.sun.xml.internal.ws.model.AbstractSEIModelImpl.postProcess(Unknown Source)
at com.sun.xml.internal.ws.model.RuntimeModeler.buildRuntimeModel(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.createSEIPortInfo(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.addSEI(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(Unknown Source)
at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(Unknown Source)
at javax.xml.ws.Service.getPort(Unknown Source)
at de.mmoell.wsclient.news.model.NewsInputProvider.getNewsContents(NewsInputProvider.java:55)
at de.mmoell.wsclient.news.view.NewsNavigationView.createPartControl(NewsNavigationView.java:51)
at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:375)
at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:229)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313)
at org.eclipse.ui.internal.ViewPane.setVisible(ViewPane.java:534)
at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180)
at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270)
at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473)
at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1245)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1198)
at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1597)
at org.eclipse.ui.internal.PartStack.createControl(PartStack.java:643)
at org.eclipse.ui.internal.PartStack.createControl(PartStack.java:570)
at org.eclipse.ui.internal.PartSashContainer.createControl(PartSashContainer.java:568)
at org.eclipse.ui.internal.PerspectiveHelper.activate(PerspectiveHelper.java:272)
at org.eclipse.ui.internal.Perspective.onActivate(Perspective.java:981)
at org.eclipse.ui.internal.WorkbenchPage.onActivate(WorkbenchPage.java:2714)
at org.eclipse.ui.internal.WorkbenchWindow$28.run(WorkbenchWindow.java:3030)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchWindow.setActivePage(WorkbenchWindow.java:3011)
at org.eclipse.ui.internal.WorkbenchWindow.busyOpenPage(WorkbenchWindow.java:799)
at org.eclipse.ui.internal.Workbench$23.runWithException(Workbench.java:1229)
at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757)
at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803)
at org.eclipse.ui.internal.Workbench$33.runWithException(Workbench.java:1600)
at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2609)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at de.mmoell.wsclient.Application.start(Application.java:20)
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:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: java.security.PrivilegedActionException: com.sun.xml.internal.bind.v2.runtime.IllegalAnnotationsException: 26 counts of IllegalAnnotationExceptions
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getOwningNewsOfCommentById". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetOwningNewsOfCommentById
at public de.mmoell.wsclient.ws.news.GetOwningNewsOfCommentById de.mmoell.wsclient.ws.news.ObjectFactory.createGetOwningNewsOfCommentById()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetOwningNewsOfCommentById
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getOwningNewsOfCommentByIdResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetOwningNewsOfCommentByIdResponse
at public de.mmoell.wsclient.ws.news.GetOwningNewsOfCommentByIdResponse de.mmoell.wsclient.ws.news.ObjectFactory.createGetOwningNewsOfCommentByIdResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetOwningNewsOfCommentByIdResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}removeNewsById". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.RemoveNewsById
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createRemoveNewsById(de.mmoell.wsclient.ws.news.RemoveNewsById)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.RemoveNewsById
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}removeNewsByIdResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.RemoveNewsByIdResponse
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createRemoveNewsByIdResponse(de.mmoell.wsclient.ws.news.RemoveNewsByIdResponse)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.RemoveNewsByIdResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}removeComment". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.RemoveComment
at public de.mmoell.wsclient.ws.news.RemoveComment de.mmoell.wsclient.ws.news.ObjectFactory.createRemoveComment()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.RemoveComment
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}removeCommentResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.RemoveCommentResponse
at public de.mmoell.wsclient.ws.news.RemoveCommentResponse de.mmoell.wsclient.ws.news.ObjectFactory.createRemoveCommentResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.RemoveCommentResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}persistNews". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.PersistNews
at public de.mmoell.wsclient.ws.news.PersistNews de.mmoell.wsclient.ws.news.ObjectFactory.createPersistNews()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.PersistNews
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}persistNewsResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.PersistNewsResponse
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createPersistNewsResponse(de.mmoell.wsclient.ws.news.PersistNewsResponse)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.PersistNewsResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}createNews". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.CreateNews
at public de.mmoell.wsclient.ws.news.CreateNews de.mmoell.wsclient.ws.news.ObjectFactory.createCreateNews()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.CreateNews
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}createNewsResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.CreateNewsResponse
at public de.mmoell.wsclient.ws.news.CreateNewsResponse de.mmoell.wsclient.ws.news.ObjectFactory.createCreateNewsResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.CreateNewsResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getCommentById". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetCommentById
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createGetCommentById(de.mmoell.wsclient.ws.news.GetCommentById)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetCommentById
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getCommentByIdResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetCommentByIdResponse
at public de.mmoell.wsclient.ws.news.GetCommentByIdResponse de.mmoell.wsclient.ws.news.ObjectFactory.createGetCommentByIdResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetCommentByIdResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getIdOfOwningNewsOfCommentById". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetIdOfOwningNewsOfCommentById
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createGetIdOfOwningNewsOfCommentById(de.mmoell.wsclient.ws.news.GetIdOfOwningNewsOfCommentById)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetIdOfOwningNewsOfCommentById
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getIdOfOwningNewsOfCommentByIdResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetIdOfOwningNewsOfCommentByIdResponse
at public de.mmoell.wsclient.ws.news.GetIdOfOwningNewsOfCommentByIdResponse de.mmoell.wsclient.ws.news.ObjectFactory.createGetIdOfOwningNewsOfCommentByIdResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetIdOfOwningNewsOfCommentByIdResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getCommentsOfNewsById". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetCommentsOfNewsById
at public de.mmoell.wsclient.ws.news.GetCommentsOfNewsById de.mmoell.wsclient.ws.news.ObjectFactory.createGetCommentsOfNewsById()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetCommentsOfNewsById
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getCommentsOfNewsByIdResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetCommentsOfNewsByIdResponse
at public de.mmoell.wsclient.ws.news.GetCommentsOfNewsByIdResponse de.mmoell.wsclient.ws.news.ObjectFactory.createGetCommentsOfNewsByIdResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetCommentsOfNewsByIdResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getAllNews". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetAllNews
at public de.mmoell.wsclient.ws.news.GetAllNews de.mmoell.wsclient.ws.news.ObjectFactory.createGetAllNews()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetAllNews
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getAllNewsResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetAllNewsResponse
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createGetAllNewsResponse(de.mmoell.wsclient.ws.news.GetAllNewsResponse)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetAllNewsResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}editNews". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.EditNews
at public de.mmoell.wsclient.ws.news.EditNews de.mmoell.wsclient.ws.news.ObjectFactory.createEditNews()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.EditNews
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}editNewsResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.EditNewsResponse
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createEditNewsResponse(de.mmoell.wsclient.ws.news.EditNewsResponse)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.EditNewsResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}editComment". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.EditComment
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createEditComment(de.mmoell.wsclient.ws.news.EditComment)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.EditComment
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}editCommentResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.EditCommentResponse
at public de.mmoell.wsclient.ws.news.EditCommentResponse de.mmoell.wsclient.ws.news.ObjectFactory.createEditCommentResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.EditCommentResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}addComment". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.AddComment
at public de.mmoell.wsclient.ws.news.AddComment de.mmoell.wsclient.ws.news.ObjectFactory.createAddComment()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.AddComment
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}addCommentResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.AddCommentResponse
at public de.mmoell.wsclient.ws.news.AddCommentResponse de.mmoell.wsclient.ws.news.ObjectFactory.createAddCommentResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.AddCommentResponse
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getNewsById". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetNewsById
at public javax.xml.bind.JAXBElement de.mmoell.wsclient.ws.news.ObjectFactory.createGetNewsById(de.mmoell.wsclient.ws.news.GetNewsById)
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetNewsById
Two classes have the same XML type name "{http://facade.news.wsServe.mmoell.de/}getNewsByIdResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at de.mmoell.wsclient.ws.news.GetNewsByIdResponse
at public de.mmoell.wsclient.ws.news.GetNewsByIdResponse de.mmoell.wsclient.ws.news.ObjectFactory.createGetNewsByIdResponse()
at de.mmoell.wsclient.ws.news.ObjectFactory
this problem is related to the following location:
at de.mmoell.wsclient.news.GetNewsByIdResponse
[/WR]
Ich hole mir einfach nur eine Liste von Modellobjekten, welche ich im Programm kurz darstellen möchte.
Java:
// Establish Connection
String serviceAddress = "http://master.de:8080/ws/facade/news?wsdl";
QName qName = new QName("http://facade.news.wsServe.mmoell.de/", "NewsFacadeService");
Service service = Service.create(new URL(serviceAddress), qName);
// Create JAX-WS SOAP Service Stub
NewsFacade client = service.getPort(NewsFacade.class);
// get Data
content = client.getAllNews();Es wäre echt schön, wenn jemand eine Idee hätte. Ich kann natürlich auch gerne noch was nachreichen, wenn ihr zum Beispiel gern das Model sehen würdet. Aber ich hoffe drauf, dass ich irgendwas Triviales bei meinem RCP Projekt vergessen hab...
