Skip to main content

Difference between getAttribute and getParameter

getParameter()
--------------------------------------------
This is used for sending a parameter from client side to server side.
Example :
On client side  :    http://test.com/servlet?parameter=hi
On server side :   request.getParameter('parameter');

The value returned by the request.getParameter is always "String". So, even if you are sending a numeric value in the parameter, on server side it will be treated as string only. So if you want a different data type in that case you have to typecast it.

For example if you want a Long value from the parameter which is set as :
 http://test.com/servlet?parameter=1 then
(Long) request.getParameter('parameter');
this will return a Long value but do check for null value else it will throw an NullPointerException.


getAttribute()
--------------------------------------------
This is commonly used on server side.

You can setAttribute value like this:
 setAttribute('nameOfAttribute',valueOfAttribute);

And retrieve it like this :
getAttribute('nameOfAttribute');

Attributes can hold not only string but any kind of Object.Values set from server can be accessed on jsp using expressions or JSTL's. It is advised to use JSTL (JavaServer pages Standard Tag Library) in jsp page since they look more cleaner and easy to maintain than expressions.

You might also like :

Difference between Linkedlist and Arraylist


Comments

Popular posts from this blog

ReferenceError: dhtmlXGrid is not defined : Resolved

For the errors like : ReferenceError: dhtmlXDataView is not defined ReferenceError: dhtmlXGrid is not defined ReferenceError: dhtmlXTree is not defined ReferenceError: dhtmlXTreeGrid is not defined etc I have been working on dhtmlx for long time now and this is one of the most basic exception faced by the developer and which in fact is very easy to resolve. Reasons: 1. You are actually referring to a wrong location of the JS file.    - This is a very common mistake done and most of the time we are so damn sure that we don't even care about checking the path once. Even though you have copied it from your existing project where it is working, if you face this issue don't forget to check the path once, it won't harm you. 2. Check for relative path.    - So now you have copied it and paste it in your new file where you are going to use the dhtmlx component and when you open your file you get this error and it becomes frustrating knowing that same thing is wo

Create Table in Liquibase

For creating table using liquibase you can use below code and add it in your liquibase file. <createTable tableName=“employee”>      <column name="id" type="int">      <constraints primaryKey="true" nullable="false"/>   </column>      <column name="first_name" type="varchar(255)"/>   <column name="last_name" type="varchar(255)"/>   <column name="username" type="varchar(255)">      <constraints unique="true" nullable="false"/>   </column> </createTable> The use is pretty simple it's the way it looks : Tag: <createTable></createTable> This is an opening/ending tag for creating a table. These tags will enclose column sub tags which will define columns for the table. Attribute:   tableName : Name of the table which you want to create. (This is a mandatory  

How databasechangeloglock and databasechangelog table used by liquibase?

Liquibase takes care of executing the query on the database while maintaining the list of queries executed and also maintaining the locks over the tables simultaneously. The two tables that are used by the liquibase for this purpose are : Databasechangeloglock : This table have following columns ID | LOCKED| LOCKGRANTED | LOCKEDBY. This maintains the locks information granted to the user. The primary purpose of this table is to make sure that two machines don't attempt to modify the data at the same time. Databasechangelog : This table have following columns ID | AUTHOR | FILENAME | DATEEXECUTED | ORDEREXECUTED | EXECTYPE | MD5SUM | DESCRIPTION | COMMENTS | TAG | LIQUIBASE This table maintains the list of the statements that are executed on the database.