Links

  • 1. Sogeti
  • 2. JBoss
  • 3. IBM
  • 4. Oracle
  • 5. SpringSource
  • 6. NL-JUG
  • 7. Java

Archives

Syndication  RSS 2.0

RSS 1.0
RSS 2.0

Bookmark this site

Add 'JCN Blog' site to delicious  Add 'JCN Blog' site to technorati  Add 'JCN Blog' site to digg  Add 'JCN Blog' site to dzone

Posted by Willem van de Griendt at 15:18 on Thursday 7 May    Add 'JBoss seminar' site to delicious  Add 'JBoss seminar' site to technorati  Add 'JBoss seminar' site to digg  Add 'JBoss seminar' site to dzone

Op woensdag 27 mei 2009 organiseert Red Hat samen met Sogeti en nog drie partners het JBoss seminar met als titel “Bedrijfskritische processen met JBoss”. Tijdens dit seminar wordt nader ingegaan op oplossingen die met JBoss zijn ontwikkeld voor de Nationale Postcodeloterij, NXP en NS-HiSpeed en welke voordelen dit heeft opgeleverd voor deze organisaties. Kortom een interessant seminar voor iedereen die meer wil weten over de voordelen die het gebruik van JBoss organisaties kan bieden.
Inschrijven voor dit gratis seminar kan via deze link.

Posted by Willem van de Griendt at 15:29 on Tuesday 21 April    Add 'JBoss training- en certificering roadmap' site to delicious  Add 'JBoss training- en certificering roadmap' site to technorati  Add 'JBoss training- en certificering roadmap' site to digg  Add 'JBoss training- en certificering roadmap' site to dzone

Na de overname van JBoss door Red Hat is het bestaande trainingaanbod niet gewijzigd, behalve enkele inhoudelijke aanpassingen. Momenteel wordt er echter hard gewerkt aan een volledig nieuw curriculum voor JBoss. De opzet van de trainingen zal meer praktijkgericht zijn. De verhouding theorie vs. labs wordt ongeveer 40-60 en daarnaast worden de trainingen meer een afspiegeling van de praktijk. Voor de administrator training betekent dit dat de cursist bijvoorbeeld de rol krijgt van ‘de nieuwe administrator bij een startup’. De training wordt vervolgens opgebouwd vanuit die rol.

Read the rest of this entry »

Posted by Willem van de Griendt at 11:48 on Tuesday 21 April    Add 'JBoss Roadmap' site to delicious  Add 'JBoss Roadmap' site to technorati  Add 'JBoss Roadmap' site to digg  Add 'JBoss Roadmap' site to dzone

Tijdens de Red Hat Partner Summit wordt ruim aandacht besteed aan de verschillende JBoss producten en de toekomstige ontwikkelingen m.b.t. JBoss. JBoss is bij velen bekend van de applicatieserver, maar er is meer.

Read the rest of this entry »

Posted by Willem van de Griendt at 9:28 on Tuesday 21 April    Add 'Partnersummit Red Hat' site to delicious  Add 'Partnersummit Red Hat' site to technorati  Add 'Partnersummit Red Hat' site to digg  Add 'Partnersummit Red Hat' site to dzone

partnersummitVan 19 t/m 22 april vindt op Malta de Partner Summit van Red Hat plaats. Dit event, dat voor de tweede keer georganiseerd wordt, heeft dit jaar als motto “Stronger together – share, leverage, benefit!”. Een motto dat goed past bij een open source organisatie als Red Hat. Zo wordt er tijdens de Partenr Summit veelvuldig gesproken over het ‘eco-systeem’ rondom de Red Hat Enterprise Linux (RHEL) en JBoss productlijnen. De open source communities, de partners en Red Hat zelf zijn de belangrijke elementen in dit eco-systeem en daarmee de basis van het succes van zowel RHEL als JBoss.

 

Read the rest of this entry »

Posted by Ruud Steeghs at 19:12 on Thursday 26 March    Add 'OpenSource, Portal, Content Management System' site to delicious  Add 'OpenSource, Portal, Content Management System' site to technorati  Add 'OpenSource, Portal, Content Management System' site to digg  Add 'OpenSource, Portal, Content Management System' site to dzone

en dat allemaal in één: JBoss Portal.

Kijk hier voor een een kijkje in JBoss Portal

Posted by Erik-Berndt Scheper at 23:35 on Wednesday 25 March    Add 'Hibernate Envers 1.2.0.GA released!' site to delicious  Add 'Hibernate Envers 1.2.0.GA released!' site to technorati  Add 'Hibernate Envers 1.2.0.GA released!' site to digg  Add 'Hibernate Envers 1.2.0.GA released!' site to dzone

This last year, I have been actively involved in setting up a new development tool-set for one of our customers. Amongst others, we have migrated from native Hibernate to JPA, using Hibernate as persistence provider (i.e. Hibernate EntityManager and Hibernate Annotations).

This is all very neat and works fine (just like everything that’s Open Source), so that’s not really worth blogging about. One of the more interesting requirements was that we needed to implement an audit trail in Java, because we are stuck with a rather primitive database that doesn’t natively support audit trails.
As a first cut, we wrote our own auditing implementation using standard JPA. Initially, that looked simple and neat. The idea was to define a default entity listener that does the auditing for every persisted object. Note that default entity listeners cannot be defined using annotations; you have to define this in the orm.xml file.
However, like all roll-your-own implementations (most at least), this lead to complications. First of all, JPA Entitylisteners are stateless. Secondly, the JPA spec insists that you may not use the same persistence context inside the entity listener. And last but not least, we could not inject Spring beans in the entity listener. So in the end we fixed it using a couple of more or less ugly hacks.

But then we (almost simultaneously with some colleagues from Logica working for the same customer) discovered Hibernate Envers. Personally, my first encounter was on theserverside.com, where an announcement had been posted that JBoss Envers was now part of the Hibernate Core and was re-dubbed to Hibernate Envers. The first release under the Hibernate flag will be 3.5, as the Hibernate implementation of JPA 2.0. But a backport for the current Hibernate (3.3.x) is available in a separate branch.

And this works great! All you have to do is configure Envers as Hibernate listeners in the persistence.xml file, and add @Audited annotations to all entities you wish to audit. You can then add @NotAudited to all properties you wish to exclude from auditing and everything is audited automatically. Envers scans the Hibernate EntityManager upon startup, creates new entities on the fly, based on the entities that have the @Audited annotation.
But you have to use Hibernate Annotations, it doesn’t work with .hbm.xml files.

Of course, we had some issues with it at first (such as  HHH-3729, HHH-3740 and HHH-3736) but my fixes for these issues are now part of the 1.2.0 GA release, and we lived happily ever after.

So if you ever need auditing with Hibernate and JPA, look out for Envers!

Posted by Jan-Hendrik Kuperus at 12:17 on Friday 5 December    Add 'Configure JBoss WS on multiple network interfaces' site to delicious  Add 'Configure JBoss WS on multiple network interfaces' site to technorati  Add 'Configure JBoss WS on multiple network interfaces' site to digg  Add 'Configure JBoss WS on multiple network interfaces' site to dzone

The JBoss WebServices package is a nice library to get your webservice kickstarted in no-time. One of its features is the automatic generation of a WSDL for your webservice endpoint. There is however a slight annoyance when you try to use this on a machine with two network interfaces.

On a single interface machine, JBoss automatically fills in the IP address or hostname of that interface in the <soap:address/> WSDL entry. No problems there. But, if you have a machine with two interfaces, for example one for internal and one for external access, then JBoss is likely to screw things up.

This is due to the following configuration directive in the jbossas/server/production/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml:


<property name="webServiceHost">${jboss.bind.address}</property>

This property causes JBoss to use the bind address in the WSDL rewriting/generation. Even if you start the server with -b 0.0.0.0, which binds it to all interfaces, JBoss still selects a single interface to use in this property.

The solution to this is luckily very simple: if this property is removed from the configuration file, JBoss will rewrite the WSDL with the address of the interface on which the request came in.

It does make me wonder, why is this not the default setting? Would it not be easier to drop in a server anywhere and it automatically exposes correct WSDL files on all interfaces? Then, if you want to restrict it to a single interface, add the property shown above.

–Jan-Hendrik Kuperus
http://blojsom.jhkuperus.nl/blog


© 2020 Java Competence Network. All Rights Reserved.