That kind of thing rocks you back on to your heels.

She wanted to know if she could get some prints done quickly ahead of the funeral tomorrow. I only got the call after lunch and I was nowhere near the office, but in an instance such as this you do what you can. I rang the pro lab I work with in Cork (JSP Imaging) and asked if they could do a rush job, ready to  be collected by the bride's husband at short notice.

I'm a great believer in working with local suppliers. You get to know them, you become buddies, and when you need a favour, they come through for you. "No problem," they said.

I got the pictures emailed from the office to the lab and rang to check that they'd come through. They had.

And then this:

"Are you charging the client for the pictures?"

It was asked tentatively - the lab technician knew the delicacy of the situation.

I'd already decided that this one was on the house.

Thing is, so had JSP.

"No," I replied.

"Then we won't charge you either," the technician said.

So, not only did they bump my order to the head of the queue, they did the job gratis.

What can I say?

Not much, other than to say "Thank you" here on the blog and to highlight the terrific people who work in the lab at JSP.

Finalmente a alternativa que faltava chegou a nossos ambientes. O glassfish, servidor de aplicações da sun inspirado no famoso pacote SunOne tomou a frente dos produtos open source e salvou a vida de nós desenvolvedores.

Com recursos interessantes, alto poder de processamento e grande facilidade de configuração, instalação e uso, promete ser o melhor dos produtos deste genero este ano.

Confira em.: http://java.sun.com/javaee/community/glassfish/

Disponível para quase todas as plataformas incluindo MAC.

