verification checklist for 1.1.0| JBoss.org Content Archive (Read Only)

15. Re: verification checklist for 1.1.0

dpalmer Nov 7, 2013 6:13 AM (in response to kcbabo)

The following are also good on OSX:

rules-camel-cbr

demos/webapp-deploy (we should probably add a Readme.md for this one)

I have added a pull request that fixes soap-mtom.

By my reckoning the list of quickstarts that haven't been tested yet is:

camel-mail-binding

demos/multiApp

demos/policy-security-basic-propagate

demos/policy-security-cert

demos/policy-security-saml

demos/policy-security-wss-signencrypt

demos/policy-security-wss-username

16. Re: verification checklist for 1.1.0

mageshbk Nov 7, 2013 6:25 AM (in response to kcbabo)

OS
- Windows 7 professional
EAP
- 6.1.1 GA
Installation
- Bundle zip -
- Installer
  - Runtime only -
  - BPEL console -
Verify console works - shows application and metrics
- BPEL console - History Query does not show any process ids in the dropdown, after running bpel-service/loan-approval QS
- Admin Console -
Test domain mode deployment in EAP
Tests
- rest-binding - (both in standalone and domain modes)
- demo/orders -
- demo/helpdesk -
- demo/policy-security-basic -

17. Re: verification checklist for 1.1.0

dpalmer Nov 7, 2013 10:19 AM (in response to kcbabo)

demos/multiApp didn't work but I have fixes for it, see SWITCHYARD-1820

18. Re: verification checklist for 1.1.0

bfitzpat Nov 7, 2013 12:49 PM (in response to kcbabo)

Environment:

Windows 7

Installation:

EAP 6.1 final

SY runtime build: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/SwitchYard-Release/1051/

Following directions held in quickstart readme.md files

bean-service

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via SOAP request/response (per soapUI 3.6.1)

* runs via included "mvn exec:java" client

* undeploys (mvn jboss-as:undeploy)

bpel-service/jms_binding

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java" client

* undeploys (mvn jboss-as:undeploy)

bpel-service/loan_approval

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via SOAP request/response (per the two sample soap request messages, their responses, and soapUI 3.6.1)

* runs via included "mvn exec:java" client

* files are missing from location recommended in readme to perform the third version of the test - src/main/resources/wsdl/ does not exist, nor does src/test/resources/xml/soap-request.xml

* was able to create soapUI project from loanServicePT.wsdl (but not riskAsseessmentPT.wsdl), but failed with generated soap request:

<html><head><title>JBoss Web/7.2.0.Final-redhat-1 - JBWEB000064: Error report</title><style></style> </head><body><h1>JBWEB000065: HTTP Status 404 - /Quickstart_bpel_loan_approvalWS</h1><HR size="1" noshade="noshade"><p><b>JBWEB000309: type</b> JBWEB000067: Status report</p><p><b>JBWEB000068: message</b> <u>/Quickstart_bpel_loan_approvalWS</u></p><p><b>JBWEB000069: description</b> <u>JBWEB000124: The requested resource is not available.</u></p><HR size="1" noshade="noshade"><h3>JBoss Web/7.2.0.Final-redhat-1</h3></body></html>

* I expect some differences between pre-deploy and post-deploy wsdls

* undeploys (mvn jboss-as:undeploy)

bpel-service/say_hello

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java" client

* runs via SOAP request/response (per the sample soap request message, its response, and soapUI 3.6.1)

* files are missing from location recommended in readme to perform the third version of the test - src/main/resources/wsdl/ does not exist, nor does src/test/resources/xml/soap-request.xml

* was able to create soapUI project from SayHelloArtifacts.wsdl, but test failed with provided soap request:

<html><head><title>JBoss Web/7.2.0.Final-redhat-1 - JBWEB000064: Error report</title><style></style> </head><body><h1>JBWEB000065: HTTP Status 404 - /SayHelloProcess</h1><HR size="1" noshade="noshade"><p><b>JBWEB000309: type</b> JBWEB000067: Status report</p><p><b>JBWEB000068: message</b> <u>/SayHelloProcess</u></p><p><b>JBWEB000069: description</b> <u>JBWEB000124: The requested resource is not available.</u></p><HR size="1" noshade="noshade"><h3>JBoss Web/7.2.0.Final-redhat-1</h3></body></html>

* I expect some differences between pre-deploy and post-deploy wsdls

* undeploys (mvn jboss-as:undeploy)

bpel-service/simple_correlation

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java" client

* attempting to run via SOAP request/response got stuck when trying the goodbye request message

