I filed some tickets in the past against the JSF Spec (meaning API definition) as well.

Here is my (incomplete) list:

I want more interfaces on javax.faces.component:
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=322

Why does Unified EL Spec say If A is String: return A. Otherwise, if A is null: return "".
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=323

I can understand why they added this guy in UIInput, but IMO this is wrong:
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=327
(Please no EditableValueHolder2 ;-))

Autocomplete was introduced on inputText, with the advent of JSF 1.2 (due to the rise of ajax),
but they forgot the html_form component:
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=418

I am pretty sure some more methods are missing on ExternalContext:
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=438
In Trinidad we have a ExternalContextUtil, where we add those bits that are missing...

Why not making subforms part of the standard (since jsf 2.0 already contains some new tags):
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=441

These came up due to bugs, Gabrielle Crawford and I worked on (since our ADF Faces Framework has an optimized JSF lifecycle):

-https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=331

-https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=332

I hope these tickets (and some others) are addressed in the next generation of JSF 2.0 :-)
Some other cool things were already added, as Ryan showed in his blog. I am really looking forward for the JSF.next (and for Servlet 3.0 as well).

First of all we need a little bit Javascript, i use the Masked Input Component from Jonas Raoni Soares Silva:

[sourcecode language='javascript']

addEvent = function(o, e, f, s){
var r = o[r = "_" + (e = "on" + e)] = o[r] || (o[e] ? [[o[e], o]] : []), a, c, d;
r[r.length] = [f, s || o], o[e] = function(e){
try{
(e = e || (window.event ? (arguments = [].slice.call(arguments)).unshift(e = event) || 1 && e : {})).preventDefault || (e.preventDefault = function(){e.returnValue = false;});
e.stopPropagation || (e.stopPropagation = function(){e.cancelBubble = true;});
e.target || (e.target = e.srcElement || null);
e.key = (e.which + 1 || e.keyCode + 1) - 1 || 0;
}catch(f){}
for(d = 1, f = r.length; f; r[--f] && (a = r[f][0], o = r[f][1], a.apply ? c = a.apply(o, arguments) : (o._ = a, c = o._(e), o._ = null), d &= c !== false));
return e = null, !!d;
}
};
removeEvent = function(o, e, f, s){
for(var i = (e = o["_on" + e] || []).length; i;)
if(e[--i] && e[i][0] == f && (s || o) == e[i][1])
return delete e[i];
return false;
};
MaskInput = function(f, m){
function mask(e){
var patterns = {"1": /[A-Z]/i, "2": /[0-9]/, "4": /[\xC0-\xFF]/i, "8": /./ },
rules = { "a": 3, "A": 7, "9": 2, "C":5, "c": 1, "*": 8};
function accept(c, rule){
for(var i = 1, r = rules[rule] || 0; i <= r; i<<=1)
if(r & i && patterns[i].test(c))
break;
return i <= r || c == rule;
}
var k, mC, r, c = String.fromCharCode(k = e.key), l = f.value.length;
(!k || k == 8 ? 1 : (r = /^(.)\^(.*)$/.exec(m)) && (r[0] = r[2].indexOf(c) + 1) + 1 ?
r[1] == "O" ? r[0] : r[1] == "E" ? !r[0] : accept(c, r[1]) || r[0]
: (l = (f.value += m.substr(l, (r = /[A|9|C|\*]/i.exec(m.substr(l))) ?
r.index : l)).length) < m.length && accept(c, m.charAt(l))) || e.preventDefault();
};
for(var i in !/^(.)\^(.*)$/.test(m) && (f.maxLength = m.length), {keypress: 0, keyup: 1})
addEvent(f, i, mask);
};
[/sourcecode]

then we define the inputfield:

[sourcecode language='html']

[/sourcecode]

and last a little bit JS-Code which decorates the current formulare after each rerender, but it at the end of your page:

[sourcecode language='html']



[/sourcecode]

That's it :) Every time A4J rerenders the page the decorator search all marked elements and creates a MaskInput object for the elements.

Try it!

Seam is an application framework based on several different technologies: JSF, Facelets, EJB3, and AJAX. If you are interested in creating rich internet applications then Seam or IceFaces are nice packages for Java based systems. Since I'm interested in building portlets for JBoss Portal using Seam is a good fit. If you're interested in IceFaces I can say its a nice package too and I've used it successfully on other applications.