Own Deployment:
1. (optional) setting bedework.build.properties under folder: C:\Documents and Settings\xxzhao; if not setting, system will use: democal.properties and democal.options.xml under folder: C:\netbeansWork\my_quickstart-3.4.1.1\bedework\config\configs
2. democal.properties: for deployment use. To decide: which app to install? etc...
3. democal.options.xml: for use in runtime. e.g.    <name>bedework</name>    <tzid>America/New_York</tzid>    <systemid>demobedework@cal.mysite.edu</systemid>
4. stylesheets and associated template images and resources: ?app.<name>.root?, ?app.<name>.cal.suite?    in the config file (e.g. C:\netbeansWork\my_quickstart-3.4.1.1\bedework\config\configs\myconfig.properties).
5. modify "personal web client" app(webapps): org.bedework.app.UserCal.tomcat.context.xml=war/META-INF/usercontext.xml;    C:\netbeansWork\my_quickstart-3.4.1.1\bedework\projects\webapps\webclient\war\META-INF    C:\netbeansWork\my_quickstart-3.4.1.1\bedework\build: for hibernate dialect
6. create a schema: The deploy process created a zip file in the C:\netbeansWork\my_quickstart-3.4.1.1\bedework\dist directory, which can be unwrapped to run the schema build.    Run bwrun schema: produces a file ?schema.sql?.    Then do: bwrun schema-export: to create all the tables and constraints
7. initialize the database: bwrun initdb -ndebug -indexroot path-for-lucene
8. To dump the database data use    bwrun dump <filename>                To restore the data use: bwrun restore <filename> -ndebug -indexroot path-for-lucene
9. __newThread__: use this res file: C:\netbeansWork\my_quickstart-3.4.1.1\bedework\dist\dumpres.zip        extract it to: C:\netbeansWork\my_quickstart-3.4.1.1\xxz\dumpres
10. stop hsqldb, rename hsqldb-1.7.3.3/demo folder.
11. Restart HSQL, and Hypersonic will create a new, empty demo database: cd C:\netbeansWork\my_quickstart-3.4.1.1\    ant.bat    ant hsqldb    (use gui tool: cd C:\netbeansWork\my_quickstart-3.4.1.1\hsqldb-1.7.3.3\lib    java -cp hsqldb.jar org.hsqldb.util.DatabaseManager    Type: HSQL Database Engine Server    url: jdbc:hsqldb:hsql://localhost:8887 (from democal.properties)    sa    ""    try SELECT * FROM bw_calendars)        as you see, the database is empty, and a new "hsqldb-1.7.3.3/demo" folder is created.
12. to insert data, under dumpres folder: bwrun.bat schema-export        so the structure is established, yet no data.
13. Finally, initialize the database with dumpres/data/initbedework.xml: bwrun.bat initdb    this takes some time...... Elapsed time: 0:19    (full version: bwrun.bat initdb -ndebug -indexroot path-for-lucene)
14. build: in cd C:\netbeansWork\my_quickstart-3.4.1.1: ant clean.deploy.debug    (takes some time: Total time: 2 minutes 53 seconds)    (or doing it without debug: ant clean.deploy)    This will create a number of WAR files in <bedwork>/dist/ including for example: cal.war, caladmin.war, and ucal.war                in C:\netbeansWork\my_quickstart-3.4.1.1 do: ant tomcatstart (INFO: Server startup in 35950 ms)    now it's deployed: goto: http://localhost:8080/bedework
15. continue from here: 30 of 49 of the manual

The Java Servlet API is a Standard Extension to the Java platform that provides web application developers with a simple consistent mechanism for extending the functionality of a web server. A servlet can almost be thought of as an applet that runs on the server side -- without a face. Novell exteNd 3.0 currently implements the Servlet 2.1 API.

Servlets are Java technology's answer to CGI programming. They are programs that run on a Web server and build Web pages. Building Web pages on the fly is useful (and commonly done) for a number of reasons:

* The Web page is based on data submitted by the user. For example the results pages from search engines are generated this way, and programs that process orders for e-commerce sites do this as well.
* The data changes frequently. For example, a weather-report or news headlines page might build the page dynamically, perhaps returning a previously built page if it is still up to date.
* The Web page uses information from corporate databases or other such sources. For example, you would use this for making a Web page at an on-line store that lists current prices and number of items in stock.

JSP-
Java Server Pages (JSP) is a technology that lets you mix regular, static HTML with dynamically-generated HTML. Many Web pages that are built by CGI programs are mostly static, with the dynamic part limited to a few small locations. But most CGI variations, including servlets, make you generate the entire page via your program, even though most of it is always the same. JSP lets you create the two parts separately.

El diseño queda a disposicion de ustedes, ahora hay un sin fin de herramientas que permiten realizar este tipo de trabajo, esto es solo para uso didactico. obviamente esta tabla de logueo lo mantendremos dentro de un "form" dado que utilizaremos el metodo POST y en el action colocaremos el Servlet al cual llamaremos "GeneraSession".

Una vez hecho esto, creamos el archivo "principal.jsp" el cual nos servira para mostrar el resultado luego de realizar el logueo.

Luego creamos nuestra clase que actuara como servlet. Hacemos click derecho sobre nuestro proyecto y elejimos New --> Servlet, le damos el nombre (GeneraSession.java) y se nos mostrara un cuadro en donde nos dice que este nombre del servlet sera añadido al archivo de configuración "web.xml" el cual servira para poder ubicarlo y luego le damos click en terminar

Una vez hecho esto solo quedaria agregar el codigo dentro del metodo "processRequest", quedando algo como esto:

Podemos observar que estamos obteniendo los datos del formulario mediante el request para ser validado y asi poder generar la sesion, para luego enviarnos a la pagina principal. Ahora esto no quedaria alli; en la pagina "principal.jsp" que ha sido creada tendriamos que realizar tambien la validacion de la sesion, dado que como sabemos las sesiones tienen un tiempo de vida, si sobrepasa este tiempo la sesion automaticamente se destruye (a no ser que personalize el tiempo de vida), entonces en la pagina "principal.jsp" tendriamos algo como esto:

De esta forma validamos si la sesion persite, en caso contrario te enviaria a la pagina de inicio para volver ha realizar el logueo.

Como veran es una forma practica de trabajar con sesiones mediante un servlet; obviamente esto tendria que mejorarse, pero esto puede ser un punto de partida para muchos.

Dreamweaver MX'te çalışmaya başlamadan önce, yapacağımız çalısmaların derli toplu olması için bir site tanımlamasi yapmakta fayda vardır. Dreamweaver MX gerek sayfalarımızı kaydederken gerekse sayfalarda kullandığımız resim, stil veya animasyonlar için bize kaydetmek istediğimiz dosyaların ait olduğu siteyi soracaktır. Bir site için dosyalar tasarlıyor olmasak da tanımlanmış bir sitemizin olması işimize yarayacaktır.

Site tanımlamak için Site>>New Site... menüsünü kullanırız. Bu menü ile içerisinde Basic ve Adavanced sekmeleri bulunan Site Definition for Unnamed Site 1 penceresine ulaşırız.

Bu dersimizde biz Basic sekmesini tıklayarak bu sekmeyi kullanarak site tanımlamayı öğreneceğiz.

Basic sekmesinde ilk olarak "What would you like to name your site?" sorusunun altindaki metin alanına sitemizin ismini yazmamiz gerekir. Ben DWTurk yazıyorum. Next dediğimizde karşımıza ColdFusion, JSP, PHP veya ASP gibi bir server teknoloji kullanıp kullanmayacağımıza dair bir seçim yapmamızı gerektiren aşağıdaki ekran gelir.

Biz su an için html uzantılı sayfalar tasarlayacağımız için ilk seçenek olan "No, I do not want to use a server technology" seçiyoruz.

Tekrar next dediğimizde sitenin yapım aşamasında dosyalarla nasıl çalışacağımızı seçmemiz istenir. Burada aşağıda görülen 3 seçenek vardır.

Biz dosyalarımızı tasarladıktan sonra web alanına yükleyeceğimiz için ilk seçeneği seçiyoruz.
İkinci seçenek olan "Edit directly on server using local network" dosyalara yerel bir ağ üzerindeki bir makineden ulaşarak işlem yapmak için, üçüncü seçenek ise site dosyalarına FTP ya da RDS kullanarak ulaşmak içindir.
Bu ekranda "Where on your computer do you want to store your files?" sorusu altındaki metin alanında site dosyalarımızı saklayacağımız bir klasör belirtmemiz istenir. Bunun için  düğmesine tıklarız ve açılan pencerede site dosyalarımızı saklayacağımız dizini seçeriz.

Next diyerek ulaştığımız bir sonraki aşamada sitemizi barındıracağımız sunucuya erişim yöntemimizi seçmemiz istenmektedir. Biz şimdilik dosyalarımızla bilgisayarımızda islem yapacağımız için ilk seçenek olan "None"i seçeriz.

Son aşamada ise karşımıza yaptığımız seçimlerin yer aldığı "Summary" kısmı gelir.

Done tuşuna tıkladığımızda sitemizi oluşturmuş oluruz ve Site penceresi açılır.

Not: Site penceresi Dreamweaver MX Workspace görünümünde pencerenin sağında yer alan Files panelinin içerisindeki Site sekmesinde açılır. Bu sekmeyi panelden dışarıya sürüklediğinizde yukarıdaki resimde görülen pencere haline dönüşür. ]]> http://izletv.wordpress.com/?p=730 Thu, 09 Oct 2008 09:55:48 +0000 tg3788 http://izletv.fr.wordpress.com/2008/10/09/site-tanimlamak-1/

Dreamweaver MX'te çalışmaya başlamadan önce, yapacağımız çalısmaların derli toplu olması için bir site tanımlamasi yapmakta fayda vardır. Dreamweaver MX gerek sayfalarımızı kaydederken gerekse sayfalarda kullandığımız resim, stil veya animasyonlar için bize kaydetmek istediğimiz dosyaların ait olduğu siteyi soracaktır. Bir site için dosyalar tasarlıyor olmasak da tanımlanmış bir sitemizin olması işimize yarayacaktır.

Site tanımlamak için Site>>New Site... menüsünü kullanırız. Bu menü ile içerisinde Basic ve Adavanced sekmeleri bulunan Site Definition for Unnamed Site 1 penceresine ulaşırız.

Bu dersimizde biz Basic sekmesini tıklayarak bu sekmeyi kullanarak site tanımlamayı öğreneceğiz.

Basic sekmesinde ilk olarak "What would you like to name your site?" sorusunun altindaki metin alanına sitemizin ismini yazmamiz gerekir. Ben DWTurk yazıyorum. Next dediğimizde karşımıza ColdFusion, JSP, PHP veya ASP gibi bir server teknoloji kullanıp kullanmayacağımıza dair bir seçim yapmamızı gerektiren aşağıdaki ekran gelir.