14:52:19,399 ERROR [org.riftsaw.engine.internal.BPELEngineImpl] (http-/127.0.0.1:8080-2) Timeout or execution error when waiting for response to MEX {MyRoleMex#hqejbhcnphr8qh8q422bpa [Client hqejbhcnphr8qh8q422bp9] calling {urn:switchyard-quickstart:bpel-simple-correlation:0.1.0}simpleCorrelationService.goodbye(...)} java.util.concurrent.TimeoutException: Message exchange org.apache.ode.bpel.engin

e.MyRoleMessageExchangeImpl$ResponseFuture@1599ac9 timed out(120000 ms) when waiting for a response!: java.util.concurrent.TimeoutException: Message exchange org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl$ResponseFuture@1599ac9 timed out(120000 ms) when waiting for a response!

at org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl$ResponseFuture.get(MyRoleMessageExchangeImpl.java:257) [riftsaw-bpel-runtime-3.1.0.Final.jar:]

at org.riftsaw.engine.internal.BPELEngineImpl.invoke(BPELEngineImpl.java:857) [engine-3.1.1.Final.jar:3.1.1.Final]

at org.switchyard.component.bpel.riftsaw.RiftsawBPELExchangeHandler.handleMessage(RiftsawBPELExchangeHandler.java:276) [switchyard-component-bpel-1.1.0.CR1.jar:1.1.0.CR1]

at org.switchyard.bus.camel.processors.ProviderProcessor.process(ProviderProcessor.java:29) [switchyard-bus-camel-1.1.0.CR1.jar:1.1.0.CR1]

at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61) [camel-core-2.10.0.jar:2.10.0]

at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) [camel-core-2.10.0.jar:2.10.0]

at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) [camel-core-2.10.0.jar:2.10.0]

at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) [camel-core-2.10.0.jar:2.10.0]

...

at org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:360) [camel-core-2.10.0.jar:2.10.0]

at org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:331) [camel-core-2.10.0.jar:2.10.0]

at org.apache.camel.impl.ProducerCache.doInProducer(ProducerCache.java:227) [camel-core-2.10.0.jar:2.10.0]

at org.apache.camel.impl.ProducerCache.sendExchange(ProducerCache.java:331) [camel-core-2.10.0.jar:2.10.0]

at org.apache.camel.impl.ProducerCache.send(ProducerCache.java:153) [camel-core-2.10.0.jar:2.10.0]

at org.apache.camel.impl.DefaultProducerTemplate.send(DefaultProducerTemplate.java:106) [camel-core-2.10.0.jar:2.10.0]

at org.apache.camel.impl.DefaultProducerTemplate.send(DefaultProducerTemplate.java:92) [camel-core-2.10.0.jar:2.10.0]

at org.switchyard.bus.camel.ExchangeDispatcher.dispatch(ExchangeDispatcher.java:87) [switchyard-bus-camel-1.1.0.CR1.jar:1.1.0.CR1]

at org.switchyard.bus.camel.CamelExchange.sendInternal(CamelExchange.java:234) [switchyard-bus-camel-1.1.0.CR1.jar:1.1.0.CR1]

... 42 more

