Summary

Very good book on what is arguably the most popular JSF component library. Covers the less well used but very important ajax features of Richfaces, including the use of ajax regions, containers as well as the plug-n-skin features.

Details

To all intents and purposes, this book is not for a beginner JSF developer, because it assumes familiarity with JSF 1.2. It starts off by delving into the history of the Richfaces component framework, which in eons past was just Ajax4jsf. It gives a short introduction (which is expounded later) on the ajax capabilities, the component set and skinability features of Richfaces for Rich Internet Application development.

It then sets off showing you step by step, how to create a simple JSF application that takes advantage of Richfaces as it’s JSF components library. It presents the seam-gen tool, a nifty tool for creating skeletons jsf projects based on the JBoss Seam project. Following the instructions on seam-gen enables you to create a quick prototype to start playing around with. This is then followed by instructions on how to manually create a project which is not Seam based, for fans of other frameworks which also integrate JSF, or for the pure JSF purists. This also includes configuring facelets support, and finally a look at how the IDEs provide support for development using the Richfaces component set.

The rest of the book, chapter by chapter, then focuses on using Richfaces components in building an interactive, intuitive and rich UI for your JSF application.

The following chapter delves into creating a JSF application using seam-gen (which I felt was repetitive, given that they’d actually created one in the preceding chapter), with additional parameters for defining the persistence model (entities) that were to be used in the application. It is worth noting from here forward almost all the examples now make use of the Seam framework’s programming model, something which could be a problem for those who are not Seam adherents. Also, with the stated assumption that this book is targeted at people with a basic knowledge of JSF, there didn’t seem to be the need to go over the basics of templating with Facelets and defining managed beans in a faces-config.xml file.

The next two chapters then introduce us to the intricate details of what the application is actually supposed to look like in terms of UI and functionality. The reader is taken through creating a database and generating entities from these, as well as creating a login page. I felt that these two chapters were the weakest chapters of the book, seeing as they dwelt more on entities, JPA and entities generation and Seam’s identity and login management than it did on the particular component framework in question – Richfaces. This may be explained by the fact that Richfaces enables the user to hook into Hibernate Validator for DRY enforcement on the domain model, the user could have been spared the parts on how to create the database, etc as well as Seam’s login management features.

Subsequently, the next chapter gives some very good insight on skinning, and implementing a means for the user to dynamically change skins. It explains the Richfaces’s use of XCSS, a powerful xml based means of describing CSS properties, as well as how to use some of the default Plug-n-Skin examples.

Chapter 6 then takes us deep into a real ajax experience, showing us the lesser explored but very important features provided by the rich:dataTable and rich:column components, as well as the appropriate use of the datascroller component for displaying tabular data. It also talks extensively about other data iteration components like the DataGrid and the DataList. Additionally, it goes into detail on the appropriate use of ajax placeholders, especially on using Richfaces outputPanel in achieving really ajax based changes to UI after changes are made to content, instead of just using JSF’s rendered attribute only.

The next chapter then deals with using the RichEditor as well as how to implement Drag’n'Drop support in your application. Finally an in-depth score is done on using the Richfaces FileUpload component.

Chapter 8 and 9 deal into more detail with skinning support in Richfaces, including how to create your own Plug’n'Skin skins, which can be quite easy if you follow the author’s guidance.

Chapter 10 dwells on advanced ajax capabilities such as Poll, Push as well as the partial update of data iteration components in the UI.

Of course, this book would not have been complete without discussing the Richfaces Component Development Kit (CDK). From creating a maven project using Richfaces’s CDK archetypes, to creating your own user defined components and registering them with the application, this chapter covers it all.

It ends with an appendix giving a short description of all the components currently provided by the Richfaces team.

What I like about this book.

This book contains a lot of information about how to really take advantage of the ajax capabilities provided by the Richfaces framework, and makes important mention of very valuable points to look out for when ajaxifying your application. I highly commend the indepth knowledge of Richfaces placeholders and the use of attributes like ajaxSingle and process, which gives your JSF application a true ajax feel.

What I don’t like about this book.

I’m an avowed fan of JBoss Seam, but I’d have preferred the book didn’t delve so deeply into Seam to make it’s point. As i mentioned before, some chapters dealt more with Seam than with Richfaces, and those may actually be quite annoying to someone who is developing with say Spring Web Flow.

Packt Publishing has attempted to pull off a book that provides an indepth look at the 3.3 version of the popular JSF component library, Richfaces. In a lot of ways, I believe they have managed to do just that, give or take a few points.

Funny,

a co-worker yesterday called me about using the Expression Language MR stuff. Interestingly my body Lincoln wrote a blog on that one, a little while ago.

Check it out. Good read!

Hi
I found one of the best solution for creating and running seam projects in eclipse on Tomcat so quickly :
http://techieexchange.wordpress.com/2007/11/11/rad-seam-development-with-eclipse-and-tomcat-step-by-step-tutorial-screencast/

bye

this is a great movement of people who are looking to help ex-child soldiers who make some amazing quality bags for women, and i think men. check it out and support the cause by buying some cool gifts for Christmas. Save a life!

The women employed in our program are formerly abducted child soldiers, often used in captivity as sex slaves. Those lucky enough to escape, often with children of their own, are ostracized due to their affiliation with the rebels. They lack education, and are taught sewing as a part of their brief rehabilitation. With demand for seamstresses already sparse due to the war, many are left without the means to support themselves and their children.

