BROCKED was Re: [jboss-dev] JBossXB parse error for bean deployment

Anil Saldhana Anil.Saldhana at redhat.com
Tue Mar 25 20:13:01 EDT 2008


Apparently, it is the XB upgrade from CR6 to CR7 that is the causing the 
parsing error.
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/build/build-thirdparty.xml?r1=70926&r2=70929

What changed between CR6 and CR7?

The design thread is : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=131725


Adrian Brock wrote:
> On Tue, 2008-03-25 at 10:55 -0500, Anil Saldhana wrote:
>> Oh. By the way, I did ask in the design forum thread wherever the last 
>> XB change was:
>> http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138560
>>
>> I have not seen any response to this question. Only after this, have I 
>> broached the dev list for a potential Brock.
> 
> Some people are just more polite and leave you with dead air 
> for unanswerable questions. ;-)
> 
>> Whoever deals with JBossXB, either correct us or tell us why we have 
>> this behavioral change in 2-3 days.
>>
> 
> Hmmm, upgrade of xerces 44 hours ago. D'ya think? :-)
> 
> http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/build/build-thirdparty.xml?view=log
> 
>> Anil Saldhana wrote:
>>> The schema has existed in jboss/docs/schema for more than 2 years now. 
>>> The error has started showing up when Stefan updated his AS workspace 
>>> (in the last 2-3 days). He was ready to commit a critical change. What 
>>> changed in the space of 2 days with AS workspace when he implemented the 
>>> stuff and updated his workspace to commit the change?
>>>
>>> I was not expecting answers from you but whoever made changes to XB in 
>>> the last 2-3 days.
>>>
>>> I will use the dev forums until I get answers to whoever broke security 
>>> team's code.
>>>
>>> Unlike others, we did not commit the code and break stuff. We are asking 
>>> before committing.
>>>
>>> Adrian Brock wrote:
>>>> Nice.
>>>>
>>>> A stacktrace on some code/config that we can't see
>>>> because it is uncommitted.
>>>>
>>>> Here's a simple "20 questions" to help you learn how
>>>> to debug things properly, or at least provide
>>>> enough information that the question can be answered.
>>>>
>>>> http://wiki.jboss.org/wiki/Wiki.jsp?page=HelpExpertSystem
>>>>
>>>>
>>>> ** GUESS **
>>>>
>>>> You haven't defined a mechanism to parse the schema
>>>> urn:jboss:security-config:5.0
>>>>
>>>> or if you have, it is getting defined after the parsing deployer
>>>> parses the xml you show in the stacktrace.
>>>>
>>>> ** WARNING **
>>>>
>>>> Please do not use the dev-forums/list if you can't be
>>>> bothered even doing enough work to make your question
>>>> answerable.
>>>>
>>>> The dev forums aren't even for help requests
>>>> EVEN THOUGH YOU MAYBE A DEVELOPER.
>>>>
>>>> ** SUMMARY **
>>>>
>>>> SHOW THE CODE
>>>> SHOW THE CONFIG
>>>> SHOW SOMETHING more than cutting and pasting a stacktrace
>>>> from your log into the dev-forums/list and expecting
>>>> others to use their (non-existant) psychic powers to figure out
>>>> what is going on. :-)
>>>>
>>>> On Tue, 2008-03-25 at 09:44 -0500, Anil Saldhana wrote:
>>>>> Stefan tells me that he is getting a JBossXB parse error for bean 
>>>>> deployments in the last 3-4 days.
>>>>> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=131725
>>>>>
>>>>> Any quick solutions for this?



More information about the jboss-development mailing list