Sahan's Blog

Android HttpUrlConnection Disable default content encoding in gzip

2015-06-04T12:00:00.001+05:00

At present i have came across a scenario that our ESB is not responding to gzip format content encoded requests. Though ESB successfully call back end service after decoding these gzip requests originated from android apps which use HttpUrlConnection, ESB is not capable of respond the request after backend service successfully hand the response to ESB

Neither web nor Google helped me to understand how the default gzip encoding stops.

And then it came to my mind. Just set “Content-Encoding” to “identity” and you are done.

HttpURLConnection con = (HttpURLConnection) url.openConnection();

con.setRequestProperty(“Content-Encoding”, “identity”);

con.setRequestProperty(“Accept-Encoding”, “identity”);

http://ift.tt/eA8V8J June 04, 2015 at 12:18PM

Still not using Maven ? Then here is some dependancy tips

2014-09-26T06:19:00.000+05:00

AXIS2 CLIENT

   axis2-xmlbeans-1.6.2
   axis2-transport-http-1.6.2
   axis2-transport-local-1.6.2
   axis2-adb-1.6.2
   axis2-kernel-1.6.2
   axiom-api-1.2.13
   axiom-impl-1.2.13
   neethi-3.0.2
   XmlSchema-1.4.7
   httpcore-4.0
   mail-1.4
   commons-httpclient-3.1
   commons-codec-1.3
   commons-logging-1.1.1
   wsdl4j-1.6.2

JAX-WS
    jaxb-impl.jar
    jaxws-api.jar
    jaxws-rt.jar
    gmbal-api-only.jar
    management-api.jar
    stax-ex.jar
    streambuffer.jar
    policy.jar
   ha-api.jar
   jaxb-core.jar

JERSEY
   asm-3.1.jar
   jackson-core-asl-1.9.2.jar
   jackson-jaxrs-1.9.2.jar
   jackson-mapper-asl-1.9.2.jar
   jackson-xc-1.9.2.jar
   jersey-client-1.17.1.jar
   jersey-core-1.17.1.jar
   jersey-json-1.17.1.jar
   jersey-server-1.17.1.jar
   jersey-servlet-1.17.1.jar
   jettison-1.1.jar
   jsr311-api-1.1.1.jar

LOG4J
   log4j-1.2.17.jar

STRUTS 2
   commons-fileupload-x.y.z.jar
   commons-io-x.y.z.jar
   commons-lang-x.y.jar
   commons-logging-x.y.z.jar
   commons-logging-api-x.y.jar
   freemarker-x.y.z.jar
   javassist-.xy.z.GA
   ognl-x.y.z.jar
   struts2-core-x.y.z.jar
   xwork-core.x.y.z.jar
   commons-lang3-3.1.jar

OPEN SAML 2.6
   serializer-2.10.0
   xalan-2.7.1
   xercesImpl-2.10.0
   xml-apis-2.10.0
   xmltooling-1.4.1
   xmlsec-1.5.6
   slf4j-api-1.7.5
   openws-1.5.1
   opensaml-2.6.1
   joda-time-2.2
   esapi-2.0.1
   commons-lang-2.6

HIBERNATE 4.1
   commons-collections-3.2.1.jar
   antlr-2.7.7.jar
    commons-lang3-3.1.jar
    commons-logging-1.1.3.jar
    dom4j-1.6.1.jar
    hibernate-commons-annotations-4.0.1.Final.jar
    hibernate-core-4.2.0.Final.jar
    hibernate-jpa-2.0-api-1.0.1.Final.jar
    javassist-3.15.0-GA.jar
    jboss-logging-3.1.0.GA.jar
    jboss-transaction-api_1.1_spec-1.0.0.Final.jar

JBOSS - java.lang.NoSuchMethodError: org.jboss.logmanager.LogContext.getAttachment

2014-09-23T07:13:00.000+05:00

I came through below error while i was trying to use newer version of hibernate with jboss 5.1.2 EAP. The reason for this is with the classloader. Even though we created a jboss-classloading.xml file and instruct jboss to give priority to our classloader, it still try to pick jboss logging from server class loader than the jar inside war file.

Caused by: java.lang.NoSuchMethodError: org.jboss.logmanager.LogContext.getAttachment(Ljava/lang/String;Lorg/jboss/logmanager/Logger$AttachmentKey;)Ljava/lang/Object;

  at org.jboss.logging.JBossLogManagerProvider.doGetLogger(JBossLogManagerProvider.java:52)

  at org.jboss.logging.JBossLogManagerProvider.getLogger(JBossLogManagerProvider.java:47)

  at org.jboss.logging.Logger.getLogger(Logger.java:2164)

  at org.jboss.logging.Logger.getMessageLogger(Logger.java:2263)

  at org.jboss.logging.Logger.getMessageLogger(Logger.java:2215)

So how to over come this is as follow.

1. Download the zip from here.

2. Unzip it and run ant in the project’s root folder.

3. Copy the resulting .jar in the dist directory to $JBOSS_HOME/server/$PROFILE/deployers.

4. Create a file named jboss-classloading.xml and place it in your deployment’s WEB-INF or META-INF folders with the following contents:

<classloading xmlns="urn:jboss:classloading:1.0"

              domain="MyDeploymentDomain"

              parent-domain="NoHibernateNoJBLoggingDomain"

              parent-first="false"

              export-all="NON_EMPTY"

              import-all="true">

</classloading>

The set of packages filtered from your deployment is defined in NoHibernateNoJBLoggingDomain.jar at META-INF/jboss-beans.xml. See below for the default contents of this file:

<?xml version="1.0" encoding="UTF-8"?>

<deployment xmlns="urn:jboss:bean-deployer:2.0">

   <bean name="NoHibernateNoJBLoggingDomain" class="com.jboss.examples.classloader.FilteredDefaultDomain">

       <property name="domainName">NoHibernateNoJBLoggingDomain</property>

       <property name="filterPackages">org.hibernate,org.jboss.logmanager</property>

   </bean>

</deployment>

Now You are good to go!!!

iOS - short note, how to change view of tabs in UiTabBarController

2014-08-28T02:27:00.000+05:00

for (UINavigationController * nav in self.tabBarController.viewControllers) {

[nav.tabBarItem setTitleTextAttributes:[NSDictionary dictionaryWithObjectsAndKeys:

[UIColor grayColor],

NSForegroundColorAttributeName,

[UIFont systemFontOfSize:12], NSFontAttributeName,

nil]

forState:UIControlStateNormal];

[nav.tabBarItem setTitleTextAttributes:[NSDictionary dictionaryWithObjectsAndKeys:

[UIColor colorWithRed:0.0 green:122/255.0 blue:1.0 alpha:1], NSForegroundColorAttributeName,

[UIFont systemFontOfSize:14], NSFontAttributeName,

nil]

forState:UIControlStateSelected];

}

How to force change jboss class loader method 2

2014-08-04T10:54:00.000+05:00

In my previous post there is the first method where you can force jboss to isolate class loader of your web app from server class loader. Here what happen is before adding jars in server classpath, jboss will search jars in your web app classpath. If matching jars or duplicating jars found jboss will give priority to the jars found in your web app’s classpath.

So to achieve this the first method is create an entry in jboss-web.xml which is the jboss specific deployment descriptor. The second method is creating a separate xml file “jboss-classloading.xml” in your app’s “WEB-INF” folder and add the class loading instructions in that file. An example is given below.

