jimmy Auction

JavaMail provides a common, uniform API for managing electronic mail. It allows
service-providers to provide a standard interface to their standards-based or
proprietary messaging systems using the Java programming language. Using this
API, applications access message stores, and compose and send messages.

In a portal environment, an application implemented using Java Server Faces technology can be surfaced as a portlet by creating a JSF portlet. Oracle WebLogic Portal has supported the use of JSF for the implementation of portlets by developing the WLP native bridge since a standards-based bridge did not exist. Starting in WLP 10.3.2, the support for JSF portlets continues to be enhanced with the added support for the JSR-329 standards-based JSF bridge. The new JSR-329 bridge is now the default for JSF portlets which continues to leverage all of the powerful features of WLP.

package com.util.ui;

import java.io.Serializable;
import java.util.Date;

public class PatientBackingBean implements Serializable{

private long ID;
private String firstName;
private String lastName;
private Date dOB;

public PatientBackingBean() {
System.out.println("PatientBackingBean called and instuntiated");
}

public long getID() {
return ID;
}
public void setID(long iD) {
ID = iD;
}
public String getFirstName() {
return firstName;
}
public void setFirstName(String firstName) {
this.firstName = firstName;
}
public String getLastName() {
return lastName;
}
public void setLastName(String lastName) {
this.lastName = lastName;
}
public Date getdOB() {
return dOB;
}
public void setdOB(Date dOB) {
this.dOB = dOB;
}

public String save(){
System.out.println("Entered the save method");
System.out.println("Exited the save method");
return "success";
}
}

hi ..

i have created a jboss portlet application where i need to show/hide certain portlets based on the user liscence (say the customer enter a liscence key > the application validates the liscence and then enable a portlet which comes with the liscence .) how can i implement the said.

1. .
2. is the "user.dir" system property.
3. is the "user.home" property.
4.

is a bit of a kludge no matter how you approach it. Here's an alternate technique that works if you have a class loaded from a JAR not on the system classpath.

CodeSource src = MyClass.class.getProtectionDomain().getCodeSource();
if (src != null) {
URL url = new URL(src.getLocation(), "MyApp.properties");
...
}
else {
/* Fail... */
}