Javadoc in eclipse offline?

I have noticed that JavaDoc info only works in eclipse when I am connected to the internet. Is there someway to make it work in eclipse when I am offline??

Are you getting an error message? What does it say?

Similar Messages

Generate a javadoc with eclipse

hello!!!
Is someone know how to generate a javadoc with eclipse???
I find one solution, but I have to set the javadoc.exe location, and i don't know where is it...
please could you help me???
s@bine

javadoc.exe file is in the same place as your java.exe file
%JAVA_HOME%\bin
You need to get the full JDK (not just the JRE) and I know this is the case for JDK 1.2 and above (not sure about any other previous version)

Using javadocs in Eclipse

My team and I are trying to use javadocs in eclipse to document our source codes. I have used the javadoc generator in eclipse but do I have to manual comment in the details of the javadoc such as parameters, and a summary of the method? Is it possible to hide the javadocs? We just want to have a seperate folder for javadocs where we can view/edit the javadocs and still have no javadocs or comments within our code. anyone got suggestions????

Hi,
Well, Eclipse adds nothing special here. But you have actually an interesting idea...
Some (long) time ago I used to hear that it was hailed as a big progress a possibility to store all actual descriptions along with the Java code and to generate by them the entire finished documentation automatically. But now, it seems, you want to go back in time...
I believe, the standard Javadoc is unable to support anything like this.
However, if you still want to use Javadoc in such an arrangement so as to generate the overall documentation skeleton (as well as to employ Javadoc's HTML output engine), you will need to develop your own doclet or a taglet, at least.
For instance, you could introduce some special tags using which you would specify the locations of your description files (directly or using some identifiers). Then, your taglet would process those tags, read those descriptions from the files and feed them to Javadoc.
Another way is to imply the locations of your description files from the program element (i.e. class, method or field) being processed by Javadoc. The doclet API provides all necessary information together with the location of a Java source file. So you could use it to find your custom description files somewhere nearby it.
I suggest also to look at this product:
http://www.filigris.com/products/docflex_javadoc/
This is a highly customizable Javadoc doclet. More precisely, this is a system for rapid development of professional quality doclets from scratch (with the support of both framed/single-file HTML and RTF output). If you are prepared to buy some number of licenses, we could very much customize this product for your needs. So, your task will be solved with no problem.
Regards,
Leonid Rudy
http://www.docflex.com

Javadocs in Eclipse

How to do javadocs in Eclipse?

Javadoc is a tool for generating API documentation in HTML format from doc comments in source code.
http://java.sun.com/j2se/javadoc/writingdoccomments/index.html

Viewing javadoc's in eclipse

Hello, just a quick one...
When using eclipse, if i click on a class name which is in the standard API then i can view the javadoc through eclipse, how can i set this up so i can view it for non standerd classes, which come with the source code and or javadocs in a seperate file?
Thanks for any help

Select your project, then navigate to Project > Properties; select 'Java Build Path' and select the tab 'Libraries'; select the .jar file you want to attach javadocs for (expand it) and select the option 'Javadoc location'; select the directory where the (API) docs are stored and voila.
kind regards,
Jos

Javadoc Offline ?

Hello,
I wonder if the javadoc's SDK can be accessed offline for integration into Eclipse and NetBeans ?

Unfortunately there is not a solution currently. Interestingly I had an email exchange with the LiveCycle documentation team lead last week and brought this issue to her attention. I will update this thread if (and when) something is available.
Steve

Offline-searchable javadoc

Is there an offline-searchable copy of the java docs? Knowing just where to find the documentation on JList is non-trivial for those, like me, who are new to Java.
Having to go back to the online site to conduct a search instead of intuitively knowing where to navigate through what seems like a random spattering of categories and links is very annoying.
I don't like .NET but I'll give Microsoft one thing: their MSDN Library is first rate, and if Sun offered something similar, it would make life less painful when developing Java apps.
Thanks :)
PS, I've installed netBeans 5.0 and the help that comes with it seems to deal with the IDE itself, and not with the Java language. Also, the help that comes with code-completion is only useful if you know the Java API like the back of your hand to begin with, which I don't.

And to kablair, if you don't like newcomers to Java,
and their questions, why do you read this particular
forum? If you can't handle these sorts of questions,
then perhaps you should stick to programming or
reading expert fora. There's no need to take my
question personally. I don't mind newcomer questions. I do mind people who come here and start blaring about how Javadoc sucks and MSDN rules and Sun is just so lucky they're going to write Java code. See, it really gets on my nerves because then they usually produce a list of problems that are either inaccurate or issues with them rather than the tools and documentation.
And what's wrong with autoboxing/unboxing? Anything
that makes for simpler and more readable code is a
good thing, and given that Java is the most prolix
language I've ever used, I would have thought that
such a time saver would be welcome. Maybe you should
go back to Java 1.0, because 1.5 has other,
blasphemous, shortcuts -eg, the simplified for-loop.
How dare Sun try to make their language easier (if
not the documentation)?The for-each loop is simple, readable, predictable and easily understood.
Autoboxing/unboxing is often confusing, unpredictable for those who don't know the relevent JLS chapter like the back of their hand, riddled with "gotchas" and can easily lead to bugs that are extremely hard, if not impossible, to debug. The sole benefit from all of this is less typing when converting to and from primitive wrappers. Is it easier to read? No. In fact in some cases it may obfuscate the developers intentions. In all other cases reading 0 is not profoundly more understandable than new Integer(0).

Eclipse plugin for Javadoc available?

I'm using javadoc.exe from cmd line windows and saw a few plugins for eclipse. which ones are recommended?
also, any good generic ant script code for this available?
BTW: using JDK 5 and Eclipse 3.4 with JBDS 2.0
Edited by: asookazian on Mar 17, 2009 10:04 AM
Edited by: asookazian on Mar 17, 2009 10:04 AM

asookazian wrote:
I'm using javadoc.exe from cmd line windows and saw a few plugins for eclipse. which ones are recommended?Eclipse comes with built-in javadoc (File->Export->Javadoc), no need to use a non-standard plugin.
asookazian wrote:
also, any good generic ant script code for this available?ANT comes with a javadoc task and its documentation includes several usage examples. It doesn't get anymore generic than this.

Unable to send emails through adobe offline project.

Hi Experts!!!
 I am trying to send an email through Adobe Offline Form. I am quoting the code. Plz check what's the problem with the code.
