normal | wide

Signup for Training


More trainings...

Intalio|BPMS Webinars

Latest Posts


Show last 6 hrs - 24 hrs - 7 days

Forum tags


Top Posters

Last 30 days

  • ravinderjit.singh (29)
  • Antoine (26)
  • danielandross (17)
  • venkaiah.k (16)
  • shao (14)
  • sirswendu.ganapati (13)
  • eva.das (13)
  • metabyte (12)
  • milos.vacek (7)
  • cristiano.quintao (7)

All time

  • Antoine (1492)
  • Shivanand (1194)
  • cshekhar (928)
  • psq (796)
  • jag (391)
  • metabyte (383)
  • arnaud (328)
  • jalateras (325)
  • dfrench (271)
  • venkaiah.k (214)

Show last 4 hrs - 12 hrs - 24 hrs

POLL

We are looking for more information to tailor our training to better meet the needs of our customers. Please indicate all options that apply.

I would like to attend specialized training from Intalio on BPM as it relates to my application area:

I would like to attend specialized training from Intalio on BPM as it relates to my job function:

I would like to attend specialized training from Intalio on BPM as it relates to my industry:

Login

Who's online?

MAIN arrow FORUMS
Intalio|BPMS Community Edition BPMN and Designer
Nasty behaviour of Designer (Data Mapper) (0 viewing) 
Go to bottom Post Reply Favoured: 0
TOPIC: Nasty behaviour of Designer (Data Mapper)
#16718
marcin.stefaniuk (User)
Fresh Boarder
User Offline Click here to see the profile of this user
Nasty behaviour of Designer (Data Mapper) 2 Months ago Karma: 0  
I found silent but nasty inconvenience in Designer. Services I've used are rather big - and most of them are nillable. When number of Maximum number of nillable elements generated param in Preferences -> Intalio|Designer -> BPEL Literal generation was too low Data mapper was unavailable. In .log there was only strange looking error (quoted below).