Biz su an için html uzantılı sayfalar tasarlayacağımız için ilk seçenek olan "No, I do not want to use a server technology" seçiyoruz.

Tekrar next dediğimizde sitenin yapım aşamasında dosyalarla nasıl çalışacağımızı seçmemiz istenir. Burada aşağıda görülen 3 seçenek vardır.

Biz dosyalarımızı tasarladıktan sonra web alanına yükleyeceğimiz için ilk seçeneği seçiyoruz.
İkinci seçenek olan "Edit directly on server using local network" dosyalara yerel bir ağ üzerindeki bir makineden ulaşarak işlem yapmak için, üçüncü seçenek ise site dosyalarına FTP ya da RDS kullanarak ulaşmak içindir.
Bu ekranda "Where on your computer do you want to store your files?" sorusu altındaki metin alanında site dosyalarımızı saklayacağımız bir klasör belirtmemiz istenir. Bunun için  düğmesine tıklarız ve açılan pencerede site dosyalarımızı saklayacağımız dizini seçeriz.

Next diyerek ulaştığımız bir sonraki aşamada sitemizi barındıracağımız sunucuya erişim yöntemimizi seçmemiz istenmektedir. Biz şimdilik dosyalarımızla bilgisayarımızda islem yapacağımız için ilk seçenek olan "None"i seçeriz.

Son aşamada ise karşımıza yaptığımız seçimlerin yer aldığı "Summary" kısmı gelir.

Done tuşuna tıkladığımızda sitemizi oluşturmuş oluruz ve Site penceresi açılır.

Not: Site penceresi Dreamweaver MX Workspace görünümünde pencerenin sağında yer alan Files panelinin içerisindeki Site sekmesinde açılır. Bu sekmeyi panelden dışarıya sürüklediğinizde yukarıdaki resimde görülen pencere haline dönüşür. ]]> http://nohnit.wordpress.com/2008/10/08/goodbye-struts-spring-hibernate-and-welcome-jsf-ejb-jpa/ Wed, 08 Oct 2008 20:01:15 +0000 echo http://nohnit.fr.wordpress.com/2008/10/08/goodbye-struts-spring-hibernate-and-welcome-jsf-ejb-jpa/ Walaupun kebanyakan sekarang orang menggunakan Struts1/2 untuk presentation layer, dan Spring untuk busines layer, dan Hibernate untuk persistence layer, tapi sekarang saya mau migrasi ke JSF untuk presentation layer, dan EJB untuk busines layer, dan JPA untuk persistence..

"mengapa?"

tentunya saya punya alasan tersendiri :D

tapi alasan saya belum tentu bagus untuk anda, dan alasan anda belum tentu bagus juga untuk saya :D

walaupun saya sudah migrasi dari Struts1 ke Struts2 trus akhirnya ke JSF sudah lama, tapi pura-puranya saya baru migrasi sekarang :D , hehehe.

JSF

saya pindah dari struts1-->struts2 dan akhirnya ke JSF karena ketika pertama kali saya belajar JSF disitu saya melihat ada kesamaan antara konsep JSF dan Swing. yaitu berbasis komponen. sehingga hal ini membuat pembuatan halaman web sangat mudah karena berbasiskan komponen, artinya kita membuat halaman web seperti mendesain form dalam aplikasi desktop :D

dan selain itu JSF juga mendukung Dependency Injection yang mencakup scope untuk aplikasi website seperti request, session dan application :D , sehingga ini bisa digunakan sebagai pengganti DI-nya milik Spring :D

EJB

namun untuk total migrasi dari Spring ke EJB secara total mungkin baru sekarang ini, walaupun pertamanya saya belajar EJB lalu Spring dan sekarang saya balik lagi ke EJB :D

sebenarnya banyak orang enggan menggunakan EJB karena dulu ketika EJB masih versi 2.x, EJB dikatakan sebagai nighmare (mimpi buruk) bagi pengembang, entah saya juga kurang tahu karena saya mempelajari EJB sejak versi 3, dan menurut cerita penggunaan EJB 2.x sangat komplex dan memakan resource yang boros. :D

dan untungnya, pihak pengembang tidak putus asa dengan kegagalan EJB 2.x, sehingga sekarang saya bisa menikmati kemudahan dan kehebatan EJB 3.0 (yang katanya sebentar lagi mau keluar EJB 3.1) :D

Sebenarnya, kemampuan EJB tidak terlalu dapat dibanggakan dengan Spring Framework yang udah begitu banyak, namun disini saya menitik beratkan EJB dan Spring sebagai busines layer, bukan yang lainnya.

satu hal yang menjadi daya tarik EJB adalah kemampuan Injectionnya yang hanya dengan menggunakan annotation @EJB, tanpa melakukan konfigurasi seperti di Spring. hal ini memudahkan kita untuk memanggil komponen EJB secara langsung tanpa harus menginjeknya lewat metode setter atau lewat konstruktor seperti yang dilakukan Spring.

Namun harus di perhatikan jika EJB hanya dapat berjalan pada server yang mendukung JEE, sehingga jika kita menggunakan server seperti Tomcat dan GlassFish v.3, maka EJB tak akan berjalan karena server-server tersebut hanya digunakan untuk WebServer, so untuk menjalankan EJB kita perlu menggunakan server seperti JBoss ato GlassFish v.2

JPA

jpa sebenarnya merupakan spesifikasi yang tergabung dalam EJB yang dinamakan EJB-Entity. namun JPA tidak selalu harus berjalan bersama EJB, karena JPA juga dapat berjalan dalam aplikasi desktop ato web sama seperti Hibernate ato TopLink.

Sebenarnya JPA bukanlah sebuah framework untuk persistence, tapi merupakan spesifikasi seperti JDBC, sehingga untuk menjalankan JPA kita memerlukan implementasinya seperti menggunakan TopLink, Hibernate, EclipseLink, OpenJPA, KODO dan yang lainnya.