// This file has been generated partially by the Web Dynpro Code Generator.
// MODIFY CODE ONLY IN SECTIONS ENCLOSED BY @@begin AND @@end.
// ALL OTHER CHANGES WILL BE LOST IF THE FILE IS REGENERATED.
package com.lifecyclelettersapplication;
// IMPORTANT NOTE:
// ALL IMPORT STATEMENTS MUST BE PLACED IN THE FOLLOWING SECTION ENCLOSED
// BY @@begin imports AND @@end. FURTHERMORE, THIS SECTION MUST ALWAYS CONTAIN
// AT LEAST ONE IMPORT STATEMENT (E.G. THAT FOR IPrivateFormView).
// OTHERWISE, USING THE ECLIPSE FUNCTION "Organize Imports" FOLLOWED BY
// A WEB DYNPRO CODE GENERATION (E.G. PROJECT BUILD) WILL RESULT IN THE LOSS
// OF IMPORT STATEMENTS.
//@@begin imports
import java.util.Properties;
import javax.mail.Address;
import javax.mail.BodyPart;
import javax.mail.Message;
import javax.mail.MessagingException;
import javax.mail.SendFailedException;
import javax.mail.Session;
import javax.mail.Transport;
import javax.mail.internet.AddressException;
import javax.mail.internet.InternetAddress;
import javax.mail.internet.MimeBodyPart;
import javax.mail.internet.MimeMessage;
import javax.mail.internet.MimeMultipart;
import com.lifecyclelettersapplication.wdp.IPrivateFormView;
//@@end
//@@begin documentation
//@@end
public class FormView
Logging location.
private static final com.sap.tc.logging.Location logger =
 com.sap.tc.logging.Location.getLocation(FormView.class);
static
 //@@begin id
 String id = "$Id$";
 //@@end
 com.sap.tc.logging.Location.getLocation("ID.com.sap.tc.webdynpro").infoT(id);
Private access to the generated Web Dynpro counterpart
for this controller class. 
Use <code>wdThis</code> to gain typed access to the context,
to trigger navigation via outbound plugs, to get and enable/disable
actions, fire declared events, and access used controllers and/or
component usages.
@see com.lifecyclelettersapplication.wdp.IPrivateFormView for more details
private final IPrivateFormView wdThis;
Root node of this controller's context. 
Provides typed access not only to the elements of the root node
but also to all nodes in the context (methods nodeXYZ())
and their currently selected element (methods currentXYZElement()).
It also facilitates the creation of new elements for all nodes
(methods createXYZElement()). 
@see com.lifecyclelettersapplication.wdp.IPrivateFormView.IContextNode for more details.
private final IPrivateFormView.IContextNode wdContext;
A shortcut for <code>wdThis.wdGetAPI()</code>. 
Represents the generic API of the generic Web Dynpro counterpart
for this controller. 
private final com.sap.tc.webdynpro.progmodel.api.IWDViewController wdControllerAPI;
A shortcut for <code>wdThis.wdGetAPI().getComponent()</code>. 
Represents the generic API of the Web Dynpro component this controller
belongs to. Can be used to access the message manager, the window manager,
to add/remove event handlers and so on. 
private final com.sap.tc.webdynpro.progmodel.api.IWDComponent wdComponentAPI;
public FormView(IPrivateFormView wdThis)
 this.wdThis = wdThis;
 this.wdContext = wdThis.wdGetContext();
 this.wdControllerAPI = wdThis.wdGetAPI();
 this.wdComponentAPI = wdThis.wdGetAPI().getComponent();
//@@begin javadoc:wdDoInit()
/** Hook method called to initialize controller. */
//@@end
public void wdDoInit()
 //@@begin wdDoInit()
 /* The following lines initialize the context elements;
Enter your e-mail id in the set From-method
 //wdContext.currentContextElement().setTeststatus(" do in it");
 try{
 wdContext.currentEmailElement().setFrom("[email protected]");
 wdContext.currentEmailElement().setTo("[email protected]");
 wdContext.currentEmailElement().setCc("[email protected]");
 wdContext.currentEmailElement().setBcc("[email protected]");
// wdContext.currentEmailElement().setCc(" ");
// wdContext.currentEmailElement().setBcc(" ");
 wdContext.currentEmailElement().setSubject("Test Mail By Umang");
 wdContext.currentEmailElement().setBody("You will find the address proof letter in the attachment of this e mail. Please sign this form and send it.");
 catch(Exception e)
 wdContext.currentContextElement().setTeststatus("do in it"+e.getMessage());
 //@@end
//@@begin javadoc:wdDoExit()
/** Hook method called to clean up controller. */
//@@end
public void wdDoExit()
 //@@begin wdDoExit()
 //@@end
//@@begin javadoc:wdDoModifyView
Hook method called to modify a view just before rendering.
This method conceptually belongs to the view itself, not to the
controller (cf. MVC pattern).
It is made static to discourage a way of programming that
routinely stores references to UI elements in instance fields
for access by the view controller's event handlers, and so on.
The Web Dynpro programming model recommends that UI elements can
only be accessed by code executed within the call to this hook method.
@param wdThis Generated private interface of the view's controller, as
 provided by Web Dynpro. Provides access to the view controller's
 outgoing controller usages, etc.
@param wdContext Generated interface of the view's context, as provided
 by Web Dynpro. Provides access to the view's data.
@param view The view's generic API, as provided by Web Dynpro.
 Provides access to UI elements.
@param firstTime Indicates whether the hook is called for the first time
 during the lifetime of the view.
//@@end
public static void wdDoModifyView(IPrivateFormView wdThis, IPrivateFormView.IContextNode wdContext, com.sap.tc.webdynpro.progmodel.api.IWDView view, boolean firstTime)
 //@@begin wdDoModifyView
 //@@end
