Hashtable env = new Hashtable();
env.put(“java.naming.factory.initial”, “com.sun.jndi.dns.DnsContextFactory”);
DirContext ictx = new InitialDirContext(env);
Attributes attrs = ictx.getAttributes(“gmail.com”, new String[]{“MX”});
Attribute attr = attrs.get(“MX”);

Bijection :
allows objects to be in-jected or out-jected to/from assigned variables using the @In and @Out annotations

Contexts :
Stateless context
Event (or request) context
Page context
Conversation context
Session context
Business process context
Application context

Most of these contexts are similar to other technologies but the 2 new ones are: conversation context, and business process context.
The documentation says they are:

3.1.6. Business process context
The business process context holds state associated with the long running business process. This state is managed and made persistent by the BPM engine (JBoss jBPM). The business process spans multiple interactions with multiple users, so this state is shared between multiple users, but in a well-defined manner. The current task determines the current business process instance, and the lifecycle of the business process is defined externally using a process definition language, so there are no special annotations for business process demarcation.

3.1.4. Conversation context
The conversation context is a truly central concept in Seam. A conversation is a unit of work from the point of view of the user. It might span several interactions with the user, several requests, and several database transactions. But to the user, a conversation solves a single problem. For example, “book hotel”, “approve contract”, “create order” are all conversations. You might like to think of a conversation implementing a single “use case” or “user story”, but the relationship is not necessarily quite exact.

A conversation holds state associated with “what the user is doing now, in this window”. A single user may have multiple conversations in progress at any point in time, usually in multiple windows. The conversation context allows us to ensure that state from the different conversations does not collide and cause bugs.

It might take you some time to get used to thinking of applications in terms of conversations. But once you get used to it, we think you’ll love the notion, and never be able to not think in terms of conversations again!

Some conversations last for just a single request. Conversations that span multiple requests must be demarcated using annotations provided by Seam.

Some conversations are also tasks. A task is a conversation that is significant in terms of a long-running business process, and has the potential to trigger a business process state transition when it is successfully completed. Seam provides a special set of annotations for task demarcation.

Conversations may be nested, with one conversation taking place “inside” a wider conversation. This is an advanced feature.

Usually, conversation state is actually held by Seam in the servlet session between requests. Seam implements configurable conversation timeout, automatically destroying inactive conversations, and thus ensuring that the state held by a single user login session does not grow without bound if the user abandons conversations.

Seam serializes processing of concurrent requests that take place in the same long-running conversation context, in the same process.

Alternatively, Seam may be configured to keep conversational state in the client browser.

<field-validator type=”required”>
<param name=”trim”>true</param>
<message>Zip Code is required</message>
</field-validator>

<field-validator type=”regex”>
<param name=”expression”><![CDATA[^\d{5}$]]></param>
<message>Zip Code must be 5 characters</message>
</field-validator>

</field>

• Part 1. Separate software concerns with aspect-oriented programming
• Part 2. Learn AspectJ to better understand aspect-oriented programming
• Part 3. Use AspectJ to modularize crosscutting concerns in real-world problems

response.setContentType("application/vnd.ms-excel");
response.setHeader("Content-Disposition","inline" );

Those 2 lines make the instant translation of the HTML I put in the page go to excel.  Now something massive to remember here: The formatting is pretty unpredictable if you use css or any fruity styles.  Luckally in my case I didn’t need to use either; just output the data.

In either case you simply draw the HTML as you would to output a basic page with the response lines telling your browser that excel owns the page.

Link to Content

public class SomeApplet extends JApplet implements DropTargetListener {

The first step is to implement the DropTargetListener as you extend JApplet (or Applet). This is going to provide the applet the ability to contain a Drop Target. That is right, I said “contain”. I have tried this attaching the Drop Target Listener to the Applet itself unsuccessfully however; it attaches fine to a JPanel or even a Label.

JPanel jp1 = new JPanel();
DropTarget dt2 = new DropTarget(jp1, this);
jp1.setDropTarget(dt2);

Next declare the panel and a Drop Target then attach the drop target to the panel (once again this could be done with a label or whatever).

public void drop(DropTargetDropEvent dtde) {
int action = dtde.getDropAction();

dtde.acceptDrop(action);

fromTransferable(dtde.getTransferable());

dtde.dropComplete(true);
}

First you get the Drop Action from the dtde object which represents the Drop Target Event then accept the Drop using the acceptDrop function. This registers the accepted drop with the applet. Once you accept then you dispatch the function which handles the drop (uploading the file in our case) then tell the applet the drop is complete using the dropComplete function. This is a great place for error handling to return false if there is an error or true if the drop function was successful. Both will have different display consequences which can be seen through testing

Object data = t.getTransferData(DataFlavor.javaFileListFlavor);
java.util.List<File> fileList = (java.util.List<File>) data;

for (File file : fileList) {
if (!is_in_list(file_names, file.getAbsolutePath()) && !file.isDirectory()) {

Lastly we cycle through the list of files we got and decide whether to save them or what to do.

And there you have it: a medium level overview on how to drop a file into the browser on an applet and have it upload.

1. Run javascript commands from within your applet
2. Control your applet through javascript

Step 1 Setup the Object Tag:

<object type=”…”>
<param name=”mayscript” value=”true”>
<param name=”scriptable” value=”true”>
</object>

*Note – I did not show the archive, code or other params needed to setup an object as they are dependent on your applet.
*Note – This setup allows for javascript communication in and out of your applet

Step 2 From within the java call some javascript

import javascript.*;
….
JSObject win = JSObject.getWindow(this);
win.eval(“alert(‘test’);”);

*Note – To make this work you need to add plugin.jar from within your jdk/lib folder in the project classpath and include it in your deployment (archive = “…, plugin.jar”).

And tada you can call java functions (yes the public ones) from javascript just by referencing the id of the object (dot) the function name. The translation between object types can get a bit tricky if you try to do a map or hash but with strings, ints and the like its pretty straight forward. The primary use for this was in setting up an event and using javascript to trigger it on submission of a form however the possibilites are endless

/* File Loaded here into a File Object as f */
PreparedStatement ps = conn.prepareStatement(“INSERT INTO TBL VALUES(?, ?)”);
ps.setString(1, f.getName());
FileInputStream fis = new FileInputStream(f);
ps.setBinaryStream(2, fis, fis.available());
ps.execute();
ps.close();

And tada your record will be loaded into the blob.

*** Not Shown ***
Oracle JDBC Connection – This example does not use any framework/connection helper (i.e. Hibernate/EJB)