sehingga JPA bisa dikatakan sebagai JDBC tingkat tinggi :D (ngarang), karena emang penggunaannya sangat mudah dari pada JDBC dan hampir mirip seperti Hibernate.

hanya saja karena JPA merupakan spesifikasi yang bisa diimplementasi oleh berbagai framework, sehingga bisa dibilang JPA kurang komplete jika dibandingkan dengan Hibernate, terutama dalam hal Query.

namun alasan kenapa saya memilih JPA karena hal pertama adalah JPA merupakan kesatuan EJB, sehingga penggunaannya sangat mudah dengan EJB, dan selain itu dengan bantuan EJB proses transaksi untuk JPA jadi mudah karena kita tak perlu memikirkan "TRANSACTION" untuk proses-proses persistence yang kita lakukan karena semuanya di handle langsung oleh EJB.

Dan yang paling bermanfaat adalah JPA dapat diinjek hanya dengan menggunakan annotation @PersistenceContext atau @PersistenceUnit, sehingga penggunaannya semakin mudah, dan hal ini tanpa bantuan EJB ato Spring, sehingga andai kita tak menggunakan EJB, kita tetap bisa melakukan injeksi ke JPA

Facelets + SEAM

Facelets dan SEAM merupakan framework yang patut digunakan jika kita menggunakan JSF+EJB+JPA, karena :

dengan facelets kita dapat dengan mudah menkoneksikan antara JSP dan JSF yang kadang ditemukan berbagai kendala seperti dalam "ExpressionLanguage" misalnya. dan selain itu dengan facelets, pembuatan halaman web dapat berbasiskan template, sehingga mempermudah pembuatan halaman web ketika kita memerlukan halaman yang banyak namun memiliki kesamaan layout.

dengan SEAM, kita dapat dengan mudah mengintregasikan antara JSF dan EJB, dan selain itu SEAM mendukung facelets dan SEAM juga memiliki kemampuan yang banyak seperti kemampuan untuk menampilkan Chart, kemampuan membangun RSS, integrasi untuk Email, dan lainnya. Dan semua itu berbasiskan JSF dan EJB, sehingga SEAM akan membuat pengguna JSF dan EJB lebih termanjakan, hahahaha :D

tapi tidak selamanya pendapat saya sesuai dengan keinginan anda bukan?

itu tergantung selera :D

see you!!!

http://java.sun.com/products/ejb/

https://facelets.dev.java.net/

http://www.seamframework.org/

http://www.hibernate.org/

http://www.springframework.org/

http://struts.apache.org/

http://struts.apache.org/2.x/

Supposed you have this usual Java class acting as our first created java beans. 
package pages;

public class HelloWorld {

public String getMessage(){
           return "Hello Word";
} 

} 

and then you have a regular HTML in a JSP file like below,

<html>
<head>
<title>Simple JSP Part 4</title>
</head>
<body>
</body>
</html>

and let's name it message.jsp

Now, the idea is to display message from our HelloWorld class to our jsp page. How we will do it?
Add below java instruction between body tag in our message.jsp

<%

pages.HelloWord hw = new pages.HelloWorld();
out.println("message is: "+hw.getMessage()); 

%>

To putting it all together, below is the full code.

<html>
<head>
<title>Simple JSP Part 4</title>
</head>
<body>

<%

pages.HelloWord hw = new pages.HelloWorld();
out.println("message is: "+hw.getMessage()); 

%>

</body>

</html>

Then you will see a nice hello word message.
This is just a tiny example of how usefull java beans will be. The other benefit is if separate our logic into our java class, then we will able to test it first and will not having much difficulties in debuging compared to when we join our java instructions in our jsp pages.
But.. there is always a backside of this. If you want to update your java class, then you have to restart your web server to get it work.

So... have a nice try n error.

        <jsp:useBean id="sche" class="bean.scheduleBean" scope="request" >
            <jsp:setProperty name="sche" property="testing" value="y"/>
            <jsp:getProperty name="sche" property="testing"/>
        </jsp:useBean>

And I got following error message:
org.apache.jasper.JasperException: /Catalog/itemsview.jsp(2,0) The value for the useBean class attribute bean.scheduleBean is invalid.
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:39)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:357)
......

Reason: when doing "<jsp:useBean id="sche" class="bean.scheduleBean" scope="request" >", Java needs the bean class having a no-argument constructor, which my scheduleBean didn't have. So I added following code to the bean class, and solved problem:

    public scheduleBean() {
    }

BrickRed is India’s leading provider of commercial grade offshore software development services to technology and IT enabled SME’s worldwide. Lead by technocrat’s from IIT’s, our mission has been to provide professional and process oriented outsourcing services to SME sector that only fortune companies could muster till date by paying high prices to big service providers.

BrickRed Technologies, founded in 2002 is a privately held organization head quartered at a state-of-art offshore development center in Noida, Delhi. With offices in US, UK and Dubai, we have been providing services for end to end development of commercial grade software products and applications to Start-up, Emerging and Established technology companies & IT enabled organizations. Till date, we have successfully partnered with more than 40 technology companies in various domains like travel, retail, insurance, banking, security, e-learning and many more for offshore development of their successful products. More than 50 mid sized organizations, where software forms the back bone for running their operations, have benefited financially as well as technically by successfully outsourcing their software development, testing and maintenance needs to BrickRed.

Designation: Technical Lead - Java/J2ee (Position Code : BRT/102)

• 5+ Years of Experience
• BE/B.Tech/MCA
• Good Experience in java j2ee development, exposure in J2EE, JSP, SERVLETS, EJB, XML, Hibernate is required
• Good Communication and client interfacing skills.
• No. of Position: 2

This Job is posted in http://www.brickred.com/ for more details visit http://www.brickred.com/careers/careers.jsp

What is the World Wide Web?

• The Web is a network of computers all over the world.
• All the computers in the Web can communicate with each other.
• All the computers use a communication standard called HTTP.

How does the  WWW work?

• Web information is stored in documents called web pages.
• Web pages are files stored on computers called web servers.
• Computers reading the web pages are called web clients.
• Web clients view the pages with a program called a web browser.
• Popular browsers are Internet Explorer and Mozilla Firefox.

How does a Browser Fetch a Web Page?