In this post I'm not really going to discuss in too many details the platforms and how they work - if you want more info on Seam then go to their site or Google it. The Seam site is really quite nice. I'm going to detail out how I got my system configured, what tips/tricks I learned, and make a decision on if I'll use these tools on a real project that I have coming up.

Getting going with Seam is really quite simple. There's one basic rule: RTFM. The Seam site is good and has great docs on getting everything setup so use it. Because I'm into self torture I'm going with the Seam 2.0 beta version and I'm going to use this with Elcipse 3.4 and add on top of that the latest JBoss Tools suite of plugins and features. I've grabbed all these from the JBoss CVS repo {CVS? dudes! SVN is way better!}. I'm also using the latest JBossAS 4.2 build for Win32 and MySQL 5.1 as well. I'm using JDK 1.6U7

I messed around with JSF about a year ago so the first thing I wanted to do was get a refresher on JSF. I found these sites useful:

• http://www.jsftutorials.net/
• http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JSFIntro.html
• http://java.sun.com/javaee/5/docs/tutorial/doc/bnaph.html

I got thru those pretty quickly and started looking thru examples and then used the JBoss Tools in eclipse to generate and deploy a test seam application using this page as a guide. The tools interface is pretty nice.

The interface is pretty obvious if you are into Eclipse. In order to really work with seam you need to be in the right perspective. Once you are there the menu options for creating projects will have wizards and stuff. In this shot I've generated my basic project and deployed it within the environment to my jboss AS. The console output is right in the window. On the right are various widgets for the UI layout views. In the lower left is the properties panel - to me that's in an odd place, but you can move it around.

I was able to deploy and then re-deploy this to my jboss server. You can make incremental updates to some kinds of things like xhtml docments and see the changes in the running app server. Other things in typical J2EE fashion require a full restart or a re-deploy action.

Now that I've got that working I'm onto my first attempt to use the application generation tools to reverse engineer a complete application. What I have is a MySQL database with a bunch of tables and relations and I want to generate some basic user interfaces from that. The process is pretty simple, just click click on your project and pick off "Generate Seam Entities" and off it will go. You can review some settings in your project if things do not work right. The output of this will be a complete set of hibernate objects, POJOs to work against them and a set of web content and forms to display and show data.

Doing this against my schema had some mixed results. Immediately following the generation I had several compile issues. In one class an annotation was duplicated for some reason. I deleted the second copy and that was solved. Another issue proved more difficult. I happen to have a table called "Messages" in my schema. When seam RE's the table it names the object "Messages" of couse, but this causes a conflict with some internal objects in Seam itself called "Messages". I refactored my objects to "BerenMessages", but this does not fix all the references in the XHTML so I've got more work to do there. Here's a shot of that:

I can't see why that would cause an issue. I even fully qualified all the packages to see if that would fix the issue. I guess I'll have to dig into this a bit more. In any case I got around this temporarily by just deleting the method and then removing the message functions from the xhtml menuing that was generated so that I wouldn't get any errors at deploy time. With that done my application will deploy to the JBoss server with no errors.

What is produced is a bare bones set of DAOs, POJOs, controller logic, and a set of xHTML screens and forms for data entry/manipulation. There's also a sample authentication mechanism that is while functional not actually authenticating against anything in particular, but it does show how sessions work.

So well - hey that's pretty darn cool. In about 2 hours a relatively ignorant person can generate an app like this? Not too bad.I suspect that my issues with the initial generation are due to using some MySQL specific things (like the enum type) and then perhaps some back luck with tables and things that are unfortunately named.

I'm going to play around with this and see how to get a few portal gadets working and I'll post my "part three" on this topic.

Dentro de nuestro proyecto web se nos crean comunmente las páginas jsp, y su contraparte en código java dentro de un paquete en la carpeta Source Packages, dentro de ese paquete vamos a colocar el archivo .properties, teniendo en cuenta que este se va a llamar igual que la clase que lo va a leer, (por ejemplo: En mi paquete tengo una clase llamada Reportes.java, dentro del mismo paquete pondré un archivo de propiedades llamado reportes.properties), el código para ller este archivo quedaria así:

  String nombrePROP = Reportes.class.getSimpleName().toLowerCase() + ".properties";
  Properties props = new Properties();
  props.load(Reportes.class.getResourceAsStream(nombrePROP));
  String strPathOrigen = props.getProperty("pathORI");
  String strPathXLS = props.getProperty("pathXLS");

