Sun Java System Application Server Platform Edition 8.1 2005Q2 Update 2 Release Notes

- Previous: Container Managed Persistence
- Next: Documentation

## Deploytool

This section describes known Deploytool issues and associated solutions.

### Deploytool often will not create `message-destination` elements in the following Sun deployment descriptors (ID 6197393):

- `sun-application-client.xml`

- `sun-ejb-jar.xml`

- `sun-web.xml`

  A JMS destination resource specified as the JNDI Name in the Message Destinations tab may not be saved to the Sun descriptor. After specifying the Destination Name (for example, `PhysicalQueue`, a physical destination created with `create-jmsdest`) and pressing Enter, the Destination Name appears under Display Name, and the client or bean name appears in the Producers list. After typing “`jms/Queue`” in the Sun-specific JNDI Name text field and pressing Enter, the application does not show as “`(changed)`” in the title bar, and an error is written to `~/.deploytool/logfile`. When saving the application and going back to the tab, the JNDI Name field is blank again. When viewing the Sun descriptor using Tools\>Descriptor Viewer\>Application Server Descriptor, the `<message-destination\>` element within the `<jndi-name\>` element has not been created.

  The problem is that during a deploytool session, the first time a value is entered for a Message Destination JNDI Name, the value appears correct in the Sun descriptor but an `IllegalArgumentException` is thrown by `org.netbeans.modules.schema2beans.BeanProp.setElement()`. Subsequent changes or additions of a Message Destination JNDI Name in the same application or other applications will not be saved to the Sun descriptor.

#### Solution

To edit an existing JNDI Name of a Message Destination:

#### To edit an existing JNDI name

1. Delete the existing JNDI Name by leaving the JNDI Name text field blank and pressing Enter.

2. Type the new JNDI Name and press Enter.

3. Review the Sun descriptor by clicking Tools\>Descriptor Viewer\>Application Server Descriptor.

4. Save the application by clicking File\>Save.

   If the JNDI Name is not saved to the Sun descriptor:

5. Restart deploytool.

6. On the Message Destinations tab, select a Message Destination or add a new Message Destination.

7. Enter the JNDI Name for the Message Destination in the Sun-specific JNDI Name text field, and then press Enter.

8. Review the Sun descriptor by clicking Tools\>Descriptor Viewer\>Application Server Descriptor.

9. Save the application by clicking File\>Save.

   Repeat the above steps each time a value needs to be entered in the Sun-specific JNDI Name on the Message Destinations tab, unless a value is being entered in the JNDI Name text field for the first time during a deploytool session.

### Broken panels in the New Web Service Wizard (ID 6198981)

This problem manifests with two sets of symptoms:

- Clicking Next on the WSDL File panel does not go to the next panel, and an exception is thrown:

      java.lang.NoClassDefFoundError: com/sun/org/apache/xpath/internal/XPathAPI

- On Create Packaged Endpoint panel, select Create Web Service Endpoint and Package. Clicking Finish on the Next Steps panel does not create the Endpoint module in the output directory, and an exception is thrown:

      java.lang.NoClassDefFoundError: com/sun/org/apache/xpath/internal/XPathAPI.

  The problem is that `xalan.jar`, which contains the `XPathAPI.class`, is missing from the `CLASSPATH`. Note that this problem does not exist with JDK 5.0.

#### Solution

Add `xalan.jar` to the `CLASSPATH includes` for the `s1as-deploytool` process of install_dir`/lib/processLauncher.xml`; for example:

    includes="appserv-assemblytool.jar,activation.jar,appserv-admin.jar,
    appserv-cmp.jar,appserv-rt.jar,j2ee.jar,jaxrpc-impl.jar,appserv-ext.jar,
    deployhelp.jar,admin-cli.jar,dom.jar,xercesImpl.jar, xalan.jar"

### “Home” incorrectly translated as “installation directory” in Deploytool for Simplified Chinese. (ID 6203658)

When you create an Enterprise Bean in deploytool, and then navigate to the Transaction or Security tab for the bean node, the “Local Home” and “Remote Home” labels are incorrectly translated as “Local Installation Directory” and “Remote Installation Directory.”

- Previous: Container Managed Persistence
- Next: Documentation

- © 2010, Oracle Corporation and/or its affiliates