A passion, technology.
Imagine a working environment which promotes technological innovation and curiosity.
Imagine a group where you will have opportunity to work and to share with people among the most gifted.
Imagine a culture and stocks in break with SSII.
Imagine a society where your talents and your ideas will be admitted and encouraged.
Imagine an organisation which gives you the medium reals to work, to advance, to accomplish your personal plans.
Do not imagine any more, live him!
Do not hesitate to contact us across the Form of contact or directly at address recrutement@xebia.fr.
ADDM Adobe Android annotation GAPED development Devoxx Eclipse ESB WORKING FLASH FLEX GOOGLE GROOVY GWT HIBERNATE IBM J2EE POPULAR DANCE JAVAFX JAZOON JBOSS jdk-7 scala SCRUM SOA JEE JPA JSF JVM agile Methods MAVEN ORACLE OSGI PARIS JUG PERFORMANCE RIA SPRING SPRINGSOURCE SUN TOMCAT WEBSPHERE WICKET XEBIA XP
You go through at present the archives of the category J2EE.
Xebia is a brain tumour, exclusively devoted to technologies J2EE.
Except opposite mention, the contents of this blog are under contract Creative Commons.
During a performance test on an application J2EE, I note that this one has worries of rise in load. Generally one or two thread dumps can highlight the points of satisfied. In my case, nothing convincing. I rethink then in the article published on our blog Columns of performance: Regarding satisfied. I recover the sources of the agent and instal him on the server of application, Weblogic 8.1 JVM 1.4.2. Launching of shooting.
MOE and working have to collaborate from day to day: MOE accomplishes and delivers applications, working is charging up to instal them and to exploit them. However, these two teams, although they work in the same purpose, have no same needs or the same problems.
This divergence is not dramatic as long as the collaboration takes place well: MOE is aware of needs of working and takes into account it by simplifying the taking care of applications by the teams of working. Things become more complicated of course when problems and dissensions arrive.
One of the recurrent problems that makes intercede both teams is the deployment of applications.
Paris JUG accepts on Wednesday at 18 h 45 Patrick Curran, president of the Popular dance Community Process for a round table around the opening of JCP.
French members of the JCP will participate in debate: Guillaume Laforge (spec lead of JSR 241: The Groovy Programming Language), Cedric Thomas (CEO of OW2 ObjectWeb), Eric Samson (CTO of Dated Service) and Antonio Goncalves (member of the JSR POPULAR DANCE EE 6, EJB 3.1 and JPA 2.0).
Two years after the call of IBM and BEA to open the platform Popular dance, at a time of the controversy OSGI VERSUS POPULAR DANCE MODULE System, of the broad success of Flash facing JAVAFX, delicate relations between Sun and Apache foundation and of the emergence of SCA / SDO, it is a chance to include stakes which the platform Popular dance meets today and can be to attend the change of the gouvernance of Popular dance.
This round table contacts the experts Popular dance as much as to the managers who define strategies of System of Information.
All details of the party .
The announcement of SpringSource has paces of schism. After years to criticise complexity and monolithic nature of Popular dance Enterprise Edition (Popular dance EE), the teams of Rod Johnson crossed Rubicon and offer a server of applications Popular dance which will not rest specification on monolithic Popular dance EE.
SpringSource Application Platform limits itself to some fragments of this specification (mainly Servlet and JPA) put together in a container OSGI augmented by some features Spring. Applications web will not be any more put together in form of WAR with a file web but in form of several BUNDLES OSGI with files of shape Spring.
Read the continuation of this article
In the previous articles on Wicket, we explored the bases of the framework. We are going to be interested now in some functionality moved forward as templating or internationalisation.
With Wicket, even the templating is very simple. The realisation of the templating in Wicket is very close of the way of making of (at least for the part HTML). The implementation is made by mechanisms of inheritance: Wicket names this him . Let us take as a concrete model.
It would be necessary to be able to change the name of DataSource according to environments
Ouh, it is complicated, it is necessary to relax the archive of application MonApp and 5 files.war and 8 files.jar of ejb. This will take minimum 3 weeks, and without material!
(Functionality plans of deployment described in this article is available from WebLogic 9)
During the previous article, we had shown how packager a pool of connections JDBC with EAR. It seems obvious that if this solution is interesting, she is sufficient to define this application in different environments plans (Recipe, Preproduction or Production). It is not possible that for every environment, it is necessary to open archive, to change the file XML with new parametres and to end up closing again it.
The idea of the plans of deployment is to leave archive such which and to link him at the time of deployment new parametres. A plan of deployment is a file XML which takes back all new parametres to be overloaded.
Read the continuation of this article
TV4IT goes on debate with the third and last part of this live broadcast on March 3rd, 2008.
TV4IT goes on debate with the second part of this live broadcast on March 3rd, 2008.
TV4IT opens debate with the first one left this live broadcast on March 3rd, 2008.
This article inaugurates a series around often misread and advanced functions appeared in the last versions of the server of application WebLogic.
A J2EE application uses generally one or several sources of data (Datasources). Specification J2EE allows at best to classify the name JNDI of the source of data in the descripteur of deployment of application (or of the web - app). On the other hand, the complete definition of parametres of the source of data (Type, URL JDBC, Size of the Pool) is an operation specific for every server of application. When comes the time of the delivery of application except the environment of development (Integration, Recipe), teams give generally the archive of application to be displayed and a document of installation in format Word. It describes operations, with the aid of many copies of screen, to be performed across the application of administration to declare and to define the sources of data before undertaking the deployment of the file MonApplication as such. This article shows how with the server of application Weblogic 9 +, it is possible to link, in application to display, group of its resources, especially, the definition of parametres of its sources of data.
Example: To illustrate my purpose, I will use an application web, MYWEBAPPLICATION, which shows information on a connection JDBC got by DataSource registered in the tree JDNI. This application is traditionally packag e in form of an archive web, MYWEBAPPLICATION.WAR, itself encapsul e in an archive MYWEBAPPLICATIONEAR.EAR.
Xebia IT Architects lock France
Defence Colis e - 10/12, avenue of The Ark
92419 Courbevoie Cedex
T l : +33 (0) 1 46 91 76 16
Fax : +33 (0) 1 46 91 88 00
E-mail : info@xebia.fr