facebook

MyEclipse 3.8 preference defaults to crimson (SAX for JBoss)

đź’ˇ
Our Forums Have Moved

For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub

  1. MyEclipse IDE
  2.  > 
  3. Installation, Configuration & Updates
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #209683 Reply

    mherv
    Member

    This causes many errors. when starting JBOSS and using XDoclet
    Seems that MyEclipse should default to Xerces as recommended in the forum

    Best regards,

    MH

    #209685

    Riyad Kalla
    Member

    Can you explain in more detail which problem you are describing? What version of Eclipse, MyEclipse, JDK, JBoss are you using? What are you trying to do? What is going wrong?

    #209697

    mherv
    Member

    hi, here are the details

    jdk : j2sdk1.4.2_05
    eclipse : Version: 3.0.0 Build id: 200406251208
    hypersonic replaced by MYSQL
    mysql : mysql-4.0.20d-win
    JBOSS :jboss-4.0.0DR4
    MyEclipse : Version: 3.7.101 Build id: 200405301200-3.8-Beta1

    here is what happens when crimson is on :
    when I launch JBOSS from Myeclipse

    Caused by: org.xml.sax.SAXException: Le type dĂ©lĂ©ment “{0}” nest pas dĂ©clarĂ©. @ jar:file:/I:/java/serveurs/jboss-4.0.0DR4/server/all/tmp/deploy/tmp19860jboss-local-jdbc.rar!/META-INF/ra.xml[5,-1]
    at org.jboss.xml.binding.Unmarshaller$MetaDataErrorHandler.error(Unmarshaller.java:170)
    at org.apache.crimson.parser.Parser2.error(Parser2.java:3359)
    at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1502)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
    at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
    at org.jboss.xml.binding.Unmarshaller.unmarshal(Unmarshaller.java:153)
    at org.jboss.deployment.SimpleSubDeployerSupport.parseMetaData(SimpleSubDeployerSupport.java:213)
    … 106 more
    12:53:24,468 WARN [Unmarshaller] SAX feature not recognized: http://apache.org/xml/features/validation/schema
    12:53:24,468 WARN [Unmarshaller] SAX feature not recognized: http://apache.org/xml/features/validation/schema-full-checking
    12:53:24,468 WARN [Unmarshaller] SAX feature not recognized: http://apache.org/xml/features/validation/dynamic
    12:53:24,468 WARN [Unmarshaller] Les documents valides doivent comporter une déclaration <!DOCTYPE. @ jar:file:/I:/java/serveurs/jboss-4.0.0DR4/server/all/tmp/deploy/tmp19861jboss-xa-jdbc.rar!/META-INF/ra.xml[5,-1]
    12:53:24,468 ERROR [MainDeployer] Could not initialise deployment: file:/I:/java/serveurs/jboss-4.0.0DR4/server/all/deploy/jboss-xa-jdbc.rar
    org.jboss.deployment.DeploymentException: Error parsing meta data jar:file:/I:/java/serveurs/jboss-4.0.0DR4/server/all/tmp/deploy/tmp19861jboss-xa-jdbc.rar!/META-INF/ra.xml; – nested throwable: (org.xml.sax.SAXException: Le type dĂ©lĂ©ment “{0}” nest pas dĂ©clarĂ©. @ jar:file:/I:/java/serveurs/jboss-4.0.0DR4/server/all/tmp/deploy/tmp19861jboss-xa-jdbc.rar!/META-INF/ra.xml[5,-1])
    at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:39)
    at org.jboss.deployment.SimpleSubDeployerSupport.parseMetaData(SimpleSubDeployerSupport.java:217)
    at org.jboss.deployment.SimpleSubDeployerSupport.init(SimpleSubDeployerSupport.java:102)
    at org.jboss.deployment.MainDeployer.init(MainDeployer.java:727)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:664)
    at org.jboss.deployment.MainDeployer.addDeployer(MainDeployer.java:267)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:232)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:643)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:174)
    at $Proxy34.addDeployer(Unknown Source)
    at org.jboss.deployment.SubDeployerSupport.startService(SubDeployerSupport.java:108)
    at org.jboss.resource.deployment.RARDeployer.startService(RARDeployer.java:138)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:232)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:643)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:844)
    at $Proxy17.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:369)
    at org.jboss.system.ServiceController.start(ServiceController.java:391)
    at org.jboss.system.ServiceController.start(ServiceController.java:391)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:232)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:643)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:174)
    at $Proxy4.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:260)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:863)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:674)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:637)
    at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:232)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:643)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:174)
    at $Proxy7.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:274)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:232)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:643)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:844)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:369)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:232)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:643)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:174)
    at $Proxy4.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:260)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:863)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:674)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:637)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:621)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:232)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:643)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:174)
    at $Proxy5.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:386)
    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)
    at org.jboss.Main.boot(Main.java:150)
    at org.jboss.Main$1.run(Main.java:395)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: org.xml.sax.SAXException: Le type dĂ©lĂ©ment “{0}” nest pas dĂ©clarĂ©. @ jar:file:/I:/java/serveurs/jboss-4.0.0DR4/server/all/tmp/deploy/tmp19861jboss-xa-jdbc.rar!/META-INF/ra.xml[5,-1]
    at org.jboss.xml.binding.Unmarshaller$MetaDataErrorHandler.error(Unmarshaller.java:170)
    at org.apache.crimson.parser.Parser2.error(Parser2.java:3359)
    at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1502)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
    at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
    at org.jboss.xml.binding.Unmarshaller.unmarshal(Unmarshaller.java:153)
    at org.jboss.deployment.SimpleSubDeployerSupport.parseMetaData(SimpleSubDeployerSupport.java:213)
    … 106 more

    etc……

    this is what happens when I try to modify the xdoclet parameters of a simple EJB (I added Jboss in the parameters)
    1) I get a popup window about a failure of backgrouns ant build
    2) the console reports the following errors :
    [ejbdoclet] org.xml.sax.SAXParseException: LĂ©lĂ©ment “{0}” nĂ©cessite des Ă©lĂ©ments additionnels.
    [ejbdoclet] at org.apache.crimson.parser.Parser2.error(Parser2.java:3354)
    [ejbdoclet] at org.apache.crimson.parser.ValidatingParser$ChildrenValidator.done(ValidatingParser.java:361)
    [ejbdoclet] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1703)
    [ejbdoclet] at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
    [ejbdoclet] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
    [ejbdoclet] at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667)
    [ejbdoclet] at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
    [ejbdoclet] at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
    [ejbdoclet] at xdoclet.util.XmlValidator.doValidate(XmlValidator.java:220)
    [ejbdoclet] at xdoclet.util.XmlValidator.validate(XmlValidator.java:189)
    [ejbdoclet] at xdoclet.XmlSubTask.engineFinished(XmlSubTask.java:242)
    [ejbdoclet] at xdoclet.TemplateSubTask.startEngine(TemplateSubTask.java:562)
    [ejbdoclet] at xdoclet.TemplateSubTask.startProcessForAll(TemplateSubTask.java:616)
    [ejbdoclet] at xdoclet.TemplateSubTask.startProcess(TemplateSubTask.java:597)
    [ejbdoclet] at xdoclet.XmlSubTask.startProcess(XmlSubTask.java:198)
    [ejbdoclet] at xdoclet.modules.ejb.dd.EjbDotXmlSubTask.execute(EjbDotXmlSubTask.java:217)
    [ejbdoclet] at xdoclet.XDocletMain.start(XDocletMain.java:48)
    [ejbdoclet] at xdoclet.DocletTask.start(DocletTask.java:464)
    [ejbdoclet] at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:110)
    [ejbdoclet] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269)
    [ejbdoclet] at org.apache.tools.ant.Task.perform(Task.java:364)
    [ejbdoclet] at org.apache.tools.ant.Target.execute(Target.java:301)
    [ejbdoclet] at org.apache.tools.ant.Target.performTasks(Target.java:328)
    [ejbdoclet] at org.apache.tools.ant.Project.executeTarget(Project.java:1215)
    [ejbdoclet] at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:635)
    [ejbdoclet] at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:412)
    [ejbdoclet] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [ejbdoclet] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [ejbdoclet] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [ejbdoclet] at java.lang.reflect.Method.invoke(Method.java:324)
    [ejbdoclet] at org.eclipse.ant.core.AntRunner.run(AntRunner.java:350)
    [ejbdoclet] at org.eclipse.ant.internal.ui.launchConfigurations.AntLaunchDelegate$1.run(AntLaunchDelegate.java:182)
    [ejbdoclet] at java.lang.Thread.run(Thread.java:534)
    [ejbdoclet] (XDocletMain.start 53 ) Running XDoclet failed.
    [ejbdoclet] (XDocletMain.start 54 ) <<Couldn’t validate document I:\java\eclipse\workspace\CoucouEJB\src\META-INF\ejb-jar.xml>>
    [ejbdoclet] I:\java\eclipse\workspace\CoucouEJB\xdoclet-build.xml:27: XDoclet failed.
    [ejbdoclet] at xdoclet.DocletTask.start(DocletTask.java:467)
    [ejbdoclet] at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:110)
    [ejbdoclet] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269)
    [ejbdoclet] at org.apache.tools.ant.Task.perform(Task.java:364)
    [ejbdoclet] at org.apache.tools.ant.Target.execute(Target.java:301)
    [ejbdoclet] at org.apache.tools.ant.Target.performTasks(Target.java:328)
    [ejbdoclet] at org.apache.tools.ant.Project.executeTarget(Project.java:1215)
    [ejbdoclet] at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:635)
    [ejbdoclet] at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:412)
    [ejbdoclet] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [ejbdoclet] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [ejbdoclet] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [ejbdoclet] at java.lang.reflect.Method.invoke(Method.java:324)
    [ejbdoclet] at org.eclipse.ant.core.AntRunner.run(AntRunner.java:350)
    [ejbdoclet] at org.eclipse.ant.internal.ui.launchConfigurations.AntLaunchDelegate$1.run(AntLaunchDelegate.java:182)
    [ejbdoclet] at java.lang.Thread.run(Thread.java:534)
    [ejbdoclet] Caused by: xdoclet.XDocletException: Couldn’t validate document I:\java\eclipse\workspace\CoucouEJB\src\META-INF\ejb-jar.xml
    [ejbdoclet] at xdoclet.util.XmlValidator.doValidate(XmlValidator.java:224)
    [ejbdoclet] at xdoclet.util.XmlValidator.validate(XmlValidator.java:189)
    [ejbdoclet] at xdoclet.XmlSubTask.engineFinished(XmlSubTask.java:242)
    [ejbdoclet] at xdoclet.TemplateSubTask.startEngine(TemplateSubTask.java:562)
    [ejbdoclet] at xdoclet.TemplateSubTask.startProcessForAll(TemplateSubTask.java:616)
    [ejbdoclet] at xdoclet.TemplateSubTask.startProcess(TemplateSubTask.java:597)
    [ejbdoclet] at xdoclet.XmlSubTask.startProcess(XmlSubTask.java:198)
    [ejbdoclet] at xdoclet.modules.ejb.dd.EjbDotXmlSubTask.execute(EjbDotXmlSubTask.java:217)
    [ejbdoclet] at xdoclet.XDocletMain.start(XDocletMain.java:48)
    [ejbdoclet] at xdoclet.DocletTask.start(DocletTask.java:464)
    [ejbdoclet] … 15 more
    [ejbdoclet] — Nested Exception —
    [ejbdoclet] xdoclet.XDocletException: Couldn’t validate document I:\java\eclipse\workspace\CoucouEJB\src\META-INF\ejb-jar.xml
    [ejbdoclet] at xdoclet.util.XmlValidator.doValidate(XmlValidator.java:224)
    [ejbdoclet] at xdoclet.util.XmlValidator.validate(XmlValidator.java:189)
    [ejbdoclet] at xdoclet.XmlSubTask.engineFinished(XmlSubTask.java:242)
    [ejbdoclet] at xdoclet.TemplateSubTask.startEngine(TemplateSubTask.java:562)
    [ejbdoclet] at xdoclet.TemplateSubTask.startProcessForAll(TemplateSubTask.java:616)
    [ejbdoclet] at xdoclet.TemplateSubTask.startProcess(TemplateSubTask.java:597)
    [ejbdoclet] at xdoclet.XmlSubTask.startProcess(XmlSubTask.java:198)
    [ejbdoclet] at xdoclet.modules.ejb.dd.EjbDotXmlSubTask.execute(EjbDotXmlSubTask.java:217)
    [ejbdoclet] at xdoclet.XDocletMain.start(XDocletMain.java:48)
    [ejbdoclet] at xdoclet.DocletTask.start(DocletTask.java:464)
    [ejbdoclet] at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:110)
    [ejbdoclet] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269)
    [ejbdoclet] at org.apache.tools.ant.Task.perform(Task.java:364)
    [ejbdoclet] at org.apache.tools.ant.Target.execute(Target.java:301)
    [ejbdoclet] at org.apache.tools.ant.Target.performTasks(Target.java:328)
    [ejbdoclet] at org.apache.tools.ant.Project.executeTarget(Project.java:1215)
    [ejbdoclet] at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:635)
    [ejbdoclet] at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:412)
    [ejbdoclet] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [ejbdoclet] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [ejbdoclet] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [ejbdoclet] at java.lang.reflect.Method.invoke(Method.java:324)
    [ejbdoclet] at org.eclipse.ant.core.AntRunner.run(AntRunner.java:350)
    [ejbdoclet] at org.eclipse.ant.internal.ui.launchConfigurations.AntLaunchDelegate$1.run(AntLaunchDelegate.java:182)
    [ejbdoclet] at java.lang.Thread.run(Thread.java:534)
    BUILD FAILED: I:\java\eclipse\workspace\CoucouEJB\xdoclet-build.xml:27: Unexpected error

    Now If I replace crimson by xerces in the jboss 4 server parameters and I add the xerces external jars in Ant, I do not get thse errors any more.
    However, when I try to generate XDOCLET, I get another error, but I have no time to invesitgate more on it at this time.

    Will have to wait for another thread.

    I hope this helped,
    Sincerely, MH

    #209701

    Riyad Kalla
    Member

    Thank you for the clarification, I will send this to the dev team and see what they can find.

    #209764

    mherv
    Member

    The second set of errors I still got with XDOCLET parameters and XERCES is solved : I was giving bad parameters.

    There is another problem I forwarded to JBOSS : in the JBOSS Xdoclet descriptor of myeclipse, when you answer 4.0 to the version topic, you get an error upon the EJB generation because jbosscmp-jdbc_4_0.dtd (the name might be slightly different) does not exist.

    regards,

    MH

    —-
    PS I have got a small eclipse question. Maybe you could answer me, because I don’t find out how to use their newsgroups :
    I have a bad install of the XSD plugin that I cannot uninstall automatically to replace it. I would like to remove the plugin manually, in order to reinstall it from new, but I fail to find all the files to remove. Do you have a clue?

    Sincerely MH

    #209774

    Scott Anderson
    Participant

    here is what happens when crimson is on :
    when I launch JBOSS from Myeclipse

    So are you simply letting us know that for JBoss 4, the default value we fill into the connector preference page should be changed from cromson to Xerces, or is it something more?

    I have got a small eclipse question. Maybe you could answer me, because I don’t find out how to use their newsgroups

    I don’t know the answer to the XSD plugins question off the top of my head, but you can get an Eclipse newsgroup account here:
    http://eclipse.org/newsgroups/index.html

    #209787

    mherv
    Member

    Your last thread :
    >>So are you simply letting us know that for JBoss 4, the default value we fill into the connector preference page
    >>should be changed from cromson to Xerces, or is it something more?

    Yes there is something more :
    when I run this tutorial :
    http://www.laliluna.de/tutorial/simpleEJB/xDoclet_jboss_first_EJB.html

    at step 8 of the tutorial you write :
    “# The following settings must be set.
    # Jboss Version, it is 3.2 for all 3.2.x ”

    this works with jBoss 3.2 and 4.0

    but if you fill in the “Version” parameter with 4.0 (as JBoss version is), the EJB will not be generated, because there is no JBOSSCMP-JDBC 4_0.dtd delivered with jBoss 4.0

    Hope this is clear
    regards, MH

    #209788

    Scott Anderson
    Participant

    Very good. Thanks!

Viewing 8 posts - 1 through 8 (of 8 total)
Reply To: MyEclipse 3.8 preference defaults to crimson (SAX for JBoss)

You must be logged in to post in the forum log in