MEND is a socially and environmentally responsible company, made in afflicted emergent regions in hopes of stimulating growth, local employment, and economic stability. Similar to its parent company- Invisible Children, MEND is beginning with northern Uganda, with the possibility of heedful worldwide expansion. In October of 2007, 13 women began to MEND. Our dream is that many more will follow.

MEND Explanation Video from MEND on Vimeo.

Dear *,

I am glad to announce you we will have a JBoss and Fedora Booth – separated ones – at FOSDEM’10. – details below -

FEDORA

– on Saturday from 10:00 to 18:00 and Sunday from 10:00 to 17:00,
– 2 table(s) of 2 meter width and 1 meter depth, 2 seats per table,
– most probably in the H
building,
– best-effort wireless interenet and one(!) type C/E power plug.

JBoss

– on Saturday from 10:00 to 18:00 and Sunday from 10:00 to 17:00,
– 1 table(s) of 2 meter width and 1 meter depth, 2 seats per table,
– most probably in the AW
building,
– best-effort wireless interenet and one(!) type C/E power plug.

See you there.
Frederic

Dear *,

I am glad to announce you that we  have a JBoss room for FOSDEM’10 – slots of 50 minutes -.

JBoss Room availability:
For 1 day, on Saturday 6th February from 13:00 to 19:00.

Now, I am looking for JBoss Speakers on the following subjects :

• Infinispan
• JBoss Application Server
• Seam
• Drools
• Hibernate
• jBPM
• Hibernate Search

See also the following URL : https://fedoraproject.org/wiki/FOSDEM_2010_Technical_Talk_Propositions#JBoss_Talks_or_Subject_Propositions

Thanks to  http://jbug.be/ for there help.

In this post we build on another and present a code framework with accompanying in-depth explanations that can be used to get you up and running with Quartz scheduling quickly.

You should also be able to incorporate this code into any Seam example application in no time and the in-depth explanations should help you further mould the framework to your requirements. For reference, we are using Seam 2.0.1.GA & JBoss 4.2.2.GA and we assume you have the Seam example applications handy although this will only become relevant when looking at the build.xml files in Step 2.

Quartz Background

In a nutshell, if you use a Unix-like operating system, and you know cron, then you know Quartz. This is an oversimplification of course, the extent to which you’ll be able to gauge if you have a look at the available Quartz Features and Quartz Tutorials, however the syntax used for calendar-like job scheduling by and large matches that of cron (see the CronTrigger Tutorial for more detail).

Step 1: Create the seam.quartz.properties File

In your resources folder, which contains your seam.properties file, amongst others, create a file alongside named seam.quartz.properties an drop the following text in it:

#==============================================================
# Configure Main Scheduler Properties
#==============================================================

org.quartz.scheduler.instanceName Sched1
org.quartz.scheduler.instanceId AUTO
org.quartz.scheduler.rmi.export false
org.quartz.scheduler.rmi.proxy false

#==============================================================
# Configure ThreadPool
#==============================================================

org.quartz.threadPool.class org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount 3

#==============================================================
# Configure JobStore
#==============================================================

org.quartz.jobStore.misfireThreshold 60000
org.quartz.jobStore.class org.quartz.simpl.RAMJobStore

Digging deeper

Lets consider what the above means:

• org.quartz.scheduler.instanceName Sched1 – The Scheduler name, significant if you need to identify multiple Schedulers in your client code.
• org.quartz.scheduler.instanceId AUTO – As can be inferred, this is an automatically generated Id for the Schedule instance.
• org.quartz.scheduler.rmi.export false – With this set to true the Scheduler cannot be accessed remotely via RMI.
• org.quartz.scheduler.rmi.proxy false – Only relevant, if you want to connect to a remotely served scheduler, we don’t so we set it to false.

• org.quartz.threadPool.class org.quartz.simpl.SimpleThreadPool – Has an associated fixed-size pool of threads that live the lifetime of the Scheduler.
• org.quartz.threadPool.threadCount 3 – The number of threads available for concurrent execution of jobs. Exactly how many threads one will need appears to be more of a thumb suck than exact science, but apparently if you only have a few jobs that fire a few times a day, then 1 thread is good enough, so we’ve thrown in two extras here for good measure. If you have too few threads though you may get a “mis-fire”, see the next property, the misfireThreshold, for more clarity on this.

• org.quartz.jobStore.misfireThreshold 60000 – Accourding to the documentation, this is the number of milliseconds the scheduler will ‘tolerate’ a trigger to pass its next-fire-time by, before being considered “misfired”. What happens when a trigger misfires can be specified with a mis-fire instruction which is a property of the Quartz Trigger class. There is a default mis-fire instruction and the relevant section of the Quartz Scheduler Documentation recommends familiarity with the misfire instructions that are defined on the given trigger types, as explained in their JavaDoc, and also mentions that the misfire instruction for a given trigger instance can be configured using the setMisfireInstruction(..) method. One would think that some kind of logging or other corrective action would be appropriate in such a method.
• org.quartz.jobStore.class org.quartz.simpl.RAMJobStore – with this all scheduling information  (job, triggers and calendars) is stored in memory and naturally all such information will be lost when the Scheduler terminates. A persistent alternative to this is JDBCJobStore.

Finally, for more information on Quartz configuration, please consult the Quartz Configuration Reference.

Step 2: Tweak your build.xml file

If you want to build any of the Seam example applications, you’ll notice a build file that has application specific options and then there is an import of an upper level build file. All you need to do is to add the following line into the example application build file (the details are in the imported build file if you are interested):

<property name="quartz.lib" value="yes"/>

Digging deeper

