I went ahead and implemented my proposed solution locally just to see,
and yeah it stopped the double parsing.
The tests all run fine from command line (mvn clean test). However,
some fail when I run from IDE (specifically some of the packaging tests
again; ScannerTest was the culprit today). Bu
Would love some feedback on
http://in.relation.to/Bloggers/RFCXSDValidationInBothJDK15And16
--
Steve Ebersole
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5543
In JEE bootstrapping, mapping documents are parsed and validated twice
(details in the jira issue).
Problem is this code is extremely confusing and so I wanted to validate
my idea on the solution. Could y'all take a look?
--
S
On Wed, 2010-09-08 at 18:05 +0200, Emmanuel Bernard wrote:
> On 8 sept. 2010, at 10:35, Hardy Ferentschik wrote:
>
> > - So far I haven't renamed any package names. This has the advantage our
> > existing users don't have to change their code.
> > Does it make sense to rename the packages?
>
On 8 sept. 2010, at 10:35, Hardy Ferentschik wrote:
> Hi,
>
> I was working on the issues around upgrading HSearch to Lucene 3.0
> (HSEARCH-424).
> Before even thinking about utilizing any of the new Lucene features like
> numeric fields and so on, we
> have to deal with HSEARCH-593 - the up
Hi,
I was working on the issues around upgrading HSearch to Lucene 3.0
(HSEARCH-424).
Before even thinking about utilizing any of the new Lucene features like
numeric fields and so on, we
have to deal with HSEARCH-593 - the upgrade of the Solr analyzer framework.
We are using the Solr analyze