***** parent daomain is optional.

JBOSS EAP 5.1.2 & Sun Metro JAX-WS

2014-08-04T04:48:00.000+05:00

Jboss does have their own web service implementation which is JBossWS-CXF, based out of Apache CXF. But if you are into JAX-WS metro stack you can simply use it with jboss.

1. Overide the class loader to load SUN Metro stack instead jboss supplied jax-ws version.

create “jboss-web.xml” file in “WEB-INF” folder with following content.

<?xml version=”1.0” encoding=”UTF-8”?>
<jboss-web>
   <context-root>/MyApp</context-root>
   <class-loading java2ClassLoadingCompliance=”false”>
       <loader-repository>
           org.myapp:loader=MyApp.war
           <loader-repository-config>
               java2ParentDelegation=false
           </loader-repository-config>
       </loader-repository>
   </class-loading>
</jboss-web>

2. Add WSServletContextListener listner to web.xml file

<listener>
<listener-class>com.sun.xml.ws.transport.http.servlet.WSServletContextListener</listener-class>
</listener>

3. Add servlet and servlet mapping for WSServlet

<servlet>
    <servlet-name>WSServlet</servlet-name>
    <servlet-class>
           com.sun.xml.ws.transport.http.servlet.WSServlet
        </servlet-class>
    <load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
    <servlet-name>WSServlet</servlet-name>
    <url-pattern>/*</url-pattern>
   <!— <url-pattern>/services/*</url-pattern> —>
</servlet-mapping>

You may now get your web service not only work but dynamic WSDL creation also working.

WSO2 IS SAML SSO using openSAML java library

2014-07-23T03:28:00.000+05:00

In this blog post i will explain how to write a sample SSO service provider code using wso2is as the identity provider and openSAML as the supporting library to create SAML request.

First download the wso2IS from [1] and openSAML release from [2]. Then startup the wso2is. Create a new java web application project and import below jars from opensaml lib and lib/endorsed folders.

serializer-2.10.0
   xalan-2.7.1
   xercesImpl-2.10.0
   xml-apis-2.10.0
   xmltooling-1.4.1
   xmlsec-1.5.6
   slf4j-api-1.7.5
   openws-1.5.1
   opensaml-2.6.1
   joda-time-2.2
   esapi-2.0.1
   commons-lang-2.6

Also include “axiom-api.jar” from apache axis project which has the UIDGenerator.java class.

Lets take our service provider name is “test.com” & our consumer landing page is “http://localhost:8080/test.com/home.jsp”. (You have to register a new service provider with above fields in wso2 identity server. To do so please refer [3] )

You can use below code to sent login & logout saml requests.

import java.io.ByteArrayInputStream;
import java.io.ByteArrayOutputStream;
import java.io.IOException;
import java.io.StringWriter;
import java.net.URLEncoder;
import java.util.HashMap;
import java.util.Iterator;
import java.util.List;
import java.util.Map;
import java.util.Random;
import java.util.zip.Deflater;
import java.util.zip.DeflaterOutputStream;

import javax.xml.namespace.QName;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.ParserConfigurationException;

import org.joda.time.DateTime;
import org.opensaml.Configuration;
import org.opensaml.DefaultBootstrap;
import org.opensaml.common.SAMLVersion;
import org.opensaml.saml2.core.Assertion;
import org.opensaml.saml2.core.Attribute;
import org.opensaml.saml2.core.AttributeStatement;
import org.opensaml.saml2.core.AuthnContextClassRef;
import org.opensaml.saml2.core.AuthnContextComparisonTypeEnumeration;
import org.opensaml.saml2.core.AuthnRequest;
import org.opensaml.saml2.core.Issuer;
import org.opensaml.saml2.core.LogoutRequest;
import org.opensaml.saml2.core.NameID;
import org.opensaml.saml2.core.NameIDPolicy;
import org.opensaml.saml2.core.RequestAbstractType;
import org.opensaml.saml2.core.RequestedAuthnContext;
import org.opensaml.saml2.core.Response;
import org.opensaml.saml2.core.SessionIndex;
import org.opensaml.saml2.core.impl.AuthnContextClassRefBuilder;
import org.opensaml.saml2.core.impl.AuthnRequestBuilder;
import org.opensaml.saml2.core.impl.IssuerBuilder;
import org.opensaml.saml2.core.impl.LogoutRequestBuilder;
import org.opensaml.saml2.core.impl.NameIDBuilder;
import org.opensaml.saml2.core.impl.NameIDPolicyBuilder;
import org.opensaml.saml2.core.impl.RequestedAuthnContextBuilder;
import org.opensaml.saml2.core.impl.SessionIndexBuilder;
import org.opensaml.xml.ConfigurationException;
import org.opensaml.xml.XMLObject;
import org.opensaml.xml.XMLObjectBuilder;
import org.opensaml.xml.XMLObjectBuilderFactory;
import org.opensaml.xml.io.Marshaller;
import org.opensaml.xml.io.MarshallingException;
import org.opensaml.xml.io.Unmarshaller;
import org.opensaml.xml.io.UnmarshallerFactory;
import org.opensaml.xml.io.UnmarshallingException;
import org.opensaml.xml.util.Base64;
import org.opensaml.xml.util.XMLHelper;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.xml.sax.SAXException;

import com.opensymphony.xwork2.util.logging.Logger;
import com.opensymphony.xwork2.util.logging.LoggerFactory;

public class SAMLConsumer {

   private static final Logger logger = LoggerFactory.getLogger(SAMLConsumer.class);
   private static boolean isBootstraped = false;

   private static final String ISSUER_URL = “test.com”;
   private static final String CONSUMER_URL = “http://localhost:8080/test.com/home.jsp”;

   private static final String NAME_SPACE_URI_ISSUER = “urn:oasis:names:tc:SAML:2.0:assertion”;
   private static final String NAME_SPACE_URI_AUTH = “urn:oasis:names:tc:SAML:2.0:protocol”;
   private static final String SAML_TRANSPORT_TYPE_PWD_PROTECTED = “urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport”;
   private static final String SAML_TRANSPORT_PROTOCOL_BINDING = “urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST”;

   private static final String LOCAL_NAME_ISSUER = “Issuer”;
   private static final String LOCAL_NAME_AUTHRQ = “AuthnRequest”;
   private static final String NAME_SPACE_PREFIX = “samlp”;
   private static final String AUTH_CNTXT_REF = “AuthnContextClassRef”;
   private static final String SAML = “saml”;

   public static String buildLoginRequest() throws IllegalArgumentException, SecurityException, IllegalAccessException, NoSuchFieldException, MarshallingException, IOException {
       logger.info(“started”);

       IssuerBuilder issuerBuilder = new IssuerBuilder();
       Issuer issuer = issuerBuilder.buildObject(NAME_SPACE_URI_ISSUER, LOCAL_NAME_ISSUER, “samlp”);
       issuer.setValue(ISSUER_URL);

       NameIDPolicyBuilder nameIdPolicyBuilder = new NameIDPolicyBuilder();
       NameIDPolicy nameIdPolicy = nameIdPolicyBuilder.buildObject();
       nameIdPolicy.setFormat(“urn:oasis:names:tc:SAML:2.0:nameid-format:persistent”);
       nameIdPolicy.setSPNameQualifier(“Isser”);
       nameIdPolicy.setAllowCreate(new Boolean(true));

       AuthnContextClassRefBuilder authnContextClassRefBuilder = new AuthnContextClassRefBuilder();
       AuthnContextClassRef authnContextClassRef =
                                                    authnContextClassRefBuilder.buildObject(NAME_SPACE_URI_ISSUER,
                                                           AUTH_CNTXT_REF, SAML);
       authnContextClassRef.setAuthnContextClassRef(SAML_TRANSPORT_TYPE_PWD_PROTECTED);

       RequestedAuthnContextBuilder requestedAuthnContextBuilder =
                                                       new RequestedAuthnContextBuilder();
       RequestedAuthnContext requestedAuthnContext = requestedAuthnContextBuilder.buildObject();
       requestedAuthnContext.setComparison(AuthnContextComparisonTypeEnumeration.EXACT);
       requestedAuthnContext.getAuthnContextClassRefs().add(authnContextClassRef);

       DateTime issueInstant = new DateTime();
       AuthnRequestBuilder authnRequestBuilder = new AuthnRequestBuilder();
       AuthnRequest authnRequest = authnRequestBuilder.buildObject(NAME_SPACE_URI_AUTH, LOCAL_NAME_AUTHRQ, NAME_SPACE_PREFIX);
       authnRequest.setForceAuthn(new Boolean(false));
       authnRequest.setIsPassive(new Boolean(false));
       authnRequest.setIssueInstant(issueInstant);
       authnRequest.setProtocolBinding(SAML_TRANSPORT_PROTOCOL_BINDING);
       authnRequest.setAssertionConsumerServiceURL(CONSUMER_URL);
       authnRequest.setIssuer(issuer);
       authnRequest.setNameIDPolicy(nameIdPolicy);
       authnRequest.setRequestedAuthnContext(requestedAuthnContext);

       String authReqRandomId = Integer.toHexString(new Double(Math.random()).intValue());

       authnRequest.setID(authReqRandomId);
       authnRequest.setVersion(SAMLVersion.VERSION_20);

       return marshall(authnRequest);

   }

   public static String buildLogoutRequest(String user) throws MarshallingException, IOException {

       LogoutRequest logoutReq = new LogoutRequestBuilder().buildObject();

       logoutReq.setID(createID());

       DateTime issueInstant = new DateTime();
       logoutReq.setIssueInstant(issueInstant);
       logoutReq.setNotOnOrAfter(new DateTime(issueInstant.getMillis() + 5 * 60 * 1000));

       IssuerBuilder issuerBuilder = new IssuerBuilder();
       Issuer issuer = issuerBuilder.buildObject();
       issuer.setValue(ISSUER_URL);
       logoutReq.setIssuer(issuer);

       NameID nameId = new NameIDBuilder().buildObject();
       nameId.setFormat(“urn:oasis:names:tc:SAML:2.0:nameid-format:entity”);
       nameId.setValue(user);
       logoutReq.setNameID(nameId);

       SessionIndex sessionIndex = new SessionIndexBuilder().buildObject();
       sessionIndex.setSessionIndex(UIDGenerator.generateUID());
       logoutReq.getSessionIndexes().add(sessionIndex);

       logoutReq.setReason(“Single Logout”);

       return marshall(logoutReq);
   }

   private static String marshall(RequestAbstractType authnRequest) throws MarshallingException, IOException {
       doBootstrap();
       Marshaller marshaller = Configuration.getMarshallerFactory().getMarshaller(authnRequest);
       Element authDOM = marshaller.marshall(authnRequest);


       StringWriter rspWrt = new StringWriter();
       XMLHelper.writeNode(authDOM, rspWrt);
       String requestMessage = rspWrt.toString();

       System.out.println(requestMessage);

       Deflater deflater = new Deflater(Deflater.DEFLATED, true);
       ByteArrayOutputStream byteArrayOutputStream = new ByteArrayOutputStream();
       DeflaterOutputStream deflaterOutputStream = new DeflaterOutputStream(byteArrayOutputStream, deflater);
       deflaterOutputStream.write(requestMessage.getBytes());
       deflaterOutputStream.close();

       /* Encoding the compressed message */
       String encodedRequestMessage = Base64.encodeBytes(byteArrayOutputStream.toByteArray(), Base64.DONT_BREAK_LINES);
       String encodedAuthnRequest = URLEncoder.encode(encodedRequestMessage,”UTF-8”).trim();;

       return encodedAuthnRequest;
   }


   public static <T> T createSAMLObject(final Class<T> clazz) throws IllegalArgumentException, SecurityException, IllegalAccessException, NoSuchFieldException {
       XMLObjectBuilderFactory builderFactory = Configuration.getBuilderFactory();

       QName defaultElementName = (QName)clazz.getDeclaredField(“DEFAULT_ELEMENT_NAME”).get(null);
       Map<QName, XMLObjectBuilder> builderMap= builderFactory.getBuilders();
       System.out.println(“is nul “ + builderMap.get(defaultElementName));

       return null;
   }

   private static void doBootstrap() {
       if(!isBootstraped) {
           try {
               DefaultBootstrap.bootstrap();
               isBootstraped = true;
           } catch (ConfigurationException e) {
               logger.error(“Error calling bootstrap”, e);
           }
       }
   }

   public static Map<String, String> processResponse(String response) {

       XMLObject resp = null;

       try {
           resp = unmarshall(response);
       } catch (ConfigurationException e) {
           // TODO Auto-generated catch block
           e.printStackTrace();
       } catch (ParserConfigurationException e) {
           // TODO Auto-generated catch block
           e.printStackTrace();
       } catch (SAXException e) {
           // TODO Auto-generated catch block
           e.printStackTrace();
       } catch (IOException e) {
           // TODO Auto-generated catch block
           e.printStackTrace();
       } catch (UnmarshallingException e) {
           // TODO Auto-generated catch block
           e.printStackTrace();
       }

       return getResult(resp);

   }

   private static XMLObject unmarshall(String responseMessage) throws ConfigurationException,
                           ParserConfigurationException, SAXException, IOException, UnmarshallingException {

       doBootstrap();
       DocumentBuilderFactory documentBuilderFactory = DocumentBuilderFactory.newInstance();
       documentBuilderFactory.setNamespaceAware(true);
       DocumentBuilder docBuilder = documentBuilderFactory.newDocumentBuilder();

       byte[] base64DecodedResponse = Base64.decode(responseMessage.trim());

       System.out.println(new String(base64DecodedResponse));

       ByteArrayInputStream is = new ByteArrayInputStream(base64DecodedResponse);

       Document document = docBuilder.parse(is);
       Element element = document.getDocumentElement();
       UnmarshallerFactory unmarshallerFactory = Configuration.getUnmarshallerFactory();
       Unmarshaller unmarshaller = unmarshallerFactory.getUnmarshaller(element);
       return unmarshaller.unmarshall(element);

   }

   private static Map<String, String> getResult(XMLObject responseXmlObj) {

       if (responseXmlObj.getDOM().getNodeName().equals(“saml2p:LogoutResponse”)) {
           logger.error(“user logout”);
           return null;
       }

       Response response = (Response) responseXmlObj;
       logger.info(“SAML resp” + response);

       Assertion assertion = response.getAssertions().get(0);
       Map<String, String> resutls = new HashMap<String, String>();

       /*
       * If the request has failed, the IDP shouldn’t send an assertion.
       * SSO profile spec 4.1.4.2 <Response> Usage
       */
       if (assertion != null) {

           String subject = assertion.getSubject().getNameID().getValue();
           resutls.put(“Subject”, subject); // get the subject

           List<AttributeStatement> attributeStatementList = assertion.getAttributeStatements();

           if (attributeStatementList != null) {
               // we have received attributes of user
               Iterator<AttributeStatement> attribStatIter = attributeStatementList.iterator();
               while (attribStatIter.hasNext()) {
                   AttributeStatement statment = attribStatIter.next();
                   List<Attribute> attributesList = statment.getAttributes();
                   Iterator<Attribute> attributesIter = attributesList.iterator();
                   while (attributesIter.hasNext()) {
                       Attribute attrib = attributesIter.next();
                       Element value = attrib.getAttributeValues().get(0).getDOM();
                       String attribValue = value.getTextContent();
                       resutls.put(attrib.getName(), attribValue);
                   }
               }
           }
       }
       return resutls;
   }

   public static String createID() {

        byte[] bytes = new byte[20]; // 160 bit

        new Random().nextBytes(bytes);

        char[] charMapping = {‘a’, ‘b’, ‘c’, ‘d’, ‘e’, ‘f’, ‘g’, ‘h’, ‘i’, ‘j’, ‘k’, ‘l’, ‘m’, ‘n’, ‘o’, ‘p’};

        char[] chars = new char[40];

        for (int i = 0; i < bytes.length; i++) {
            int left = (bytes[i] » 4) & 0x0f;
            int right = bytes[i] & 0x0f;
            chars[i * 2] = charMapping[left];
            chars[i * 2 + 1] = charMapping[right];
        }

        return String.valueOf(chars);
    }

}