• A browser fetches a page from a web server by a request.
• A request is a standard HTTP request containing a page address.
• An address may look like this: http://www.someone.com/page.htm.

How does a Browser Display a Web Page?

• All web pages contain instructions for display
• The browser displays the page by reading these instructions.
• The most common display instructions are called HTML tags.
• HTML tags look like this <p>This is a Paragraph</p>.

If you want to learn more about HTML,

What is a Web Server?

• The collection of all your web pages is called your web site.
• To let others view your work, you must publish your web site.
• To publish your work, you must copy your site to a web server.
• Your own PC can act as a web server if it is connected to a network.
• Most common is to use an Internet Service Provider (ISP).

What is an Internet Service Provider?

• ISP stands for Internet Service Provider.
• An ISP provides Internet services.
• A common Internet service is web hosting.
• Web hosting means storing your web site on a public server.
• Web hosting normally includes email services.
• Web hosting often includes domain name registration.

Summary

If you want other people to view your web site, you must copy your site to a public server. Even if you can use your own PC as a web server, it is more common to let an Internet Service Provider (ISP) host your site.

Included in a Web hosting solution you can expect to find domain name registration and standard email services.

You can read more about domain name registration, email and other services in the next chapters of this tutorial.

Web Hosting Providers

If you want your web site to be visible to the world,  you have to store it on a web server.

Most small businesses and companies store their web site on a server provided by an Internet Service Provider (ISP).

Hosting Your Own Web

Hosting your web site on your own server is always an option. Here are some problems to consider:

Hardware Expenses

To run a "real" web site, you will have to buy some powerful server hardware. Don't expect that a low cost PC will do the job. You will also need a permanent (24 hours a day ) high speed connection to your office, and such connections are expensive.

Software Expenses

Don't forget to count the extra cost for software licenses. Remember that server licenses often are much higher than client licenses. Also note that some server software licenses might have limits on number of concurrent users.

Labor Expenses

Don't expect low labor expenses. Remember that you have to install your own hardware and software. You also have to deal with bugs and viruses, and keep your server constantly running in an environment where "everything could happen".

Using an Internet Service Provider

Renting a server from an Internet Service Provider (ISP) is a common option. Here are some advantages:

Connection Speed

Most providers have very fast connections to the Internet, like full T3 fiber-optic 45Mps connections equivalent to about 2000 traditional (28K) modems or 1000 high speed (56K) modems.

Powerful Hardware

Service providers often have many powerful web servers that can be shared by several companies. You can also expect them to have an effective load balancing, and necessary backup servers.

Security and Stability

Internet Service Providers are specialists on web hosting. Expect their servers to have more than 99% up time, the latest software patches, and the best virus protection.

Things to Consider

24-hour support

Make sure your Internet service provider offers 24-hours support. Don't put yourself in a situation where you cannot fix critical problems without having to wait until the next working day. Toll-free phone could be vital if you don't want to pay for long distance calls.

Daily Backup

Make sure your service provider runs a secure daily backup routine, otherwise you may lose some valuable data.

Traffic Volume

Study the provider's traffic volume restrictions. Make sure that you don't have to pay a fortune for unexpected high traffic if your web site becomes popular.

Bandwidth or Content Restrictions

Study the provider's bandwidth and content restrictions. If you plan to publish pictures or broadcast video or sound, make sure that you can.

Email Capabilities

Make sure your provider fully supports the email capabilities you need. (You can read more about email capabilities in a later chapter)

Front Page Extensions

Make sure your provider fully supports FrontPage server extensions if you plan to use FrontPage to develop your site.

Database Access

Make sure your provider fully supports the database access you need if you plan to use databases from your site. (You can read more about database access in a later chapter)

Hosting and Domain Names

A Domain Name is a unique name for your web site.

Choosing a hosting solution should include domain name registration.

Your domain name should be easy to remember and easy to type.

What is a Domain Name?

A domain name is a unique name for a web site, like microsoft.com and w3schools.com.

Domain names must be registered. When domain names are registered they are added to a large domain name register, and information about your site - including your internet IP address - is stored on a DNS server.

DNS stands for Domain Name System. A DNS server is responsible for informing all other computers on the Internet about your domain name and your site address.

Registering a Domain

Domains can be registered from domain name registration companies such as http://www.dotdnr.com.

These companies provide interfaces to search for available domain names and they offer a variety of domain name extensions that can be registered at the same time.

Domain Name Registration provides registration services for .com .net .org .biz .info .us .nu .ws .cc and .tv domains.

Newer domain extensions such as .biz .info and .us have more choices available as many of the popular domains have yet to be taken. While .com and .net domains are well established and recognized, most popular domains with these extensions are already registered.

Choosing Your Domain

Choosing a domain is a major step for any individual or organization.

While domains are being registered at a record, new domain extensions and creative thinking still offer thousands of excellent choices. When selecting a name it is important to consider the purpose of a domain name, which is to provide people an easy way to reach your web site. The best domains have the following characteristics:

Short - People don't like to type! The shorter your domain, the easier it is to reach and the less are the chance the user will make a typographical error while typing it.

Meaningful - A short domain is nothing without meaning, 34i4nh69.com is only 8 characters long but would not be easy to enter or remember. Select a domain that relates to your site in a way that people will understand.

Clear - Clarity is important when selecting a domain name. You should avoid selecting a name that is difficult to spell or pronounce. Also, pay close attention to how your domain sounds and how effectively it can be communicated over the phone.

Exposure: Just like premium real-estate on the ground that gets the most exposure, names that are short and easy to remember are an asset. In addition to humans viewing your domain, you should consider search engines. Search engines index your site and rank it for relevance against terms people search for online. In order to maximize your sites exposure, consider including a relevant search term in your domain. Of course, this should only be considered if it still maintains a short, clear and meaningful domain.

Sub Domains

Most people are unaware but they already use sub domains on a daily basis. The famous "www" of the World Wide Web is the most common example of a sub domain. Sub domains can be created on a DNS server and they don't need to be registered with a domain registrar, of course, the original domain would need to be registered before a sub domain could be created. Common examples of sub domains used on the internet are http://store.apple.com and http://support.microsoft.com.