All this does is to result in your Quartz properties file going where it needs to go in terms of packaging, and likewise for the Quartz jar file. There is not much more one can say about this apart from that the Seam example build file structure can be quite handy, a lot of work has already gone into it so it seems to make sense to use it in your application. You may want to check up on what version of Quartz you are using.

Step 3: Edit the components.xml file

There’s very little to this file, located in your WEB-INF directory, just add in the following namespace scheme pointer in the components main node:

xmlns:async="http://jboss.com/products/seam/async"

Then add the following element to start the Quartz dispatcher:

<async:quartz-dispatcher/>

Step 4: Create the Processor and Controller classes

ScheduleProcessor.java:

package com.newco.services;

import java.util.Date;
import org.jboss.seam.ScopeType;
import org.jboss.seam.annotations.AutoCreate;
import org.jboss.seam.annotations.In;
import org.jboss.seam.annotations.Logger;
import org.jboss.seam.log.Log;
import org.jboss.seam.annotations.Name;
import org.jboss.seam.annotations.Scope;
import org.jboss.seam.annotations.Transactional;
import org.jboss.seam.annotations.async.Asynchronous;
import org.jboss.seam.annotations.async.Expiration;
import org.jboss.seam.annotations.async.IntervalCron;
import org.jboss.seam.async.QuartzTriggerHandle;

@Name("processor")
@AutoCreate
@Scope(ScopeType.APPLICATION)
public class ScheduleProcessor {

    @Logger
    private Log log;

    @Asynchronous
    @Transactional
    public QuartzTriggerHandle createQuartzTestTimer(
                @Expiration Date when, @IntervalCron String interval) {

    	String date = new Date().toString();
    	log.info( "Quartz Test: " + date );
    	return null;
    }
}

Digging deeper

As noted in the referenced post, this is where we place the work that needs to be done, or what we are actually scheduling. As you can see all we do here is to log that date periodically, with the period being defined by IntervalCron. Also note that the Processor class has an APPLICATION scope and is AutoCreate-ed, there are alternative ways one could achieve this (via an org.jboss.seam.postInitialization event) and which approach is superior, if any, is debatable.

ScheduleController.java:

package com.newco.services;

import java.io.Serializable;
import java.util.Date;
import static org.jboss.seam.ScopeType.APPLICATION;
import org.jboss.seam.annotations.AutoCreate;
import org.jboss.seam.annotations.Create;
import org.jboss.seam.annotations.In;
import org.jboss.seam.annotations.Logger;
import org.jboss.seam.annotations.Name;
import org.jboss.seam.annotations.Scope;
import org.jboss.seam.annotations.Startup;
import org.jboss.seam.async.QuartzTriggerHandle;
import org.jboss.seam.log.Log;

@Name("controller")
@Scope(APPLICATION)
@AutoCreate
@Startup
public class ScheduleController implements Serializable {

    private static final long serialVersionUID = 7609983147081676186L;

    @In
    ScheduleProcessor processor;    

    @Logger
    Log log;  

    private QuartzTriggerHandle quartzTestTriggerHandle;
    private static String CRON_INTERVAL = "0 * * * * ?";

    @Create
    public void scheduleTimer() {
	    quartzTestTriggerHandle =
                processor.createQuartzTestTimer(new Date(), CRON_INTERVAL);
	}
}

Digging deeper

Our schedule is such that the trigger will fire every minute of every day so that we can see some action happening in the log in Step 5, for full coverage of alternatives and cron syntax, please consult the manual.

When looking at this, you might wonder what happened to the potential mis-fire instruction, where would it go if it where necessary? Also, with appropriate test cases, we would want to intentionally cause mis-fires so that our misfire instruction, that we had duly set via the setMisfireIntruction() method, can flex its muscles. These are important questions that we won’t answer in this post right now, but potentially in future.

Step 5: Deploy and watch your JBoss log file

All you need to do now is deploy the application, and if you watch the server log file, or console output, you should see something like this every minute:

12:55:00,134 INFO  [ScheduleProcessor] Quartz Test: Tue Dec 01 12:55:00 SAST 2009
12:56:00,029 INFO  [ScheduleProcessor] Quartz Test: Tue Dec 01 12:56:00 SAST 2009
12:57:00,025 INFO  [ScheduleProcessor] Quartz Test: Tue Dec 01 12:57:00 SAST 2009
12:58:00,025 INFO  [ScheduleProcessor] Quartz Test: Tue Dec 01 12:58:00 SAST 2009
12:59:00,031 INFO  [ScheduleProcessor] Quartz Test: Tue Dec 01 12:59:00 SAST 2009

JBoss EL is a powerful tool if you are using JSF. You can pass parameters to methods in JSF with it. It is my favorite tool right now while developing with JSF. I thought it was coming with Seam only, I mean I thought that you cannot use it without Seam but then in a PrimeFaces-Spring-Hibernate project I needed this. It turns out that you can use JBoss el w/o Seam also and it is very easy to integrate.

1. Just download JBoss EL jar to your web-ing/lib folder, or add it as a dependency in your pom.xml file ( if you’re using maven)

and put this in your web.xml file:

<context-param>
<param-name>com.sun.faces.expressionFactory</param-name>
<param-value>org.jboss.el.ExpressionFactoryImpl</param-value>
</context-param>

that is it. now you can do a lot of tricks like :

<ui:repeat var="day"  value="#{bean.user.getWorkingDays(bean.periodStartDate, bean.periodEndDate)}">
<p:commandButton value="#{day}" action="#{bean.selectDay(day)}"/>
</ui:repeat>

