RE: [jBoss-User] Deployment Error when using jaws file

[marc fleury]

Title: Deployment Error when using jaws file

ejx is not yet adapted to use the proper mappings, nor does it really behave nicely by outputting only what is needed (as you noticed).

 

The simples solution is to change the jaws.xml file manually for now,

 

marc

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Caron, Jonathan (Jon)
Sent: Monday, September 18, 2000 10:01 AM
To: 'jBoss<[EMAIL PROTECTED]>'
Subject: [jBoss-User] Deployment Error when using jaws file

There seem to be some missing mappings in the standardjaws.xml.

I'm trying to deploy a bean with Hypersonic and it is being prevented by the mappings for the other databases that the jaws.xml file provides. I am using EJX to create the file,and it always adds the mappings to the jaws.xml file. It does not check to see if the mapping is complete. JBoss, however checks this and prevents deployment.

Should the exportXml method in TypeMapping.java be changed to only output the Xml mapping node if all parts are complete, or should the null mappings be removed from the standardjaws.xml?

[JAWS] Initializing JAWS plugin for Fault
[JAWS] Loading standardjaws.xml : jar:file:/D:/jboss-build/dist/lib/ext/jboss.ja
r!/org/jboss/ejb/plugins/jaws/metadata/standardjaws.xml
[JAWS] jar:file:/D:/jboss-build/dist/tmp/deploy/tmpejbjar17966.jar!/META-INF/jaw
s.xml found. Overriding defaults
[Container factory] Unrecognized jdbc-type: DATETIME, using Types.OTHER
[Container factory] Unrecognized jdbc-type: IMAGE, using Types.OTHER
[Container factory] org.jboss.ejb.DeploymentException: Error in jaws.xml for typ
e-mapping SOLID: jdbc-type cannot be null