//@@begin javadoc:onPlugFromFirstview(ServerEvent)
/** Declared validating event handler. */
//@@end
public void onPlugFromFirstview(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
 //@@begin onPlugFromFirstview(ServerEvent)
 wdContext.currentContextElement().setTeststatus("from first view");
 //wdDoInit();
 //@@end
//@@begin javadoc:onActionBack(ServerEvent)
/** Declared validating event handler. */
//@@end
public void onActionBack(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
 //@@begin onActionBack(ServerEvent)
 wdThis.wdFirePlugToFirstView();
 //@@end
//@@begin javadoc:onActionSend(ServerEvent)
/** Declared validating event handler. */
//@@end
public void onActionSend(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
 //@@begin onActionSend(ServerEvent)
 Properties props = new Properties();
 String host = "rmail070.zmail.ril.com";
 props.put("rmail070.zmail.ril.com", host);
 Session session = Session.getInstance(props, null);
 MimeMessage message = new MimeMessage(session);
 Address toAddress = new InternetAddress();
 Address fromAddress = new InternetAddress();
 Address ccAddress = new InternetAddress();
 Address bccAddress = new InternetAddress();
 wdContext.currentContextElement().setTeststatus("1");
 try
 MimeMultipart multipart = new MimeMultipart();
 wdContext.currentContextElement().setTeststatus("2");
 BodyPart messageBodyPart = new MimeBodyPart();
 if (! wdContext.currentEmailElement().getFrom().equals(""))
 fromAddress = new InternetAddress(wdContext.currentEmailElement().getFrom());
 message.setFrom(fromAddress);
 wdContext.currentContextElement().setTeststatus("3");
 if (! wdContext.currentEmailElement().getTo().equals(""))
 toAddress = new InternetAddress(wdContext.currentEmailElement().getTo());
 message.setRecipient(Message.RecipientType.TO, toAddress);
 wdContext.currentContextElement().setTeststatus("4");
 if (! wdContext.currentEmailElement().getCc().equals(""))
 ccAddress = new InternetAddress(wdContext.currentEmailElement().getCc());
 message.setRecipient(Message.RecipientType.CC, ccAddress);
 wdContext.currentContextElement().setTeststatus("5");
 if (! wdContext.currentEmailElement().getBcc().equals(""))
 bccAddress = new InternetAddress(wdContext.currentEmailElement().getBcc());
 message.setRecipient(Message.RecipientType.BCC, bccAddress);
 wdContext.currentContextElement().setTeststatus("6");
 if (! wdContext.currentEmailElement().getSubject().equals(""))
 message.setSubject(wdContext.currentEmailElement().getSubject());
 wdContext.currentContextElement().setTeststatus("7");
 if (! wdContext.currentEmailElement().getBody().equals(""))
 messageBodyPart.setText(wdContext.currentEmailElement().getBody());
 wdContext.currentContextElement().setTeststatus("8");
 multipart.addBodyPart(messageBodyPart);
 wdContext.currentContextElement().setTeststatus("10");
//// A new part will be added this will be the attachment
 messageBodyPart = new MimeBodyPart();
// String filename = "temp
webdynpro
web
local
LifeCycleLetters
Components
com.lifecyclelettersapplication.LifeCycleLettersApplication
LifeCycle.pdf";
// DataSource source = new FileDataSource(filename);
// messageBodyPart.setDataHandler(new DataHandler(source));
// messageBodyPart.setFileName(source.getName());
// messageBodyPart.setHeader("Content-Type","application/pdf");
// multipart.addBodyPart(messageBodyPart);
 message.setContent(multipart);
 Transport.send(message);
 wdContext.currentContextElement().setTeststatus("11");
 catch (AddressException e)
 wdComponentAPI.getMessageManager().reportWarning(e.getLocalizedMessage());
 e.printStackTrace();
 catch (SendFailedException e)
 wdComponentAPI.getMessageManager().reportWarning(e.getLocalizedMessage());
 e.printStackTrace();
 catch (MessagingException e)
 wdComponentAPI.getMessageManager().reportWarning(e.getLocalizedMessage());
 e.printStackTrace();
 catch(Exception e)
 wdContext.currentContextElement().setTeststatus("action send"+e.getMessage());
 //@@end
The following code section can be used for any Java code that is
not to be visible to other controllers/views or that contains constructs
currently not supported directly by Web Dynpro (such as inner classes or
member variables etc.). 
Note: The content of this section is in no way managed/controlled
by the Web Dynpro Designtime or the Web Dynpro Runtime.
//@@begin others
//@@end

Hi,
I think u need to set up the SMTP So that u can send the email.
Regards
Mustafa.

Error during generation of the WSDL: BUILD FAILED java.lang.NoClassDefFoundError: com/sun/javadoc/Type

When I create an EJB Transport Business Service, after selecting the jar that has the EJB 2.1 artefacts (Remote, Home, etc) the oepe plugin fails and can't continue.
As I understand it seems that there is a problem with the classpath of ant build.xml that oepe creates inside folder /tmp/alsbejbtransport/ to compile the bs and generate the wsdl. I checked if tools.jar is in the classpath (in eclipse) and is included, so I can't figure out wich is the problem.
I found this in Oracle, but not helps solve the problem:
BEA-398120
Error: The WSDL for the typed transport endpoint could not be accessed.
Description
There was a problem retrieving the WSDL from the typed transport service endpoint at the time of service registration
Action
Contact technical support
This is the the full stacktrace that shows eclipse.
Generate : Error during generation of the WSDL:
BUILD FAILED
java.lang.NoClassDefFoundError: com/sun/javadoc/Type
 at com.bea.util.jam.provider.JamServiceFactoryImpl.createSourceBuilder(JamServiceFactoryImpl.java:205)
 at com.bea.util.jam.provider.JamServiceFactoryImpl.createBuilder(JamServiceFactoryImpl.java:158)
 at com.bea.util.jam.provider.JamServiceFactoryImpl.createClassLoader(JamServiceFactoryImpl.java:137)
 at com.bea.util.jam.provider.JamServiceFactoryImpl.createService(JamServiceFactoryImpl.java:78)
 at weblogic.wsee.util.JamUtil.parseSource(JamUtil.java:152)
 at weblogic.wsee.tools.anttasks.JwsLoader.loadJClasses(JwsLoader.java:186)
 at weblogic.wsee.tools.anttasks.JwsLoader.load(JwsLoader.java:75)
 at weblogic.wsee.tools.anttasks.JwsModule.loadWebServices(JwsModule.java:569)
 at weblogic.wsee.tools.anttasks.JwsModule.generate(JwsModule.java:369)
 at weblogic.wsee.tools.anttasks.JwsModule.build(JwsModule.java:256)
 at weblogic.wsee.tools.anttasks.JwscTask.execute(JwscTask.java:184)
 at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
 at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
 at org.apache.tools.ant.Task.perform(Task.java:348)
 at org.apache.tools.ant.Target.execute(Target.java:357)
 at org.apache.tools.ant.Target.performTasks(Target.java:385)
 at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
 at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
 at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
 at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
 at org.apache.tools.ant.Main.runBuild(Main.java:758)
 at org.apache.tools.ant.Main.startAnt(Main.java:217)
 at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
 at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Caused by: java.lang.ClassNotFoundException: com.sun.javadoc.Type
 at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1400)
 at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1341)
 at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1088)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
 ... 27 more
