-
1. Re: bad stream errors on two xml/xsd files in JBT2GA
maxandersen Jan 28, 2008 4:11 PM (in response to shareme)say what ? ,)
bad stream errors where ? stacktraces ? -
2. Re: bad stream errors on two xml/xsd files in JBT2GA
shareme Jan 28, 2008 5:57 PM (in response to shareme)No in the web.xml xsd declaration..
So I went to windows>preferences and viewed the XML catalog and two xsd files are showing up with errors Java5.xsd contributed by a JBoss plugin and web-faces-config 1.2 also contributed by a JBossTools plugin..
Rest of the XML catalog entries contributed by JbossTools plugins show no errors except for those two.. -
3. Re: bad stream errors on two xml/xsd files in JBT2GA
shareme Jan 28, 2008 6:39 PM (in response to shareme)I may have found the reoslution in the plugin.xml for C:\Java\eclipse_plugins3311\eclipse\plugins\org.jboss.tools.jst.web_2.0.0.GA
Plugin lists the entirs for Javaee xsd and etc with catalog..other Jboss plugins uae schemas..
Hold on will try changign and see if it works.. -
4. Re: bad stream errors on two xml/xsd files in JBT2GA
maxandersen Jan 29, 2008 3:39 AM (in response to shareme)i still don't understand why you say "bad stream error" ?
Please state exactly what error you are seeing - thanks ;) -
5. Re: bad stream errors on two xml/xsd files in JBT2GA
shareme Jan 30, 2008 7:44 AM (in response to shareme)Okay, I will go slowly..
In elcispe under web and xml and under catalog..if the xml schema file is unable to be vlaidated it shows a little red bo xindicator..
Now in the xml declaration in the Jboo sconfigs such say as portlet.xml ti than shows as bad stream error..
One set of errors generated because Jboss moved their portal dtdt url..now gives 404 errors..
Other set of errros sens ie bad sream results form the underlying dtd description being loaded by Jbosstools plugins from sun being not validated as underlyign dtd linke din javaee5.xsd is lsited as not reachable.. -
6. Re: bad stream errors on two xml/xsd files in JBT2GA
maxandersen Jan 31, 2008 4:27 PM (in response to shareme)I still don't know why you are saying "bad stream". Are you actually getting an Bad Stream exception somewhere - if yes, what is it ?
please report in jira with screenshots and logs.