yes, like above all kind of tricks can be done now.

Java EE servers are based on the Java™ 2 Platform, Enterprise Edition (J2EE™) and is used widely to provide code portability, reuse across tiers, platform support, scalability and for EJB strengths. Instead these supports are provided by the most of the java EE servers, this article is the place where you can share the Java EE servers used during your project development. I have assessed most of the Java EE servers used by the developers in the below. Kindly choose the Java EE server(Choose all that apply) which you use, also share the reason why you choose the particular Java EE server for your project development. Also if your option is others remark your Java EE server in the comments.

Hier auch ne scharfe Kombination, frische Farben der Saison, volle Funktion, und Super Style, Scott Locksmith Jacke und die passende Hose dazu.

Giro G10 in cyan und die Scott goggle in der passenden Farbe .

Freestyle Ski Head Black Jack

alles frisch aus der www.bergzentrale.de aus 44805 Bochum, Geisental 4

Hi
In seam, when you want to inject some components such as EntityManager,POJOs,or … to threads, Probably you will  see all your objects is NULL.
The reason of this scenario is SeamApplicationContext missing in your threads, OK what is the solution?

You should use Lifecycle.begin() and Lifecycle.end() methods before and after your codes :

….
…….
Lifecycle.begin()
EntityManager em = (EntityManager)Component.getInstance(“em”,true);
Lifecycle.End()
……
…

So when you write your codes between these two methods, You will be in the SeamApplicationContext and you will not see any exceptions for EntityManager too like :

EntityManager is closed
no Transaction is in progress
….
..

bye.

Hi
If you are new to Seam framework and you get this stupid exception,You should read Seam annotation reference as well. OK this is my code :

[Sample class] …
…
@Name(“sample”)
public Class Sample ..
..
..

and next class is :

@Name(“sampleAction”)
public Class SampleAction …
….
..
@In
private Sample sample

public void someMethod(){
System.out.println(“I love Seam ….”);
}

…

….

And probably you get this exception :

javax.faces.FacesException: #{sampleAction.sample}: org.jboss.seam.
RequiredException: @In attribute requires non-null value: sampleAction.sample
	com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118)
	javax.faces.component.UICommand.broadcast(UICommand.java:387)
	org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
	org.ajax4jsf.component.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:296)
	org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:253)
	org.ajax4jsf.component.AjaxViewRoot.processApplication(AjaxViewRoot.java:466)
	com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)

OK, You should modify @In annotation :

@In(create=true)

enjoy it …
bye

En Filadelfia se desarrolla un encuentro de trabajo sobre la construcción de una nueva visión del desarrollo chaqueño, realizada en el departamento Boquerón. El evento culminará mañana sábado.

Los debates se centran sobre cinco ejes temáticos que apuntan a desarrollar el chaco paraguayo, según explicó el ministro del ambiente Oscar Rivas en declaraciones a la 1300 AM Radio Fe y Alegría Paraguay

Ellos son: medio ambiente, agua y energía, geopolítica social, obras y salud, educación y cultura.

Escuche Audio:

Hi
If  you want to work with some rss or rdf or atom protocol, You can use YARFRAW library. This library help you so easily to use rss in your works.
This is the snapshot of architecture :

bye

Selalu menyenangkan dan memberikan inspirasi tersendiri kalau bicara jiwa-jiwa muda yang bersemangat untuk berkarya. Dalam dunia fashion, ada pemain baru yang baru mekar. Mereka adalah Yosafat Dwi Kurniawan dan Krista Rompas. Baru beberapa bulan yang lalu mereka lulus dari Laselle College International Jakarta. Yosafat baru berumur 21 tahun, Krista lebih muda lagi, baru 18 tahun !

Yosafat dinobatkan menjadi “The Best Student Graduate” 2009 oleh Lasalle pada Juli lalu. Ia adalah satu-satunya finalis dari Indonesia yang lolos untuk ikut dalam “Hempel Award”, salah satu kompetisi fashion bergengsi di Beijing. Krista tidak kalah hebatnya. Ia merupakan salah satu murid termuda yang lulus dari Lasalle ketika itu. Hasil kerjanya termasuk yang terbaik di kelas, terbukti dari prestasinya yang pernah menjadi salah satu finalis yang mendapat kesempatan “manggung” di “Greener Nation” 2008 di Senayan City.

Malam ini di Jakarta Fashion Week 09/10, mereka berkolaborasi dengan membawa brand yang baru mereka godok, SeaM. Bahasa Indonesianya, jahitan. “SeaM dipilih menjadi brand karena dalam setiap baju pasti ada “seam” yang dipakai. Seam ini juga menggambarkan ketika dua hal disatukan, seperti saya dan Krista,” kata Yosafat. Tapi jangan bikin gossip macam-macam ya. Maksudnya disatukan dalam karya.

Uniknya, mereka langsung membawa karya yang jauh berbeda dari yang lain. Mereka membuat Romeo dan Juliet dalam versi Punk! Oi oi oi, Punk not Death!! Hehe. “Kita udah punya tema ini sejak lama. Dari kuliah dulu udah sering diskusi bareng. Kita coba buka sendiri dan event JFW ini cocok buat launching label kita ini,” kata Yos.

