Menu
▾
▴
exist-development — eXist Developer's List
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(22) |
Nov
(85) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(47) |
Feb
(127) |
Mar
(268) |
Apr
(78) |
May
(47) |
Jun
(38) |
Jul
(131) |
Aug
(221) |
Sep
(187) |
Oct
(54) |
Nov
(111) |
Dec
(84) |
| 2011 |
Jan
(152) |
Feb
(106) |
Mar
(94) |
Apr
(90) |
May
(53) |
Jun
(20) |
Jul
(24) |
Aug
(37) |
Sep
(32) |
Oct
(70) |
Nov
(22) |
Dec
(15) |
| 2012 |
Jan
(33) |
Feb
(110) |
Mar
(24) |
Apr
(1) |
May
(11) |
Jun
(8) |
Jul
(12) |
Aug
(37) |
Sep
(39) |
Oct
(81) |
Nov
(38) |
Dec
(50) |
| 2013 |
Jan
(23) |
Feb
(53) |
Mar
(23) |
Apr
(5) |
May
(19) |
Jun
(16) |
Jul
(16) |
Aug
(9) |
Sep
(21) |
Oct
(1) |
Nov
(2) |
Dec
(8) |
| 2014 |
Jan
(16) |
Feb
(6) |
Mar
(27) |
Apr
(1) |
May
(10) |
Jun
(1) |
Jul
(4) |
Aug
(10) |
Sep
(19) |
Oct
(22) |
Nov
(4) |
Dec
(6) |
| 2015 |
Jan
(3) |
Feb
(6) |
Mar
(9) |
Apr
|
May
(11) |
Jun
(23) |
Jul
(14) |
Aug
(10) |
Sep
(10) |
Oct
(9) |
Nov
(18) |
Dec
(4) |
| 2016 |
Jan
(5) |
Feb
(5) |
Mar
|
Apr
(2) |
May
(15) |
Jun
(2) |
Jul
(8) |
Aug
(2) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(2) |
Feb
(12) |
Mar
(22) |
Apr
(6) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(5) |
Oct
(2) |
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(7) |
Oct
(19) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Adam R. <ad...@ex...> - 2015-01-05 08:43:07
|
Alister, can you share the last few messages from 'git log' for your
develop branch and any other branch you want to migrate. Happy for you to
email me privately if it is sensitive
On 5 Jan 2015 06:04, "Alister Pillow" <gsp...@gm...> wrote:
> Hi Adam,
> As you have kindly offered…
>
> I’ve made two commits since updating (recently) from exist develop. The
> first of these is “8fe9eebf5a49a95bd1857d6d67c7d48a92c6f4b8”.
> So I think the rebase command should be
> git rebase —onto ac160ba32bfb721abe120ec558ca3f22eeb63c5c
> 8fe9eebf5a49a95bd1857d6d67c7d48a92c6f4b8~1
>
> Does that look correct? (I am tempted to start again by cloning from
> develop.)
>
> Prior to running this I’ll need to deal with the uncommitted changes -
> which is where I’ve been uncertain for a while.
>
> In my working directory, git status shows as modified all the
> lib/core/*.jar files.
> Are these modified when signing the code?
> How should I deal with them prior to running rebase?
>
> Thanks,
> Alister.
>
> On 5 Jan 2015, at 10:48 am, Adam Retter <ad...@ex...> wrote:
>
>
> Any questions, about adjusting your fork/clone branches, please just
> ask, I would like this to be as painless for everyone as possible.
>
> Cheers Adam.
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>
>
|
|
From: Alister P. <gsp...@gm...> - 2015-01-05 06:04:55
|
Hi Adam,
As you have kindly offered…
I’ve made two commits since updating (recently) from exist develop. The first of these is “8fe9eebf5a49a95bd1857d6d67c7d48a92c6f4b8”.
So I think the rebase command should be
git rebase —onto ac160ba32bfb721abe120ec558ca3f22eeb63c5c 8fe9eebf5a49a95bd1857d6d67c7d48a92c6f4b8~1
Does that look correct? (I am tempted to start again by cloning from develop.)
Prior to running this I’ll need to deal with the uncommitted changes - which is where I’ve been uncertain for a while.
In my working directory, git status shows as modified all the lib/core/*.jar files.
Are these modified when signing the code?
How should I deal with them prior to running rebase?
Thanks,
Alister.
On 5 Jan 2015, at 10:48 am, Adam Retter <ad...@ex...> wrote:
>
> Any questions, about adjusting your fork/clone branches, please just
> ask, I would like this to be as painless for everyone as possible.
>
> Cheers Adam.
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
|
|
From: Adam R. <ad...@ex...> - 2015-01-05 00:18:15
|
Just a heads-up to let you know that we have undone the latest merge
to the 'develop' branch as we discovered that there were conflicts in
revisions making up the commit. You won't see a merge as this was done
using `git reset`.
So if you have your own fork of 'develop' and/or branches based on
'develop' with your commits based on (i.e. after) af2fe83 (11 days
ago) then you may need to reabse locally. The 'develop' branch has
been reset to ac160ba.
If your own clone branch ('develop' or otherwise) was not past commit
ac160ba before you started making changes (if any), then you can
safely ignore this email.
Otherwise, if you were until now completely up to date, then you can
use the command `git rebase --onto` whilst on your branch to get back
in sync. Obviously, please make a backup of your local clone before
attempting this, and then check the results locally using `git log`,
and for more details of how to rebase onto, see:
http://pivotallabs.com/git-rebase-onto/.
Any questions, about adjusting your fork/clone branches, please just
ask, I would like this to be as painless for everyone as possible.
Cheers Adam.
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Wolfgang M. <wol...@ex...> - 2014-12-30 09:38:12
|
> Java 8 looks good for me. In production for several months. Same here. eXist 2.2 runs perfectly well on java 8. We tested this extensively before the release. There are a few minor test failures which still have to be addressed (see Dannes' report), but I assume they are more likely issues of the test suite rather than real problems. In production I have not been able to see any issue at all. So from an end user perspective, it should all be ok. For sure we'll completely switch to 8 with the next release. I don't see a need to keep java 7 compatibility for much longer. Wolfgang |
|
From: Dmitriy S. <sha...@gm...> - 2014-12-30 08:50:15
|
BTW, there is no much options anyway -) On Tue, Dec 30, 2014 at 12:46 PM, Dmitriy Shabanov <sha...@gm...> wrote: > Java 8 looks good for me. In production for several months. > > On Tue, Dec 30, 2014 at 2:30 AM, Adam Retter <ad...@ex...> wrote: > >> Hey Guys, >> >> Just read this - >> http://www.oracle.com/technetwork/java/javase/downloads/eol-135779.html >> >> Whilst I was aware that public Oracle OpenJDK 7 was going to be EOL in >> April 2015, it looks like the upgrade path actually starts in January >> 2015. It would seem to me sensible, to release a 2.3 version of eXist >> which is built and compiled for Java 8 in January. >> >> What does everyone else think? >> >> -- >> Adam Retter >> >> eXist Developer >> { United Kingdom } >> ad...@ex... >> irc://irc.freenode.net/existdb >> >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming! The Go Parallel Website, >> sponsored by Intel and developed in partnership with Slashdot Media, is >> your >> hub for all things parallel software development, from weekly thought >> leadership blogs to news, videos, case studies, tutorials and more. Take a >> look and join the conversation now. http://goparallel.sourceforge.net >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development >> > > > > -- > Dmitriy Shabanov > -- Dmitriy Shabanov |
|
From: Dmitriy S. <sha...@gm...> - 2014-12-30 08:46:59
|
Java 8 looks good for me. In production for several months. On Tue, Dec 30, 2014 at 2:30 AM, Adam Retter <ad...@ex...> wrote: > Hey Guys, > > Just read this - > http://www.oracle.com/technetwork/java/javase/downloads/eol-135779.html > > Whilst I was aware that public Oracle OpenJDK 7 was going to be EOL in > April 2015, it looks like the upgrade path actually starts in January > 2015. It would seem to me sensible, to release a 2.3 version of eXist > which is built and compiled for Java 8 in January. > > What does everyone else think? > > -- > Adam Retter > > eXist Developer > { United Kingdom } > ad...@ex... > irc://irc.freenode.net/existdb > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- Dmitriy Shabanov |
|
From: Adam R. <ad...@ex...> - 2014-12-29 22:30:44
|
Hey Guys, Just read this - http://www.oracle.com/technetwork/java/javase/downloads/eol-135779.html Whilst I was aware that public Oracle OpenJDK 7 was going to be EOL in April 2015, it looks like the upgrade path actually starts in January 2015. It would seem to me sensible, to release a 2.3 version of eXist which is built and compiled for Java 8 in January. What does everyone else think? -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
|
From: Alister P. <gsp...@gm...> - 2014-12-16 11:52:50
|
Thanks, Adam, that's good news. Congrats for the book. Sent from my iPad > On 16 Dec 2014, at 10:06 pm, Adam Retter <ad...@ex...> wrote: > > Hi Alister that is now solved the problem was in the ModuleContext > rather than the XQueryContext > >> On 14 December 2014 at 05:06, Alister Pillow <gsp...@gm...> wrote: >> Hi, >> I’ve done some more investigation into this problem ( https://github.com/eXist-db/exist/issues/388 ). The “real user” is null, causing an NPE. >> It appears that (in XQueryContext) the Real User is being set to null after prepareForExecution. >> >> I added some notes to the Issue. >> >> Regards, >> Alister. >> ------------------------------------------------------------------------------ >> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server >> from Actuate! Instantly Supercharge Your Business Reports and Dashboards >> with Interactivity, Sharing, Native Excel Exports, App Integration & more >> Get technology previously reserved for billion-dollar corporations, FREE >> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development > > > > -- > Adam Retter > > eXist Developer > { United Kingdom } > ad...@ex... > irc://irc.freenode.net/existdb |
|
From: Alister P. <gsp...@gm...> - 2014-12-14 05:07:10
|
Hi, I’ve done some more investigation into this problem ( https://github.com/eXist-db/exist/issues/388 ). The “real user” is null, causing an NPE. It appears that (in XQueryContext) the Real User is being set to null after prepareForExecution. I added some notes to the Issue. Regards, Alister. |
|
From: <ale...@gm...> - 2014-11-24 17:48:58
|
Hi, ale...@gm... wants to follow you. ****** Is ale...@gm... you friend? ****** If Yes please follow the link below: http://invites.info-emailer.com/signup_e.html?fullname=&email=exi...@li...&invitername=alexei.tarnakin&inviterid=35335719&userid=0&token=0&emailmasterid=c06118e1-27bb-4b3b-bcc2-a1666feaced1&from=ale...@gm...&src=txt_yes If No please follow the link below: http://invites.info-emailer.com/signup_e.html?fullname=&email=exi...@li...&invitername=alexei.tarnakin&inviterid=35335719&userid=0&token=0&emailmasterid=c06118e1-27bb-4b3b-bcc2-a1666feaced1&from=ale...@gm...&src=txt_no Follow the link below to remove yourself from all such emails http://invites.info-emailer.com/uns_inviter.jsp?email=exi...@li...&iid=c06118e1-27bb-4b3b-bcc2-a1666feaced1&from=ale...@gm... |
|
From: Adam R. <ad...@ex...> - 2014-11-23 20:58:37
|
Just a heads-up to let you know that we have undone the latest merge
to the 'develop' branch as we felt that there were still problems in
the commit. You won't see a merge as this was done using `git reset`.
So if you have your own branches with your commits based later than
97bbbdd (3 days ago) then you may need to reabse locally.
Cheers Adam.
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Chris T. <chr...@gm...> - 2014-11-12 23:28:14
|
Hello,
I’ve attached a small patch for your consideration to allow specification of the minimumNumberShouldMatch for BooleanQuery(s) in XMLToQuery.
The feature is not available in the classic Lucene query syntax. It is made available in the Solr eDisMax query parser.
The feature allows to cut-off needless disjunctive searches.
It used like:
> let $min := if (count($terms) le 3) then $terms else (count($terms) + 1) idiv 2
> let $query :=
> <bool min="{$min}">{
> for $term in $terms
> return
> <term>{$term}</term>
> }</bool>
Thank you,
Chris
|
|
From: Tobias K. <tob...@be...> - 2014-11-04 13:04:53
|
Hi, Tried to fix this on my branch. See: https://github.com/zwobit/exist/releases/tag/eXist-2.2.RC2 Steps i have done: 1. delete local tag git tag -d eXist-2.2.RC2 2. create a new local signed tag git tag -s eXist-2.2.RC2 28f90f702e9f8228485985f8bfe093d4392a8666 3. Delete remote tag git push origin :refs/tags/eXist-2.2.RC2 4. Push new tag to remote git push --tags 5. git describe returns eXist-2.2.RC2-167-g56775dc Should i do the same for the "offical" eXist-repo? And if so do we have an "offical" signing key? Cheers Tobi Am 14.10.2014 um 18:18 schrieb Dannes Wessels: > I tried to create the tag by 'drafting a new release' via the github > releases page. I remember it did not go fluently I might have ruined then? > > The tag was created too late for sure, weeks after releasing RC2, this > was the cause of my struggle. > > if it is bad...... i'd could not say :-/ is it repairable? > > cheers > > Dannes > > > eXist-db Native XML Database > http://www.exist-db.org > > > > On 14 Oct 2014, at 12:59 , Adam Retter <ad...@ex... > <mailto:ad...@ex...>> wrote: > >> I am not sure how the eXist-2.2.RC2 tag was created in our Git repo, >> but it seems that however it was done was not correct. >> >> If I run `git describe` on `develop` then Git thinks that the last tag >> that was cut is eXist-2.2.RC1. >> >> Can anyone comment on this? >> >> I think we should discuss fixing this as it leads to problems with Git >> tools which try and work out the latest tag (release) of eXist. >> >> Thanks Adam. > > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > > > > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- Tobias Krebs betterFORM Project Web: www.betterform.de Office: +49 30 83 22 55 50 Fax: +49 30 83 22 55 04 |
|
From: Yair B. A. <ya...@tk...> - 2014-10-27 18:49:51
|
<p dir="ltr">betterFORM</p> <div class="quote">On Oct 27, 2014 7:52 PM, Joern Turner <joe...@gm...> wrote:<br type='attribution'><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>The error is coming from an xforms which you obviously try to run. Not sure, why it's failing but assume it has to do with the redirection. The XForms processor is using its own internal http client and i suspect that requests made my that client are not redirected. <br><br><br></div><div>Which XForms engine are you using?<br><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 27, 2014 at 6:41 PM, Yair Ben Avraham <span dir="ltr"><<a href="mailto:ya...@tk..." target="_blank">ya...@tk...</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br> <br> I have (what I'm thinking is) a redirect issue:<br> <br> When trying to run .xq file I get the following message:<br> "xforms-link-exception: uri resolution failed..."<br> <br> The details are:<br> eXist-db server running on port 8080.<br> external users who wants to connect to the data-base, use the server's IP<br> address with *another* port number, i.e: IP_address:7070.<br> The HTTP server configure to redirect IP_address:7070 to IP_address:8080.<br> New, external users can see the dashboard, to login, enter into<br> application but when trying to run .xq file they get the above message.<br> <br> Any help is welcome!<br> <br> Thanks,<br> Yair<br> --<br> Yair Ben-Avraham<br> <a href="mailto:ya...@tk...">ya...@tk...</a><br> 052-343-2297<br> <br> ------------------------------------------------------------------------------<br> _______________________________________________<br> Exist-development mailing list<br> <a href="mailto:Exi...@li...">Exi...@li...</a><br> <a href="https://lists.sourceforge.net/lists/listinfo/exist-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/exist-development</a><br> </blockquote></div><br></div> </blockquote></div> |
|
From: Joern T. <joe...@gm...> - 2014-10-27 17:52:37
|
The error is coming from an xforms which you obviously try to run. Not sure, why it's failing but assume it has to do with the redirection. The XForms processor is using its own internal http client and i suspect that requests made my that client are not redirected. Which XForms engine are you using? On Mon, Oct 27, 2014 at 6:41 PM, Yair Ben Avraham <ya...@tk...> wrote: > Hi all, > > I have (what I'm thinking is) a redirect issue: > > When trying to run .xq file I get the following message: > "xforms-link-exception: uri resolution failed..." > > The details are: > eXist-db server running on port 8080. > external users who wants to connect to the data-base, use the server's IP > address with *another* port number, i.e: IP_address:7070. > The HTTP server configure to redirect IP_address:7070 to IP_address:8080. > New, external users can see the dashboard, to login, enter into > application but when trying to run .xq file they get the above message. > > Any help is welcome! > > Thanks, > Yair > -- > Yair Ben-Avraham > ya...@tk... > 052-343-2297 > > > ------------------------------------------------------------------------------ > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > |
|
From: Yair B. A. <ya...@tk...> - 2014-10-27 17:41:05
|
Hi all, I have (what I'm thinking is) a redirect issue: When trying to run .xq file I get the following message: "xforms-link-exception: uri resolution failed..." The details are: eXist-db server running on port 8080. external users who wants to connect to the data-base, use the server's IP address with *another* port number, i.e: IP_address:7070. The HTTP server configure to redirect IP_address:7070 to IP_address:8080. New, external users can see the dashboard, to login, enter into application but when trying to run .xq file they get the above message. Any help is welcome! Thanks, Yair -- Yair Ben-Avraham ya...@tk... 052-343-2297 |
|
From: Adam R. <ad...@ex...> - 2014-10-26 11:39:34
|
> We need to give users some time to update their index definitions, so we have to keep the old index for a while. As we did for the legacy full-text index, I would suggest to disable the legacy range index in the default configuration after 2.2 has been released and then remove it entirely in 2.3.
>
Okay how do you see that working in Git? i.e. Can I remove it from the
'develop' branch once the 2.2 release is out the door?
> There’s also some work to do: 1) @xml:id are still using the legacy range index, 2) fn:matches is not supported due to regex limitations in lucence. Both issues need to be addressed before we disable the old index.
>
Okay, assuming this can be done in develop after the 2.2. release. I
would be happy to undertake that work. Do you want to assign me some
tasks?
> I agree the legacy range index is polluting NativeBroker with lots of nasty code, which can be removed once we drop the index.
>
Yay :-)
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: <wol...@ex...> - 2014-10-26 11:19:38
|
> 1) Remove it after 2.2 release? We need to give users some time to update their index definitions, so we have to keep the old index for a while. As we did for the legacy full-text index, I would suggest to disable the legacy range index in the default configuration after 2.2 has been released and then remove it entirely in 2.3. There’s also some work to do: 1) @xml:id are still using the legacy range index, 2) fn:matches is not supported due to regex limitations in lucence. Both issues need to be addressed before we disable the old index. I agree the legacy range index is polluting NativeBroker with lots of nasty code, which can be removed once we drop the index. Wolfgang |
|
From: Adam R. <ad...@ex...> - 2014-10-26 11:02:21
|
Hi there,
I am just wondering what the plan is for the NativeValueIndex (i.e.
legacy range index) in eXist. I am wondering if the plan is either:
1) Remove it after 2.2 release?
2) Migrate it to fit entirely into the newer indexing pipeline format,
cleaning up NativeBroker#endElement. And if so, what is the perceived
value in keeping the legacy range index?
3) Something else?
I notice that it does some quite nasty dirty reads against the dom.dbx
before the transaction that represents that data is actually committed
- see the calls to getNodeValue in NativeBroker#endElement. I would
like to eliminate that sort of behaviour.
Cheers Adam.
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Dannes W. <da...@ex...> - 2014-10-25 09:58:47
|
Hi Adam, > On 24 Oct 2014, at 23:16 , Adam Retter <ad...@ex...> wrote: > > Am I being stupid? Nobody from the community ever claimed this, i hope :-P > ...and if not, any objections to me removing the extraneous code? As you present it, it makes sense, but maybe @dmitriy or @wolf have a scenario where it might be relevant…. regards Dannes |
|
From: Adam R. <ad...@ex...> - 2014-10-24 21:16:41
|
So I have noticed that when creating a new Collection in eXist the
collection is being configured twice, which to me looks totally
unnecessary. I think we have a bug!
Looking at HEAD of the develop branch, the call chain looks like this -
1) NativeBroker#getOrCreateCollection, line 702:
collectionConfigurationManager.addConfiguration(transaction,
this, current, initCollectionConfig);
2) CollectionConfigurationManager#addConfiguration, line 130:
confCol.store(txn, broker, info, config, false);
3) Collection#storeXMLInternal, lines 1409 and 1410:
manager.invalidate(getURI(), broker.getBrokerPool());
manager.loadConfiguration(broker, this);
4) CollectionConfigurationManager#addConfiguration, lines 137 and 138:
configurations.remove(new CollectionURI(path.getRawCollectionPath()));
loadConfiguration(broker, confCol);
So you can see that the Configuration is invalidated and re-loaded
first in frame (3) and then again in frame (4). As far as I can see,
we only need to do this once. The code in frame (4) I *think* was
added more recently by Dmitriy but seems unnecessary as this is
already done by the more general function in (3).
I propose to remove the redundant code in (4). Have I missed anything
obvious? Am I being stupid? ...and if not, any objections to me
removing the extraneous code?
Thanks Adam.
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Loren C. <lor...@gm...> - 2014-10-14 16:23:23
|
Ok. Will do. On Oct 14, 2014, at 12:20 PM, Dannes Wessels <da...@ex...> wrote: > Hi, > > on https://github.com/lcahlander/doc2/releases you can draft a release (tag) and attach the binary; > > quite easy to use, makes things tracable and keeps things together.... > > On 14 Oct 2014, at 14:20 , Loren Cahlander <lor...@gm...> wrote: > >> Here is the git repository: https://github.com/lcahlander/doc2 >> Here is the xar: http://greatlinkup.com/foo/doc2-0.1.2.xar >> >> > |
|
From: Dannes W. <da...@ex...> - 2014-10-14 16:20:11
|
Hi, on https://github.com/lcahlander/doc2/releases you can draft a release (tag) and attach the binary; quite easy to use, makes things tracable and keeps things together.... On 14 Oct 2014, at 14:20 , Loren Cahlander <lor...@gm...> wrote: > Here is the git repository: https://github.com/lcahlander/doc2 > Here is the xar: http://greatlinkup.com/foo/doc2-0.1.2.xar > > |
|
From: Dannes W. <da...@ex...> - 2014-10-14 16:18:21
|
I tried to create the tag by 'drafting a new release' via the github releases page. I remember it did not go fluently I might have ruined then? The tag was created too late for sure, weeks after releasing RC2, this was the cause of my struggle. if it is bad...... i'd could not say :-/ is it repairable? cheers Dannes eXist-db Native XML Database http://www.exist-db.org On 14 Oct 2014, at 12:59 , Adam Retter <ad...@ex...> wrote: > I am not sure how the eXist-2.2.RC2 tag was created in our Git repo, > but it seems that however it was done was not correct. > > If I run `git describe` on `develop` then Git thinks that the last tag > that was cut is eXist-2.2.RC1. > > Can anyone comment on this? > > I think we should discuss fixing this as it leads to problems with Git > tools which try and work out the latest tag (release) of eXist. > > Thanks Adam. |
|
From: Loren C. <lor...@gm...> - 2014-10-14 12:20:30
|
Here is the git repository: https://github.com/lcahlander/doc2 Here is the xar: http://greatlinkup.com/foo/doc2-0.1.2.xar On Oct 14, 2014, at 4:10 AM, Jens Østergaard Petersen <oe...@gm...> wrote: > Hi Loren, > > Sounds interesting: could you add a link to the installer – or a link to a publicly available installation? > > Jens > > On 14 Oct 2014 at 01:44:50, Loren Cahlander (lor...@gm...) wrote: > >> Hello folks, >> >> I have been working on a updated doc app that fully utilizes the templating features of eXist. I would appreciate your feedback. >> >> Checkout: >> >> http://localhost:8080/exist/apps/doc2/getting-started.xml >> http://localhost:8080/exist/apps/doc2/templating.xml >> >> Thanks, >> Loren >> >> ------------------------------------------------------------------------------ >> Comprehensive Server Monitoring with Site24x7. >> Monitor 10 servers for $9/Month. >> Get alerted through email, SMS, voice calls or mobile push notifications. >> Take corrective actions from your mobile device. >> http://p.sf.net/sfu/Zoho_______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development |
64 messages has been excluded from this view by a project administrator.