Con esto ya podriamos leer las propiesades que se tenga dentro de nuestro archivo properties.

Seguir leyendo en christmo99.wordpress.com

Saludos...

Dentro de nuestro proyecto web se nos crean comunmente las páginas jsp, y su contraparte en código java dentro de un paquete en la carpeta Source Packages, dentro de ese paquete vamos a colocar el archivo .properties, teniendo en cuenta que este se va a llamar igual que la clase que lo va a leer, (por ejemplo: En mi paquete tengo una clase llamada Reportes.java, dentro del mismo paquete pondré un archivo de propiedades llamado reportes.properties), el código para ller este archivo quedaria así:

  String nombrePROP = Reportes.class.getSimpleName().toLowerCase() + ".properties";
  Properties props = new Properties();
  props.load(Reportes.class.getResourceAsStream(nombrePROP));
  String strPathOrigen = props.getProperty("pathORI");
  String strPathXLS = props.getProperty("pathXLS");

Con esto ya podriamos leer las propiesades que se tenga dentro de nuestro archivo properties.

Ahora para poder poner las propiedades sacadas del archivos en variables globales, tendremos que hacer lo siguiente, fuera de cualquier método y dentro de la clase vamos a poner esto, como un método más.

  private static String strPathOrigen;
  private static String strPathXLS;

  static {
      try {
         String nombrePROP = Reportes.class.getSimpleName().toLowerCase() + ".properties";
         Properties props = new Properties();
         props.load(Reportes.class.getResourceAsStream(nombrePROP));
         strPathOrigen = props.getProperty("pathORI");
         strPathXLS = props.getProperty("pathXLS");
      } catch (IOException ex) {
         Logger.getLogger(Reportes.class.getName()).log(Level.SEVERE, null, ex);
      }
  }

Así todo lo que se saque del archivo properties se almacenará globalmente y se podrá usar dentro de toda la clase si es necesario.

Espero que les haya servido...

Saludos christmo...

Hola había tenido problemas al tratar de descargar un archivo desde el servidor, para que sea visualizado en los computadores clientes del sistema usando JSF, pero buscando un poco por allí pude encontrar como hacerlo, este método sirve para descargar archivos *.XLS y *.PDF con los que he probado, pero me imagino que debe funcionar para cualquier tipo de archivo, lo importante es reconocer que MIME Type tiene este archivo eso lo podremos encontrar en esta página.

File ficheroXLS = new File(strPathXLS);
FacesContext ctx = FacesContext.getCurrentInstance();
FileInputStream fis = new FileInputStream(ficheroXLS);
byte[] bytes = new byte[1000];
int read = 0;

if (!ctx.getResponseComplete()) {
   String fileName = ficheroXLS.getName();
   String contentType = "application/vnd.ms-excel";
   //String contentType = "application/pdf";
   HttpServletResponse response =(HttpServletResponse) ctx.getExternalContext().getResponse();
   response.setContentType(contentType);
   response.setHeader("Content-Disposition","attachment;filename=\"" + fileName + "\"");
   ServletOutputStream out = response.getOutputStream();

   while ((read = fis.read(bytes)) != -1) {
        out.write(bytes, 0, read);
   }

   out.flush();
   out.close();
   System.out.println("\nDescargado\n");
   ctx.responseComplete();
}

Saludos christmo ]]> http://christmo99.wordpress.com/?p=76 Fri, 15 Aug 2008 15:10:13 +0000 christmo http://christmo99.wordpress.com/?p=76 Hola había tenido problemas al tratar de descargar un archivo desde el servidor, para que sea visualizado en los computadores clientes del sistema usando JSF, pero buscando un poco por allí pude encontrar como hacerlo, este método sirve para descargar archivos *.XLS y *.PDF con los que he probado, pero me imagino que debe funcionar para cualquier tipo de archivo, lo importante es reconocer que MIME Type tiene este archivo eso lo podremos encontrar en esta página.

