A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_URI::$config is deprecated

Filename: core/URI.php

Line Number: 101

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Router::$uri is deprecated

Filename: core/Router.php

Line Number: 127

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$benchmark is deprecated

Filename: core/Controller.php

Line Number: 82

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$hooks is deprecated

Filename: core/Controller.php

Line Number: 82

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$config is deprecated

Filename: core/Controller.php

Line Number: 82

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$log is deprecated

Filename: core/Controller.php

Line Number: 82

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$utf8 is deprecated

Filename: core/Controller.php

Line Number: 82

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$uri is deprecated

Filename: core/Controller.php

Line Number: 82

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$exceptions is deprecated

Filename: core/Controller.php

Line Number: 82

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$router is deprecated

Filename: core/Controller.php

Line Number: 82

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$output is deprecated

Filename: core/Controller.php

Line Number: 82

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$security is deprecated

Filename: core/Controller.php

Line Number: 82

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$input is deprecated

Filename: core/Controller.php

Line Number: 82

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$lang is deprecated

Filename: core/Controller.php

Line Number: 82

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$db is deprecated

Filename: core/Loader.php

Line Number: 396

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_DB_mysqli_driver::$failover is deprecated

Filename: database/DB_driver.php

Line Number: 371

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on true

Filename: libraries/Email.php

Line Number: 978

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$email is deprecated

Filename: core/Loader.php

Line Number: 1283

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 295

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 169

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 238

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 318

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 359

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 282

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 289

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 304

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 314

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 315

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 375

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$session is deprecated

Filename: core/Loader.php

Line Number: 1283

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blogs::$user_model is deprecated

Filename: core/Loader.php

Line Number: 358

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$load is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$pgmodule is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$benchmark is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$hooks is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$config is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$log is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$utf8 is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$uri is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$exceptions is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$router is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$output is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$security is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$input is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$lang is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$db is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$email is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$session is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$user_model is deprecated

Filename: core/Loader.php

Line Number: 931

Backtrace:

File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view

File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once

webMethods Regular Expressions | Post Details - SKML Home Tuitions
webMethods Regular Expressions
Apr 17, 2013 08:53 2 Comments WebMethods Asadul

 

A regular expression is a text string that describes some set of strings. Regular expressions are a pattern-matching technique supported in a variety of tools and software but are most commonly known from UNIX tools such as grep, sed, vi and emacs. Using regular expressions (regex for short) you can determine if a string matches a specific pattern.
webMethods Integration Server provides regex support. The syntax and usage is described in the webMethods Developer User's Guide (Appendix D in version 4.6, Appendix B in 6.0).
This webMethods Ezine article addresses using regex patterns in:

  • The label property of a child step within a BRANCH
  • webMethods Query Language (WQL) statements

Built-in String Services

Regex in Labels

Using regular expressions can greatly simplify your BRANCH constructs. The regular expression in a label must be surrounded with slashes. As an example, consider the common task of needing to determine if a pipeline variable contains at least one non-space character. Without using regex the FLOW steps to accomplish this might look like this:

alt

Using a regular expression can greatly simplify the steps needed. The following FLOW steps accomplish this easily:

 alt

The following table provides a few regular expressions samples for common tasks.


alt

regex and WQL

WQL is the webMethods precursor to XQL. Both languages are supported by the query service (pub.xml:queryXMLNode in v6.0, pub.web:queryDocument in v4.6 and earlier). WQL supports using regex to specify a pattern-matching string to select members of an element array.
This facility is described in the Working with XML Documents document shipped with v6.0 and in the Developer User's Guide with v4.6 and earlier. From an example described in the webMethods documentation, the following query:

doc.bitterrootboards['*Pro Series*'].text

returns every bitterrootboards element that contains the string "Pro Series" anywhere within it. WQL coupled with regex provides significant power and flexibility in processing XML.

 

regex and Built-In String Services

There are two built-in services that support regex:

  1. pub.string:lookupTable
  2. pub.string:replace

The pub.string:lookupTable service can use a regular expression to perform a lookup on the table. It returns the first value in the table whose key matches the specified regex pattern.
The pub.string:replace service supports using a regular expression as the search string. For example post to strip leading zeroes from a number. The screen shot below is the results tab after running pub.string:replace.

alt


 

In this example, "+0000" in the inString is replaced by "+" as shown by the variable named value. The search string can be described as "look at the beginning of the string for a + followed by one or more zeroes." The search string uses these regex features:

  • The ^ specifies that the pattern must be at the start of the inString.
  • The + character has a special meaning in regex. For this pattern we want to use the + character literally. The escapes the + telling the regex engine to use + as a literal rather than a regex operator.
  • The 0 is used literally. The second + character is a regex operator indicating that the preceding element (in this case the character 0) can occur 1 or more times.

We can add some flexibility to Eric's regex example to support a optional leading + or - and keep it in the resulting value. The screen shot below again shows the results tab after running pub.string:replace with the indicated parameters. Note the differences in the searchString parameter in this example as compared to the first example.

 

alt


The search string in this second example can be described as "look at the beginning of the string for an optional + or - followed by one or more zeroes." This search string uses these regex features:

  • The ^ specifies that the pattern must be at the start of the inString.
  • The parentheses indicate a subexpression that can be used as a substitution variable in the replacement string. In this case, any leading + or - will be placed where $1 appears, so the resulting value will have the same leading sign as the input string. If there is no leading sign, then the resulting value will not have a leading sign.
  • The brackets indicate a character set. The set here is the + and the - characters. The \ escapes the + (since it is a regex operator character and we want to use it literally).
  • The ? is a regex operator which indicates that the preceding item can occur zero or one times. The preceding item in this case is a character set, so the pattern will match only if one of the characters from the set appears in inString.
  • The 0 is used literally. The second + is a regex operator indicating that the preceding element (in this case the character 0) can occur 1 or more times.

As you can see, just a few characters in a regular expression can do quite a bit of work. Any regular expression can be used to search for and replace substrings.
The best way to learn to use regular expressions is to play around with them. Run pub.string:replace directly in Developer to learn the basics and expand your regex abilities.


Example:

You can use regular expressions as the labels on your branch step even when evaluate labels is false.  A simple example is checking the http status values from a RESTful call:

  • Branch header->status
    • /^2[0-9][0-9]$/ (OK)
    • /^4[0-9][0-9]$/ (Non retry enabled error)
    • /^5[0-9][0-9]$/ (Retry enabled error)

Much easier than trying to list all combinations.

Here I am trying to Bran on a http status string which can in the range i) 200 - 299 ii) 400 - 499 and 500 - 599

Conclusion

Regular expressions are a powerful way to easily process strings and control process flow. While they can't do everything (e.g. using regex to try to trim whitespace from all elements in an XML string would be ill-advised) they can make many tasks a breeze.


Prev Next
About the Author
Topic Replies (2)
  1. 1
    idnkx user

    Raj Kumar

    For checking if a string contains a certain word e.g. 'Test' Try with [b]/Test/[/b] But don't anchor your pattern.

    1
    idnkx user

    Pavan

    Also you can use the below expression for checking null or empty values in a string: Set evaluate labels to true and use &#xva;r% = $null or &#xva;r% = --

Leave a Reply
Guest User

You might also like

Not sure whare to join tuition right for you?

Choose the right one for you.
Get the help of the experts and find a solution that best suits your needs.


Let`s Connect