Kok berani banget baru muncul langsung “nyeleneh” gitu? Yosafet jawab, “Memang punk banyak yang gak suka. Tapi dari situ justru membuat kita berbeda. Kita terinspirasi yang generally orang gak suka, dan kita tarik itu, ambil yang bisa kita ambil. Garis kerasnya itu kita alihkan ke bahan-bahan yang kaku seperti jeans. Kita menyadari bahwa kalau ambil punk yg murni orang gak menarik, maka kita tarik juga Romeo and Juliet, jadi ada unsur feminimnya, gak selalu keras.”

Menanggapi pertanyaan wartawan tentang pasar, Yos bercerita, “Untuk segmentasi pasar, kita membawa audience kita dari belasan tahun sampai yang sedikit tua. Kalau sekarang kita hanya tersedia by order. Tapi kita juga sudah mengundang beberapa ritel. Price range-nya beragam banget. Ada yang 300 rb-2 jt. Tapi generally kalau sudah masuk butik kebanyakan di bawah 2 juta.

“Malam ini, SeaM show dengan membawa 24 set,” kata Yos, “Kebanyakan (tiap set terdiri dari, pen) 3 pieces (yaitu, pen) jaket, blous, dan busana. Kita mau tampil beda. Kalau bawa gaun seperti desainer lainnya kita gak bakal dapat suara. Jadi kita mau tampil beda. Untuk koleksi ini kita belum pakai batik, tapi kita banyak klien yang banyak pakai kebaya. Kita ada rencana masukin batik dalam koleksi kita. Kebetulan kita suka print. Kita mau modifikasi batik itu menjadi modern dan bisa relate dengan relasi kita.” Pastinya generasi akan terus berganti. Saat itu, yang muda yang kemudian akan bicara.

Dok: SeaM.

The creative team at Badec Bros Deco was recently commissioned to manufacture a stainless steel, cascading water feature for a client. Firstly, we created seven Cubedec B pots – troughs – in varying dimensions from grade 304 stainless steel.

The stainless steel sheets were folded and welded together along a single seam line, to create a flawless overall appearance. Once all of the troughs were manufactured, we installed the water feature on site, with the lowest trough being filled with black pebbles.

We can also manufacture this stunning water feature from mild steel and finish it in one of three finishes, namely: a mild steel finish, rusted finish and powder coating finish. There are literally hundreds of different colours to choose from for your powder coating finish and this finish is SABS approved. Our Cubedec water features can be customized to any size and shape. As our CEO, Edrich Badenhorst likes to say; “The sky is not the limit.”

Please feel free to contact us with your ideas and we will be sure to bring them to fruition. We love a creative challenge!

Should you wish to have your very own signature Cubedec water feature, 3 dimensional garden sculpture, 3 dimensional signage, slim mirror pot, Cubedec bench with your laser-cut logo, modern pergola, Cubedec steel dustbin, interactive sculpture, Cubedec shelving, Cubedec miniature Zen garden box, 2010 Soccer World Cup décor, mild steel lamp shade, mild steel screen, gabion counter, narration stand, gabion light cage, gabion bollard, gabion water feature, sculptured living wall, sculptured flagpoles, unique pot and drip tray, customized sculpture, trendy steel décor with your company logo emblazoned on it, mild steel inspirational slogan, steel laser-cut signage, mild steel mould, Cubedec Pot, hanging sculpture, gabion pot, gabion wall or gabion terrace, wooden or steel feature poles, bar code trellis, arch, sculpture or trellis, please feel free to contact our energetic and knowledgeable sales representative, Mareleen van Zijl, on her cell phone at 078 800 5112, the office number at 012 460 7990, or via e-mail at mareleen@badecbros.com

She will gladly arrange an appointment with you to listen to your ideas and to stun you with our own creative ideas! You dream it, we manufacture it!

Badec Bros Deco will create a 3 dimensional render and calculate a quotation FREE OF CHARGE for you! We can deliver your unique Badec Bros Deco product(s) within 10 to 15 working days, upon acceptance of the design and quotation and the required 50% deposit. These services come standard and will not cost you a cent extra! We offer a 1 year guarantee on all our products.

Como es de público conocimiento el 6 de Noviembre del 2009, un grupo de sojeros brasileros ha  intentado desalojar por la fuerza, con camiones y camionetas a las 140 familias que conforman las comunidades Avá Guaraní de Loma Tajy, Ka’a Poty, Formosa, Kaaguy Roky e Ysatî del distrito Itakyry Departamento de Alto Paraná, amedrentamiento que se ha ejercido sin importarles la presencia de niños, niñas, adolescentes, mujeres embarazadas y ancianos, atemorizando a toda la comunidad y generando la reacción en defensa propia de los Avá Guaraní con lo que lograron la expulsión de los sojeros de sus tierra y territorios ancestrales, en los últimos momentos del conflicto campesinos de la zona se solidarizaron con los indígenas.

A pocos minutos de ocurrido el primer percance posteriormente los sojeros ejecutan una segunda arremetida enviando un avión a vuelo razante con el objeto de intimidar aún más a los nativos, ellos han denunciado que dicho avión ha fumigado con agrotóxicos a un grupo de al menos 200 pobladores del lugar, 6 de ellos fueron internados en hospitales de la Región. Se ha encontrado evidencia de fumigación con glifosato en áreas cercanas al cementerio y la escuela en lugares donde no existen plantaciones de ningún tipo, según técnicos de la SEAM.