File ficheroXLS = new File(strPathXLS);
FacesContext ctx = FacesContext.getCurrentInstance();
FileInputStream fis = new FileInputStream(ficheroXLS);
byte[] bytes = new byte[1000];
int read = 0;

if (!ctx.getResponseComplete()) {
   String fileName = ficheroXLS.getName();
   String contentType = "application/vnd.ms-excel";
   //String contentType = "application/pdf";
   HttpServletResponse response =
   (HttpServletResponse) ctx.getExternalContext().getResponse();

   response.setContentType(contentType);

   response.setHeader("Content-Disposition",
                      "attachment;filename=\"" + fileName + "\"");

   ServletOutputStream out = response.getOutputStream();

   while ((read = fis.read(bytes)) != -1) {
        out.write(bytes, 0, read);
   }

   out.flush();
   out.close();
   System.out.println("\nDescargado\n");
   ctx.responseComplete();
}

Saludos y espero que sea de utilidad para ustedes...

$email_from = ""; // Who the email is from
$email_subject = ""; // The Subject of the email
$email_message = ""; // Message that the email has in it

$email_to = ""; // Who the email is too

$headers = "From: ".$email_from;

$semi_rand = md5(time());
$mime_boundary = "==Multipart_Boundary_x{$semi_rand}x";

$headers .= "\nMIME-Version: 1.0\n" .
"Content-Type: multipart/mixed;\n" .
" boundary=\"{$mime_boundary}\"";

$email_message .= "This is a multi-part message in MIME format.\n\n" .
"--{$mime_boundary}\n" .
"Content-Type:text/html; charset=\"iso-8859-1\"\n" .
"Content-Transfer-Encoding: 7bit\n\n" .
$email_message . "\n\n";

/********************************************** First File ********************************************/

$fileatt = ""; // Path to the file
$fileatt_type = "application/octet-stream"; // File Type
$fileatt_name = ""; // Filename that will be used for the file as the attachment

$file = fopen($fileatt,'rb');
$data = fread($file,filesize($fileatt));
fclose($file);

$data = chunk_split(base64_encode($data));

$email_message .= "--{$mime_boundary}\n" .
"Content-Type: {$fileatt_type};\n" .
" name=\"{$fileatt_name}\"\n" .
//"Content-Disposition: attachment;\n" .
//" filename=\"{$fileatt_name}\"\n" .
"Content-Transfer-Encoding: base64\n\n" .
$data . "\n\n" .
"--{$mime_boundary}--\n";
unset($data)
unset($file)
unset($fileatt)
unset($fileatt_type)
unset($fileatt_name)

/********************************************** Second File ********************************************/

$fileatt = ""; // Path to the file
$fileatt_type = "application/octet-stream"; // File Type
$fileatt_name = ""; // Filename that will be used for the file as the attachment

$file = fopen($fileatt,'rb');
$data = fread($file,filesize($fileatt));
fclose($file);

$data = chunk_split(base64_encode($data));

$email_message .= "--{$mime_boundary}\n" .
"Content-Type: {$fileatt_type};\n" .
" name=\"{$fileatt_name}\"\n" .
//"Content-Disposition: attachment;\n" .
//" filename=\"{$fileatt_name}\"\n" .
"Content-Transfer-Encoding: base64\n\n" .
$data . "\n\n" .
"--{$mime_boundary}--\n";
unset($data)
unset($file)
unset($fileatt)
unset($fileatt_type)
unset($fileatt_name)

/********************************************** End of File Config ********************************************/

// To add more files just copy the file section again, but make sure they are all one after the other! If they are not it will not work!

$ok = @mail($email_to, $email_subject, $email_message, $headers);

if($ok) {
echo "<font face=verdana size=2>The file was successfully sent!</font>";
} else {
die("Sorry but the email could not be sent. Please go back and try again!");
}
?>

My first post is this, on Trinidad 1.2.9.

This does NOT mean I give up this private blog. Just once in a while I'll post some news/entries there ;-)

1.0.9 release notes are here.

1.2.9 release notes are here.

If you are using Trinidad it would be great if you add your company / client to this wiki page.

For Feedback, questions or bug reports the Trinidad community is a great resource!