Doorgaan naar hoofdcontent

Cordys BOP4: Some pitfalls

1 - Exposed webservices not WSDL compliant

During exposing of a BPM process as a WebService or of a database (WS-AppServer) i ran into the problem that the generated WSDL was nog conform the
implementation.
So when you run the webservice with a webservice client (for example soapUI) you get a response that is not compliant with the WSDL generated by Cordys BOP4.
This can be very ackward when using tools (for example thta generates JAX-WS) to generate the webservice client. In our case the XML response returned could
not be binded to the generated Java object. To circumvent this problem we adapted the WSDL file conform the implementation generated by BOP4 (CU9).

2 - Be aware when changing process message names

When you change the name of input- and/or output messages of a business process you have to be aware to change the data mapping inside the process and ALSO
the mappings that use this process.



 

 

 

 

 

 

 

 

3 - Spaces at the end are trimmed

I generated a webservice on a database table of type string and everything worked fine. Until a string was placed within a column that had spaces at the end.
When a query method was called the spaces were gone. In our case these spaces are very important.
A solution lies in a parameter within the generated implementation of the webservice. This is the preserveSpace="true" setting.




Notes


Ad 1 - This is solved within BOP4 CU10
Labels:

Reacties

Een reactie posten

Populaire posts van deze blog

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h
12 reacties
Meer lezen

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .
48 reacties
Meer lezen

Book review: Data Management at Scale (Piethein Strengholt)

 This blog is a review of the book "Data Management at Scale (See also at bol.com ) Data Management is a hot topic nowadays and this book does a fantastic job at adding value to this topic. It is a must read and one of the few technical books I finished reading in a weekend. The book gives a fantastic overview on how to implement a Data Mesh data architecture. The Data Mesh concept is explained by Martin Fowler here . The book is a good mix between conceptual and implementation architecture level. It gives a lot of examples of how this architecture at scale can work, for both small and big companies. It is practical and I used it to implement it at one of my customers. The book describes an architecture in which the focus is on the DIAL (Data- and Integration Access Layer).  On a high level the book covers the following topics: The key principles for data management at scale - Domain-Driven Design  - Domain Data Stores - Meta data management Ready Data Store The concept of servin
5 reacties
Meer lezen