Este hecho forma parte de un plan de despojo de las tierras ancestrales pertenecientes a los Avá Guaraní, que según la Constitución Nacional, la Ley 904 y Convenios Internacionales ratificados por la República del Paraguay como el Convenio 169, deben ser respetados teniendo en cuenta que los Pueblos Indígenas son los dueños originales de estas tierras. Además este predio de 2638 Has cuenta con título de propiedad a nombre de las comunidades por parte del INDI, ante el cual los brasileros anteponen otro titulo de dudosa procedencia; es un secreto a voces que capitalistas nacionales y extranjeros han coimeado y comprado a jueces, fiscales, políticos y funcionarios de instituciones públicas en todos los niveles del Estado, en compras fraudulentas y duplicación de títulos de tierra y delitos ambientales.

Itakyry no es un caso aislado, todo el país fue testigo del asesinato de 12 indígenas en  en Ava’i Departamento de Caazapa, generando en las últimas décadas hambre, enfermedades y muerte de indígenas y campesinos en el campo, invisibilizados premeditadamente por los medios masivos de incomunicación y confusión, no olvidemos aquí a Silvino Talavera niño campesino de 8 años del Departamento de Itapua, muerto por intoxicación de agro tóxicos.

Toda la población rural, los pobres del campo, indígenas y campesinos soportamos históricamente la violación de nuestra soberanía territorial y alimentaria, sufriendo atentados contra nuestra salud con el manejo criminal de agrotóxicos, produciendo la muerte silenciosa de muchos compatriotas en connivencia con las autoridades locales, departamentales y nacionales, hecho que denunciamos GENOCIDIO EN SILENCIO / LO MITÂ JEJUKA ÑEMIHAME.

Repudiamos enérgicamente e interpelamos la criminal determinación de la senadora de la nación ANA MARÍA MENDOZA DE ACHA, “supuesta representante del pueblo”, por organizar y decidir en una reunión interinstitucional llevada a cabo en la Honorable Cámara de Senadores el desalojo de los avá guaraní de itakyry de sus tierras ancestrales, sin tomar en cuenta “la consulta previa, la participación y el consentimiento informado”, violando todos sus derechos garantizados por la constitución nacional, la ley 904 y el convenio 169 de la OIT con el agravante de ser presidenta de la comisión de comisión de derechos humanos de la honorable cámara de senadores, y que en su práctica ha demostrado incoherencia y su falta de moral ética y humana para ocupar este cargo tan importante para nuestro pueblo tan sacrificado y oprimido, ya que ha favorecido los intereses económicos de los que lucran a costa de la muerte de nuestro pueblo, atentando contra la soberanía nacional, pisando sobre derechos humanos innegociables como el derecho a la vida, en perjuicio de los dueños legítimos de este territorio, itakyry, los avá guaraní.

En solidaridad con nuestras hermanas y hermanos de Itakyry y de todas las comunidades indígenas y campesinas que son víctimas de los agrotóxicos convocamos a toda la ciudadanía, a las organizaciones sociales de niños y niñas, de mujeres, jóvenes, estudiantes, comisiones vecinales barriales, asentamientos urbanos, sin techo, sin tierras, a los trabajadores y trabajadoras, a los educadores, a los indígenas urbanos y campesinos que viven en la ciudad y el campo a participar de la Movilización a realizarse el Lunes 16 de Noviembre de 2009.

“YVY RESAî TEKOVE RENDA” Tierra sin contaminación, lugar de VIDA!

MOVIMIENTO INDIGENA URBANO – RED CULTURAL DE PUEBLOS INDIGENAS – COORDINADORA NACIONAL DE VÍCTIMAS DE AGROTÓXICOS – KUCHINGUI MAI REKOTY PUEBLO ACHE – SIFEPOSNNA – COORDINADORA DE PASTORAL INDIGENA – SUNU – BASE IS – COMUNIDADES URBANAS DE CERRO POTY, COMUNIDAD CENTRO NUEVA ESPERANZA, TARUMANDYMI, ORGANIZACIÓN DE MUJERES NIVACHE, MARIN KAAGUY, VIÑAS CUE, TERMINAL, CATEURA, COMUNIDAD MAKA DE MARIANO ROQUE ALONSO-

Purple Label Ribbon Business Letterhead is easy to customize! Our 8.5″ x 11″ letterhead is great for all your invitations, promotional materials and professional mailings. Choose from five paper types and colors. Laser and inkjet compatible. Vibrant, full-bleed, full-color printing!

Purple Label Ribbon Business Letterhead by SublimeStationery
Create business stationery at zazzle.com

Powder Blue Label Ribbon Business Cards are great for self employed small business professionals or personal use. Copyright 2009-2010 Sublime Stationery

Powder Blue Label Ribbon Business Cards by SublimeStationery
More Powder Business Cards

Portal de Informações da Via Embratel. Os dados são carregados de forma massiva por arquivo, e visualizados no WebSite. Conta com visualização de Notícias e download de Arquivos.

Noticia

busca

..: Atuação

Atuação como Analista/Desenvolvedor JEE.

..: Cliente

Via Embratel

..: Tipo / Ano

Sistema Web / 2009

..: Tecnologias

Java, JEE, Oracle DB, Apache Tomcat, JPA/Hibernate, JSF/Jboss Rich-Faces,  Jboss Seam

In the last post, I talked about the first day of The Developers Conference. Now lets talk about day number 2.

Very different from the previous day, this one started full of coding. And during the day, we kept seeing lighting talks and Vinicius’ toys. The only real problem we had was that the place ran out of eletricity for a while… but at least it didn’t last too long and the event could finish right.

Rod Johnson

The first speech was again from Rod Johnson. But this time, it was not philosophical at all. He presented Spring Roo, a project that aims at bringing to Java the productivity found in Rails. After seeing what he showed, I believe it. And love it.