[1] http://wso2.com/products/identity-server/

[2] https://wiki.shibboleth.net/confluence/display/OpenSAML/Home

[3] http://pavithramadurangi.blogspot.com/2013/09/saml-20-sso-with-wso2-is-450.html

WSO2 esb JSON proxy REST API SAMPLE

2014-03-19T02:28:00.000+05:00

<?xml version=”1.0” encoding=”UTF-8”?>
<api xmlns=”http://ws.apache.org/ns/synapse”
     name=”SelfcareMobile”
     context=”/a/b”>
   <resource methods=”POST” url-mapping=”/c/*”>
      <inSequence>
         <property name=”messageType”
                   value=”application/json”
                   scope=”axis2”
                   type=”STRING”/>
         <property name=”contentType”
                   value=”application/json”
                   scope=”axis2”
                   type=”STRING”/>
         <log level=”full”/>
         <send>
            <endpoint>
               <http format=”rest”
                     method=”post”
                     uri-template=”YOUR_BACK_END_URL”/>
            </endpoint>
         </send>
      </inSequence>
      <outSequence>
         <send/>
      </outSequence>
   </resource>

</api>

*** URL-mapping

Lets say our external url (which we give to outside )will be “http://www.mysite.com/a/b/c/someservice” and back end service will be “http://yourip:port/something/c/someservice" .

Then our url context for the api will be “/a/b”. Which means what has the url pattern of “/a/b” should go into this API.

url-mapping will be “/c/*” which meas what ever has “/c” and after what ever string should use the given resource.

Last not least, our endpoint address should be like below. (note “uri-template” which is the back end address of the real REST service.

Yeah you see it right, we ommit the “/c/someservice" part from real back end url because when we tell to url-mapping in the resource tag it will put that part and append it to the uri-template to determine the final destination.

WSO2 ESB - sample REST to REST API configuration

2013-12-17T03:41:00.000+05:00

<api xmlns=”http://ws.apache.org/ns/synapse” name=”TestApi” context=”/helloWorld”>
   <resource methods=”GET” url-mapping=”/hello”>
      <inSequence>
         <property name=”ContentType” value=”text/xml” scope=”axis2” type=”STRING”/>
         <switch source=”$axis2:HTTP_METHOD”>
            <case regex=”GET”>
               <property name=”HTTP_METHOD” value=”GET” scope=”axis2” type=”STRING”/>
            </case>
            <case regex=”POST”>
               <property name=”HTTP_METHOD” value=”POST” scope=”axis2” type=”STRING”/>
            </case>
            <default/>
         </switch>
         <log/>
         <send>
            <endpoint>
               <address uri=”http://localhost:8080/HelloRestFul” format=”pox”/>
            </endpoint>
         </send>
      </inSequence>
      <outSequence>
         <log/>
         <send/>
      </outSequence>
   </resource>
</api>

WSO2 ESB exposing Web Service Proxy to a TCP client PART 2 : Sending batch responses from ESB to TCP server

2013-12-05T01:24:00.000+05:00

In my last post regarding how to expose a web service for a TCP client we have discussed about retrieving a request in plain text format from a TCP client, convert it to SOAP message and send to the back end webservice.

In that post I have mentioned that according to our implementation we did not need to send the response back to the TCP client immediately due to that our responses are not synchronous.

So what we did to achieve this asynchronous status is converting the ESB it self to a TCP client and send the responses as batches to a TCP server.

So in this article I am going to explain how to use the WSO2 ESB as a TCP client where we needed to convert the XML responses to delimited string sequences before sending to TCP server.

To convert the XML file to delimited string sequence we have used the smooks mediator. (Refer the smooks configuration below)

In above example we are converting a xml file that has an entity called “Login”. Each login element has three child elements.

Freemarker tool has been used to convert the XML elements to text fields and delimit two values.

<smooks-resource-list xmlns=”http://www.milyn.org/xsd/smooks-1.1.xsd” xmlns:ftl=”http://www.milyn.org/xsd/smooks/freemarker-1.1.xsd” xmlns:core=”http://www.milyn.org/xsd/smooks/smooks-core-1.3.xsd” xmlns:file=”http://www.milyn.org/xsd/smooks/file-routing-1.1.xsd”>
      <core:filterSettings type=”SAX” defaultSerialization=”false”/>
      <resource-config selector=”//batchTransfer/returnVal/login”>
         <resource>org.milyn.delivery.DomModelCreator</resource>
      </resource-config>
      <ftl:freemarker applyOnElement=”login”>
         <ftl:template>${.vars[“login”].id},${.vars[“login”].password},${.vars[“login”].userName}
           </ftl:template>
      </ftl:freemarker>
   </smooks-resource-list>

Save above smooks configuration as a Local XML entry.

Then to send a batch of responses to ESB from our back end, we have created a dummy web service proxy inside ESB. This dummy web service connect to the TCP server, thus the TCP server now acts as the back end. Also we have hand written a WSDL and expose that hand written WSDL through the ESB. This way we can configure what kind or SOAP structure accept by this dummy proxy web service and then convert the XML resides within that proxy and then send those converted text to the back end TCP server.

Below is the WSDL which we hand written for the above “Login batch response” example.

<wsdl:definitions xmlns:wsdl=”http://schemas.xmlsoap.org/wsdl/” xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:soap=”http://schemas.xmlsoap.org/wsdl/soap/” xmlns:tns=”com.mobitel.test” name=”test” targetNamespace=”com.mobitel.test”>
      <wsdl:types>
         <xsd:schema targetNamespace=”com.mobitel.test”>
            <xsd:element name=”batchTransfer” type=”tns:batchTransfer”/>
            <xsd:element name=”batchTransferResponse” type=”tns:batchTransferResponse”/>
            <xsd:complexType name=”batchTransfer”>
               <xsd:sequence>
                  <xsd:element name=”returnVal” type=”tns:logins”/>
               </xsd:sequence>
            </xsd:complexType>
            <xsd:complexType name=”logins”>
               <xsd:sequence>
                  <xsd:element name=”login” type=”tns:login” nillable=”true” minOccurs=”0” maxOccurs=”unbounded”/>
               </xsd:sequence>
            </xsd:complexType>
            <xsd:complexType name=”login”>
               <xsd:sequence>
                  <xsd:element name=”id” type=”xsd:int”/>
                  <xsd:element name=”password” type=”xsd:string”/>
                  <xsd:element name=”userName” type=”xsd:string”/>
               </xsd:sequence>
            </xsd:complexType>
            <xsd:complexType name=”batchTransferResponse”/>
         </xsd:schema>
      </wsdl:types>
      <wsdl:message name=”batchTransferRequest”>
         <wsdl:part element=”tns:batchTransfer” name=”parameters”/>
      </wsdl:message>
      <wsdl:message name=”batchTransferResponse”>
         <wsdl:part element=”tns:batchTransferResponse” name=”parameters”/>
      </wsdl:message>
      <wsdl:portType name=”test”>
         <wsdl:operation name=”batchTransfer”>
            <wsdl:input message=”tns:batchTransferRequest”/>
            <wsdl:output message=”tns:batchTransferResponse”/>
         </wsdl:operation>
      </wsdl:portType>
      <wsdl:binding name=”testSOAP” type=”tns:test”>
         <soap:binding style=”document” transport=”http://schemas.xmlsoap.org/soap/http”/>
         <wsdl:operation name=”batchTransfer”>
            <soap:operation soapAction=”com.mobitel.test/NewOperation”/>
            <wsdl:input>
               <soap:body use=”literal”/>
            </wsdl:input>
            <wsdl:output>
               <soap:body use=”literal”/>
            </wsdl:output>
         </wsdl:operation>
      </wsdl:binding>
      <wsdl:service name=”test”>
         <wsdl:port binding=”tns:testSOAP” name=”testSOAP”>
            <soap:address location=”http://localhost:8282/services/TcpOutput”/>
         </wsdl:port>
      </wsdl:service>
   </wsdl:definitions>

This way the user of this dummy web service can create a web service client by using the above WSDl expose from WSO2 ESB’s dummy proxy service. Also the details such as back end is TCP can be hidden from the user.

Below is the dummy proxy for the “Login batch response” example.

<?xml version=”1.0” encoding=”UTF-8”?>
<proxy xmlns=”http://ws.apache.org/ns/synapse”
       name=”TcpOutput”
       transports=”https,http,tcp”
       statistics=”disable”
       trace=”disable”
       startOnLoad=”true”>
   <target>
      <inSequence>
         <log level=”full”/>
         <smooks config-key=”smooksXMLToText”>
            <input type=”xml”/>
            <output type=”text”/>
         </smooks>
         <log level=”full”/>
         <property name=”CONTENT_TYPE”
                   value=”text/plain”
                   scope=”axis2”
                   type=”STRING”/>
         <property name=”OUT_ONLY” value=”true” scope=”default” type=”STRING”/>
         <send>
            <endpoint>
               <address uri=”tcp://localhost:9448”/>
            </endpoint>
         </send>
         <property name=”FORCE_SC_ACCEPTED”
                   value=”true”
                   scope=”axis2”
                   type=”STRING”/>
      </inSequence>
      <outSequence>
         <send>
            <endpoint>
               <default/>
            </endpoint>
         </send>
      </outSequence>
   </target>
   <publishWSDL key=”testOutPutWsdl”/>
   <description/>
</proxy>

Here we have used 3 properties ( please refer the proxy xml above)

1. <property name=”CONTENT_TYPE” value=”text/plain” scope=”axis2” type=”STRING”/>

This will tell ESB that the output to back end will be “text/plain”. We needed this because our TCP server accept only text formate.

2. <property name=”OUT_ONLY” value=”true” scope=”default” type=”STRING”/>

This will tell ESB that this proxy does not send a response or simply do not need a out sequence. Though we defined empty outsequance tag we does not expect web service client to wait for a response from back end TCP server.

3. <property name=”FORCE_SC_ACCEPTED” value=”true” scope=”axis2” type=”STRING”/>

Add this property just after the SEND mediator. We use this property to send a HTTP 202 ( no content ) response to the web service client to avoid it wait for response.

Also please note that in our dummy proxy web service we have enabled all the http,https,tcp transport types because in our proxy we retrieve the “batch response” request via HTTP or HTTPS and we use TCP to transport that “batch response” request to TCP server.

(Special thanks goes to Lalaji Sureshika from WSO2)

WSO2 ESB exposing Web Service Proxy to a TCP client. ( A.K.A TCP proxy)

2013-12-03T07:17:00.000+05:00

In this article I am going to explain how to create a proxy to a back end web service which accept TCP messages.

In our case our TCP client was sending a delimited string to the ESB and we need ESB to convert the delimited string into a SOAP/XML file and call the web service.

In our case we does not intend to send the response immediately back to the client rather than sending response as batches of several requests. Since I will explain how the batch response in another article.

To accept the TCP requests you need to change your axis2.xml file inside <ESB_LOCATION>/repository/conf/axis2.xml file and add below two transport handler.

1. Configure TCPTransportListener to listen to in coming TCP requests.

<transportReceiver name=”tcp” class=”org.apache.axis2.transport.tcp.TCPTransportListener”>
<parameter name=”transport.tcp.port”>6060</parameter>
</transportReceiver>

2. Configure TCPTransportSender to send responses over TCP (this handler will not want for this article but this will be used in next article for batch response sending )

<transportSender name=”tcp” class=”org.apache.axis2.transport.tcp.TCPTransportSender”/>

Then we use inbuilt smooks handler to transform the delimited values into a XML entries.

To do this we first need to add smooks configuration which act as a template to smooks handler. We need to add the smooks configuration as a local XML entry to ESB. To do this go to Main - > Service Bus -> Local Entries. And add a in-lined XML entry.

(This is an example of smooks configuration which use to trans form delimited text to XML)

<smooks-resource-list xmlns=”http://www.milyn.org/xsd/smooks-1.1.xsd” xmlns:csv=”http://www.milyn.org/xsd/smooks/csv-1.2.xsd”>
      <resource-config selector=”org.xml.sax.driver”>
         <resource>org.milyn.csv.CSVReader</resource>
         <param name=”fields”>id,password,userName</param>
         <param name=”rootElementName”>addLogin</param>
         <param name=”recordElementName”>login</param>
      </resource-config>
   </smooks-resource-list>

Then add a new proxy which use the smooks mediator in “Advance -> smooks”, with TCP transport type allowed, and finally with port and content type properties as below.

Below is a sample

<?xml version=”1.0” encoding=”UTF-8”?>
<proxy xmlns=”http://ws.apache.org/ns/synapse”
       name=”LoginProxy”
       transports=”tcp”
       statistics=”disable”
       trace=”disable”
       startOnLoad=”true”>
   <target>
      <inSequence>
         <smooks config-key=”LoginDetails”>
            <input type=”text”/>
            <output type=”xml”/>
         </smooks>
         <send>
            <endpoint>
               <wsdl service=”HelloServiceImplService”
                     port=”HelloServiceImpl”
                     uri=”http://localhost:8080//HelloWebService/services/HelloServiceImpl?wsdl”/>
            </endpoint>
         </send>
         <log level=”full”/>
      </inSequence>
      <outSequence>
         <log/>
      </outSequence>
   </target>
   <parameter name=”transport.tcp.port”>9446</parameter>
   <parameter name=”transport.tcp.contentType”>text/plain</parameter>
   <description/>
</proxy>

How to move your blogs around.

2013-11-07T03:39:00.000+05:00

In this post I am going to describe how to move your blog from one platform to another. Since there are many famous platforms that offer various kind of user experience, it is more tend to keep several blogs in different platforms that has the same content. To synchronize these blogs we have to have some kind of automation.

Blogspot powered by google has functionality that support Wordpress but not Tumblr. In the other hand Tumblr support both Wordpress and Blogspot. Also Wordpress support backs both Tumblr and Wordpress.

1. Moving from Blogspot to Tumblr.

This tool gives an api to move your Blog in Google’s Blogspot platfrom to Tumblr.

2. Moving from Tumblr to Wordpress

This tool is giving you the ability to move your Tumblr blog posts to Wordpress platform. Its source code also available in Git repository to download and host in your own server.

3. Moving from Wordpress to Blogspot.

This tool gives the ability to move your blogs from Wordpress platform to Blogspot platform.

4. Moving from Tumblr to Blogspot.

This is a bit tricky task since google’s Blogspot does not expose an Api to directly support Tumbler platform. Hence we have to be bit tricky. First convert your Tumblr into Wordpress format by using the tool given in section 2. This will download a XML file into your computer which is in Wordpress format. Now using the tool given in section 3 convert the downloaded xml file into Blogspot fomrat and save the XML file. Go to settings>import and import the downloaded XML file.

Google App Engine DataNucles Enhancer error

2013-11-05T02:53:00.000+05:00

When you update your GAE version to the latest, you might have been struck in the following error.

java.lang.UnsupportedClassVersionError: com/google/appengine/tools/enhancer/Enhance : Unsupported major.minor version 51.0

at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(Unknown Source)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$000(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)

Reason for this is that the JDK versions and JRE versions you use are conflict with either each other or the version compatible with the latest GAE SDK version.

First thing I did is check for Java versions installed in my machine. I found out that I have java 1.6 and 1.7 both installed. So I change the default JDK to 1.7 (since newer GAE tends to be more support for java 7).

Change your JDK_HOME, JRE_HOME and PATH variables to reflect the location of newest JDK in your machine.

Though this solve the above error, it might introduce a new error which is eclipse is not able to recognize the appengine-sdk at all.

“Failed to initialize App Engine SDK at [path]”

The reason might be that when eclipse launch it do not use the default Java runtime. To force eclipse to use the default runtime, add the “-vm” argument to <eclipse-folder>\eclipse.ini file.

-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
—launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20130807-1835
-vm
C:\Program Files\Java\jdk1.7.0_45\bin\javaw.exe

WSO2 ESB exposing a secure backend through a proxy.

2013-10-28T02:53:00.000+05:00

(Special thanks goes to Sumedha Kodithuwakku @ wso2 support team)

In this post i will describe how to generate a custom certificate using keytool and use that certificate to secure a your web service and finally how to expose the secured web service using a proxy in wso2 ESB.

1. Generate a custom certificate.

Open a command prompt and use the keytool to generate a certificate. Here I use the CN as localhost since we use locally host web service(keep this in mind for later use). The rule of thumb is that CN should be matches to the hostname of the wsdl endpoint to resolve it by the ESB.

(Also using IP address as a CN would be a problematic so always stick to a host name rather than using an IP address.)

Use the following command to generate a certificate

keytool -genkey -alias localhost -keyalg RSA -keystore localhost.jks

*** When asked for the first and last name give the hostname which is localhost in our case.

Here you can use what ever name for -alias and - localhost.jks which is the alias of our certificate and name of the keystore if it newly create.

then export that certificate to a “.crt” file using command below.

keytool -export -alias localhost -file localhost.crt -keystore localhost.jks

2 Adding a keystore to web server (tomcat in our example)

Open the server.xml file in <tomcat-location>/conf/ folder and edit the <Connector port=”8443”tag as below.

<Connector port=”8443” protocol=”HTTP/1.1” SSLEnabled=”true”
               maxThreads=”150” scheme=”https” secure=”true”
               clientAuth=”false” sslProtocol=”TLS”
               keystoreFile=”C:\keyStores\localhost.jks” keystorePass=”123456” />

Here we have added the keystore and the password we newly created.

3. Adding imported certificate to wso2 keystore and truststore.

Browse to <wso2-esb>\repository\resources\security folder. There is two keystore files namely “client-truststore.jks” and “wso2carbon.jks”. Use the below command to add the newly created and stored certificate (localhost.crt as our example in part 1 ) to these two keystore. Provide alias as the host name used as CN.

keytool -importcert -v -trustcacerts -file “localhost.crt” -alias localhost -keystore “wso2carbon.jks”

keytool -importcert -v -trustcacerts -file “localhost.crt” -alias localhost -keystore “client-truststore.jks

Since we are using localhost as our host we have update “HostnameVerifier" parameter in <wso2-esb>repository/conf/axis2.xml file to allow all hosts.

<parameter name=”HostnameVerifier”>AllowAll</parameter>

(This parameter can be found in <transportSender name=”https” tags.)

4. Create a proxy as normal and add the https://localhost:8443/<your-service>?wsdl file as normally do.

Resources :

[1] http://blog.facilelogin.com/2011/02/wso2-esb-invoking-web-service-via-https.html

[2] http://stackoverflow.com/questions/8443081/how-are-ssl-certificate-server-names-resolved-can-i-add-alternative-names-using/8444863#8444863

[3] http://stackoverflow.com/questions/19540289/how-to-fix-the-java-security-cert-certificateexception-no-subject-alternative?rq=1

I WSO2ESB start up failed and hangout due to typo of wsdl saved in governance registry

2013-10-02T03:59:00.000+05:00

Ok first of all i will tell what happened before the start up fail.

1. We have added a wsdl file belong to one of our services into the governance registry.

2. While manually editing the wsdl file which have been added to governance registry, some miss typing has occurred which changed a letter of one of the XML tags into upper case

3. Without knowing about the typo we saved the wsdl, (and here is the funny part… ) ESB let that wsdl to be save in it’s governance registry without parsing it or neither complaining us about the typo we did .. ( really ??? an enterprise level ESB does not check the documents edited ??? )

4. After some time for some reason we have restarted the ESB. ( and here the fun began. ) ESB hangout printing an exception complaining XML parsing error when it try to load that wsdl file where the error happened. And the admin console is not loading because OSGI module that correspond to esb (Synapsys) is waiting until all the wsdl loads. (This is the biggest fault - not letting other services, and esb to start because a wsdl typo occurred where it should parse the wsdl before save it to registry )

At the end of the console we can see the following message printed time to time without starting the ESB and the services due to what happened that has been described above.

StartupFinalizerServiceComponent Waiting for required OSGi services: org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService

And this is the exception which complains about that our wsdl could not be parsed at startup.

WstxParsingException: Illegal processing instruction target (“xml”); xml (case insensitive) is reserved by the specs. at [row,col

There were 0 documentation and no entry about how to handle such a situation.

According to this exception we guessed the work around for this problem is just to remove the erroneous wsdl file from the governance registry. But wso2esb it self should not let that wsdl added to the registry at the first place. Even it did add, there should be some way to remove the erroneous wsdl related proxy and start up the esb and other proxy services. But it does not have that feature yet.

So how the hell we edit the governance registry without esb up.

Well, there is no proper way wso2 has exposed to do that. ( i could not find any thing on the web that’s why i write this blog entry apart from that to complement wso2 esb team about this s:D )

What we did is this,

1. Shut down the esb , copy and back up the databases folder in <wso2esb_home>/repository/database

2. Download any sql viewer tool that support h2 database management system. (yes wso2 default database is java h2 DBMS - in our case we used the default DBMS ). I used SQL Squirrel with h2 database jdbc driver.

3. open/connect to the h2 database in above folder using the sql tool.

4. find the “REG_RESOURCE” and “REG_CONTENT” tables in “WSO2CARBON_DB/PUBLIC/TABLE/” location.

5. search for erroneous wsdl file name inside “REG_RESOURCE” (hint: use sql select). File name for a resource in “REG_RESOURCE” saved in “REG_NAME” column.

6. From the resulted row note down the value of “REG_CONTENT_ID” and search for that REG_CONTENT_ID in “REG_CONTENT” table. The resulting row is where the actual wsdl file saved as sql BLOB file type.

select rc.REG_CONTENT_ID from REG_RESOURCE rr, REG_CONTENT rc where rr.REG_NAME like ‘%mywsdl.wsdl’ and rc.REG_CONTENT_ID=rr.REG_CONTENT_ID

7. To recover the wso2 esb from hanging out due to this erroneous wsdl remove the two entries related to REG_CONTENT_ID of REG_NAME of the wsdl from two tables.

8. Re start the wso2esb and you may find that exceptions are no more there and server does not hanging out any more.

Yeah i know this is bit fishy and fundamental, but if we cant access the admin console due to that ESB not finishing up loading its OSGI module (because esb let it save error-nous wsdl inside the governance registry at the first place.) we cant do much rather than cracking the database and remove the wsdl manually right ??

PS : there may be other artifacts such as proxies, sequences, endpoints using the removed wsdl, that may affected by the removal. so i instruct to remove those of which use the removed wsdl.

When WSO2 ESB does not read groups from external LDAP

2013-09-09T04:20:00.000+05:00

Once I configured external LDAP (In my case using Apache DS) to use by both WSO2 Identity Server and WSO2 ESB, I came across a situation where WSO2 ESB does not show any of the user roles that has been created through Identity Server. Neither Identity server show any roles created in ESB.

After going through lot of configurations I found it was due to this small line. So thought to blog about this for future use of other.

Within “<UserStoreManager>” tags in your external LDAP configuration (in {wso2-esb-root}/repository/conf/user-mgt.xml folder), just add following line.

Configure WSO2 Identity server to use Apache DS LDAP

2013-09-04T04:45:00.000+05:00

1. Configure a LDAP from Apache DS.

To configure Apache DS first download the latest version of apache directory studio from here.

Then install the setup (for windows users) and start the Apache Directory Studio.

Then go to “Window - > show view -> other ” and select “LDAP servers”.

In the server view click on “new server” and create a new server instance. Start the server by right clicking on the server instance and click on “start”.

Then go to connections tab next to the LDAP servers tab and create a new connection.

This will open “New LDAP Connection" wizard.

Enter the connection details and click next. (Here in my example i run on localhost port 10389.)

In the next window you will be asked for parameters for authentication details.

Enter the parameters for simple authentication. In the Bind DN or user field, enter the DN of the administrator’s account on the directory server (for the default instance of the Apache directory server, this is uid=admin,ou=system). In the Bind password field, enter the administrator’s password (for the default instance of the Apache directory server, the administrator’s password is secret). Click Finish

If the connection is successfully established, you should see an outline of the Directory Information Tree (DIT) in the LDAP Browser view. In the LDAP Browser view, drill down to the ou=users node, as shown.

Right-click on the ou=users node and select New Entry. The New Entry wizard appears. Leave the Entry Creation Method by clicking next. In the Object Classes pane, select inetOrgPerson from the list of Available object classes on the left and then click Add to populate the list of Selected object classes. Click Next.

In the Distinguished Name pane, complete the RDN field, putting uid in front and jdoe after the equals sign. Click Next.

Fill in the remaining mandatory attributes in the Attributes pane. Set the cn (common name) attribute to John Doe and the sn (surname) attribute to Doe. Click Finish.

To add a userPassword attribute to the user entry. In the LDAP Browser view, you should now be able to see a new node, uid=jdoe. Select the uid=jdoe node. Now, right-click in the Entry Editor view and select New Attribute. The New Attribute wizard appears. From the Attribute type drop-down list, select userPassword. Click Finish. The Password Editor dialog appears. In the Enter New Password field, enter the password, secret. Click Ok.

Point wso2 Identity server to the newly created external LDAP

Goto Identity server root folder and browse in to “wso2esb-{version}\repository\conf”. Open “user-mgt.xml” in the editor.

Un-comment the commented section about external LDAP.

Change the password of connection as following line. (since our previously entered default password is “secret” we entered that below)

<Property name=”ConnectionPassword”>secret</Property>

Run the Identity server and create a new user by signup.

If all goes correctly you may be able to add new users by Identity server and, in Apache DS you may see the newly added users.

Gradle how to add 'providedCompile' configuration

2013-08-06T06:30:00.000+05:00

"providedCompile" configuration is used to declare dependencies that will be provided in run time so there is no need to copy the dependencies to resources folder.

But this configuration has not added in some plugins by default (ex. “java” plugin). Thus we have to manually configure our build script for “providedCompile” configuration.

First we add configuration for providedCompile as below,

configurations { providedCompile }

Then we have to add the new configuration into classpaths as below.

sourceSets.main.compileClasspath += configurations.providedCompile
sourceSets.test.compileClasspath += configurations.providedCompile
sourceSets.test.runtimeClasspath += configurations.providedCompile

Websphere - increasing wait time when uploading an application via admin console

2013-07-03T09:31:00.000+05:00

Default time for application install (upload) in websphere has been set to 60 seconds.

To increase this you have to go to

Application servers > server1 > Web container > Web container transport chains

There are several handler chains defined for various purposes. Since in this post i m going to describe the scenario of uploading app via admin console, i l skip the rest. (though the procedure is same)

Select WCInboundAdminSecure from the above lists (since admin console use SSL).

Increase the “Read timeout" . Click Apply and save.

Using XQuery to get values from set of XPaths and return null if node is not presented.

2013-06-03T14:23:00.000+05:00

I have been stuck for few days due to that i can not return anything from querying XPath if that specific XPath is not presented in my XML file. The scenario is that we have nodes in our XML file that may be or may not be present in XML file arbitrarily.

Yes you can do it programmatically if you only use one XPath at a time. But my need is different. I want to get values of several XPaths at once and at the same time i need it to give me something pre-defined ( let's say "null"), if one of XPaths i am querying for is not presented.

So i basically had two problems to overcome. One is how to get values of several XPaths at once.
And the other is getting per-defined value if that specific node is not presented in my XML document.

First i tried using purely XPaths. In this way i have been able to overcome my first problem, that is querying several XPaths at once. That is by using XPath Union operation. XPath union operator can be use as follows

 /A/B/C/text() | /A/D/C/text() | /A/E/C/text()

 /A/B/C/text() union /A/D/C/text() union /A/E/C/text()

Here by using "|" or "union" you can join as much as XPaths you want. And i have seen that this improves performance since you can use to get several values you want through out the system at one call without calling the same function (which you use to execute your XPaths) several times.

Also order of the values return by using XPath union preserve the order of the elements appear in XML document.

Problem in this method come with this order. If you join an element that will not present in the XML file always, it will destroy the order of the values return. Which is lets say if all the "C" elements present in above example, then the returning order values should be,

 1. value of /A/B/C/text()   
 2. value of /A/D/C/text()   
 3. value of /A/E/C/text()

But, lets say that Node /A/D/C is not presented in XML file.Then the order will be,

 1. value of /A/B/C/text()   
 2. value of /A/E/C/text()

Yes you get it right!!! Nothing in the middle saying that we have no /A/D/C node. So the order of the return values have been changed.

Because of this I have find an alternative and XQuery came to rescue. Yes XPath is to do complicate stuff like querying and modifying results. That is the job of XQuery. XPath is there to show the way to XQuery ("hey dude the node you are looking for is this way")

So by using XQuery FLOWER statement i have been able to write following query to evaluate set of XPaths and get their values at the same time and also if there is some node missing in the middle to return "null" which help to preserve the order of the return values.

 let $i1:=/A/B/C/text()   
 let $i2:=/A/D/C/text()   
 let $i2:=/A/E/C/text()  
 return string-join((if($i1) then ($i1) else ('null') , if($i2) then ($i2) else ('null') ) , ';')

Here i have used string-join(string1, string2 ... stringN, 'delemeter') function of XQuery to join the results and ';' as the delimiter.

We can use if(condition or XPath) then (statement or XPath) else (statement or XPath)to check the availability of node and send a per-defined value if node is missing.

jQuery - when to use attr() ?? when to use prop() ???

2013-04-29T14:18:00.000+05:00

with effect from jQuery 1.6 a new method has been introduced to change or retrieve values of attributes (or properties).

So what is the big deal here you might ask. the problem is that new comers doesn't understand the difference between the attr() method which has been there and the new method prop() which introduced lately.

In a HTML element there is two kind of things we can see.

Attributes
Properties

I will explain this by an example. Lets take following HTML input tag for an instance.

 <input id="q" value="" class="button-gray" name="_3_keywords" readonly>

In the above example id, value, name are belong to Attribute family while readonly is a property. So when to use attr() method or when to use prop() method is depend on whether you are dealing with an attribute or a property.

For example lets say you want to change the class attribute of above INPUT tag. Here you have to use attr() method like below.

 $("#q").attr("class", "newclass")

But lets say if you want to make the above INPUT tag readable (it is readonly originally according to the code above). So here you have to use prop() from jQuery 1.6 onwards like below.

 $("#q").prop("readonly", false)

Yeah you might noticed the change. Before jQuery 1.6 you have to use attr() method like below.

 $("#q").attr("readonly", "readonly")

But with new prop() you can save life by just giving a boolean as the second attribute.

"ceylon" command throwing "UnsupportedClassVersionError" exception

2013-04-29T13:58:00.001+05:00

When i was trying to install and configure classpath for Ceylon programming language to begin coding i was getting this error which does not describe it self.

 Exception in thread "main" java.lang.UnsupportedClassVersionError: com/redhat/ce  
 ylon/launcher/CeylonClassLoader : Unsupported major.minor version 51.0  
     at java.lang.ClassLoader.defineClass1(Native Method)  
     at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)  
     at java.lang.ClassLoader.defineClass(ClassLoader.java:615)  
     at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:14  
 1)  
     at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)  
     at java.net.URLClassLoader.access$000(URLClassLoader.java:58)  
     at java.net.URLClassLoader$1.run(URLClassLoader.java:197)  
     at java.security.AccessController.doPrivileged(Native Method)  
     at java.net.URLClassLoader.findClass(URLClassLoader.java:190)  
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)  
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)  
     at java.lang.ClassLoader.loadClass(ClassLoader.java:247)  
 Could not find the main class: com.redhat.ceylon.launcher.Launcher. Program will  
  exit.

The mistake i did at the beginning seems to be avoid reading the "README.md" file in ceylon package. In there it clearly stated that "Ceylon execute on any Java 7 compatible JVM ... "

So the above error gives because of the incompatible JVM version. (as it says in the line "Unsupported major.minor version 51.0" ).

So to fix this what you need to do is simply install the JDK 7 and add it to the classpath, JAVA_HOME and JRE_HOME. That will fix this.

HAPPY CEYLON CODING !!!

tools.jar can not be found in JRE folder

2013-04-22T11:23:00.000+05:00

I came across this error other day i was trying to configure ant in my new machine. The reason for this is that the relevant jar file is not in the <JRE location>lib folder but in <JDK location>lib folder.

The most simplest fix for this is to just copy the "tools.jar" file from the <JDK location>lib to
<JRE location>lib folder.

Good luck.
:)

jQuery - checking for "null" objects...

2013-03-09T18:31:00.000+05:00

In day to day Object Oriented programming we used to check whether an object is null by comparing it with the null keyword supplied by the programming language. For an example in Java or javascripts we can use

1:  object == null

So what we use to do with jQuery is like below,

1:  $("#id") == null

This is wrong. The reason is that even there is no any HTML elements that has id of "id", $("#id") will return an empty object. (or empty array object,). So this will always make the above expression to evaluate to false.

So how we get to know whether above object (element) exist before using that object in complicate logic ???

You can use the following code.

1:  $("#id").length > 0

Now where does this length property come to HTML element. The reason is jQuery objects wrap around DOM objects and they are having their own methods and attributes. When we accessing HTML elements using jQuery, it will return an array of such elements. So if there is only one object returned we can directly access that object. If there are more than one object we can use normal array indexes to access them. But if there is no object or 0 object for what we asked, what jQuery does is return an empty array object. So what we can do to check if there is no object relevant what we have asked is to check the length of the array return by jQuery. If length of the array is not greater than 0 means there is no object to be return (only the empty array object is there).

When jQuery form submission not works , Work arounds.

2013-02-19T21:53:00.003+05:00

Let us consider the below form and various ways to do a form submission in client side programming.

1:    
2:  <form id="formId" name="formName" class="form-class" action="" method="post">  
3:  </form>

Before introducing jquery, the famous but harshful way to access DOM is using the popular getElementByID() method in javascript so accomplish a form submission we can use it like below,

1:    
2:  document.getElementById("formId").submit();  
3:

Also if there is no id for the form we can still use the form name to do a form submission as below,

1:    
2:  document.getElementsByName("formName")[0].submit();  
3:

But with jQuery life has become much easier and we can use either form ID in the way we use them to decorate using CSS or either CSS classes to pick elements. Below is how we can do a form submit using form ID

1:    
2:  $("#formID").submit();  
3:

And we can use the class selectors to access forms as well. This method returns an array of elements which has the same style class. (In our example we have only one element, and it is our form.)

1:    
2:  $(".form-class")[0].submit();  
3:

Finally we can use elements itself to access themselves. This method will return an array of same elements. (According to our example we only have one element of type "form".)

1:    
2:  $("form")[0].submit();  
3: