Benipal Technologies
Location: Bangalore
Experience: 4-6 Years
Education: Graduates, MCA, M.Sc
Skills: JAVA J2EE, XML, STRUTS, HIBERNATE, SOAP,
WALK IN INTERVIEWS ON SATURDAY, NOV 21 from 12pm – 5 pm and SUNDAY, NOV 22 from 12 pm – 5 pm.

DESIRED CANDIDATE PROFILE:

Must have a Bachelors degree with any specialization. Preference will be given to M.Sc and MCA degrees. Excellent spoken engish is an absolute must with good presentation skills.

Ability to perform under pressure will be a critical factor.

Contact Details:

Benipal Technologies

28 5th Block 4th B Cross Koramangala Industrial Layout Bangalore, India 560095

Tel: 080-3026-8000

The Apache Struts Project is the open source community that creates and maintains the Apache Struts framework. The project consists of a diverse group of volunteers who share common values regarding collaborative, community-based open source development. The Apache Struts Project is proud to share these values with our parent organization: The Apache Software Foundation. The project is called “Struts” because the framework is meant to furnish the “invisible underpinnings” that support professional application development. Struts provides the glue that joins the various elements of the standard Java platform into a coherent whole. Our goal is to leverage existing standards by producing the missing pieces we need to create enterprise-grade applications that are easy to maintain over time.

The Apache Struts Project offers two major versions of the Struts framework. Struts 1 is recognized as the most popular web application framework for Java. The 1.x framework is mature, well-documented, and widely supported. Struts 1 is the best choice for teams who value proven solutions to common problems.

Struts 2 was originally known as WebWork 2. After working independently for several years, the WebWork and Struts communities joined forces to create Struts 2. The 2.x framework is the best choice for teams who value elegant solutions to difficult problems.

Visit http://www.fortunetechnol.com/index.html and http://www.train4job.com/ for online training. 10% off for this month, for people who register for training with Fortune Technologies.

10% discount on our list price for all the online training listed on our website.

This morning I learned how to get a datetimepicker working in a Struts 2.1 application.

Firstly, the dojo library needs to be added to the project, so add the following to your pom.xml:

<dependency>
        <groupId>org.apache.struts</groupId>
        <artifactId>struts2-dojo-plugin</artifactId>
        <version>2.1.8</version>
    </dependency>

Next add the dojo tags library to the JSP pages that need it:

<%@taglib prefix="sx" uri="/struts-dojo-tags" %>

And reference it from your form:

            <sx:datetimepicker label="Expires" name="expiryDate" value="expiryDate" displayFormat="yyyy-MM-dd" labelSeparator="" labelposition="left" />

Take notice of the following points from http://struts.apache.org/2.x/docs/datetimepicker.html:

• The head tag must be included on the page, which can be configured for performance or debugging purposes.
• If the parseContent parameter for the head tag is false (it is false by default), then the id tag is required.

The bit I missed at first is that the head tag that must be included is the one from the plugin, not just the normal struts one, so I end up with:

        <s:head />
        <sx:head />

Yesterday I got Struts working in separate sub folders of my domain.
The reason for wanting to do this is so that Spring Security can require specific roles to access the contents of those folders – and this is how I did that.

The simple bit is protecting the folder, by adding the /admin URL pattern to the applicationContext.xml:

    <security:http>
        <security:intercept-url pattern="/login.jsp" filters="none" />
        <security:intercept-url pattern="/bare/**" filters="none" />
        <security:intercept-url pattern="/**" access="ROLE_USER" />
        <security:intercept-url pattern="/admin/**" access="ROLE_ADMIN"/>
        <security:form-login login-page='/login.jsp' default-target-url='/index.action' always-use-default-target='true' authentication-failure-url="/login.jsp?error=true" login-processing-url="/j_security_check" />
        <security:logout/>
        <!--<remember-me/>-->
    </security:http>

That’s all that’s needed to protect the folder, but it would be a pretty poor UI that invites users to do things that they aren’t allowed to do – so I wanted to change the links to the admin area to only be displayed if the user is in the ROLE_ADMIN role.
Firstly I had to add the Spring Security taglib to my project by changing the maven pom.xml:

<dependency>
    <groupId>org.springframework.security</groupId>
    <artifactId>spring-security-taglibs</artifactId>
    <version>2.0.4</version>
</dependency>

Then in my jsp file (which happened to be the main decorator jsp file) I use the taglib:

<%@taglib prefix="sec" uri="http://www.springframework.org/security/tags" %>
...
                    <sec:authorize ifAllGranted="ROLE_ADMIN">
                        <li><a href="users-list.action">Users</a></li>
                    </sec:authorize>
...

Bem, para quem for começar a estudar algum framework sobre a programação JAVA, aconselho que seja um framework conhecido e que possua uma boa documentação ensinando os passo que tenha que ser seguidos. Do contrário, se tornará uma missão quase impossível ou inviável.

Mas, vamos primeiro explicar o que seria Framework, e de acordo com (Oliveira, 2005) em seu artigo – O Universo dos Frameworks Java:

uma solução para um conjunto de problemas em comum, com uso de classes e interfaces, que disponibilizam objetos com capacidade de capturar funcionalidades comuns a várias aplicações.

Aquém estaram dispostos alguns frameworks que considero ser bons o bastante para qualquer aventureiro que deseje se enveredar, tendo em vista que os links em amostras nos nomes dos selecionados são oficializados, não limita que seja buscados outros, porém fica a critério e risco de cada que assim optar.

Frameworks sugeridos:

Struts – um dos mais usados em ambientes corporativos para construção de aplicações web. Usa o modelo MVC e caracterizado por uma camada de controle com uso de J2EE e XML (Oliveira, 2005).

JSF – JavaServe Faces – JavaServer (TM) Faces simplifica a criação de interfaces de usuário. Os desenvolvedores de vários níveis podem construir rapidamente aplicações web por: montagem de componentes reutilizáveis de interface do usuário em uma página, permitindo a conexão desses componentes com uma fonte de dados de aplicação e cliente fiação eventos gerados para o servidor-manipuladores de eventos secundários.(javaserverfaces: JavaServer Faces Community)

MyFaces – é uma implementação do JavaServer (TM) Faces (JSR 127), uma estrutura nova e futurística de aplicação web que exerce o MVC. Possui características e conceitos que estão além do Struts. (Open Source Web Frameworks in Java)

Tapestry – é um framework open-source para dinâmicos, robustos, e altamente escalável de criar aplicações web em Java. Tapestry complementa e reforça o padrão Java Servlet API, e assim que funciona em qualquer servlet container ou servidor de aplicação (Apache Tapestry – Welcome to Tapestry)

WebWork – é um web Java-framework de desenvolvimento de aplicativos. É construído especificamente com a produtividade do desenvolvedor e simplicidade de código em mente, oferecendo suporte robusto para a construção de modelos reutilizáveis de interface do usuário, tais como controles de formulário, temas IU, internacionalização, mapeamento dinâmico de parâmetros de formulário para JavaBeans, cliente robusto e validação do lado do servidor, e muito mais. (WebWork – WebWork)

Spring Framework – Spring aborda preocupações mais com a infra-estrutura de aplicações típicas. Vai a lugares que outros frameworks não vai. (The ServerSide – Enterprise Java Community)

A petición de un par de amigos del tecnológico voy a publicar un ejemplo de como desarrollar una aplicación web utilizando el framework de struts 1.x, en este caso solo pondré ejemplos básicos con la finalidad de hacer fácil la comprensión de la forma en que trabaja struts. Como en todos lo cursos vamos a empezar con un poco de teoría para que cuando llegue el momento de los códigos todo sea mas simple de entender. Trataré de publicar cada una de las partes cada semana, así es que empecemos con la primera.

Que es y para que utilizar struts?

Struts es un framework (marco de trabajo) que trabaja bajo la plataforma J2EE e implementa la arquitectura MVC, que nos permite ahorrar tiempo durante el desarrollo de nuestras aplicaciones web, ademas de organizar nuestro proyecto separando la lógica de negocio de la vista.

MVC en struts

Las tres capas con las que se trabaja bajo esta arquitectura son modelo, vista y controlador. La manera de que struts la implementa es la siguiente:

Modelo: En esta capa es donde se encuentra la logica de negocio, en otra palabras es toda la parte funcional de nuestra aplicacion. El modelo esta formado por tres tipos de clases:

DTO (Data Transfer Object): Estas clases nos sirven para encapsular la información en objetos, y poder transferirla entre las demás clases.

DAO (Data Access Object): La funcionalidad de este tipo de clases es acceder a una fuente de datos, realizando consultas, inserciones,actualizaciones, y todo lo demás.

BO (Bussines Object): En este tipo de clases realizamos realmente la lógica de negocios, cálculos, etcétera.

Vista: Esta capa la forman las JSP, las hojas de estilos; para formar las pantallas de los usuarios finales.

Controlador: Ya tenemos la parte de la vista y el modelo, pero falta comunicarlos y esto es la función de la capa controlador, esto se realiza a través de clases Action o DispatchAction.

Creo que con esto es suficiente para empezar a entender como funciona struts, a partir del siguiente post empezare a colocar un poco de códigos de ejemplo.

It’s quite common to want to highlight errors in a form entry like this:

This should just be a case of setting the appropriate style, but unfortunately struts doesn’t apply a class to the containing DIV that can be used for that.
As an example, the HTML for the form shown above is (reformatted):

<form id="system-update" name="system-update" onsubmit="return validateForm_system-update();" action="..." method="post"  onreset="clearErrorMessages(this);clearErrorLabels(this);" >
    <input type="hidden" name="systemId" value="Trapdoor" id="system-update_systemId"/>
    <div id="wwgrp_system-update_name" class="wwgrp">
        <span id="wwlbl_system-update_name" class="wwlbl">
            <label for="system-update_name" class="label">        Name</label>
        </span>
        <span id="wwctrl_system-update_name" class="wwctrl">
            <input type="text" name="name" value="Trapdoor" id="system-update_name"/>
        </span>
    </div>

    <div id="wwgrp_system-update_type" class="wwgrp">
        <div id="wwerr_system-update_type" class="wwerr">
            <div errorFor="system-update_type"    class="errorMessage">
                You must enter a value for the system type.
            </div>
        </div>
        <span id="wwlbl_system-update_type" class="wwlbl">
            <label for="system-update_type" class="errorLabel">        System Type</label>
        </span>
        <span id="wwctrl_system-update_type" class="wwctrl">
            <input type="text" name="type" value="" id="system-update_type"/>
        </span>
    </div>

    <div id="wwgrp_system-update_0" class="wwgrp">
        <span id="wwlbl_system-update_0" class="wwlbl">
            <label for="system-update_0" class="label"><br></label>
        </span>
        <span id="wwctrl_system-update_0" class="wwctrl">
            <input type="submit" id="system-update_0" value="Save"/>
        </span>
    </div>
</form>

What we need to do is set a style on the “wwgrp_system-update_type” DIV, which is identifiable as the parent of a DIV of class “werr” and the parent of a SPAN containing a LABEL of class “errorLabel”, but otherwise has no identifying class.

The solution is a simple bit of javascript:

function errorHighlightHandler()
{
    var s = document.getElementsByTagName('label');

    var str = '';
    for(var i=0;i<s.length;i++)
    {
        if( s[i].className == 'errorLabel' )
        {
            str+=s[i].parentNode.parentNode.className+'  ';
            s[i].parentNode.parentNode.className += ' errorContainer';
        }
    }
}

window.onload = errorHighlightHandler;

Just add a SCRIPT tag to include that in your HTML and the containing DIV will have a class you can style.
Here’s the result as seen in Firebug, showing the dynamic class applied to the DIV:

Caveat: This works for round-trip validation, if you use AJAX validation you may need to hook something other than window.onload to run the script.

DSRC requires Software Professionals (Walk-In Interviews)

Looking for dynamic Software Professionals for the following skills:

— Java – Technical Architect:
a). 7-10 years experience in J2EE Design and Architecture, UML, OOAD, Design Patterns, EJB, Struts, JSP, EJB, JDBC, JNDI, Web Services, Weblogic App Server
b). Struts Framework, Jakarta Tiles framework, Hibernate, Spring Framework, Eclipse 3.0, Solaris 9, Rational ClearCase, Rational ClearQuest, Oracle Database
c). Knowledge of SOA & SCA. Sun Certification Enterprise Architect would be preferred
— Mainframe-Developers / Sr. Developers : 3-8 years experience with extensive Real Time Project experience in COBOL, JCL, VSAM, CICS, DB2, IMS DB/DC, ASSEMBLER, PL/I

Walk-In on 31st October, 2009 between 9 am and 7 pm at:

Quality Inn Centurian Hotel
Opposite to Akaswani, Shivaji Nagar, Pune -411 005
Tel: 020 25510600
Fax:020-2552 0400

If you are unable to come on the above date, please forward your resume to jobs@dsrc.co.in

(preguiça de escrever)

Our client in SAN MATEO, CA,  is looking for a SENIOR WEB DEVELOPER for front-end development of next generation data modeling and visualization tools.  The ideal candidate would have expertise in front end development of complex Rich Internet Applications (RIA) and have demonstrated the ability to develop high quality enterprise software in a dynamic environment.

Responsibilities

• Develop front end of Rich Internet Applications for Java-based server products
• Analyze functional requirements and specifications through close interaction with Product Management and other team members
• Participate in product design and architectural discussions
• Write unit tests to ensure developed user interfaces meet product requirements
• Provide support to the QA and support organizations
• Provide feedback and guidance to technical writers
• Develop appropriate documentation for architectural, design, implementation and test activities.

Required Skills

• Bachelor’s degree in Computer Science (or related field of study)
• Minimum of 6 years experience with front end development of Web-based user interfaces
• Minimum of 2 years experience with front end development of rich internet applications (RIA)
• Expertise in building applications using the following technologies:  Flex 3/4, Flash Action Script, HTML, DHTML, JavaScript, JSON, CSS
• Experience with the following tools: Maven, ANT, Subversion, CVS
• Familiar with cross browser support issues and solutions as well as i18n issues and solutions
• Experience doing software development in a structured, automated, and distributed development environment including design, development, QA, and documentation.
• Strong communication skills with the ability to present technical concepts concisely to non-technical members of the team.

Nice to Have:

• Familiarity with existing data modeling tools is a plus: ER/Studio ERWin, TOAD
• Experience in building applications using any of the following technologies is a plus: JSP, Struts, JavaScript, JQuery, SEAM, GWT, Rich Faces, extjs, XML/XSLT, AIR

If you are interested, please send us your resume to raj@mindsource.com.

for example:

SampleAction extends DispatchAction {
String username=”"; //yep instance variable
//And scope of this action is set to session  in StrutsConfig.xml
public ActionForward Go(ActionMapping mapping, ActionForm form,
HttpServletRequest request, HttpServletResponse response)
throws Exception {
username=formbean.getUserName();

//now based on this “username” retrieve all the details from db
//and forward it to view…

//If multiple users are logged in and accessing this action..
//each user may see different results..since the username is
//declared as an instance variable..there is no guarantee that
//the details of the user that he requested will be displayed..
//for example if userA and userB are logged in at the same time
//then corresponding user details are displayed ontheir screen..
// there might be
//a chance where userA sees the details of userB or ViceVersa..
//This bug is difficult to identify..only when one user logs in
//and views his details..
//And the reason for that is simple..the actions in struts are
//not thread safe..
// if u want to still declare..them as instance variables..
//then make sure..that it is synchornized..
// If u still ignore it..be ready for some sleepless nights
//in your office..with your collegues..

//But this type of problem u may not encounter with Spring..
//since by default..actions are singleton in nature..
}
}

My little car- Ford Focus ZX3, has had a pounding! The daily drive over our little “off road” path to get to camp has taken its toll on my little girl car. Not to mention- becoming a farm car was not her idea of being cute and pretty!

She didn’t realize that hauling chicken compost, hay, tools were in the works for her. She didn’t mind getting muddy or going off road, because she’s a tom-boy car, and likes to challenge herself. But her aching joints are getting the best of her and need replacements.

Unfortunately, those replacements are about as much as she’s worth (to us anyways). So, we’ve bucked up and got a boy car! Super Sube!  A ‘94 Subaru Loyale with 4wd. So far, it is eating up the muddy roads, and we’ve taken it on 4wd roads, and it’s done well! Doesn’t particularly care for going up hill… but we’re going to try and work on that.

Passion for technology, working in agile teams, our developers build the application together with the business and testers. Our community is JEE oriented, and we all like cool new technologies. Using scrum in projects, we aim to be the best in helping out our custodes

Your passion:

As a developer, you will work as the technical leader in developing Enterprise Java software applications. In this you are responsible for the technical architecture and for steering a team of developers. You will translate functional specifications into a technical solution and monitor the quality of the application. You will also ensure that the application fits the client’s infrastructure.

As an Enterprise Java software developer, you will work on realizing software solutions. You will usually work on a project located at the client or at our in-house development center. Your focus is on designing and realizing advanced solutions interfacing with backoffice systems. You will work in a team with products such as BEA Weblogic Platform and IBM Websphere. As a software developer you will work as a designer as well as a constructor. You regard sharing knowledge with your colleagues as important.

Your profile:

Higher vocational or university education, preferably in IT/technical;

An ability to think analytically with a strong focus on results;

High potential and eager to learn;

Experience with Java, Enterprise Java and/or open source products (Struts, Spring, Hibernate, Tomcat, JBoss, MySQL, Ant, Maven, CVS, Eclipse) and knowledge of OO;

Experience with commercial application servers (IBM WebSphere, BEA Weblogic Server, Oracle application Server);

Highly motivated and prepared to invest in yourself;

Strong technological affinity;

2- 4 years experience in IT /Senior: > 4 years experience in IT.

Sincerely, Bob Morel

Talent Recruitment Manager

www.indahunt.com

Struts 2

Struts 2 is a web application framework that implements MVC design pattern, using Java. Why Struts ? The designers of software frameworks aim to facilitate software development by allowing architects and programmers to spend more time on meeting requirements rather than dealing with the more standard low-level details of providing a working system.

So, the best way to learn new things aggressively should be through practice & I’m going to learn how Struts 2 works with brief explainations & examples through http://struts2tutorial.sourceforge.net/. My aim is to create a Web 2.0 site by using Struts 2 framework, it is just for learning and training purposes. By the way, i will keep my learning progress up to date on my blog.

If you already have a Eclipse project with Struts2 , JPA and Spring running , it could be a hard time deploying it on Google App Engine ( GAE )

u have to start with downloading the GAE Java sdk and the  Eclipse Plugin for GAE . If should have been simple thereafter, but it is not….

1. Since GAE needs a folder with the name “war” which it can directly deploy, I was not able to use the Eclipse plugin.I first manually created the appengine-web.xml file which contains the application id and the version which is used by the GAE to upload the artifact to the server .
2. Then I used the command line tool to upload my stuff,  ”appcfg.cmd update PATH_TO_WAR_DIRECTORY” from the appengine SDK folder
3. It took me some time to have everything uploaded to the server.I thought that should be it, but it wasn’t the end
4. So now everything was uploaded to the GAE server, but the next problem was PersistenceAnnotationBeanPostProcessor. It uses “javax/naming/NamingException” Exception which is not supported by GAE.
5. So now, I will download the source of  PersistenceAnnotationBeanPostProcessor and try to remove this Exception with something to which GAE is nice and then try to upload everything.

Some links which helped me today

http://www.xaloon.org/blog/jpa-spring-wicket-google-app-engine

http://groups.google.com/group/google-appengine-java/web/will-it-play-in-app-engine?pli=1

Relationship http://code.google.com/appengine/docs/java/datastore/relationships.html

File upload Struts2 GAE http://whyjava.wordpress.com/2009/08/30/creating-struts2-application-on-google-app-engine-gae/

Spring + JPA http://objectuser.wordpress.com/2009/05/19/spring-jpa-in-google-app-engine/

Extra

http://groups.google.com/group/google-appengine-java/browse_thread/thread/187d41712ec1d394

http://groups.google.com/group/google-appengine-java/msg/8e82ae0ec21b6d07

Maven and GAE http://shalinsays.blogspot.com/2009/04/google-app-engine-and-maven.html , http://code.google.com/p/maven-gae-plugin/

So I’m taking this web apps course, where we’re making use of Apache Tomcat, J2EE, and generally learning how to employ the MVC framework in a modern web application (which we call “Fakebook”. Yeah I know, lollercoptorz, rite?). On the first three homework assignments, I have collectively received: 103, 100, 100. So I figured, on this fourth assignment (and with 34+ hours of built-up “penalty-less late time” with which to turn in the assignment), I had a little elbow room to experiment.

I decided to use the Struts2 and Hibernate frameworks.

Yeah, insane. Especially the latter, considering I have ZIP/ZERO/NADA/ZILCH experience with either one.

It took about a day to get the hang of how Struts organizes the MVC framework. The most difficult part, as usual, was setting up the XML configuration file. Luckily, it doesn’t require too many dependencies and is fairly straightforward to install and incorporate. It took another day to figure out the notion of Interceptors for the purpose of implementing authenticated resources, and also installing a database schema when the server was started.

Then came Hibernate. Holy Halloween, Batman.

This is seriously the most complex framework I have ever worked with. Each “module” beyond the core requires a heinous number of dependencies, some of which are optional, and woe is you if you mess them up. Supposedly v2.5 will incorporate a lot of the dependencies into a single package, but that’s still in Beta as of this post.

Maven can be effectively used to mitigate some of the difficulties in satisfying dependencies, but it’s still largely up to the user to figure out what packages are required if you want to use the Core, Search, or any of the other “modules.”

Once the dependencies are satisfied, then the real fun begins: configuring Hibernate.

The number of configuration options is mind-boggling; I feel like I’m installing Gentoo. I ended up making a post on StackOverflow when I reached a point where I could actually attempt flipping the “on” switch, and was greeted by cascading 50-level exceptions. The single response ended up being the right one (it was a simple “class” configuration option I thought wouldn’t have any effect, since – let’s face it – I have no idea what half the specified configuration options do, and the documentation isn’t much help), though it only revealed yet another exception.

Fixing that yielded another, and so on, and so on…literally at least a dozen more exceptions that were somewhat more straightforward, but revealed 1) just how little I knew how to use Hibernate, and 2) how so many different configuration options need to be perfectly specified for the damn thing to work.

But as of about an hour ago, I am proud to say that after three days of pouring through PDF documentation, Googling the hell out of phrases like “hibernate arrays” and “one-to-many hibernate exception” and “WHY WOULD ANYONE EVER USE HIBERNATE”, banging my head on the desk when the editor swore I had a phantom error in my XML config file, and satisfying concrete and transitive dependencies, my server BREATHED today by successfully executing an action within the Struts framework, which also contained a database access through Hibernate.

It’s WORKING. It’s ACTUALLY WORKING. HOLY CRAP. …and it’s due by 11:59pm tonight. WHEEE.

Also, I wanted to give a shout-out to my main man V² (my MacBook), for whom earlier this week I purchased a new battery after the previous one lasted 511 recharge/discharge cycles without ever offering less than 2+ hours of continuous use. Interestingly, the battery was beginning to bow outward (never a good sign) around the same time that OS X itself informed me that the battery needed to be replaced “soon”. So after more than three years and well over twice the average lifespan of these batteries, I dropped $130 on a new one.

V² paid for himself a long, long time ago. The new MacBook Pros are certainly the sexiest ones to hit the market so far, but this guy is a trooper. I purchased him in September of 2006, and the only expenditures I’ve had are a $150 mainboard/DVD drive/Bluetooth repair job, a $200 hard drive/RAM upgrade, and now a $130 battery replacement. Not too shabby at all for three years (and I didn’t even purchase the extended warranty!).

Anywho. Busy weekend ahead. I’ve had several more interviews, many of which have gone exceedingly well, and PhD and fellowship applications are going smoothly. Two big assignments due this week, lots of research work to be done over the weekend, and Cathryn will also be in town tomorrow night.

Senaste tiden har jag tänkt väldigt mycket på hur livet bäddas utav en själv och andra. Att man oftast hade ett val att göra som man i dagsläget  sällan kan göra ogjort. Inte att det alla gånger måste vara något negativt, (förstå mig rätt) men att man ibland önskar att valet man gjorde då var lite mer genomtänkt. Jag syftar i första hand inte på mitt liv just nu, fast visst har vi alla någon gång i våra liv suttit med facit efteråt och slagit oss för pannan? VAD TÄNKTE JAG PÅ?

I bakhuvudet finns det 2 jag syftar på. Inte det minsta lika varandra på något sätt, men båda vakna idag med insikten att de kunnat hantera situationen annorlunda. Varför man “väljer” att blunda, tolerera, tillåta och slutligen inte sätta ner sin fot vid ogillandet är för mig en gåta. Jag tror att det är så, då jag själv reagerar blixtsnabbt och agerar därefter. Inte alltid till det ultimata, men jag står för mina beslut, inser att valet gjordes utifrån min situation och jag gjorde vad jag ansett vara “bäst”. Och inser jag att det var på något sätt inte som jag avsett, kan jag försöka rätta till “problemet” och det är DET jag syftar på gällande de 2 exemplen.

Skall man inte någonsin svälja sin idiotiska “stolthet” (syftar på ex 1) och erkänna sitt misstag och våga gå vidare i sitt liv?

Och skall man invänta “rätt läge” ( ex 2) för att slutligen visa med hela handen att man fått nog?  I det sistnämnda lider jag  med henne då jag förstår rädslan för efterspelet som kan bli.

Jag har alltid gjort mina listor. Ställt upp med minus och plusspalter för att se helheten. Endast då tror jag man är riktigt ärlig mot sig själv och med den insikten kommer man betydligt längre än strutsmetoden som vissa föredrar.  Varför liksom vara olycklig/missnöjd när man kan säga ifrån, belysa problemet,  driva sin sak och så småningom om inte helt så kanske delvis få det bättre?

Course Outline:
 

• Core Java Round-up
• Introduction to Web Technologies
• Web Application Architecture, MVC
• End-to-end flow of HTTP request
• Eclipse Integrated Development Environment
• Servlets, Servlet Context, Filters
• JSP, Scriptlets, Expressions, includes, contexts
• JSP Tag Libraries, JSTL
• Struts 1.3, Introduction
• Struts Actions, Form Beans, Struts Validation
• Hibernate, OR Mapping Concepts, pooling
• JiBX, OX Mapping Concepts
• JavaScript, Element Selection, Form Submission
• JavaScript Events, Ajax, JSON
• JavaScript debugging with FireBug & Script Debugger
• Advanced JavaScript frameworks – JQuery, Mootools, ExtJS
• CSS, styles, selector, debugging with FireBug & Developer Toolbar
• Advanced tools – TamperIE, DebugBar, FireFox, ieHttpHeaders

Visit http://fortunetechnol.com/ to more about the training courses.

Java/J2EE is one of the most sought skill sets in the current job market. This course is targeted at audience who needs a jump-start on Web Development using Advanced Java/J2EE Technologies. The course covers a wide range of topics which spans the complete spectrum of Web Development using Java/J2EE. These include Servlets, JSP, Struts 1.3, and Hibernate & JiBX. Our unique syllabus makes sure that you gain knowledge not only in the Java Technologies, but also on other important supporting technologies such as Java script, CSS, JSON, XML and HTML. Also our course gives special focus on one of the most ignored, but extremely important skills: – effective debugging of Java script, CSS and Java code. We use a hands-on approach-based training methodology coupled with assignments which will enable the attendees to gain excellent exposure to the technology in an instructor-controlled atmosphere.

Med en god kopp kaffe, och söndagstidningarna på plats, är det en nyhet i dagens tidningar som lyfter pulsen något. “De omstridda tsunamibanden kan bli hemliga i 70 år sedan regeringen nu återgått till sitt ursprungliga förslag om sekretess för banden.” skriver dagens DN, och fortsätter “regeringen överlämnat ett nytt förslag om en 70 år lång sekretess för banden, även om hemligstämpeln inte blir absolut nu heller. Uppgifter kan bara lämnas ut om det sker “utan fara för att Regeringskansliets verksamhet skadas“. “Det har påståtts att man, om tsunamibanden röjs, skulle kunna kartlägga regeringskansliets arbete. Det är fullständigt obegripligt, då kan man inte ha någon offentlighetsprincip alls“, säger tryckfrihetsexpert Anders R Olsson till SvD, som inte alls tycker att regeringens taktik är bra. Det är konstigt att politikerna inte lärt sig att just genom att agera som dom gör nu genom att försöka mörka information (oavsett orsaken till detta) så kommer media att jaga dem ända in i “kaklet” i nämnda fråga. / Red.

I started my day today way later than I had planned to, and that did not make me a happy camper.  I wanted to get up early and refreshed around 9 am so that I could get a good start on my new strut installation.  However, I slept until 11:30, hitting the snooze button in an endless cycle of decision making.  For whatever reason, I was more extremely more comfortable than usual. Regardless, I knew I had to work on my car.  The comfort must’ve overwhelmed me, though, and I laid there without much concern of my day’s task.  I figured a couple more minutes wouldn’t hurt.  I was wrong to think that I could lay for only a few minutes.  Every time I hit snooze, my thought continued of “a few more minutes.” Two and a half hours later when I finally did decide to finally get up, I headed straight to the garage.  I was pissed that I had wasted so much time, but I figured I’d still be able to get my task done relatively early.  I got the engine covers out and the strut/spring assembly off the car within 30 minutes of starting, so I figured I’d have a smooth, quick day. But the fun had yet to begin.  After switching over the spring and components over to the new strut and putting them back on the car, I couldn’t get the assembly to easily fit back into the seat and holes in the fender well.  After struggling, pushing, and cutting my hands in all sorts of new ways, I was able to push the brake assembly down, compress the strut and get it into the correct position.  The fun was starting.  While I continued onto the passenger side, I knew that it would be easier than the driver’s side.  I mean, I had just learned what would be difficult and what to keep in mind.  Well that notion flew away fast, and I had the exact same problems all over again.  Though I had the same problems, I conquered them in the same manner and eventually got them in.  Afterwards, I decided it would be in my best interest to take my new wheels off the car and put my stock wheels back on.  I did this because I just bought paint for the wheels and I’ll be starting them these upcoming days.  I still have a good amount to do until I’m satisfied, but it’ll be worth it.  I’m currently awaiting my rear struts in the mail, so those will be installed whenever they arrive.  After the suspension is complete and the wheels are done, pictures will follow.  Fingers are still crossed.

I shouldn’t be premature because I haven’t evaluated JSF yet, but so far Stripes is looking like a clear winner for me in the Java web MVC framework race.

My thumbnail description of Stripes would be that it’s like Struts 2, but without the warts, moles, and scars.

It looks like everything you’ll need is provided for. They don’t reinvent the wheel; for example, in the jsp files it uses EL and you can use the standard JSTL tags (core, format, etc.), and they have their own Stripes tags for forms and whatnot. The coding convention is straightforward. Almost all configuration is done with annotations in your code; there’s a small bit of global configuration in the web.xml.

It’s quite pleasant to work with.

LP-2000 is Asalco’s best selling all-purpose lubricant and penetrant. It has been used for years in the industrial sector, renowned for its extreme high anti-wear and anti-corrosion properties. It is long lasting, moisture resistant and is CFIA approved (Canadian Food Inspection Agency) for use in food processing areas.