In summary, the tool generates a lot of boilerplate code that we would otherwise have to write ourselves. And keeps it all out of the way while you develop your project.

I liked this so much that Spring Roo will be covered in a new post, exclusive to it, soon enough. And look, I don’t like Spring, but this thing can make me change my mind.

Rod Johnson on SpringRoo

Lightning Talks

One of these lightning talks was about Spring best practices, which followed Spring Roo’s presentation. Ricardo Jun presented it, and mentioned things like how people tend to simply want to totally discard xml, instead of using it in moderation; the importance of using tools; the importance of modularization and also that we should always mind concurrency.

Jun and Spring Best Practices

Another quick demonstration about robotics had an application server installed in a device, which was accessed through http. This device was connected to a lamp, and Vinicius turned it on and off through a web interface. Meaning: I want all the power plugs in my house accessible through the internet!! =D

On the note of excited people, I must talk about Vinicius Senger again. When presenting the balloon robot for the second time now, he breathed Helium, the gas used in the balloon to make it float. The effect was that his voice got very thin for a few seconds, creating a very funny moment.

Balloon Robot

Another lightning talk was about what was previously called Web Beans – now Weld: the reference implementation of JSR 299: Contexts and Dependency Injection. Alessandro Lazzarotti, from Red Hat, gave a quick demo on the implementation which is, of course, full of annotations everywhere.

An interesting lightning talk was about performance in JPA. Alberto “Spock” talked about how the Open Session in View filter pattern can be a little bit outdated when it comes to ajax applications – an environment which wasn’t there when the pattern was created.

Alberto "Spock" on Ajax and JPA Performance

In Globalcode’s blog here, he explains this problem better. During the presentation, he also mentioned the Apache Myfaces Orchestra project, which should also help minimize the problem bringing the conversation scope to your application. The conversation scope was first introduced by JBoss Seam, and brings us a scope bigger than request, and smaller than session, which can really help us manage resources in a lot of situations.

Mike Keith

This time Mike Keith presented about JPA 2.0. The goal of JPA 2.0 is basically to standartise what we currently do with, for example, hibernate, because we can’t with JPA 1. Nothing really new was presented – unless you didn’t know anything about JPA 2 already. But a few topics are worth mentioning.

A new evictall function was added. Useful to completetly clear cache between test cases. Small change but sounds interesting.

Now my pet peeve: the new criteria API. He presented it and showed a few examples and comparisons between the criteria code and the JPQL code. Just made me dislike it more. Just as a reminder, I already said that I don’t like this thing when I wrote about Globalcode’s Casual Class #006. Trying to access a database completely through OO code is just too much purism. At least, Mike is a very funny presenter to watch =)

Mike Keith on JPA 2.0

Francisco Gioelli (Google)

The original plan was to have Chris Schalk talking about Google App Engine. Unfortunatelly, he had problems with the immigration and couldn’t get into the country. So google sent Francisco Gioelli, who did a nice job instead.

Among other languages, Google App Engine allows us to write Java web applications and publish them on the google cloud, leaveraging from the monstruous google scalability. A few features available include possibility of scheduling cron tasks through a xml file and the Big Table, their (non-relational) database. This last feature is the only thing that makes me a little bit worried about using google’s cloud.

Francisco on Google App Engine

This talk had a demo and was complemented by another one from Rafael (from Globalcode) – this last one using JSF 2.0 – nice! Two little extras mentioned by him: each request can take at the very most 30 seconds and the internal server used seems to be Jetty.

Alejandro Guizar (Red Hat Mexico)

This one was about BPEL. This is not a topic I can talk too much, so I won’t. The only thing that took my attention was something called BPEL Unit. I never heard of it and found interesting that such a thing exists. But I couldn’t find any good references…

Alejandro on BPEL

Cloud Computing Panel

To close the event, a panel on Cloud Computing, featuring the main speakers that were present. This is a trendy topic nowadays, full of buzz words, but interesting, it was!

Ed Burns started talking that Sun have something (I forgot the name…) since 2000. Makes sense… very tipical of Sun: great products, terrible marketing. He also mentioned Zembly.com. If you are insterested, go to the site now. I just went there and found out that they are closing the service permanently from November 30th. Nice… (no, not really).

From Rod Johnson, we learnt that Springsource have their hand on Cloud Computing in the form of CloudFoundry. Also, he made sure to say how important it is to have multiple players in the market. Agreed.

Some points were easily agreed by the panelists:

• private clouds will have big importance in the future;
• a good thing of the cloud is the economy;
• but a bad thing is the loss of control in a lot of senses, but probably mainly data;
• we need easy of migration between cloud providers.

Someone asked about cloud computing and peer-to-peer. The panelists didn’t seem to believe too much in this possibility. Well, who knows…

A lot of gurus on Cloud Computing

Last picture, to change the mood a litle bit:

Relaxing between presentations

And so it ends this year’s event. I’m already waiting for the one next year! =D

Comunicado

La SEAM informa sobre procedimientos en la Comunidad Ava Guaraní

Ante  los sucesos ocurridos en Ytakyry (Departamento de  Alto Paraná ) durante los últimos días de la semana del 1 al 7 de los corrientes,  La Secretaría Nacional del Ambiente informa ante la opinión pública los procedimientos realizados bajo su competencia:

De la visita constatada y de las fiscalizaciones realizadas por el Ministro del Ambiente acompañado de funcionarios de la SEAM, se ha constatado la efectiva intoxicación de miembros de las cinco comunidades indígenas asentadas en la localidad de Ytakyry, víctimas de haber sido fumigados desde un avión con sustancias tóxicas.

