You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by "Geoff M. Granum" <ge...@lookingglasssoftware.com> on 2007/06/21 08:19:43 UTC
Compling in IntelliJ / other IDE? Was: (XERCESJ-589) Bug with pattern restriction on long strings
Anyone have some quick tips for compiling Xerces using IntelliJ?
I have some thoughts on how I might re-implement this without having to
modify behavior. Which is to say, modify in-place while still removing
recursion, probably 50-100 lines of new code. Just for that method; there
are other probably-deep recursion calls, but the only bug is on this one,
I believe? If the solution is accepted as workable, the performance
increase of dropping so many nested recursion calls might merit jumping on
the other methods. Only performance tests will tell.
However, there is a slight issue: I am completely addicted to IntelliJ for
all my Java needs, and it doesn't seem to want to play (read: 'debug')
with the class files unless it gets to compile them.
I admit, I spent far more time looking at the code than trying to get
IntelliJ to let me debug it. Using the ant build I'm reproducing the bug
just fine. I'll work without if I have to, but it's worth the time to ask.
I'm guessing that I need to point to an extra JDK and replace a few files?
If there is a readme out there somewhere on the subject, I'd appreciate a
pointer.
This is a straight 'New Project from Source Control' IntelliJ project.
Thanks,
--
Geoff M. Granum
Portland, Oregon
On Wed, 20 Jun 2007 15:51:26 -0700, Michael Glavassevich (JIRA)
<xe...@xml.apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/XERCESJ-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506712
> ]
>
> Michael Glavassevich commented on XERCESJ-589:
> ----------------------------------------------
>
> Sorry, java.util.regex isn't an option here. We cannot use it because it
> doesn't support the regular expression language defined by the XML
> Schema specification [1]. The one supported by java.util.regex is quite
> different. We also cannot use java.util.regex because it was introduced
> in Java 1.4. Xerces-J is still built with Java 1.3 (and should be able
> to run on Java 1.2).
>
> [1] http://www.w3.org/TR/xmlschema-2/#regexs
>
>> Bug with pattern restriction on long strings
>> --------------------------------------------
>>
>> Key: XERCESJ-589
>> URL: https://issues.apache.org/jira/browse/XERCESJ-589
>> Project: Xerces2-J
>> Issue Type: Bug
>> Components: XML Schema Structures
>> Affects Versions: 2.3.0
>> Environment: Operating System: All
>> Platform: All
>> Reporter: Mark Woon
>> Attachments: RegularExpression.java, test.xml, test.xsd,
>> test.zip
>>
>>
>> There is a bug with applying a pattern restriction on long strings
>> while trying
>> to validate an XML file against a schema. I'm including an xml file
>> and xsd
>> file that demonstrates this problem. One character less in <sequence>
>> and the
>> problem does not occur.
>> As it is, I'm getting
>> java.lang.StackOverflowError
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.xpath.regex.RegularExpression.matchString(Unknown
>> Source)
>> ...
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Compling in IntelliJ / other IDE? Was: (XERCESJ-589) Bug with pattern
restriction on long strings
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Geoff,
I use Eclipse exclusively so can't offer any suggestions on that.
Just wanted to say that I'm glad someone is finally looking into solving
this problem. Thanks for volunteering.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
"Geoff M. Granum" <ge...@lookingglasssoftware.com> wrote on
06/21/2007 02:19:43 AM:
> Anyone have some quick tips for compiling Xerces using IntelliJ?
>
> I have some thoughts on how I might re-implement this without having to
> modify behavior. Which is to say, modify in-place while still removing
> recursion, probably 50-100 lines of new code. Just for that method;
there
> are other probably-deep recursion calls, but the only bug is on this
one,
> I believe? If the solution is accepted as workable, the performance
> increase of dropping so many nested recursion calls might merit jumping
on
> the other methods. Only performance tests will tell.
>
> However, there is a slight issue: I am completely addicted to IntelliJ
for
> all my Java needs, and it doesn't seem to want to play (read: 'debug')
> with the class files unless it gets to compile them.
>
> I admit, I spent far more time looking at the code than trying to get
> IntelliJ to let me debug it. Using the ant build I'm reproducing the bug
> just fine. I'll work without if I have to, but it's worth the time to
ask.
>
> I'm guessing that I need to point to an extra JDK and replace a few
files?
> If there is a readme out there somewhere on the subject, I'd appreciate
a
> pointer.
>
> This is a straight 'New Project from Source Control' IntelliJ project.
>
> Thanks,
> --
> Geoff M. Granum
> Portland, Oregon
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-dev-help@xerces.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org