Caused by: java.lang.Exception: Timeout or execution error when waiting for response to MEX {MyRoleMex#hqejbhcnphr8qh8q422bpd [Client hqejbhcnphr8qh8q422bpc] calling {urn:switchyard-quickstart:bpel-simple-correlation:0.1.0}simpleCorrelationService.goodbye(...)} java.util.concurrent.TimeoutException: Message exchange org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl$ResponseFuture@163485c timed

out(120000 ms) when waiting for a response!

at org.riftsaw.engine.internal.BPELEngineImpl.invoke(BPELEngineImpl.java:862) [engine-3.1.1.Final.jar:3.1.1.Final]

at org.switchyard.component.bpel.riftsaw.RiftsawBPELExchangeHandler.handleMessage(RiftsawBPELExchangeHandler.java:276) [switchyard-component-bpel-1.1.0.CR1.jar:1.1.0.CR1]

... 110 more

* tried uneploy/restart server/redeploy and got same issue

* then I tried to submit a message to Hello and all worked fine

* may want to clean up this example so something meaningful comes back if they try to submit a message the wrong way - or use that as an example of how to handle fault/error conditions

* but I ran into an entertaining state where even deploying the project didn't clean up the server

bpm-service

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via SOAP request/response (per soapUI 3.6.1)

* runs via included "mvn exec:java" client

* able to generate soapUI test invocation from src/main/resources/wsdl but unable to test with it - I expect some differences between pre-deploy and post-deploy wsdls

* undeploys (mvn jboss-as:undeploy)

camel-amqp-service

* builds (mvn clean install)

camel-binding

* builds (mvn clean install)

* tests (mvn -Dtest=CamelBindingTest test)

camel-bus-cdi

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* undeploys (mvn jboss-as:undeploy)

camel-ftp-server

* no ftp server to test with

camel-jaxb

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java" client

* undeploys (mvn jboss-as:undeploy)

camel-jms-binding

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java" client

* undeploys (mvn jboss-as:undeploy)

camel-jpa-binding

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* never saw any console output from entities stored in database - is there a missing step?

* guessed and ran mvn exec:java and saw "Hello there Captain Crunch :-)"

* undeploys (mvn jboss-as:undeploy)

camel-mail-binding

* no e-mail server to test with

camel-netty-binding

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java -Pudp" client

* undeploys (mvn jboss-as:undeploy)

camel-quartz-binding

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* undeploys (mvn jboss-as:undeploy)

camel-binding

* builds (mvn clean install)

* directions miss the deploy step??

* running the test fails (mvn -Dtest=CamelServiceTest test)

* undeploys (mvn jboss-as:undeploy)

camel-soap-proxy

* builds (mvn clean install)

* deployed RevereService.war

* deploys (mvn jboss-as:deploy)

* tested ReverseService via soapUI 3.6.1

* runs via included "mvn exec:java" client

* undeploys (mvn jboss-as:undeploy)

camel-sql-binding

* didn't create h2 database

19. Re: verification checklist for 1.1.0

bfitzpat Nov 7, 2013 6:26 PM (in response to kcbabo)

Testing round 2

Environment:

Windows 7

Installation:

EAP 6.1 final

SY runtime build: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/SwitchYard-Release/1051/

Following directions held in quickstart readme.md files

[quickstart]

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via SOAP request/response (per soapUI 3.6.1)

* runs via included "mvn exec:java" client

* undeploys (mvn jboss-as:undeploy)

http-binding

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java -Dexec.args="vineyard"" client

* undeploys (mvn jboss-as:undeploy)

remote-invoker

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java" client

* undeploys (mvn jboss-as:undeploy)

rest-binding

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java -Dexec.args="new"" client

* get some warnings in the runtime console (mostly: "15:02:45,923 WARN [org.switchyard.component.resteasy] (http-/127.0.0.1:8080-3)SWITCHYARD037600: Default RESTEasy Message Composer doesn't handle multiple input parameters."):

15:02:45,901 INFO [stdout] (http-/127.0.0.1:8080-3) ++++++ getItem 1

15:02:45,901 INFO [org.switchyard.quickstarts.rest.binding.WarehouseService] (http-/127.0.0.1:8080-3) Added item 1 with name Hydrogen Atom - No, we are not kidding!

15:02:45,912 WARN [org.switchyard.component.resteasy] (http-/127.0.0.1:8080-3)SWITCHYARD037600: Default RESTEasy Message Composer doesn't handle multiple input parameters.

15:02:45,914 INFO [stdout] (http-/127.0.0.1:8080-3) ++++++ getItem 2

15:02:45,915 INFO [org.switchyard.quickstarts.rest.binding.WarehouseService] (http-/127.0.0.1:8080-3) Added item 2 with name Handcrafted Copper Plate

15:02:45,923 WARN [org.switchyard.component.resteasy] (http-/127.0.0.1:8080-3)SWITCHYARD037600: Default RESTEasy Message Composer doesn't handle multiple input parameters.

15:02:45,924 INFO [stdout] (http-/127.0.0.1:8080-3) ++++++ getItem 3

15:02:45,925 INFO [org.switchyard.quickstarts.rest.binding.WarehouseService] (http-/127.0.0.1:8080-3) Added item 3 with name Einstein's Bust - Talks about your future

15:02:45,932 WARN [org.switchyard.component.resteasy] (http-/127.0.0.1:8080-3)SWITCHYARD037600: Default RESTEasy Message Composer doesn't handle multiple input parameters.

15:02:45,975 INFO [stdout] (http-/127.0.0.1:8080-3) ++++++ getItem 4

15:02:45,976 INFO [org.switchyard.quickstarts.rest.binding.WarehouseService] (http-/127.0.0.1:8080-3) Added item 4 with name Time Machine

15:02:45,988 INFO [org.switchyard.quickstarts.rest.binding.OrderService] (http-/127.0.0.1:8080-2) Creating new Order with no: 1

* runs via included "mvn exec:java -Dexec.args="add 1 3 10"" client

* runs via included "mvn exec:java -Dexec.args="add 1 4 1"" client

* runs via included "mvn exec:java -Dexec.args="del 1 3"" client

* runs via included "mvn exec:java -Dexec.args="get 1"" client

* undeploys (mvn jboss-as:undeploy)

rules-camel-cbr

* builds (mvn clean install)

* runs via included test "mvn -Dtest=RulesCamelCBRTest test"

rules-interview

* builds (mvn clean install)

* test runs (mvn -Dtest=RulesInterviewTest test)

* test runs (mvn -Dtest=WebServiceTest test)

rules-interview-container

* builds (mvn clean install)

* test runs (mvn -Dtest=RulesInterviewTest test)

* test runs (mvn -Dtest=WebServiceTest test)

rules-interview-dtable (no results displayed during tests)

* builds (mvn clean install)

* test runs (mvn -Dtest=RulesInterviewTest test) - did not see any results

* test runs (mvn -Dtest=WebServiceTest test) - did not see any results

soap-addressing

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java -Dexec.args="Boeing 10"" client

* undeploys (mvn jboss-as:undeploy)

soap-attachment

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java" client

* undeploys (mvn jboss-as:undeploy)

soap-binding-rpc

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java -Dexec.args=Einstein" client

* undeploys (mvn jboss-as:undeploy)

soap-mtom

* builds (mvn clean install) - FAILS

transform-jaxb

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java" client

* undeploys (mvn jboss-as:undeploy)

transform-json

* builds (mvn clean install)

* tests via included "mvn -Dtest=JsonTransformationTest test"

transform-smooks

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* tests via included "mvn -Dtest=ServiceTransformationTest test"

* undeploys (mvn jboss-as:undeploy)

transform-xslt

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java" client

* undeploys (mvn jboss-as:undeploy)

validate-xml

* builds (mvn clean install)

* deploys (mvn jboss-as:deploy)

* runs via included "mvn exec:java" client

* tested with included soap requests via soapUI - all worked as described

* undeploys (mvn jboss-as:undeploy)

20. Re: verification checklist for 1.1.0

dpalmer Nov 8, 2013 5:43 AM (in response to kcbabo)

Tested fine today:

demos/policy-security-basic-propagate

demos/policy-security-cert

demos/policy-security-saml

demos/policy-security-wss-signencrypt

demos/policy-security-wss-username

I think that means that the only quick start that hasn't been tested is camel-mail-binding.

21. Re: Re: verification checklist for 1.1.0

tcunning Nov 9, 2013 12:13 AM (in response to dpalmer)

I took a shot at camel-mail-binding. I managed to get the imap portion working okay, but I haven't gotten the smtp portion working. I have a postfix gmail relay working on my box and can reliably send mail from the command line, and I don't see anything happening in /var/log/mail.log after the quickstart consumes the imap messages. It just looks like the mail producer isn't firing, but I don't see any errors in the console log or in the mail.log. I may be doing something wrong here though.

Here's what I used for my smtp settings :

        <reference multiplicity="1..1" name="OutgoingPrintService" promote="PrintService/OutgoingPrintService">
            <mail:binding.mail xmlns:mail="urn:switchyard-component-camel-mail:config:1.0" secure="true">
                <mail:host>localhost</mail:host>
                <mail:username>switchyardtest</mail:username>
                <mail:produce>
                    <mail:subject>Forwarded message</mail:subject>
                    <mail:from>switchyardtest@gmail.com</mail:from>
                    <mail:to>tomcunningham@thecoolestdomainever.com</mail:to>
                </mail:produce>
            </mail:binding.mail>
        </reference>

I changed the email address I'm sending to, but you get the point.

Also logged https://issues.jboss.org/browse/SWITCHYARD-1827 - the Readme.md doesn't have the right location of the switchyard.xml file and it might be better if we just assumed gmail.com as an example.

22. Re: verification checklist for 1.1.0

kcbabo Nov 9, 2013 8:54 AM (in response to tcunning)

Tom - can you try with message trace enabled and with org.apache.camel logging set to DEBUG?

23. Re: Re: verification checklist for 1.1.0

tcunning Nov 10, 2013 10:41 PM (in response to kcbabo)

Attaching the message trace.

messagetrace.log.zip 3.5 KB

24. Re: Re: Re: verification checklist for 1.1.0

tcunning Nov 12, 2013 3:55 PM (in response to tcunning)

Still not sure why I couldn't get it work using localhost and the gmail relay, but I got it working using the following settings :

            <mail:binding.mail xmlns:mail="urn:switchyard-component-camel-mail:config:1.0" secure="true">
                <mail:host>smtp.gmail.com</mail:host>
                <mail:port>465</mail:port>
                <mail:username>switchyardtest2@gmail.com</mail:username>
                <mail:password>PASSWORDREMOVED</mail:password>
                <mail:produce>
                    <mail:subject>Forwarded message</mail:subject>
                    <mail:from>switchyardtest2@gmail.com</mail:from>
                    <mail:to>switchyardtest@gmail.com</mail:to>
                </mail:produce>
            </mail:binding.mail>

25. Re: Re: verification checklist for 1.1.0

mageshbk Nov 13, 2013 9:04 AM (in response to mageshbk)

Gary says about the BPEL console:

Hi Magesh

I think can be resolved by refreshing the browser - I think its a caching issue. Could you confirm, and raise a BZ.

Thanks Gary! It works after refreshing the browser.

26. Re: Re: Re: verification checklist for 1.1.0

kcbabo Nov 18, 2013 7:02 PM (in response to mageshbk)

Final staged artifacts can be found here:

http://downloads.jboss.org/switchyard/staging/switchyard-1.1.0.Final-EAP6.1.Alpha.zip

http://downloads.jboss.org/switchyard/staging/switchyard-1.1.0.Final-EAP6.1.GA.zip

http://downloads.jboss.org/switchyard/staging/switchyard-installer-1.1.0.Final.zip

http://downloads.jboss.org/switchyard/staging/switchyard-tools-1.1.0.Final.zip

In order to build and test quickstarts, you'll need to add the staging repository in JBoss Nexus in your settings.xml. You can either add the repository as another repository entry or configure it as a mirror. Here's how to configure it as a mirror:

<mirrors>
    <mirror>
        <id>jboss-staging-repository-group</id>
        <mirrorOf>jboss-public-repository-group</mirrorOf>
        <name>JBoss.org Staging Repository Group</name>
        <url>https://repository.jboss.org/nexus/content/groups/staging/</url>
     </mirror>
</mirrors>

Note that I have it mirror "jboss-public-repository-group" instead of "*". Just make sure that the repository you have defined for JBoss Nexus has the id "jboss-public-repository-group" and you'll be fine.

<repositories> 
     <repository> 
        <id>jboss-public-repository-group</id> 
        <name>JBoss Public Maven Repository Group</name> 
        <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url> 
        <layout>default</layout> 
        <releases> 
          <enabled>true</enabled> 
          <updatePolicy>never</updatePolicy> 
        </releases> 
        <snapshots> 
          <enabled>true</enabled> 
          <updatePolicy>never</updatePolicy> 
        </snapshots> 
     </repository> 
</repositories>

27. Re: verification checklist for 1.1.0

igarashitm Nov 19, 2013 5:04 AM (in response to kcbabo)

EAP6.1 + SY-1.1.0.Final installer works fine for me on Fedora19. Verified all the JCA quickstarts wait for the RAR deployment (SWITCHYARD-1789). AS7 console looks cool as well - it showed bindings and transformers detail, and could get service metrics.

28. Re: verification checklist for 1.1.0

dpalmer Nov 19, 2013 8:51 AM (in response to kcbabo)

EAP6.1 + SY-1.1.0.Final looks good on OSX too. The following quick starts are good too:

bean-service

bpel-service/jms_binding

bpel-service/loan_approval

bpel-service/say_hello

bpel-service/simple_correlation

bpm-service

camel-amqp-binding

camel-binding

camel-bus-cdi

camel-ftp-binding

camel-jaxb

camel-jms-binding

camel-jpa-binding

camel-netty-binding

camel-quartz-binding

camel-service

camel-soap-proxy

camel-sql-binding

http-binding

remote-invoker

rest-binding

rules-camel-cbr

rules-interview

rules-interview-container

rules-interview-dtable

soap-addressing

soap-attachment

soap-binding-rpc

transform-jaxb

transform-json

transform-smooks

transform-xslt

validate-xml

soap-mtom - works but requires -DskipTests=true

29. Re: verification checklist for 1.1.0

mageshbk Nov 19, 2013 10:12 AM (in response to kcbabo)

Windows:

6.1.0.Alpha, 6.1.0.GA, 6.1.1 - installer + zip + console + demos/orders

Subtle point is that the processing time in 6.1.1 of the QS is +1 sec more from 6.1.0

regards,

Magesh