El sábado 7 de noviembre se han constituido en las comunidades los Ministros del Ambiente, de Salud Publica, de la Niñez y Adolescencia, de la Secretaría de Acción Social,  el Viceministro de Asuntos Políticos del Ministerio del Interior y la Presidenta Instituto Nacional del Indígena.  En dicha visita se escuchó a los líderes indígenas de las comunidades Ava Guaraní, habitantes ancestrales del lugar. Donde, de manera análoga, comentaron la fumigación aérea que recibieron como amenaza para que abandonen sus tierras. La comitiva gubernamental constató, además, los daños sufridos en el cementerio de la comunidad y la destrucción de la escuela.  Además recibieron denuncias sobre el constante asedio que sufren, según afirman, por parte de los colonos brasileños, con complicidad del Poder Judicial y del Ministerio Público.

Cabe aclarar que las fincas pertenecen al Instituto Nacional del Indígena y en la actualidad pesa sobre las mismas medidas cautelares que protegen la posesión de las comunidades indígenas. Sin embargo, de manera totalmente arbitraria, el Ministerio Público ordenó el desalojo de las comunidades, por supuesto hecho de invasión, siendo que estas comunidades están alojadas en la región desde tiempos inmemoriales.

La Secretaría del Ambiente  procede en estos momentos a fiscalizar e intervenir toda el área perimetral de la comunidad indígena, a los efectos de constatar si los propietarios lindantes se ajustan a las normas ambientales. A simple vista se ha podido observar la violación de normas como ser la franja de seguridad alrededor de los caminos y los 100 metros exigidos de protección de las comunidades humanas. También levanta toma de muestras de tierra y agua. Estos procedimientos se realizan a los efectos de instruir posibles sumarios a  los responsables y probablemente suspender actividades en los casos que no tengan licencia ambiental o podrían afectar a la salud de las personas y el ambiente.

As I am currently working with JBoss seam, I had to install JBoss Tools on my Fedora Eclipse 3.4.2 – Fedora 11 -.

So in order to share the procedure to every one and mostly to avoid to forget or lose it I decided to write it on this blog.

In addition, it permit to avoid eclipse/JBoss Tools problems dependence such as :

And Errors such as :

Cannot complete the request.  See the details.
Unsatisfied dependency: [org.hibernate.eclipse.feature.feature.group 3.2.4.v200909151014R-H192-GA] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.wst.xml.core/1.1.0

So these are the steps :

I] Install Eclispe on your Fedora.

I.I] Open a terminal as standard user – here mine “fhornain” – and be root.

[fhornain@localhost ~]$ su -

[root@localhost ~]# yum install java-1.6.0-openjdk-devel

[root@localhost ~]# yum install eclipse-platform

II ] Launch eclipse.

II.I] Indeed you should select in you Fedora main menu bar  Applications > Programming > Eclipse

If not, launch a terminal and run the following command :

[fhornain@localhost ~]$ eclipse -vm /usr/bin/java

Rem: Change the path /usr/bin/java if it is not your java default location

Then you should see the eclipse starting banner – see below -

II.II] Then eclipse should ask you where you would like to save your projects – see image below -

The default location should be fine – well, for me -

II.III] Then Welcome screen appears – see below -. Close it with a click on the top left cross.

III ] Install JBoss Tools

III.I] When Eclipse starts, go to Help > Software Updates. The following window should appears :

III.II] Then click on the tab named “Available Software” – see below -

III.III] Then click on button “Add Site” on the right of the window – see above – :

III.IV] You see appear a new window where you are going to past the following URL : http://download.jboss.org/jbosstools/updates/stable/ which is the offcial JBoss Tools URL – see below -

Then click the OK button.

III.V] Then do the same with http://download.eclipse.org/releases/ganymede/ and http://download.eclipse.org/birt/update-site/2.3/ as mentioned for JBoss Tools in points III.III] and III.IV]

III.VI] You should see appear a new line in the “Software updates and add-ons” window – see below -

III.VII] Then click on the link “Ganymade Update Site” as show in the above picture :

III.VIII] Then go down and choose “Web and Java EE Development”

And click on the install button – see above -.

Then the installation start – see above – :

Then click on next button, accept the term of the licence and click on  the finish button.

The packages installation starts – see above – :

Finally the installation finish and the following window appear in order to reboot the eclipse IDE application – see below -

Click on the Yes button

III.IX ] Now we’ll do the same steps for JBoss Tools and Bitr as we did for Ganymed “Web and Java EE Development”.

You should see the entered JBoss Tools links done during III.III] and III.IV] steps then click on the JBoss Tools arrow and select JBoss Tools line – see above -

And do the same procedure as we did for Ganymed “Web and Java EE Development” at step III.VIII].

Let’s hope it clear.

Now you can play with seam and other JBoss projects…

IV] Launch Seam project with Eclipse and Jboss Tools.

IV.I] Indeed you should select in you Fedora main menu bar  Applications > Programming > Eclipse

If not, launch a terminal and run the following command :

[fhornain@localhost ~]$ eclipse -vm /usr/bin/java

Rem: Change the path /usr/bin/java if it is not your java default location

You should see appear the following window :

IV.II] Then click on the main menu bar File > New > Project and the following window appears – see below -

Then Choose your new JBoss Seam Project and name it.

BTW, do not forget BIRT otherwise you will not have JDBC Connectors

Enjoy !

Related links : http://www.jboss.org/community/wiki/InstallingJBossTools