[guypaladino]

When I upgraded to MyEclispe 4.1, a distributable tag was added to web.xml.

Congifiguration is Eclispe 3.1.2, MyEclipse 4.1, JBoss 4.0.3sp1, java 1.5_06.

In the MyEclipse-Xdoclet there is a option for distributable in the deployment descriptor. I am not sure what to put here. I tried false but got a java.lang.reflect.InvocationTargetException.

When I manually remove the distributable, the problem goes away.

This is causing problems with my session object.

Anyone have any suggestions?

Thanks
==================================================
web.xml code snippet below.

<?xml version=”1.0″ encoding=”UTF-8″?>

<!DOCTYPE web-app PUBLIC “-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN” “http://java.sun.com/dtd/web-app_2_3.dtd”&gt;

<web-app >
<distributable/>

<!–
To use non XDoclet filters, create a filters.xml file that
contains the additional filters (eg Sitemesh) and place it in your
project’s merge dir. Don’t include filter-mappings in this file,
include them in a file called filter-mappings.xml and put that in
the same directory.
–>

<!–
To use non XDoclet filter-mappings, create a filter-mappings.xml file that
contains the additional filter-mappings and place it in your
project’s merge dir.
–>

<!–
To use non XDoclet listeners, create a listeners.xml file that
contains the additional listeners and place it in your
project’s merge dir.
–>

[Riyad Kalla]

MyEclipse itself won’t add this flag but if you are using XDoclet to generate the web.xml file, it’s possible the update XDoclet 1.2.3 libraries are doing this. Is the problem that you need the flag but the web.xml file is marked with an error when you use it, or that you don’t need it?

[guypaladino]

I want to remove the <distributable/> tag from the generated web.xml. When using the distributable tag only serializable objects can be stored in an http session. One of my developers is storing an image which is not serializable.

We do not know what changes are required to cause this tag not to be generated. I have tried many various web searches but to no avail.

[Riyad Kalla]

Just make sure you uncheck the “distrbutable” property in the “deploymentdescriptor” doclet task. Then hit Apply, then click the Build tab and make sure “XDoclet Build Policy” is set to “Use dynamic build specification”. It’s possible you have a xdoclet build file in your project thati s just being run over and over and the new settings ignored.

[guypaladino]

I do use an xdoclet-build.xml file and unfortunately I have can’t use a dynamic build. This is because I created an ant script to perform “nightly” batch builds and these scripts rely on these files.

If you don’t know the parameters to change in the xdoclet file, I will take this advice and see if I can solve this problem. This is odd though as in the prior relase of myeclipse/eclipse/xdoclet not having the distributable tag is the default. It starts to get annoying when default behavior changes when you upgrade a development environment. I had the same issue with jaxb behavior changing as well …. and there is no clear documentation.

Otherwise I will just deal with serializing a bufferedimage.

Thanks

[guypaladino]

Just to close this off and keep any interested parties informed, I implemented a cache system to store http session information.

Didn’t want to deal with xdoclet and after 5 minutes realized I couldn’t easily serialize a bufferedimage. I always wanted to add the cache anyways.

—-

I am not sure if this was the best solution but when you are part of small dev. group and have to deal with all j2ee disciplines and need to grind out product you sometimes fix the problem instead of implementing a proper solution.

[Riyad Kalla]

You are doing what we all do, solve problems 😉

[Author]

Posts