Total time: 0 seconds
Eclipse Installation details:
*** System properties:
eclipse.application=org.eclipse.ui.ide.workbench
eclipse.buildId=M20110909-1335
eclipse.commands=-os
linux
-ws
gtk
-arch
x86_64
-showsplash
-launcher
{home}/Development/oepe-indigo/eclipse
-name
Eclipse
--launcher.library
{home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505/eclipse_1407.so
-startup
{home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.overrideVmargs
-exitdata
1e418010
-vm
/usr/bin/java
eclipse.home.location=file:{home}/Development/oepe-indigo/
eclipse.launcher={home}/Development/oepe-indigo/eclipse
eclipse.launcher.name=Eclipse
[email protected]/../p2/
eclipse.p2.profile=PlatformProfile
eclipse.product=org.eclipse.platform.ide
eclipse.startTime=1374623921455
eclipse.vm=/usr/bin/java
eclipse.vmargs=-Xms256m
-Xmx768m
-XX:MaxPermSize=512m
-Dsun.lang.ClassLoader.allowArraySyntax=true
-Dweblogic.home={home}/Oracle/Middleware/wlserver_10.3
-Dharvester.home={home}/Oracle/Middleware/Oracle_OSB1/harvester
-Dosb.home={home}/Oracle/Middleware/Oracle_OSB1
-Dosgi.bundlefile.limit=750
-Dosgi.nl=en_US
-Dmiddleware.home={home}/Oracle/Middleware
-jar
{home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
equinox.use.ds=true
file.encoding=UTF-8
file.encoding.pkg=sun.io
file.separator=/
guice.disable.misplaced.annotation.check=true
harvester.home={home}/Oracle/Middleware/Oracle_OSB1/harvester
http.nonProxyHosts=localhost
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path={home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
java.class.version=50.0
java.endorsed.dirs=/usr/lib/jvm/jdk1.6.0_45/jre/lib/endorsed
java.ext.dirs=/usr/lib/jvm/jdk1.6.0_45/jre/lib/ext:/usr/java/packages/lib/ext
java.home=/usr/lib/jvm/jdk1.6.0_45/jre
java.io.tmpdir=/tmp
java.library.path=/usr/lib/jvm/jdk1.6.0_45/jre/lib/amd64/server:/usr/lib/jvm/jdk1.6.0_45/jre/lib/amd64:/usr/lib/jvm/jdk1.6.0_45/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
java.protocol.handler.pkgs=null|com.bea.wli.sb.resources.url|com.bea.wli.sb.resources.jca.upgrade.url|weblogic.utils|weblogic.utils|weblogic.utils|weblogic.net|weblogic.net
java.runtime.name=Java(TM) SE Runtime Environment
java.runtime.version=1.6.0_45-b06
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.6
java.vendor=Sun Microsystems Inc.
java.vendor.url=http://java.sun.com/
java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi
java.version=1.6.0_45
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=Sun Microsystems Inc.
java.vm.version=20.45-b01
javax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
javax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
jna.platform.library.path=/usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib
line.separator=
middleware.home={home}/Oracle/Middleware
oracle.eclipse.tools.weblogic.ui.isWebLogicServer=true
org.apache.commons.logging.Log=org.apache.commons.logging.impl.NoOpLog
org.eclipse.equinox.launcher.splash.location={home}/Development/oepe-indigo/plugins/org.eclipse.platform_3.7.1.v201109091335/splash.bmp
org.eclipse.equinox.simpleconfigurator.configUrl=file:org.eclipse.equinox.simpleconfigurator/bundles.info
org.eclipse.m2e.log.dir={home}/workspace/pragma/.metadata/.plugins/org.eclipse.m2e.logback.configuration
org.eclipse.update.reconcile=false
org.omg.CORBA.ORBClass=weblogic.corba.orb.ORB
org.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,OSGi/Minimum-1.2,JRE-1.1,J2SE-1.2,J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6
org.osgi.framework.language=en
org.osgi.framework.os.name=Linux
org.osgi.framework.os.version=3.8.0
org.osgi.framework.processor=x86-64
org.osgi.framework.system.capabilities=osgi.ee; osgi.ee="OSGi/Minimum"; version:List<Version>="1.0, 1.1, 1.2",osgi.ee; osgi.ee="JavaSE"; version:List<Version>="1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6"
org.osgi.framework.system.packages=javax.accessibility,javax.activation,javax.activity,javax.annotation,javax.annotation.processing,javax.crypto,javax.crypto.interfaces,javax.crypto.spec,javax.imageio,javax.imageio.event,javax.imageio.metadata,javax.imageio.plugins.bmp,javax.imageio.plugins.jpeg,javax.imageio.spi,javax.imageio.stream,javax.jws,javax.jws.soap,javax.lang.model,javax.lang.model.element,javax.lang.model.type,javax.lang.model.util,javax.management,javax.management.loading,javax.management.modelmbean,javax.management.monitor,javax.management.openmbean,javax.management.relation,javax.management.remote,javax.management.remote.rmi,javax.management.timer,javax.naming,javax.naming.directory,javax.naming.event,javax.naming.ldap,javax.naming.spi,javax.net,javax.net.ssl,javax.print,javax.print.attribute,javax.print.attribute.standard,javax.print.event,javax.rmi,javax.rmi.CORBA,javax.rmi.ssl,javax.script,javax.security.auth,javax.security.auth.callback,javax.security.auth.kerberos,javax.security.auth.login,javax.security.auth.spi,javax.security.auth.x500,javax.security.cert,javax.security.sasl,javax.sound.midi,javax.sound.midi.spi,javax.sound.sampled,javax.sound.sampled.spi,javax.sql,javax.sql.rowset,javax.sql.rowset.serial,javax.sql.rowset.spi,javax.swing,javax.swing.border,javax.swing.colorchooser,javax.swing.event,javax.swing.filechooser,javax.swing.plaf,javax.swing.plaf.basic,javax.swing.plaf.metal,javax.swing.plaf.multi,javax.swing.plaf.synth,javax.swing.table,javax.swing.text,javax.swing.text.html,javax.swing.text.html.parser,javax.swing.text.rtf,javax.swing.tree,javax.swing.undo,javax.tools,javax.transaction,javax.transaction.xa,javax.xml,javax.xml.bind,javax.xml.bind.annotation,javax.xml.bind.annotation.adapters,javax.xml.bind.attachment,javax.xml.bind.helpers,javax.xml.bind.util,javax.xml.crypto,javax.xml.crypto.dom,javax.xml.crypto.dsig,javax.xml.crypto.dsig.dom,javax.xml.crypto.dsig.keyinfo,javax.xml.crypto.dsig.spec,javax.xml.datatype,javax.xml.namespace,javax.xml.parsers,javax.xml.soap,javax.xml.stream,javax.xml.stream.events,javax.xml.stream.util,javax.xml.transform,javax.xml.transform.dom,javax.xml.transform.sax,javax.xml.transform.stax,javax.xml.transform.stream,javax.xml.validation,javax.xml.ws,javax.xml.ws.handler,javax.xml.ws.handler.soap,javax.xml.ws.http,javax.xml.ws.soap,javax.xml.ws.spi,javax.xml.ws.wsaddressing,javax.xml.xpath,org.ietf.jgss,org.omg.CORBA,org.omg.CORBA_2_3,org.omg.CORBA_2_3.portable,org.omg.CORBA.DynAnyPackage,org.omg.CORBA.ORBPackage,org.omg.CORBA.portable,org.omg.CORBA.TypeCodePackage,org.omg.CosNaming,org.omg.CosNaming.NamingContextExtPackage,org.omg.CosNaming.NamingContextPackage,org.omg.Dynamic,org.omg.DynamicAny,org.omg.DynamicAny.DynAnyFactoryPackage,org.omg.DynamicAny.DynAnyPackage,org.omg.IOP,org.omg.IOP.CodecFactoryPackage,org.omg.IOP.CodecPackage,org.omg.Messaging,org.omg.PortableInterceptor,org.omg.PortableInterceptor.ORBInitInfoPackage,org.omg.PortableServer,org.omg.PortableServer.CurrentPackage,org.omg.PortableServer.POAManagerPackage,org.omg.PortableServer.POAPackage,org.omg.PortableServer.portable,org.omg.PortableServer.ServantLocatorPackage,org.omg.SendingContext,org.omg.stub.java.rmi,org.w3c.dom,org.w3c.dom.bootstrap,org.w3c.dom.css,org.w3c.dom.events,org.w3c.dom.html,org.w3c.dom.ls,org.w3c.dom.ranges,org.w3c.dom.stylesheets,org.w3c.dom.traversal,org.w3c.dom.views,org.w3c.dom.xpath,org.xml.sax,org.xml.sax.ext,org.xml.sax.helpers
org.osgi.framework.uuid=901615cd-f3f3-0012-11b6-a3bca4d97ac1
org.osgi.framework.vendor=Eclipse
org.osgi.framework.version=1.6.0
org.osgi.supports.framework.extension=true
org.osgi.supports.framework.fragment=true
org.osgi.supports.framework.requirebundle=true
os.arch=amd64
os.name=Linux
os.version=3.8.0-26-generic
osb.home={home}/Oracle/Middleware/Oracle_OSB1
osgi.arch=x86_64
osgi.bundlefile.limit=750
osgi.bundles=reference:file:javax.transaction_1.1.1.v201105210645.jar,reference:file:org.eclipse.equinox.simpleconfigurator_1.0.200.v20110502-1955.jar@1:start
osgi.bundles.defaultStartLevel=4
osgi.bundlestore={home}/Development/oepe-indigo/configuration/org.eclipse.osgi/bundles
osgi.configuration.area=file:{home}/Development/oepe-indigo/configuration/
osgi.framework=file:{home}/Development/oepe-indigo/plugins/org.eclipse.osgi_3.7.1.R37x_v20110808-1106.jar
osgi.framework.extensions=reference:file:javax.transaction_1.1.1.v201105210645.jar
osgi.framework.shape=jar
osgi.framework.version=3.7.1.R37x_v20110808-1106
osgi.frameworkClassPath=., file:{home}/Development/oepe-indigo/plugins/javax.transaction_1.1.1.v201105210645.jar
osgi.install.area=file:{home}/Development/oepe-indigo/
osgi.instance.area=file:{home}/workspace/pragma/
osgi.instance.area.default=file:{home}/workspace/
osgi.logfile={home}/workspace/pragma/.metadata/.log
osgi.manifest.cache={home}/Development/oepe-indigo/configuration/org.eclipse.osgi/manifests
osgi.nl=en_US
osgi.nl.user=en_US
osgi.os=linux
osgi.splashLocation={home}/Development/oepe-indigo/plugins/org.eclipse.platform_3.7.1.v201109091335/splash.bmp
osgi.splashPath=platform:/base/plugins/org.eclipse.platform
osgi.syspath={home}/Development/oepe-indigo/plugins
osgi.tracefile={home}/workspace/pragma/.metadata/trace.log
osgi.ws=gtk
path.separator=:
securerandom.source=file:/dev/./urandom
socksNonProxyHost=localhost
sun.arch.data.model=64
sun.boot.class.path=/usr/lib/jvm/jdk1.6.0_45/jre/lib/resources.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/rt.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/sunrsasign.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/jsse.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/jce.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/charsets.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/modules/jdk.boot.jar:/usr/lib/jvm/jdk1.6.0_45/jre/classes
sun.boot.library.path=/usr/lib/jvm/jdk1.6.0_45/jre/lib/amd64
sun.cpu.endian=little
sun.cpu.isalist=
sun.desktop=gnome
sun.io.unicode.encoding=UnicodeLittle
sun.java.command={home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar -os linux -ws gtk -arch x86_64 -showsplash -launcher {home}/Development/oepe-indigo/eclipse -name Eclipse --launcher.library {home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505/eclipse_1407.so -startup {home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.overrideVmargs -exitdata 1e418010 -vm /usr/bin/java -vmargs -Xms256m -Xmx768m -XX:MaxPermSize=512m -Dsun.lang.ClassLoader.allowArraySyntax=true -Dweblogic.home={home}/Oracle/Middleware/wlserver_10.3 -Dharvester.home={home}/Oracle/Middleware/Oracle_OSB1/harvester -Dosb.home={home}/Oracle/Middleware/Oracle_OSB1 -Dosgi.bundlefile.limit=750 -Dosgi.nl=en_US -Dmiddleware.home={home}/Oracle/Middleware -jar {home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
sun.java.launcher=SUN_STANDARD
sun.jnu.encoding=UTF-8
sun.lang.ClassLoader.allowArraySyntax=true
sun.management.compiler=HotSpot 64-Bit Tiered Compilers
sun.os.patch.level=unknown
svnkit.http.methods=Basic
svnkit.library.gnome-keyring.enabled=false
user.country=AR
user.dir={home}/Development/oepe-indigo
user.home={home}
user.language=es
user.name={username}
user.timezone=America/Argentina/Buenos_Aires
weblogic.home={home}/Oracle/Middleware/wlserver_10.3
Thanks!!

run this one in command prompt and then convert the applet using converter tool
JC_HOME = C:\java_card_kit-2_2_2\bin\
set CLASSES=%JCHOME%\lib\apduio.jar;%JC_HOME%\lib\apdutool.jar;%JC_HOME%\lib\jcwde.jar;%JC_HOME%\lib\converter.jar;%JC_HOME%\lib\scriptgen.jar;%JC_HOME%\lib\offcardverifier.jar;%JC_HOME%\lib\api.jar;%JC_HOME%\lib\installer.jar;%JC_HOME%\lib\capdump.jar;
D:\NareshPalle\jcardRE\Smart\src>java -classpath %_CLASSES% com.sun.javacard.con
verter.Converter -out EXP JCA CAP -exportpath .\exp -applet 0x0a:0x00:0x00:0x00:0x0e:0x01:0x02:
0x03:0x04:0x05:0x06 PackageName appletName 0x01:0x02:0x03:0x04:0x05:0x0
6:0x07:0x08 1.0
or
go to following directory and run the converter tool in command prompt
step 1: cd C:\java_card_kit-2_2_2\bin\
then run this command under the above directory
step 2:converter -classdir E:\Pathof Your applet class file -out EXP JCA CAP -exportpath E:\path of exp files folder -applet AID PackageName AppletName PackAID major.minor no
For more doubts mail me....
*[removed by moderator]*
Thanks and Regards
NareshPalle
Edited by: EJP on 31/03/2012 20:09: removed your email address. Unless you like spam and unless you think these forums are provided for your personal benefit only, posting an email address here serves no useful purpose whatsoever.

DocFlex/Javadoc 1.5.6, a multi-format doclet development tool and more

DocFlex/Javadoc is both a multi-format Javadoc Doclet and a rapid doclet development tool, which allows easy creation of professional quality Java API documentation generated by Javadoc in various output formats.
More in this article:
Key Features
Availability
This Version
What is DocFlex?
Main Concepts
Other Applications
Links
KEY FEATURES
Template-driven doclet architecture
- Actual doclets are created in the form of special templates interpreted by the DocFlex Doclet, which is the template interpreter / output generator wrapped in the form of a Javadoc Doclet.
- The high quality graphic Template Designer allows you to visually design most of things, whose development was possible so far only by direct Java coding.
- The templates are designed independently on a particular output format. All formatting is specified in some universal way using properties of template components. During the generation, it is rendered with the suitable features available in the selected output format.
- The elaborated support of template parameters (including multivalued list parameters). The parameters are defined and accessed within templates to adjust dynamic properties of template components. Most of options previously used to control an ordinary doclet now simply become template parameters!
- The possibility to call templates from one another. This feature (along with the template parameters) makes possible re-using the same templates for different tasks as well as organizing template libraries.
Data processing
- The entire Doclet API is represented in the form of a virtual XML document (called Doclet DSM), on which the designing and processing of all templates is based.
- Sophisticated capabilities for data querying and sorting based on an extension of XPath.
- Full support of new Java 5.0 language features: Generic Types, Enums, Annotations.
- Simultaneous support of Java 1.4 and Java 5.
Creating hyperlinks
- Generation of an extensive network of hyperlinks interconnecting the whole documentation.
- The hyperlinks can be generated in all output formats that support them (this currently includes HTML and RTF).
- The universal way of defining documentation cross-links based on the link/target keys specified in templates.
- In RTF, the cross-links can be generated in the form of page number references, which effectively makes them usable even in the printed documentation.
- In HTML, the possibility of loading several frame windows from a single hyperlink at once.
Universal support of various formatting techniques
- text formatting: fonts, colors, borders
- paragraph formatting: margins, pagination control, borders, colors
- border formatting: styles (solid, double, dashed, dotted), thickness, colors
- tables: arbitrary cell layouts, borders, nested tables
- lists: bulleted, numbered, delimited
- document fields (RTF): page number, number of pages, TOC, etc.
- page formatting: size, orientation, margins, headers/footers
- formatting styles
- rendering of embedded HTML, which means interpreting in non-HTML output formats (such as RTF) the HTML tags embedded in text data (e.g. documentation comments). Almost all HTML tags practically usable in doc-comments are supported.
Inserting images
- statically specified in templates
- dynamically, obtained by <img> tags found in Java comments
- supported image formats: GIF, PNG, JPG, WMF, EMF, BMP
Output formats
- HTML (both framed multi-file and single-file output)
- RTF (version 1.6 - supported since Word 2000).
- TXT (plain text), which may be particularly useful for various utilizations of the Java code information provided by the Doclet API generate XML files by it, or SQL files to import into a database).
Standard Template Set
- The ready-to-use Standard Template Set included in all editions of DocFlex/Javadoc allows you to immediately generate:
(*) The framed HTML Java API documentation similar to that generated by the standard Javadoc.
(*) The same documentation packed in a single HTML file.
(*) The unmatched quality RTF JavaDoc.
- Special features supported by standard templates:
(*) Excluding classes/methods/fields by custom tags and annotations.
(*) Selective omitting of package qualifiers.
(*) Selective documenting of custom tags (similar to -tag option of Standard Doclet).
- By modifying the standard templates, you can quickly customize the generated documentation according to your needs.
Doclet GUI
- Besides command line options, DocFlex Doclet supports an alternative user-friendly way to control the template-based doclets interactively -- the high quality Doclet GUI.
- The Doclet GUI starts with the Generator Dialog, where you can specify all general settings (such as the main template, the output format and the output directory), start the generation, track its progress and stop at any moment you need.
- The grid-tree-based Parameter Inspector invoked from the Generator Dialog for a selected template allows you to view the descriptions of all template parameters controlling the doclet and set their values according to the parameter data types.
- The generator options specific for the selected output format can be set in the corresponding Format Option Inspector (also invoked from the Generator Dialog).
- Once the generation is finished (or cancelled), you can start it again with different settings or a new main template without restarting the whole Javadoc.
Integrations
- With any system that runs Javadoc (in particular, see below)
- Apache Ant
- Apache Maven 2
- Eclipse
For lots more information, see DocFlex/Javadoc homepage: [http://www.filigris.com/products/docflex_javadoc/]
AVAILABILITY
DocFlex/Javadoc comes in two editions:
(1) The full edition called "DocFlex/Javadoc" as it is. This is commercial software, which includes all the implemented functionality.
(2) The reduced freeware edition called "DocFlex/Doclet". It includes only the output generator and can be used as an interpretor of any custom templates. It also includes the standard template set, which allows you to instantly use it as an HTML doclet (similar to the standard one, however with some special features) plus an excellent quality RTF doclet.
Both editions are available for downloads on the page: [http://www.filigris.com/downloads/]
THIS VERSION
New features:
- The template interpretor works 15-20% faster
- Improvement of RTF output
- Multi-valued (list) template parameters
- Custom elements
- Standard Templates: Selective documenting of custom tags (similar to -tag option of standard doclet)
For more details, see product Readme | Change Log on the downloads page: [http://www.filigris.com/downloads/]
WHAT IS DOCFLEX?
DocFlex is an innovative technology for development of high quality template-driven documentation/report generators by any kind of data obtained from various software applications via the Java APIs they provide.
MAIN CONCEPTS
The whole DocFlex technology is based on four generalizations:
(1) The mapping of an entire Java API onto a virtual XML-like representation made of some elements and attributes so as to process any such a representation in a universal way using techniques borrowed from the field of XML, like XPath (or more precisely, a conceptual analogue of XPath with some extensions not present in it).
(2) The abstract formatting concept based on four layouts (flow of text, flow of paragraphs or paragraph-like objects, tables and lists), which can be rendered in most modern document formats (e.g. HTML, RTF, XSL-FO etc.)
(3) The automatic generation of hyperlinks (or their page number reference equivalents) by matching the sets of keys produced from certain natural properties of the things (entities) being documented and hyper-linked.
(4) The representation of the object controlling structure of the output generator (made on the first three principles) in the form of a plain-text template with a possibility to create and edit such templates using a graphic Template Designer, which visualizes the controlling objects (now becoming template components) in a form resembling the output they will produce.
OTHER APPLICATIONS
In fact, DocFlex/Javadoc is not the only application of DocFlex technology. The following is a summary of other DocFlex software:
DocFlex/XML
The SDK and runtime environment for rapid development and execution of template-driven automatic documentation/report generators by any data obtained from XML files.
This is currently the most complex and advanced application of DocFlex technology. Actually, this tool can be considered a powerful alternative to XSLT. At least, it is definitely able to do what XSLT apparently not (for example, see XSDDoc below). We will publish a more detailed comparison DocFlex/XML versus XSLT with the next DocFlex/XML release, which is coming very soon.
DocFlex/XML home page: [http://www.filigris.com/products/docflex_xml/]
DocFlex/XML | XSDDoc
A template set for DocFlex/XML that implements a high quality W3C XML Schema documentation generator in HTML and RTF output formats.
For more details, please see: [http://www.filigris.com/products/docflex_xml/xsddoc/]
DocFlex/XML | WSDLDoc
A similar template set for DocFlex/XML that will implement a high-end WSDL documentation generator.
This product is not released yet.
DocFlex/Together
A template-driven documentation generator for [Borland Together|http://www.borland.com/us/products/together/] (which is a UML modeling tool).
This is the earliest application of DocFlex technology and probably the most beautiful one. It works only with Together Architect 1.x, which is now obsolete. Unfortunately, since Together 2005, Borland eliminated any open APIs (for unknown reasons). Because of this, further development of DocFlex/Together was impossible.
DocFlex/Together home page: [http://www.filigris.com/products/docflex_together/]
See also examples of the UML documentation generated with it: [http://www.filigris.com/products/docflex_together/examples/]
The future DocFlex/UML is going to generate something like this as well.
DocFlex/UML
A template-driven UML documentation generator based on [Eclipse EMF|http://www.eclipse.org/emf/]. This tool is in early development stage yet. In a sense, it will continue DocFlex/Together with the focus on integration with other UML tools that use Eclipse EMF.
LINKS
This original article can be found at:
[http://www.filigris.com/ann/docflex_javadoc_v1.5.6/]
DocFlex/Javadoc home page:
[http://www.filigris.com/products/docflex_javadoc/]
DocFlex/XML home page:
[http://www.filigris.com/products/docflex_xml/]
DocFlex/XML | XSDDoc, the XML schema documentation generator:
[http://www.filigris.com/products/docflex_xml/xsddoc/]
Free downloads:
[http://www.filigris.com/downloads/]

Now, DocFlex/Javadoc v1.4 has been released specifically dedicated to Linux (Mac OS X) support:
(*) Some early bugs have been fixed, which prevented it working properly under Linux.
(*) A special RTF option was introduced to generate OpenOffice.org friendly RTF (see below)
(*) Improved support for external document viewers.
(*) Now, DocFlex/Javadoc software includes the shell script files prepared to quickly install and launch it under Linux
New RTF option
A new RTF output option "Tune output for MS Word� has been introduced. This option, actually, allows switching off that very tuning (which until now was the default mode) to produce an RTF friendly to open with other non MS Word applications, e.g. OpenOffice.org Writer under Linux.
Read full announcement (and screenshot) by this link:
http://www.filigris.com/ann/docflex_javadoc_v1.4/
Regards,
Leonid Rudy
http://www.docflex.com

Export OSB configuration from eclipse using ant script

I am trying to export an OSB project from eclipse using ant script
I followed the link below http://biemond.blogspot.com/2010/07/osb-11g-ant-deployment-scripts.html
It is using com.bea.alsb.core.ConfigExport to do the export. This export is always set to resource level.
I see it generates a file ExportInfo setting some properties. It has a property that set the export level as below
<imp:property name="projectLevelExport" value="false"/>*
How can I export the project in project level? basically setting projectLevelExport to true?
So that if a file does not exist in the sbconfig.jar file , then while importing the jar to OSB server it will delete the file from the server instead of skipping it?
I appreciate any help
here is the ant script snippet that gets executed to export from eclipse
<target name="exportFromWorkspace">
 <delete failonerror="false" includeemptydirs="true"
dir="${metadata.dir}"/>
 
<java dir="${eclipse.home}"
jar="${eclipse.home}/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar"
fork="true" failonerror="true" maxmemory="768m">
<jvmarg line="-XX:MaxPermSize=256m"/>
<arg line="-data ${workspace.dir}"/>
<arg line="-application com.bea.alsb.core.ConfigExport"/>
<arg line="-configProject ${config.project}"/>
<arg line="-configJar ${config.jar}"/>
<arg line="-configSubProjects ${config.subprojects}"/>
 <arg line="-exportLevel true"/>
<arg line="-includeDependencies ${config.includeDependencies}"/>
<sysproperty key="weblogic.home" value="${weblogic.home}"/>
<sysproperty key="osb.home" value="${osb.home}"/>
<sysproperty key="osgi.bundlefile.limit" value="500"/>
<sysproperty key="harvester.home" value="${osb.home}/harvester"/>
<sysproperty key="osgi.nl" value="en_US"/>
<sysproperty key="sun.lang.ClassLoader.allowArraySyntax" value="true"/>
</java>
</target>

yes, I specified the project name to export the whole project.
Here is few lines from my properties file
# properties for workspace export
config.project="OSB Configuration-GW"
config.jar=D:/workspace/osb/scripts/gateway/mycode2/ant_osb/dist/sbconfig.jar
config.subprojects="GatewaySecurity"
config.includeDependencies=true
workspace.dir=D:/workspace/osb/gateway-workspace
But this property does not make it to export at project level ,it export the specified project at resource level.
And while importing this jar to OSB server, if a file is missing it skips the file instead of deleting the file from the OSB server
If I unjar sbconfig.jar file, open ExportInfo file and update the line in bold below to true then it deletes the file from OSB server, if not exist in sbconfig.jar
<imp:property name="exporttime" value="Thu Dec 29 13:57:44 EST 2011"/>
<imp:property name="productname" value="Oracle Service Bus"/>
<imp:property name="productversion" value="11.1.1.4"/>
*<imp:property name="projectLevelExport" value="false"/>*
Here is few lines from Oracle API java doc
http://docs.oracle.com/cd/E13171_01/alsb/docs26/javadoc/com/bea/wli/sb/management/importexport/ALSBImportOperation.Operation.html
public static final ALSBImportOperation.Operation Delete
Indicates that the resource is deleted in the importing domain. This is the default operation when the project is exported in its entirety and the resource exists in the target domain but not in the jar file
public static final ALSBImportOperation.Operation Skip
Indicates that the resource is skipped meaning the resource is not touched in the importing domain. This is the default operation if the jar file was exported at the resource level, and a resource that exists in the target domain, does not exist in the jar file.

FlexPMD 1.2 and Eclipse Plug-In

Hi, I'm probably missing something simple here but Flex PMD (using the eclipse plugin) isn't working for me: Nothing gets populated in either the Flex PMD view or the CPD view but the views do open when I run Flex PMD.
My configuration is:
FlexPMD command line installation: C:\Software\FlexPmdAll\flex-pmd-command-line-1.2.jar
FlexPMD custom ruleset: C:\Software\FlexPmdAll\pmd.xml
Java command line: java -Xms512m -Xmx512m
FlexCPD command line installation: C:\Software\FlexPmdAll\flex-pmd-cpd-command-line-1.2.jar
There are no spaces in my workspace path, it is simply: C:\Views\ProjectNameHere\
Using these settings I get a pop-up error message saying: 'add markers job' has encountered a problem.
Expanding on this error gives me: An internal error occurred during: "add markers job". Index: 0, Size: 0
If I change the Java command line (a tip found on the web) to: java -Xms512m -Xmx512m -Djava.io.tmpdir=C:\Users\NameGoesHere\AppData\Local\Temp
I get the same error.
If I remove the custom ruleset value no error message shows when I run Flex PMD but nothing happens either.
If you have any idea what's wrong let me know. The open source website is offline and I can't find any reference sites that don't link to it for an answer.
Cheers,
Tony

Looks like you were right, I see a File Not Found Exception for a pmd.xml file:
java.io.FileNotFoundException: C:\Users\NameHere\AppData\Local\Temp\flexpmd2207206954593694710dir\pmd.xml (The system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at com.adobe.ac.pmd.eclipse.flexpmd.cmd.FlexPMDResultsParser.parse(FlexPMDResultsParser.java :112)
at com.adobe.ac.pmd.eclipse.flexpmd.cmd.FlexPMD.processResultsFile(FlexPMD.java:180)
at com.adobe.ac.pmd.eclipse.flexpmd.cmd.FlexPMD.process(FlexPMD.java:68)
at com.adobe.ac.pmd.eclipse.flexpmd.cmd.FlexPMD.process(FlexPMD.java:1)
at com.adobe.ac.pmd.eclipse.flexpmd.actions.RunFlexPMDJob.run(RunFlexPMDJob.java:83)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Followed by what looks to be an eclipse-specific Unhandled event loop exception caused by a NPE at com.adobe.ac.pmd.eclipse.flexpmd.actions.RunFlexPmdAction$2.run(RunFlexPmdAction.java:145 )
I wonder why it is looking for a pmd.xml file in a temp directory? Note that these errors are when FLexPMD is run withoit any Java arguments specified. When I run FlexPMD with the Java arguments specified I get a third error message the same as the one mentioned above (Class Not Found).
Also, if I include a custom ruleset, it still throws the FileNotFoundException and lists another temp folder in AppData\Local\Temp
Cheers,
Tony

Offline running - can "GetResources() for an embedded file ever work?

This question has come up in various guises in the past, but has often then become confused with other issues (see [t-5123126] ) so I've not been able to find a useful answer. I've tried to bring the problem down to the essentials, and just want to know if what I'm trying to do can ever work, or if I should just abandon Web Start for this particular need.
Our app is J2SE Swing and creates a Derby database locally on a PC. The application then captures keyed data and stores it on the local database. Persistence is via JPA (provider was Toplink, now EclipseLink).
The data capture is performed using laptops running the application "offline" with no network connection. This is because the location has no network access of any description. Periodically, each laptop is reconnected to upload its data to a central server.
To help with software distribution, we are using Java Web Start. All the jars are signed and the .jnlp file specifes offline usage is allowed.
When running the application while connected to the network, there are no issues - everything works fine.
When running offline, the application starts up so the Java Web Start caching is working and the code is obviously accessible. However, it throws a MalformedURLException within the EclipseLink code (which we do not wish to modify). The actual statement is:
Enumeration resources = classLoader.getResources("META-INF/persistence.xml"); META-INF/persistence.xml exists within one of the jar files specified as resources in the .jnlp file.
The classloader in question is the Java Web Start classloader ( com.sun.jnlp.JNLPClassLoader) which presumably retrieves classes and resources from the remote server or from the cache depending on how the app is being run. In online mode, the persistence.xml resource is found ok, in offline a MalformedURLException is thrown.
My question: is this a fundamental "restriction" of the Web Start environment in offline mode? i.e. it can't load resources such as this xml file from a cached jar using the format shown?. My feeling is that this is just the way it is, and I should move on and try another form of software distribution, but it seems a shame to abandon Web Start as it otherwise meets our needs.
Any relevent experience of this problem would be appreciated.
Edited by: GrayMan on Aug 21, 2009 8:20 AM

A system we're developing make use of a similar setup. I'm not sure if you run into this problem, but the classes in our app uses persistence annotations and do not rely on the orm.xml mapping file. After solving the persistence.xml show stopper, I could see that the application had really slow startup times in offline mode. By looking at the access logs in online mode, I could see that the app was requesting META-INF/orm.xml and META-INF/eclipselink-orm.xml. In online mode, the web server simply returned HTTP 404 with much delay. In offline mode, this resulted in really slow startup times due to timeouts for the mentioned requests.
Creating valid xml files bundling them into the jar file of course didn't help.
I successfully disabled lookup for eclipselink-orm.xml by specifying the following entry in persistence.xml:
<property name="eclipselink.exclude-eclipselink-orm" value="true"/>
To disable lookup for orm.xml, I modified the method loadStandardMappingFiles(String) in org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.MetadataProcessor (eclipselink 1.1.0).
Perhaps this is useful for someone else also.

How to use webui ui:upload in eclipse 3.2

Hi,
I would like to use file upload using sun products.
I tried with <ui:upload> but i am not able to render that component.
my jsf:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
<%@ taglib uri="http://www.sun.com/web/ui" prefix="ui"%>
<f:view>
<html>
<head>
<title>Portfolio Analyzer</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="stylesheet" type="text/css" href="css/menu.css" />
<link rel="stylesheet" type="text/css" href="css/stylesheet.css" />
</head>
 <ui:page id="page1">
 <ui:html id="html1">
 <ui:body id="body1">
 <ui:form id="form1">
 <ui:upload id="fileUpload1" />
 </ui:form>
 </ui:body>
 </ui:html>
 </ui:page>
</html>
</f:view>my web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
 <display-name>
 GPJ</display-name>
 <context-param>
 <param-name>javax.faces.CONFIG_FILES</param-name>
 <param-value>/WEB-INF/faces-config.xml</param-value>
 </context-param>
 <context-param>
 <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
 <param-value>server</param-value>
 </context-param>
 <context-param>
 <param-name>org.apache.myfaces.ALLOW_JAVASCRIPT</param-name>
 <param-value>true</param-value>
 
 </context-param>
 
 <filter>
 <filter-name>UploadFilter</filter-name>
 <filter-class>com.sun.rave.web.ui.util.UploadFilter</filter-class>
 <init-param>
 <description>
 The maximum allowed upload size in bytes. If this is set
 to a negative value, there is no maximum. The default
 value is 1000000.
 </description>
 <param-name>maxSize</param-name>
 <param-value>1000000</param-value>
 </init-param>
 <init-param>
 <description>
 The size (in bytes) of an uploaded file which, if it is
 exceeded, will cause the file to be written directly to
 disk instead of stored in memory. Files smaller than or
 equal to this size will be stored in memory. The default
 value is 4096.
 </description>
 <param-name>sizeThreshold</param-name>
 <param-value>4096</param-value>
 </init-param>
</filter>
 <filter-mapping>
 <filter-name>UploadFilter</filter-name>
 <servlet-name>Faces Servlet</servlet-name>
 </filter-mapping>

<servlet>
 <servlet-name>Faces Servlet</servlet-name>
 <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
 <load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
 <servlet-name>Faces Servlet</servlet-name>
 <url-pattern>/faces/*</url-pattern>
</servlet-mapping>

<welcome-file-list>
 <welcome-file>faces/addCampaignGroup.jsp</welcome-file>
</welcome-file-list>

<login-config>
<auth-method>BASIC</auth-method>
</login-config>



<listener>
<listener-class>com.sun.faces.config.ConfigureListener</listener-class>
</listener>
</web-app>I think i have some problem with my web.xml
Could anyone pls help me regarding.
Thanks,
Ambika.

I just tested it at my Eclipse environment. It was set to UTF-8 and the following line was not allowed:
String 試験 = "試験";When I set the encoding to UTF-16, it was accepted. If you still fails in this somehow, consult the eclipse boys, as said before.
However. In name of reusability I don't recommend to use other languages than English thoroughout the whole Java code. Maybe only in javadocs. But still, English is preferred over all other languages. The core Java API itself is also all in English.

Javadoc in eclipse offline?

Similar Messages

Maybe you are looking for