Sub domains can be requested from your web hosting provider or created by yourself if you manage your own DNS server.

False Domain Names - Directory Listings

Some providers will offer you a unique name under their own name like:  www.theircompany.com/yourcompany/

This is not a real domain name, it is a directory - and you should try to avoid it.

These URLs are not desirable, especially for companies. Try to avoid them if you can afford to register a domain. Typically these are more commonly used for personal sites and free sites provided by your ISP, you may have seen www.theircompany.com/~username as a common address, this is just another way to share a single domain and provide users their own address.

Open competition in domain name registration has brought about a dramatic decrease in pricing so domain sharing is far less common since people can register their own domains for only $15 per year.

Expired Domains

Another source for domain registrations is expired domains. When you register a domain, think of it as a rental, assuming there are no legal or trademark issues with the domain name, you are free to use it as long as you continue to pay the yearly fee (you can now also register in advance as many as 10 years). Some people register domains as speculators, hoping that they can later sell them, while others may have planned to use a domain and never had the time. The result is that domains that were previously registered regularly become available for registration again. You can see, and search through a list of recently expired domains for free at http://www.dotdnr.com. If you wish to register an expired domain you pay the same fee as you would for a new registration.

Use Your Domain Name

After you have chosen - and registered - your own domain name, make sure you use it on all your web pages and on all your correspondence, like email and traditional mail.

It is important to let other people be aware of your name, and to inform your partners and customers about your web site.

DotDNR offers .com .net .org .ws .cc and .tv domains for as little as $15 per year.

In addition, you can transfer your domain to DotDNR and add a full year to your existing registration for only $15. Save $20 or more over other major registrars.

International domain name registration is also offered.

www.dotdnr.com

Hosting Capacities

Make sure you get the disk space and the traffic volume you need.

How Much Disk Space?

A small or medium web site will need between 10 and 100MB of disk space.

If you look at the size of HTML pages, you will see that the average size is very small. Maybe even smaller than 1KB. But if you look at the size of the images (button, gif, banner, jpg) used inside the pages, you will often find images many times larger than the page itself.

Expect each HTML page to take up between 5 and 50KB of disk space on your web server, depending on the use of images or other space consuming elements.

If you plan to use lots of images or graphic elements (not to mention sound files or movies), you might be needing much more disk space.

Make sure that you know your needs before you start looking for your web host.

Monthly Traffic

A small or medium web site will consume between 1GB and 5GB of data transfer per month.

You can calculate this by multiplying your average page size with the number of expected page views per month. If your average page size is 30KB and you expect 50,000 page views per month, you will need 0.03MB x 50,000 = 1.5GB.

Larger, commercial sites often consume more than 100GB of monthly traffic.

Before you sign a contract with a host provider, make sure to check this:

• What are the restrictions on monthly transfer
• Will your site be closed if you exceed the volume
• Will you be billed a fortune if you exceed the volume
• Will my future need be covered
• Is upgrading a simple task

Connection Speed

Visitors to your web site will often connect via a modem, but your host provider should have a much faster connection.

In the early days of the Internet a T1 connection was considered a fast connection. Today connection speeds are much faster.