Code: :

 
!MESSAGE HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. 
!STACK 0
org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. 
    at com.sun.org.apache.xerces.internal.dom.ParentNode.internalInsertBefore(Unknown Source)
    at com.sun.org.apache.xerces.internal.dom.ParentNode.insertBefore(Unknown Source)
    at com.sun.org.apache.xerces.internal.dom.NodeImpl.appendChild(Unknown Source)
    at com.intalio.n3.designer.process.bpeldata.dependencies.objecttypes.prototypes.DomWrapperForDataObject.buildNode(DomWrapperForDataObject.java:711)
    at com.intalio.n3.designer.process.bpeldata.dependencies.objecttypes.prototypes.DomWrapperForDataObject.buildNode(DomWrapperForDataObject.java:870)
    at com.intalio.n3.designer.process.bpeldata.dependencies.objecttypes.prototypes.DomWrapperForDataObject.buildNode(DomWrapperForDataObject.java:870)
    at com.intalio.n3.designer.process.bpeldata.dependencies.objecttypes.prototypes.DomWrapperForDataObject.buildNode(DomWrapperForDataObject.java:870)
    at com.intalio.n3.designer.process.bpeldata.dependencies.objecttypes.prototypes.DomWrapperForDataObject.buildNode(DomWrapperForDataObject.java:870)
    at com.intalio.n3.designer.process.bpeldata.dependencies.objecttypes.prototypes.DomWrapperForDataObject.buildNode(DomWrapperForDataObject.java:870)
    at com.intalio.n3.designer.process.bpeldata.dependencies.objecttypes.prototypes.DomWrapperForDataObject.buildNode(DomWrapperForDataObject.java:870)
    at com.intalio.n3.designer.process.bpeldata.dependencies.objecttypes.prototypes.DomWrapperForDataObject.buildNode(DomWrapperForDataObject.java:870)
    at com.intalio.n3.designer.process.bpeldata.dependencies.objecttypes.prototypes.DomWrapperForDataObject.buildNode(DomWrapperForDataObject.java:870)
    at com.intalio.n3.designer.process.bpeldata.dependencies.objecttypes.prototypes.DomWrapperForDataObject.buildNode(DomWrapperForDataObject.java:870)
    at com.intalio.n3.designer.process.bpeldata.dependencies.objecttypes.prototypes.DomWrapperForDataObject.buildNode(DomWrapperForDataObject.java:870)
    at com.intalio.n3.designer.process.bpeldata.dependencies.objecttypes.prototypes.DomWrapperForDataObject.buildPrototype(DomWrapperForDataObject.java:419)
    at com.intalio.n3.designer.process.bpeldata.dependencies.objecttypes.prototypes.DomWrapperForDataObject.buildPrototypeWSDLMessagePart(DomWrapperForDataObject.java:138)
    at com.intalio.n3.designer.process.bpeldata.dependencies.objecttypes.impl.WSDLMessagePart.getPrototypeFragment(WSDLMessagePart.java:202)
    at com.intalio.n3.designer.process.bpeldata.declarations.bpel.DeclarationForPart.getPrototypeFragment(DeclarationForPart.java:188)
    at com.intalio.n3.designer.process.bpeldata.expressions.model.ExpressionUnitsController.<init>(ExpressionUnitsController.java:181)
    at com.intalio.n3.designer.process.bpeldata.expressions.model.ExpressionUnitsController.<init>(ExpressionUnitsController.java:144)
    at com.intalio.n3.designer.process.bpeldata.expressions.model.trees.ExpressionUnitsControllerWithPartnerEPR.<init>(ExpressionUnitsControllerWithPartnerEPR.java:44)
    at com.intalio.n3.designer.process.bpeldata.BPELDataAdapterFactory.buildExpressionUnitsController(BPELDataAdapterFactory.java:1071)
    at com.intalio.n3.designer.eclipse.views.mapper.MapperView.setModel(MapperView.java:578)
    at com.intalio.n3.designer.eclipse.views.mapper.MapperView.updateModel(MapperView.java:1720)
    at com.intalio.n3.designer.eclipse.views.mapper.MapperView$DirectSelectionListener.selectionChanged(MapperView.java:277)
    at org.eclipse.ui.internal.AbstractSelectionService.fireSelection(AbstractSelectionService.java:156)
    at org.eclipse.ui.internal.AbstractSelectionService$1.selectionChanged(AbstractSelectionService.java:62)
    at org.eclipse.gmf.runtime.diagram.ui.parts.DiagramGraphicalViewer.flushSelectionEvents(DiagramGraphicalViewer.java:269)
    at org.eclipse.gmf.runtime.diagram.ui.parts.DiagramGraphicalViewer$1.run(DiagramGraphicalViewer.java:247)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
    at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
    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:508)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1148)



When number of nillable elements was increased everything was working fine. I suppose in this case more accurate message should be shown.

Best regards
Marcin Stefaniuk
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
#16723
Antoine (Admin)
Admin
User Offline Click here to see the profile of this user
Re:Nasty behaviour of Designer (Data Mapper) 2 Months ago Karma: 28  
I'd be happy to test Designer with your schema, see if I can reproduce and fix the problem in a better way. My gutfeel is that your schema somehow triggered an exception related to the nillable elements. If you can attach it here, I will investigate.

Thanks,

Antoine
 
Report to moderator   Logged Logged  
 
Intalio, the Open Source BPMS company
www.intalio.com
  The administrator has disabled public write access.
#16727
marcin.stefaniuk (User)
Fresh Boarder
User Offline Click here to see the profile of this user
Re:Nasty behaviour of Designer (Data Mapper) 2 Months ago Karma: 0  
I cannot attach WSDL to my message (privacy policy). But I think that I can provide several facts that can help to identify a problem:

  • all services (including WSDL) are automagically generated using standard Weblogic ant tool

  • most of services are working without any modifications

  • only some of them are returning or accepting huge documents (most of elements are nillable, around 95%) and Data Mapper fails only in that case

  • I assume that when maximal number of nillable elements is created Designer tool try to handle this situation without success

  • originally I had different numbers in Maximum number of elements and attributes generated (100000) and Maximum number of nillable elements generated (10000) - equalling these fields (up to 100000) was the resolution in my case



I think that using simple WSDL defining service with 100 elements (99 nillable) and decreasing above parameters should reproduce similar situation.

Best regards
Marcin Stefaniuk
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
Go to top Post Reply
get the latest posts directly to your desktop