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: Dan M. <dan...@gm...> - 2012-10-19 14:02:35
|
There is also a version of format-number() in XSLT. As a short-term workaround we could write a wrapper for that function. - Dan On Fri, Oct 19, 2012 at 8:34 AM, Wolfgang Meier <wol...@ex...> wrote: > Hi guys, > > in preparation for the 2.0 release, I was just checking which functions are still missing from the XQuery 3.0 spec. I might miss some, but the list is rather short: > > Trigonometric and exponential functions > format-number > innermost/outermost > unparsed-text > environment-variable > parse-xml > parse-xml-fragment > > serialize > > With the exception of format-number, most of this is easy to implement or already provided through similar eXist-db extension functions. I'm thus astonished nobody wants to work on it. The goal should be to have ALL functions, even if they are just copies of already available eXist-db functions. > > Wolfgang > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development -- Dan McCreary NoSQL Evangelist office: (952) 931-9198 cell: (612) 986-1552 |
|
From: Wolfgang M. <wol...@ex...> - 2012-10-19 13:35:34
|
Hi guys, in preparation for the 2.0 release, I was just checking which functions are still missing from the XQuery 3.0 spec. I might miss some, but the list is rather short: Trigonometric and exponential functions format-number innermost/outermost unparsed-text environment-variable parse-xml parse-xml-fragment serialize With the exception of format-number, most of this is easy to implement or already provided through similar eXist-db extension functions. I'm thus astonished nobody wants to work on it. The goal should be to have ALL functions, even if they are just copies of already available eXist-db functions. Wolfgang |
|
From: Loren C. <lor...@gm...> - 2012-10-18 21:00:47
|
I have updated the xqDoc XML Schema from the xqdoc website to add an optional schema tag to parameter and return. I would appreciate feedback. Thanks, Loren |
|
From: Loren C. <lor...@gm...> - 2012-10-18 18:26:22
|
Hello Adam, Can you take a look at branches/lcahlander/xqDoc/schema/system.xsd? For the different attributes in the job element, I created two attributeGroups and included both in the job element. It would be nice if there could be an xs:choice for attributes. Loren On Oct 17, 2012, at 6:57 PM, Loren Cahlander <lor...@gm...> wrote: > I was not thrilled with redefining the structure, but I had to bring it up. I will explore the attributes in an XML Schema more. > > Sent from my iPhone > > On Oct 17, 2012, at 4:52 PM, Adam Retter <ad...@ex...> wrote: > >> Rather than refactoring the XML jobs bit, I think some of the output >> needs to be refactored. So we should define what a job is and that >> should be common between the two, but could contain additional >> optional/substituted children for a running job or scheduled job as >> appropriate. >> >> On 17 October 2012 21:19, Loren Cahlander <lor...@gm...> wrote: >>> I am currently working on the system module and have to create the schema >>> for it. I found a problem with the results from get-running-jobs and >>> get-scheduled-jobs. Both use the root of jobs and then have an element of >>> job for each job. The problem is that the running jobs uses the following >>> attributes: >>> >>> id >>> action >>> start >>> info >>> >>> >>> and the scheduled jobs uses the following attributes: >>> >>> name >>> group >>> triggerName >>> startTime >>> endTime >>> fireTime >>> nextFireTime >>> finalFireTime >>> triggerExpression >>> triggerState >>> running >>> >>> >>> This does not make for a nice XML Schema for the element job. I am thinking >>> that I change the element for scheduled jobs to scheduledJob for a better >>> schema. >>> >>> There is another thing for the addition of the XML Schemas into the xqDoc. >>> Can we indicate the root element from the XML Schema in our URI, or do we >>> need an additional tag of @root after @schema? >>> >>> The returned item from each of these calls has the same namespace, but >>> different structure. >>> >>> export >>> - collection >>> - resource >>> >>> jobs >>> - job >>> >>> xqueries >>> - xquery >>> >>> ... >>> >>> >>> >>> On Oct 16, 2012, at 4:06 PM, Loren Cahlander <lor...@gm...> >>> wrote: >>> >>> I will start a branch off of trunk and start the work then. Get the java >>> function modules with the optional XML Schemas in the signature. >>> >>> Once I get the mechanism in place, I am hoping that the community can aid in >>> making sure that we identify and have the up to date XML Schemas necessary >>> for the internal function modules. >>> >>> On Oct 16, 2012, at 3:56 PM, Wolfgang Meier <wol...@ex...> wrote: >>> >>> Hi Loren, >>> >>> I certainly like the idea. The XQuery parser just stores the raw XQDoc >>> comment to avoid loosing time during normal compilation. The comment is >>> later parsed upon request, so the additional schema field could be extracted >>> there and the schema file retrieved. >>> >>> Wolfgang >>> >>> >>> Am Dienstag, 16. Oktober 2012 um 22:49 schrieb Loren Cahlander: >>> >>> Hello Wolfgang, >>> >>> I know that my idea would need to go into a later release, but I would like >>> to have your feedback on the idea. I can go through the Java functions to >>> add the schema, but need an agreed upon concept for this. It would >>> eventually need to be added to the XQuery parser. >>> >>> Thanks, >>> Loren >>> >>> >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Everyone hates slow websites. So do we. >>> Make your web apps faster with AppDynamics >>> Download AppDynamics Lite for free today: >>> http://p.sf.net/sfu/appdyn_sfd2d_oct >>> _______________________________________________ >>> 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: Loren C. <lor...@gm...> - 2012-10-17 23:57:33
|
I was not thrilled with redefining the structure, but I had to bring it up. I will explore the attributes in an XML Schema more. Sent from my iPhone On Oct 17, 2012, at 4:52 PM, Adam Retter <ad...@ex...> wrote: > Rather than refactoring the XML jobs bit, I think some of the output > needs to be refactored. So we should define what a job is and that > should be common between the two, but could contain additional > optional/substituted children for a running job or scheduled job as > appropriate. > > On 17 October 2012 21:19, Loren Cahlander <lor...@gm...> wrote: >> I am currently working on the system module and have to create the schema >> for it. I found a problem with the results from get-running-jobs and >> get-scheduled-jobs. Both use the root of jobs and then have an element of >> job for each job. The problem is that the running jobs uses the following >> attributes: >> >> id >> action >> start >> info >> >> >> and the scheduled jobs uses the following attributes: >> >> name >> group >> triggerName >> startTime >> endTime >> fireTime >> nextFireTime >> finalFireTime >> triggerExpression >> triggerState >> running >> >> >> This does not make for a nice XML Schema for the element job. I am thinking >> that I change the element for scheduled jobs to scheduledJob for a better >> schema. >> >> There is another thing for the addition of the XML Schemas into the xqDoc. >> Can we indicate the root element from the XML Schema in our URI, or do we >> need an additional tag of @root after @schema? >> >> The returned item from each of these calls has the same namespace, but >> different structure. >> >> export >> - collection >> - resource >> >> jobs >> - job >> >> xqueries >> - xquery >> >> ... >> >> >> >> On Oct 16, 2012, at 4:06 PM, Loren Cahlander <lor...@gm...> >> wrote: >> >> I will start a branch off of trunk and start the work then. Get the java >> function modules with the optional XML Schemas in the signature. >> >> Once I get the mechanism in place, I am hoping that the community can aid in >> making sure that we identify and have the up to date XML Schemas necessary >> for the internal function modules. >> >> On Oct 16, 2012, at 3:56 PM, Wolfgang Meier <wol...@ex...> wrote: >> >> Hi Loren, >> >> I certainly like the idea. The XQuery parser just stores the raw XQDoc >> comment to avoid loosing time during normal compilation. The comment is >> later parsed upon request, so the additional schema field could be extracted >> there and the schema file retrieved. >> >> Wolfgang >> >> >> Am Dienstag, 16. Oktober 2012 um 22:49 schrieb Loren Cahlander: >> >> Hello Wolfgang, >> >> I know that my idea would need to go into a later release, but I would like >> to have your feedback on the idea. I can go through the Java functions to >> add the schema, but need an agreed upon concept for this. It would >> eventually need to be added to the XQuery parser. >> >> Thanks, >> Loren >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_sfd2d_oct >> _______________________________________________ >> 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: Adam R. <ad...@ex...> - 2012-10-17 21:54:10
|
Also... should we actually be changing this XML output? I ask, because if people are processing it with their apps in XQuery/XSLT then we will break their existing apps. It might be better just to create a lax schema that validates the current output? On 17 October 2012 22:52, Adam Retter <ad...@ex...> wrote: > Rather than refactoring the XML jobs bit, I think some of the output > needs to be refactored. So we should define what a job is and that > should be common between the two, but could contain additional > optional/substituted children for a running job or scheduled job as > appropriate. > > On 17 October 2012 21:19, Loren Cahlander <lor...@gm...> wrote: >> I am currently working on the system module and have to create the schema >> for it. I found a problem with the results from get-running-jobs and >> get-scheduled-jobs. Both use the root of jobs and then have an element of >> job for each job. The problem is that the running jobs uses the following >> attributes: >> >> id >> action >> start >> info >> >> >> and the scheduled jobs uses the following attributes: >> >> name >> group >> triggerName >> startTime >> endTime >> fireTime >> nextFireTime >> finalFireTime >> triggerExpression >> triggerState >> running >> >> >> This does not make for a nice XML Schema for the element job. I am thinking >> that I change the element for scheduled jobs to scheduledJob for a better >> schema. >> >> There is another thing for the addition of the XML Schemas into the xqDoc. >> Can we indicate the root element from the XML Schema in our URI, or do we >> need an additional tag of @root after @schema? >> >> The returned item from each of these calls has the same namespace, but >> different structure. >> >> export >> - collection >> - resource >> >> jobs >> - job >> >> xqueries >> - xquery >> >> ... >> >> >> >> On Oct 16, 2012, at 4:06 PM, Loren Cahlander <lor...@gm...> >> wrote: >> >> I will start a branch off of trunk and start the work then. Get the java >> function modules with the optional XML Schemas in the signature. >> >> Once I get the mechanism in place, I am hoping that the community can aid in >> making sure that we identify and have the up to date XML Schemas necessary >> for the internal function modules. >> >> On Oct 16, 2012, at 3:56 PM, Wolfgang Meier <wol...@ex...> wrote: >> >> Hi Loren, >> >> I certainly like the idea. The XQuery parser just stores the raw XQDoc >> comment to avoid loosing time during normal compilation. The comment is >> later parsed upon request, so the additional schema field could be extracted >> there and the schema file retrieved. >> >> Wolfgang >> >> >> Am Dienstag, 16. Oktober 2012 um 22:49 schrieb Loren Cahlander: >> >> Hello Wolfgang, >> >> I know that my idea would need to go into a later release, but I would like >> to have your feedback on the idea. I can go through the Java functions to >> add the schema, but need an agreed upon concept for this. It would >> eventually need to be added to the XQuery parser. >> >> Thanks, >> Loren >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_sfd2d_oct >> _______________________________________________ >> 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 -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
|
From: Adam R. <ad...@ex...> - 2012-10-17 21:52:59
|
Rather than refactoring the XML jobs bit, I think some of the output needs to be refactored. So we should define what a job is and that should be common between the two, but could contain additional optional/substituted children for a running job or scheduled job as appropriate. On 17 October 2012 21:19, Loren Cahlander <lor...@gm...> wrote: > I am currently working on the system module and have to create the schema > for it. I found a problem with the results from get-running-jobs and > get-scheduled-jobs. Both use the root of jobs and then have an element of > job for each job. The problem is that the running jobs uses the following > attributes: > > id > action > start > info > > > and the scheduled jobs uses the following attributes: > > name > group > triggerName > startTime > endTime > fireTime > nextFireTime > finalFireTime > triggerExpression > triggerState > running > > > This does not make for a nice XML Schema for the element job. I am thinking > that I change the element for scheduled jobs to scheduledJob for a better > schema. > > There is another thing for the addition of the XML Schemas into the xqDoc. > Can we indicate the root element from the XML Schema in our URI, or do we > need an additional tag of @root after @schema? > > The returned item from each of these calls has the same namespace, but > different structure. > > export > - collection > - resource > > jobs > - job > > xqueries > - xquery > > ... > > > > On Oct 16, 2012, at 4:06 PM, Loren Cahlander <lor...@gm...> > wrote: > > I will start a branch off of trunk and start the work then. Get the java > function modules with the optional XML Schemas in the signature. > > Once I get the mechanism in place, I am hoping that the community can aid in > making sure that we identify and have the up to date XML Schemas necessary > for the internal function modules. > > On Oct 16, 2012, at 3:56 PM, Wolfgang Meier <wol...@ex...> wrote: > > Hi Loren, > > I certainly like the idea. The XQuery parser just stores the raw XQDoc > comment to avoid loosing time during normal compilation. The comment is > later parsed upon request, so the additional schema field could be extracted > there and the schema file retrieved. > > Wolfgang > > > Am Dienstag, 16. Oktober 2012 um 22:49 schrieb Loren Cahlander: > > Hello Wolfgang, > > I know that my idea would need to go into a later release, but I would like > to have your feedback on the idea. I can go through the Java functions to > add the schema, but need an agreed upon concept for this. It would > eventually need to be added to the XQuery parser. > > Thanks, > Loren > > > > > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > 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: Loren C. <lor...@gm...> - 2012-10-17 20:20:05
|
I am currently working on the system module and have to create the schema for it. I found a problem with the results from get-running-jobs and get-scheduled-jobs. Both use the root of jobs and then have an element of job for each job. The problem is that the running jobs uses the following attributes: id action start info and the scheduled jobs uses the following attributes: name group triggerName startTime endTime fireTime nextFireTime finalFireTime triggerExpression triggerState running This does not make for a nice XML Schema for the element job. I am thinking that I change the element for scheduled jobs to scheduledJob for a better schema. There is another thing for the addition of the XML Schemas into the xqDoc. Can we indicate the root element from the XML Schema in our URI, or do we need an additional tag of @root after @schema? The returned item from each of these calls has the same namespace, but different structure. export - collection - resource jobs - job xqueries - xquery ... On Oct 16, 2012, at 4:06 PM, Loren Cahlander <lor...@gm...> wrote: > I will start a branch off of trunk and start the work then. Get the java function modules with the optional XML Schemas in the signature. > > Once I get the mechanism in place, I am hoping that the community can aid in making sure that we identify and have the up to date XML Schemas necessary for the internal function modules. > > On Oct 16, 2012, at 3:56 PM, Wolfgang Meier <wol...@ex...> wrote: > >> Hi Loren, >> >> I certainly like the idea. The XQuery parser just stores the raw XQDoc comment to avoid loosing time during normal compilation. The comment is later parsed upon request, so the additional schema field could be extracted there and the schema file retrieved. >> >> Wolfgang >> >> >> Am Dienstag, 16. Oktober 2012 um 22:49 schrieb Loren Cahlander: >> >>> Hello Wolfgang, >>> >>> I know that my idea would need to go into a later release, but I would like to have your feedback on the idea. I can go through the Java functions to add the schema, but need an agreed upon concept for this. It would eventually need to be added to the XQuery parser. >>> >>> Thanks, >>> Loren >> >> >> > |
|
From: Loren C. <lor...@gm...> - 2012-10-16 21:06:38
|
I will start a branch off of trunk and start the work then. Get the java function modules with the optional XML Schemas in the signature. Once I get the mechanism in place, I am hoping that the community can aid in making sure that we identify and have the up to date XML Schemas necessary for the internal function modules. On Oct 16, 2012, at 3:56 PM, Wolfgang Meier <wol...@ex...> wrote: > Hi Loren, > > I certainly like the idea. The XQuery parser just stores the raw XQDoc comment to avoid loosing time during normal compilation. The comment is later parsed upon request, so the additional schema field could be extracted there and the schema file retrieved. > > Wolfgang > > > Am Dienstag, 16. Oktober 2012 um 22:49 schrieb Loren Cahlander: > >> Hello Wolfgang, >> >> I know that my idea would need to go into a later release, but I would like to have your feedback on the idea. I can go through the Java functions to add the schema, but need an agreed upon concept for this. It would eventually need to be added to the XQuery parser. >> >> Thanks, >> Loren > > > |
|
From: Leif-Jöran O. <lj...@ex...> - 2012-10-16 10:01:48
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jens, to start with the quick fix. If you give property *use.autodeploy.feature*=false or give property *public-repo* any other value than "http://demo.exist-db.org/exist/apps/public-repo/public/" then you can build without external interference. On my agenda is though to make the public repos distributed so that we have failover to cover these kinds of short outages. Leif-Jöran Den 2012-10-15 16:12, Jens Østergaard Petersen skrev: > Hi, > > Since building eXist now involves downloading .xar's for the main apps, a standard build fails when the server is down (as it was for some time this afternoon). > > Is it possible to have alternate download sites in the build script? > > Jens > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iD8DBQFQfTB8hcIn5aVXOPIRAjYOAJ4tCZ+qsiTyAb0gsMedJvrM1K61KACglzDD oK380u7xkSIZycIKN5xlyZg= =XAoG -----END PGP SIGNATURE----- |
|
From: Jens Ø. P. <oe...@gm...> - 2012-10-15 14:12:15
|
Hi, Since building eXist now involves downloading .xar's for the main apps, a standard build fails when the server is down (as it was for some time this afternoon). Is it possible to have alternate download sites in the build script? Jens |
|
From: Вячеслав С. <sch...@gm...> - 2012-10-12 14:23:27
|
what about jabber extensions too? :) 2012/10/12 Evgeny Gazdovsky <gaz...@gm...>: > Yes, this is correct, I'l make an example > > 2012/10/11 Joe Wicentowski <jo...@gm...>: >> Hi Evgeny, >> >> I need your help to add information about your Netedit extension to >> the eXist-db 2.0 documentation. I remember that you created Netedit >> to make editing eXist documents user-friendly. The only way users can >> benefit from the user-friendly features of Netedit is if they can read >> a description in the eXist documentation. So if you can help me, I >> think this will really help users. >> >> I tried creating a description from the information in your source >> code and the mailing list records (remember when it was called >> "Gate"?). Here is what I have so far: > the "gate" was first name >> >> "Netedit is an eXist-db extension that enables users to edit documents >> stored in eXist-db using their desktop applications. Once Netedit is >> enabled in your build of eXist-db, users can download and start the >> Netedit java applet (http://localhost:8080/exist/netedit). From the >> applet, users can select and download any document (XML or binary) in >> the eXist-db database. Once a file is downloaded, the Netedit applet >> will watch the local hard disk for any changes to the file, such as >> when the user saves a change to the document. When Netedit detects a >> change in the file, it uploads the new version of the file to >> eXist-db. Thus, Netedit serves as a transparent bridge between >> eXist-db and the user's applications. It gives users the ability to >> uses eXist-db as remote storage, while simplifying the task of >> finding, editing, and saving XML documents or binary files on the >> desktop. To enable Netedit, change include.feature.netedit from false >> to true in extensions/local.build.properties, then rebuild eXist-db, >> then start eXist-db, then start the Netedit java applet via >> http://localhost:8080/exist/netedit." >> >> I *know* this is not all correct, so I need you to help me make it >> correct. Please! >> >> Thank you very much! >> >> Joe > > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development |
|
From: Evgeny G. <gaz...@gm...> - 2012-10-12 14:11:26
|
Yes, this is correct, I'l make an example 2012/10/11 Joe Wicentowski <jo...@gm...>: > Hi Evgeny, > > I need your help to add information about your Netedit extension to > the eXist-db 2.0 documentation. I remember that you created Netedit > to make editing eXist documents user-friendly. The only way users can > benefit from the user-friendly features of Netedit is if they can read > a description in the eXist documentation. So if you can help me, I > think this will really help users. > > I tried creating a description from the information in your source > code and the mailing list records (remember when it was called > "Gate"?). Here is what I have so far: the "gate" was first name > > "Netedit is an eXist-db extension that enables users to edit documents > stored in eXist-db using their desktop applications. Once Netedit is > enabled in your build of eXist-db, users can download and start the > Netedit java applet (http://localhost:8080/exist/netedit). From the > applet, users can select and download any document (XML or binary) in > the eXist-db database. Once a file is downloaded, the Netedit applet > will watch the local hard disk for any changes to the file, such as > when the user saves a change to the document. When Netedit detects a > change in the file, it uploads the new version of the file to > eXist-db. Thus, Netedit serves as a transparent bridge between > eXist-db and the user's applications. It gives users the ability to > uses eXist-db as remote storage, while simplifying the task of > finding, editing, and saving XML documents or binary files on the > desktop. To enable Netedit, change include.feature.netedit from false > to true in extensions/local.build.properties, then rebuild eXist-db, > then start eXist-db, then start the Netedit java applet via > http://localhost:8080/exist/netedit." > > I *know* this is not all correct, so I need you to help me make it > correct. Please! > > Thank you very much! > > Joe |
|
From: Loren C. <lor...@gm...> - 2012-10-11 18:01:58
|
I think that we also need the OAuth client for LinkedIn On Oct 11, 2012, at 12:31 PM, Dmitriy Shabanov <sha...@gm...> wrote: > On Thu, Oct 11, 2012 at 10:29 PM, Joe Wicentowski <jo...@gm...> wrote: > Thanks, Dmitriy! I'll work on that and may have some questions. > > I will also contact you offlist about the possibility of adding > twitter - which just disabled unauthenticated requests (and atom) - > now the only way to get one's timeline is via OAuth-authenticated > requests and JSON responses. Ugh. > > I see some demand for OAuth client, like twitter or gdocs needs. > > > I'm suprised that we have to add support on the java level for each > OAuth API provider - I guess they're not as standardized as they > should be. > > Yes, they are not -( > > -- > Dmitriy Shabanov > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev_______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development |
|
From: Dmitriy S. <sha...@gm...> - 2012-10-11 17:31:39
|
On Thu, Oct 11, 2012 at 10:29 PM, Joe Wicentowski <jo...@gm...> wrote: > Thanks, Dmitriy! I'll work on that and may have some questions. > > I will also contact you offlist about the possibility of adding > twitter - which just disabled unauthenticated requests (and atom) - > now the only way to get one's timeline is via OAuth-authenticated > requests and JSON responses. Ugh. > I see some demand for OAuth client, like twitter or gdocs needs. > > I'm suprised that we have to add support on the java level for each > OAuth API provider - I guess they're not as standardized as they > should be. > Yes, they are not -( -- Dmitriy Shabanov |
|
From: Joe W. <jo...@gm...> - 2012-10-11 17:29:33
|
Thanks, Dmitriy! I'll work on that and may have some questions. I will also contact you offlist about the possibility of adding twitter - which just disabled unauthenticated requests (and atom) - now the only way to get one's timeline is via OAuth-authenticated requests and JSON responses. Ugh. I'm suprised that we have to add support on the java level for each OAuth API provider - I guess they're not as standardized as they should be. Joe On Thu, Oct 11, 2012 at 1:23 PM, Dmitriy Shabanov <sha...@gm...> wrote: > Hello, > > Just was thinking that OAuth need article too -) > > yes, with small change. Current config file should looks like > > <realm id="OAuth" version="1.0"> > <service name="nnn" key="kkk" secret="sss" provider="facebook"/> > </realm> > > supported only facebook & google. > > > On Thu, Oct 11, 2012 at 10:02 PM, Joe Wicentowski <jo...@gm...> wrote: >> >> Hi Dmitriy, >> >> Are your directions about using OAuth at >> http://markmail.org/message/y4ptzpweonprix4b from last October still >> current? >> >> If so, I can adapt these into the section on the "OAuth Realm" in the >> security article in the documentation. > > > > -- > Dmitriy Shabanov |
|
From: Dmitriy S. <sha...@gm...> - 2012-10-11 17:23:22
|
Hello,
Just was thinking that OAuth need article too -)
yes, with small change. Current config file should looks like
<realm id="OAuth" version="1.0">
<service name="nnn" key="kkk" secret="sss" provider="facebook"/>
</realm>
supported only facebook & google.
On Thu, Oct 11, 2012 at 10:02 PM, Joe Wicentowski <jo...@gm...> wrote:
> Hi Dmitriy,
>
> Are your directions about using OAuth at
> http://markmail.org/message/y4ptzpweonprix4b from last October still
> current?
>
> If so, I can adapt these into the section on the "OAuth Realm" in the
> security article in the documentation.
>
--
Dmitriy Shabanov
|
|
From: Joe W. <jo...@gm...> - 2012-10-11 17:02:54
|
Hi Dmitriy, Are your directions about using OAuth at http://markmail.org/message/y4ptzpweonprix4b from last October still current? If so, I can adapt these into the section on the "OAuth Realm" in the security article in the documentation. Thanks! Joe |
|
From: Joe W. <jo...@gm...> - 2012-10-11 16:13:45
|
On Thu, Oct 11, 2012 at 8:01 AM, Jens Østergaard Petersen <oe...@gm...> wrote: > the quickstart assumes that you have to install it yourself On Thu, Oct 11, 2012 at 11:48 AM, Wolfgang Meier <wol...@ex...> wrote: > Most new users will download the installer, which has a panel to select the apps to install (dashboard, documentation, function docs, demo, eXide are available). Jens is right - I've left these aspects of the quickstart document incomplete, on purpose in fact, because the installation & setup aspects of eXist 2.0 have been in rapid development lately. Could I request that once the installation & setup aspects of 2.0 are considered complete and stable, the devs can release a new "2.0 preview" installer for the purposes of ensuring the documentation accurately reflects installation and set up procedures? Joe |
|
From: Jens Ø. P. <oe...@gm...> - 2012-10-11 16:10:04
|
OK, that seems a good way to handle this - didn't know that this was the way you followed. Jens On Oct 11, 2012, at 5:48 PM, Wolfgang Meier <wol...@ex...> wrote: > Hi Jens, Adam, > > Most new users will download the installer, which has a panel to select the apps to install (dashboard, documentation, function docs, demo, eXide are available). On a server you can choose not to install any apps at all, so this should not be a problem. > > If you check out from SVN, you probably know how to proceed anyway, so installing the documentation by default may not be required. > > Wolfgang > > > Am Donnerstag, 11. Oktober 2012 um 16:49 schrieb Jens Østergaard Petersen: > >> Hi Adam, >> >> Well, I guess I am looking at this from the perspective of the prospective user. For this kind of user, the Dashboard, eXide, _and_ the documentation should be there from the start, to make it possible to dive in right away. Those deploying servers will surely know how to optimise their system in this way as well, so we needn't think too much about them. It is all just a click away, we know this, but for the first-time user, who is told that a feature-complete system is being installed, not to be able to look around in the documentation without jumping the hoops of installing an app (an app to view documentation - what weird thing is this?!?). Of course, the user can read all about installing this and that and how easy it is - in the documentation! >> >> Jens >> >> >> On Oct 11, 2012, at 3:46 PM, Adam Retter <ad...@ex... (mailto:ad...@ex...)> wrote: >> >>> I think there are different scenarios here: >>> >>> 1) For a server deployment, you really dont want anything installed, >>> not even the dashboard. >>> >>> 2) For a development machine deployment, you probably want everything installed. >>> >>> IMHO - I think the compromise is just to have the dashboard installed >>> by default. From the Dashboard, you should be able to install other >>> things with 1 click, and also (for server deployments) uninstall the >>> Dashboard. >>> >>> Thoughts? >>> >>> >>> On 11 October 2012 13:01, Jens Østergaard Petersen <oe...@gm... (mailto:oe...@gm...)> wrote: >>>> Hi, >>>> >>>> Has a decision been made about which apps are installed as default? Dashboard and eXide, but I am thinking about the documentation - the quickstart assumes that you have to install it yourself. I think it would be best to have it pre-installed. >>>> >>>> Jens >>>> ------------------------------------------------------------------------------ >>>> Don't let slow site performance ruin your business. Deploy New Relic APM >>>> Deploy New Relic app performance management and know exactly >>>> what is happening inside your Ruby, Python, PHP, Java, and .NET app >>>> Try New Relic at no cost today and get our sweet Data Nerd shirt too! >>>> http://p.sf.net/sfu/newrelic-dev2dev >>>> _______________________________________________ >>>> Exist-development mailing list >>>> Exi...@li... (mailto:Exi...@li...) >>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>> >>> >>> >>> >>> >>> -- >>> Adam Retter >>> >>> eXist Developer >>> { United Kingdom } >>> ad...@ex... (mailto:ad...@ex...) >>> irc://irc.freenode.net/existdb (http://irc.freenode.net/existdb) >> >> >> >> >> ------------------------------------------------------------------------------ >> Don't let slow site performance ruin your business. Deploy New Relic APM >> Deploy New Relic app performance management and know exactly >> what is happening inside your Ruby, Python, PHP, Java, and .NET app >> Try New Relic at no cost today and get our sweet Data Nerd shirt too! >> http://p.sf.net/sfu/newrelic-dev2dev >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... (mailto:Exi...@li...) >> https://lists.sourceforge.net/lists/listinfo/exist-development > > > |
|
From: Leif-Jöran O. <lj...@ex...> - 2012-10-11 15:59:29
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Den 2012-10-11 17:48, Wolfgang Meier skrev: > Hi Jens, Adam, > > Most new users will download the installer, which has a panel to select the apps to install (dashboard, documentation, function docs, demo, eXide are available). On a server you can choose not to install any apps at all, so this should not be a problem. > > If you check out from SVN, you probably know how to proceed anyway, so installing the documentation by default may not be required. Just make sure to put use.autodeploy.feature=false in $EXIST_HOME/local.build.properties so that you dont install them (the default ones) by accident on rebuild. Leif-Jöran -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iD8DBQFQduzShcIn5aVXOPIRAigJAJ9awTMJ+ah3f6mqwqyceTXkTVeTIQCgtBA1 v2YjyWsCCe5vg8+t14D1mG0= =asbP -----END PGP SIGNATURE----- |
|
From: Wolfgang M. <wol...@ex...> - 2012-10-11 15:48:58
|
Hi Jens, Adam, Most new users will download the installer, which has a panel to select the apps to install (dashboard, documentation, function docs, demo, eXide are available). On a server you can choose not to install any apps at all, so this should not be a problem. If you check out from SVN, you probably know how to proceed anyway, so installing the documentation by default may not be required. Wolfgang Am Donnerstag, 11. Oktober 2012 um 16:49 schrieb Jens Østergaard Petersen: > Hi Adam, > > Well, I guess I am looking at this from the perspective of the prospective user. For this kind of user, the Dashboard, eXide, _and_ the documentation should be there from the start, to make it possible to dive in right away. Those deploying servers will surely know how to optimise their system in this way as well, so we needn't think too much about them. It is all just a click away, we know this, but for the first-time user, who is told that a feature-complete system is being installed, not to be able to look around in the documentation without jumping the hoops of installing an app (an app to view documentation - what weird thing is this?!?). Of course, the user can read all about installing this and that and how easy it is - in the documentation! > > Jens > > > On Oct 11, 2012, at 3:46 PM, Adam Retter <ad...@ex... (mailto:ad...@ex...)> wrote: > > > I think there are different scenarios here: > > > > 1) For a server deployment, you really dont want anything installed, > > not even the dashboard. > > > > 2) For a development machine deployment, you probably want everything installed. > > > > IMHO - I think the compromise is just to have the dashboard installed > > by default. From the Dashboard, you should be able to install other > > things with 1 click, and also (for server deployments) uninstall the > > Dashboard. > > > > Thoughts? > > > > > > On 11 October 2012 13:01, Jens Østergaard Petersen <oe...@gm... (mailto:oe...@gm...)> wrote: > > > Hi, > > > > > > Has a decision been made about which apps are installed as default? Dashboard and eXide, but I am thinking about the documentation - the quickstart assumes that you have to install it yourself. I think it would be best to have it pre-installed. > > > > > > Jens > > > ------------------------------------------------------------------------------ > > > Don't let slow site performance ruin your business. Deploy New Relic APM > > > Deploy New Relic app performance management and know exactly > > > what is happening inside your Ruby, Python, PHP, Java, and .NET app > > > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > > > http://p.sf.net/sfu/newrelic-dev2dev > > > _______________________________________________ > > > Exist-development mailing list > > > Exi...@li... (mailto:Exi...@li...) > > > https://lists.sourceforge.net/lists/listinfo/exist-development > > > > > > > > > > > > -- > > Adam Retter > > > > eXist Developer > > { United Kingdom } > > ad...@ex... (mailto:ad...@ex...) > > irc://irc.freenode.net/existdb (http://irc.freenode.net/existdb) > > > > > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > _______________________________________________ > Exist-development mailing list > Exi...@li... (mailto:Exi...@li...) > https://lists.sourceforge.net/lists/listinfo/exist-development |
|
From: Jens Ø. P. <oe...@gm...> - 2012-10-11 14:49:48
|
Hi Adam, Well, I guess I am looking at this from the perspective of the prospective user. For this kind of user, the Dashboard, eXide, _and_ the documentation should be there from the start, to make it possible to dive in right away. Those deploying servers will surely know how to optimise their system in this way as well, so we needn't think too much about them. It is all just a click away, we know this, but for the first-time user, who is told that a feature-complete system is being installed, not to be able to look around in the documentation without jumping the hoops of installing an app (an app to view documentation - what weird thing is this?!?). Of course, the user can read all about installing this and that and how easy it is - in the documentation! Jens On Oct 11, 2012, at 3:46 PM, Adam Retter <ad...@ex...> wrote: > I think there are different scenarios here: > > 1) For a server deployment, you really dont want anything installed, > not even the dashboard. > > 2) For a development machine deployment, you probably want everything installed. > > IMHO - I think the compromise is just to have the dashboard installed > by default. From the Dashboard, you should be able to install other > things with 1 click, and also (for server deployments) uninstall the > Dashboard. > > Thoughts? > > > On 11 October 2012 13:01, Jens Østergaard Petersen <oe...@gm...> wrote: >> Hi, >> >> Has a decision been made about which apps are installed as default? Dashboard and eXide, but I am thinking about the documentation - the quickstart assumes that you have to install it yourself. I think it would be best to have it pre-installed. >> >> Jens >> ------------------------------------------------------------------------------ >> Don't let slow site performance ruin your business. Deploy New Relic APM >> Deploy New Relic app performance management and know exactly >> what is happening inside your Ruby, Python, PHP, Java, and .NET app >> Try New Relic at no cost today and get our sweet Data Nerd shirt too! >> http://p.sf.net/sfu/newrelic-dev2dev >> _______________________________________________ >> 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: Adam R. <ad...@ex...> - 2012-10-11 13:47:07
|
I think there are different scenarios here: 1) For a server deployment, you really dont want anything installed, not even the dashboard. 2) For a development machine deployment, you probably want everything installed. IMHO - I think the compromise is just to have the dashboard installed by default. From the Dashboard, you should be able to install other things with 1 click, and also (for server deployments) uninstall the Dashboard. Thoughts? On 11 October 2012 13:01, Jens Østergaard Petersen <oe...@gm...> wrote: > Hi, > > Has a decision been made about which apps are installed as default? Dashboard and eXide, but I am thinking about the documentation - the quickstart assumes that you have to install it yourself. I think it would be best to have it pre-installed. > > Jens > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > _______________________________________________ > 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: Jens Ø. P. <oe...@gm...> - 2012-10-11 12:01:48
|
Hi, Has a decision been made about which apps are installed as default? Dashboard and eXide, but I am thinking about the documentation - the quickstart assumes that you have to install it yourself. I think it would be best to have it pre-installed. Jens |
64 messages has been excluded from this view by a project administrator.