1 byte equals to 8 bits (and that's the number of bits used to transport one character). Low speed communication modems can transport from about 14 000 to 56 000 bits per second (14 to 56 kilobits per second). That is somewhere between 2000 and 7000 characters per second, or about 1 to 5 pages of written text.

One kilobit (Kb) is 1024 bits. One megabit (Mb) is 1024 kilobits. One gigabit (Gb) is 1024 megabits.

These are connection speeds used on the Internet today:

Before you sign up a contract with any hosting provider, surf some other web sites on their servers, and try to get a good feeling about their network speed. Also compare the other sites against yours, to see if it looks like you have the same needs. Contacting some of the other customers is also a valuable option.

Hosting Email Services

Hosting services should include proper Email Accounts and Email Services.

Email Accounts

Hosting solutions should include email accounts for each person in your company. Email addresses should appear like this:

peter@mycompany.com

paul@mycompany.com

mary@mycompany.com

Most common is to use first name or first initial and last name.

POP Email

POP stands for Post Office Protocol. POP is a standard client/server protocol for sending and receiving email.

The emails are received and held on your internet server until you pick it up with a client email program, like Outlook, Outlook Express, Netscape Messenger, etc. POP email programs are built into Netscape and Internet Explorer browsers (i.e. Microsoft Outlook Express).

IMAP Email

IMAP stands for Internet Message Access Protocol. IMAP is another standard protocol for sending and receiving email.

The emails are received and held on your internet server until you pick it up with a client email program, like Outlook, Outlook Express, Netscape Messenger, etc.

IMAP represents an improvement over POP because email stored on an IMAP server can be manipulated from several computers (a computer at home, a workstation at the office, etc.) without having to transfer messages back and forth between computers. POP was designed to support email access on a single computer.

Web-based Email

Web-based email services enable you to access email via a web browser. You log into your email account via the Web to send and retrieve email. Being able to access your email from any browser anywhere in the world is a very attractive option.

Examples of web-based email services are Yahoo! Mail and Hotmail.

Email Forwarding

Email forwarding allows you to have multiple email personalities.

With email forwarding, you can setup aliases for other email accounts like

postmaster@mycompany.com should be forwarded to peter@mycompany.com

sales@mycompany.com should be forwarded to mary@mycompany.com

Mailing Lists

Some service providers offer mailing list capabilities. This is a valuable plus if you plan sending out email to a large number of users.

Web Hosting Server Technologies

This section describes some of the most common hosting technologies.

Windows Hosting

Windows hosting means hosting of web services that runs on the Windows operating system.

You should choose Windows hosting if you plan to use ASP (Active Server Pages) as server scripting, or if you plan to use a database like Microsoft Access or Microsoft SQL Server. Windows hosting is also the best choice if you plan to develop your web site using Microsoft Front Page.

Unix Hosting

Unix hosting means hosting of web services that runs on the Unix operating system.

Unix was the first (original) web server operating system, and it is known for being reliable and stable. Often less expensive than Windows.

Linux Hosting

Linux hosting means hosting of web services that runs on the Linux operating system.

CGI

Web pages can be executed as CGI scripts. CGI scripts are executables that will execute on the server to produce dynamic and interactive web pages.

Most Internet service providers will offer some kind of CGI capabilities. And many will offer preinstalled, ready to run, guest-books, page-counters, and chat-forums solutions written in CGI scripts.

The use of CGI is most common on Unix or Linux servers.

ASP - Active Server Pages

Active Server Pages is a server-side scripting technology developed by Microsoft.

With ASP you can create dynamic web pages by putting script code inside your HTML pages. The code is executed by the web server before the page is returned to the browser. Both Visual Basic and JavaScript can be used.

ASP is a standard component in Windows 95,98, 2000, and XP. It can be activated on all computers running Windows.

Many web hosting providers are offering ASP, as it is becoming a more and more popular technology.

If you want to learn more about ASP, please visit our ASP tutorial.

Chili!Soft ASP

Microsoft's ASP technology runs only on Windows platforms.

However, Chili!Soft ASP is a software product that allows ASP to run on UNIX and some other platforms.

JSP

JSP is a server-side technology much like ASP developed by Sun.

With JSP you can create dynamic web pages by putting Java code inside your HTML pages. The code is executed by the web server before the page is returned to the browser.

Since JSP uses Java, the technology is not restricted to any server-specific platform.

FrontPage

FrontPage is a very common web site design tool developed by Microsoft.

FrontPage allows users to develop a web site without any deep knowledge of web development. Most Windows hosting solutions support FrontPage server extensions for users that use FrontPage to develop their web site.

If you plan to use FrontPage, you should look for a Windows hosting solution (meaning not Unix / Linux).

PHP

Just like ASP, PHP is a server-side scripting language which allows you to create dynamic web pages by putting script code inside your HTML pages. The code is executed by the web server before the page is returned to the browser.

Cold Fusion

Cold Fusion is another server-side scripting language used to develop dynamic web pages.

Cold Fusion is developed by Macromedia.

Secure Server

A secure server can transmit data encrypted.

If you plan to do online credit card transactions, or other types of web communication that needs to be protected against unauthorized access, your web host must provide a secure server.

Web Hosting Database Technologies

MS SQL Server or Oracle for high traffic database-driven web sites.

MySQL for low-cost database-access.

MS Access for low traffic web sites.

Web Databases

If your web site needs to update large quantities of information via the web, you will need a database to store your information.

There are many different database systems available for web hosting. The most common are MS Access, MySQL, SQL Server, and Oracle.

Using the SQL Language

SQL is the language for accessing databases.

If you want your web site to be able to store and retrieve data from a database, your web server should have access to a database-system that uses the SQL language.

SQL Server

Microsoft's SQL Server is one of the most popular database software for database-driven web sites with high traffic.

SQL Server is a very powerful, robust and full featured SQL database system.

Oracle

Oracle is also a popular database software for database-driven web sites with high traffic.

Oracle is a very powerful, robust and full featured SQL database system.

Access

When a web site requires a simple database, Microsoft Access can be a solution.

Access is not well suited for very high-traffic, and not as powerful as Oracle or SQL Server.

MySQL

MySQL is also a popular database software for web sites.

MySQL is an inexpensive alternative to the expensive Microsoft and Oracle solutions.

Web Hosting Types

Hosting can be FREE, SHARED or DEDICATED.

Free Hosting

Some service providers offer free web hosting.

Free web hosting is best suited for small sites with low traffic, like family sites or sites about hobbies. It is not recommended for high traffic or for real business. Technical support is often limited, and technical options are few.

Very often you cannot use your own domain name at a free site. You have to use a name provided by your host like http://www.freesite/users/~yoursite.htm. This is hard to type, hard to remember, and not very professional.

Shared (Virtual) Hosting

Shared hosting is very common, and very cost effective.

With shared hosting, your web site is hosted on a powerful server along with maybe 100 other web sites. On a shared host it is common that each web site have their own domain name.

Shared solutions often offer multiple software solutions like email, database, and many different editing options. Technical support tends to be good.

Dedicated Hosting

With dedicated hosting your web site is hosted on a dedicated server.

Dedicated hosting is the most expensive form of hosting. The solution is best suited for large web sites with high traffic, and web sites that use special software.

You should expect dedicated hosting to be very powerful and secure, with almost unlimited software solutions.

Collocated Hosting

Collocation means "co-location". It is a solution that lets you place (locate) your own web server on the premises (locations) of a service provider.

This is pretty much the same as running your own server in your own office, only that it is located at a place better designed for it.

Most likely a provider will have dedicated resources like high-security against fire and vandalism, regulated backup power, dedicated Internet connections and more.

Your Checklist

Before you choose your web host, make sure that:

• The hosting type suits your current needs
• The hosting type is cost effective
• Upgrading to a better server is a possible solution
• If needed, upgrading to a dedicated server is possible

Before you sign up a contract with any hosting provider, surf some other web sites on their servers, and try to get a good feeling about their network speed. Also compare the other sites against yours, to see if it looks like you have the same needs. Contacting some of the other customers is also a valuable option.

Web Hosting E-Commerce

If you are selling a product or a service, e-commerce might be a smart way to do business.

Internet Commerce

E-Commerce is about selling products or services over the Internet.

If you are selling a product or a service, e-commerce might be a smart way to do business. Over the Internet you can reach a large number of customers.

E-Commerce Systems

It is not a very good idea to build your own e-commerce system. Some (larger) companies might do it, but we will not recommend it if you run a smaller business. Building an e-commerce system is a complicated process, with the potential for a lot of errors.

You might buy a ready-to-use system and run it on your own server. Many systems are available on the market today, and most of them will cover your basic needs for order management and processing. But again, if you are not familiar with hosting your own web site, starting with an e-commerce site is not the right thing.

The best solution, in our opinion, is to find a hosting provider that offers an e-commerce solution.

Hosting Providers

E-commerce covers a very huge range of products. With different hosting providers you will find anything from very simple to very complex solutions.

Most providers will offer a simple and inexpensive solution that allow you to run your own "virtual store".

Your Checklist

• How does it handle customers?
• How does it handle product catalogs?
• How does it handle orders?
• How does it handle inventory?
• How does it handle back orders?
• How does it handle shipment?
• How does it handle accounts?
• How does it handle billing?
• How does it handle payment?
• How does it handle foreign currency?
• How does it handle credit cards?
• How does it handle taxes?
• How does it handle security?
• How does it handle integrity (encryption)?

Also check if the most time-consuming tasks are automated. Look for automated billing, invoice handling, accounting, and report generation.

Before you sign up a contract with any hosting provider, surf some other e-commerce sites on their servers. Find out how it works. Actually try some shopping and see if you get a good feeling. Also compare the other sites against yours, to see if it looks like you have the same needs. Contacting some of the other customers is also a valuable option.

Tax Issues

Taxes is a complex issue for most on-line stores. Especially VAT (Value Added Tax).

If you are selling on-line, you will most likely be in the export business.

Trading with different countries is easy, but tax issues might be tricky. Exporting goods may not be the subject of VAT in your country, but often your customers will have to pay their local VAT when they pick up the goods.

In addition, there will be the issue of income tax for your shop, depending on how you report your income from sales.

Before starting an on-line store, be sure to consult your tax adviser.

Now I may get a chance to compare the .net technologies with java technologies. Hopefully my journey in  will be exciting.

• We are seeking an outstanding software engineer to join our Production technical support team. This software engineer will be responsible for troubleshooting and remediating customer-encountered problems in our web based application, primarily during European business hours.

Main responsibilities include:

• Initial investigation and reproduction of client issues, including but not limited to functional, analytical, data and infrastructure tickets.
• Escalation to the core software development team: analyzing which functionality is most likely to be causing the problem and passing the issue to the appropriate developers who are responsible for that area.
• Development of short-term solutions or work-arounds for problems and communicating them to Customer Support and/or IT
• Maintenance of production knowledge base
• The candidate must have strong communications, interpersonal, and software development skills.

Mandatory Requirements:

• Several years of Java programming experience.
• One or more scripting languages such as Ruby or Perl
• Familiarity with Microsoft SQL Server
• Good knowledge of statistics
• High degree of motivation, with strong verbal and written communications skills and ability to learn quickly

Desirable Skills:

• Web application development technologies, especially Apache, Tomcat, JSP, JavaScript.
• Networking (FTP, TCP/IP protocols etc.)
• Knowledge of financial engineering

laszlo_spiller@kellyservices.hu

Using IBM RSA 7.0

1.Create  a new dynamic web project with Struts support

2.Add dojo toolkit to project

Dojo toolkit can be obtained from:http://download.dojotoolkit.org/release-1.1.1/dojo-release-1.1.1.tar.gz

Details about Adding explained using screenshot

That means its included in the Webcontent. You can see tons of warning messages caused by silly test html pages inside the toolkit folder,just search around and delete the stuff. Basically it has nothing to do with a struts controller or so.But I just tried using jsp pages,instead of html just to check if we can include toolkit with no problems in the jsp page.

Things to notice.

.Struts link the property of element in the form with form bean.

Like:

<html:text property="beanprop"></html:text>

Here beanprop is one property in the  form bean.

Here after succesfully deploying the code will be like

<input type="text" name="beanprop" size="20">    in the html file we are viewing.

Now getting into details:

My JSP page:index.jsp  >> Index.jsp

Here instead of putting property attribute in the text field element ,i have used name because if you are using property here in this jsp page ,your dojo parser wont recognise the tag and the purpose for introducing dojo is defeated.

So our aim is to:

1.retain the dojo functionality

2.Obtain the value from page to formBean

My widget is specified like:

<input type="text" id="use" name="username" size="30"
dojoType="dijit.form.ValidationTextBox"
required="true"
promptMessage="Enter username"
invalidMessage="Username is required."
onchange="user()"
/>

Here look at the name attribute its username,which is same as my bean property :) and your problem  is solved.The tag itself is self explainatory:

dojoType="dijit.form.ValidationTextBox" <<Causes dojo parser to recognise it as a ValidationTextbox having validation features included to normal textbox

required="true" specifies whether field is required( Hurray!U guessed;It helps the parser to recognise whether validation is enabled).(But that alone is not sufficient(We have to specify a regExpression or rule to accept the textbox value)

promptMessage="Enter username" is the prompting message on clicking the form element it will be visible

invalidMessage="user()" causes a javascript function user() to be called when text changes in text field.

So inorder to make this all happen,we have to include

<script type="text/javascript"
src="dojo-release-1.1.1/dojo/dojo.js"
djConfig="parseOnLoad: true"></script>
<script type="text/javascript">
dojo.require("dojo.parser");
dojo.require("dijit.form.ValidationTextBox");
</script>

inside your header

Tells dojoParser to load on document load and  parse the html before display

and dojo.require("dijit.form.ValidationTextBox") tells parser that  dijit.form.ValidationTextBox is used in the page here,index.html

Output screen

Now if you have skipped the field this will be the result (beware)

Además la presentadora Azucena Valdés y Juan Manuel Ruiz departieron de la temas de actualidad como es el 11º Congreso Socialista de Cantabria o las declaraciones del Secretario General de NNGG donde tachaban de anticuados a los socialistas, palabras que recordaron al Secretario de JSP que el Sº General de NNGG hace una autentica política dictatorial en el seno de NNGG al no dejar aparecer a la palestra a ningún miembro de NNGG que no sea el mismo, al contrario de Antonio Bezanilla Sº General de JSC, quien fomenta la diversidad de opiniones.

La entrevista duro alrededor de 25 minutos, siendo la primera vez que un integrante bien de JSP o Psoe Polanco asistía al plato.

JSP quiere agradecer a AQUITV y en especial a Azucena Valdés el interés que han mostrado por los temas relacionados al municipio de Polanco.

Muchas gracias

Senior Software Engineer (Java)

Position Summary:

As a key figure in an international engineering team, you will be responsible for

• Requirements gathering, systems analysis, design and build/implementation of 3 tier Java technology solutions which support worldwide premium products. ( The services involved with support revenue generation from external customers in multiple countries and time zones. )
• Hands on development, there is a significant proportion of the role required to provide internal consultat