Our company moving our Open Source projects from present top.touk.pl host on github. It is a good moment to refresh knowledge why they can be useful and how run them.<\/p>\n
In this post I want to focus on projects associated with Apache ODE<\/a>. For somebody who is not familiar with this project: it is Orchestration Engine using BPEL as language to describe Business Projects. It can be used as web application deployed on Java EE container or as a Servicemix 3.x component.<\/p>\n <\/p>\n Available projects:<\/p>\n maven-ode-plugin<\/a><\/strong><\/p>\n This maven plugin allows you compile BPEL files with Apache ODE bpel compilator.<\/p>\n Maven pom.xml configuration<\/p>\n Following configuration will compile PrototypeCase.bpel file during maven compile phase:<\/p>\n odeUnitTests<\/a><\/strong><\/p>\n Quoting mail<\/a> of Maciek aka mpr on ode-dev mailing list:<\/p>\n In our project at touk we ended up having quite large & complex<\/p>\n processes. We found it difficult to do testing based e.g. on soapUI, as<\/p>\n we had to make many mock requests, responses and so on. We didn\u2019t find<\/p>\n any tool enabling testing single scopes, sequences or assigns, so I<\/p>\n developed our own.<\/p>\n How it works:<\/p>\n Testing is based on processes compiled to .cbp format. The base class<\/p>\n for tests is pl.touk.ode.scopeEvaluator.ActivityTest.<\/p>\n The test looks more or less like this:<\/p>\n Currently things like picks, invokes, receives, extVars (limited) are<\/p>\n supported. The config (e.g. process properties) can be read from<\/p>\n deploy.xml file (we use only jbi packaging). Simple examples are in<\/p>\n src\/test.<\/p>\n There is also simple expressionEvaluator, which enables quick testing of<\/p>\n xpath\/xquery read from process, also using defined variables.<\/p>\n ode-validator<\/a><\/strong><\/p>\n This is a command line tool for validating expressions inside bpel processes using Saxon SA (Schema Aware).<\/p>\n Usage:<\/p>\n \u00a0<\/p>\n FAQ<\/p>\n \u2013 I get errors \u201cno schema imported for xsd namespace\u201d.<\/p>\n This occurs if you declare variable in \u201celement=\u2019xsd:string'\u201d way. There\u2019s no element declaration in xsd namespace. So correct way is: \u201ctype=\u2019xsd:string'\u201d declaration.<\/p>\n \u2013 How to assign value to a complex type variable?<\/p>\n There\u2019s an extension for it, you should do: (ode is a standard ODE extensions namespace: xmlns:ode=\u201dhttp:\/\/www.apache.org\/ode\/type\/extension\u201d)<\/p>\n \u00a0<\/p>\n \u00a0<\/p>\n \u2013 I\u2019ve got problem while using schemas from subdirectories. They do not get imported.<\/p>\n In schema imports from inside subdirectory, currently there\u2019s no relative path resolution. So you need to provide full paths for schemas from subdirs.<\/p>\n...\r\n ...pl.touk.topmaven-ode-plugin1.3.0${project.build.directory}\/classes\/PrototypeCase.bpel${project.build.directory}\/classes\/\r\n false\r\n\r\n compile\r\n\r\n bpelc<\/pre>\n@Test\r\npublic void testAssign2() throws Exception {\r\n \/\/we set value of string variable a to 'first'\r\n addVariable(\"a\", \"first\");\r\n \/\/we run activity with name = 'sequence1'\r\n runEngine(\"sequence1\");\r\n \/\/we assert after running activity the variable a has expected value\r\n assertEquals(\"firstsecondthird\", getSimpleVariable(\"a\"));\r\n }<\/pre>\node-validator-1.0.0\/bpelc -od process-dir process-dir\/process.bpel<\/pre>\n
...\r\n\r\n...<\/pre>\n