[
https://issues.apache.org/jira/browse/JCR-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12592754#action_12592754
]
Thomas Mueller commented on JCR-1551:
-
Thanks for the tip! Indeed the
Hi,
On Sun, Apr 27, 2008 at 2:10 PM, Tobias Bocanegra
[EMAIL PROTECTED] wrote:
The release was already pushed out to the central Maven repository and
pulling it back would be a bit troublesome. How about if we treated
this as a regression and fixed it ASAP (next week) in 1.4.4?
ok
Hi,
Jira and svn are both down at the moment, so let's do some planning. :-)
As discussed in relation to jackrabbit-core 1.4.3, the change in the
PersistenceManager interface introduced in JCR-1428 should be
postponed until 1.5 (see JCR-1556). I'm treating this issue as a
regression in 1.4.3 and
Hi,
But we're diverging from the shutdown() issue.
Yes. I propose create a new public interface
JackrabbitManagedRepository extends Repository {
void shutdown(JackrabbitSession session);
}
This would have the following advantages:
- Developers can write applications against an interface.
[
https://issues.apache.org/jira/browse/JCR-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sébastien Launay updated JCR-1435:
--
Attachment: jackrabbit-1.4.x-mysql-engine-2008-04-28.patch
Hi,
before I get into some conceptual thoughs, I think the main question
regarding shutdown() is:
Do people need to be able to call shutdown() remotely?
I consider the interface Repository as part of the JCR client API.
The actually started JCR-server is IMHO a different entity, which
Hi,
On Mon, Apr 28, 2008 at 1:25 PM, Thomas Müller [EMAIL PROTECTED] wrote:
- It is possible to write applications that work with Jackrabbit and
other implementations (for example Day CRX).
But how many applications really need to shutdown the repository in
the generic case? You need to do
Hi,
More details should be available soon, but right now
http://monitoring.apache.org/status/ indicates that https access to
the ASF's subversion repository is disabled.
Watch that page for updates, our beloved infra team is working on
resolving the issue.
-Bertrand
On Mon, Apr 28, 2008 at 1:34 PM, Bertrand Delacretaz
[EMAIL PROTECTED] wrote:
...our beloved infra team is working on
resolving the issue
Looks like new hardware needs to be brought up to avoid any risks, I
assume that will take a few hours.
http://monitoring.apache.org/status/ will
Hi,
What about the other points? I repeat them here and I hope I get an
answer on them as well:
- Developers can write applications against an interface.
- Developers can use Javadocs. Also, the autocomplete feature in the
IDE would list relevant methods.
- Access right checking can be
hi,
i really think we need a management API/Class that controls creation
and destruction of the repository. currently this is hidden in the
RepositoryImpl. so other infrastructure applications (other than
TransientRepository) can make use of that. after all, it's not the
job or the responsibility
Hi,
RepositoryManagement mgmgt = new JackrabbitRepositoryMgmt();
Repository mgmt.createRepository()
mgmt.shutdown(Repository rep)
This looks good as well, as long as RepositoryManagement is an
interface. There are some advantages compared to having shutdown on
the
[
https://issues.apache.org/jira/browse/JCR-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated JCR-1557:
---
Attachment: repository.xml
Attaching example configuration which uses same DB (but different
Avoid exceptions during shutting repository down if several PMs/FSs use same DB
---
Key: JCR-1557
URL: https://issues.apache.org/jira/browse/JCR-1557
Project: Jackrabbit
Hi,
On Mon, Apr 28, 2008 at 3:29 PM, Thomas Müller [EMAIL PROTECTED] wrote:
What about the other points? I repeat them here and I hope I get an
answer on them as well:
Your other points are good, no concerns about them.
But how many applications really need to shutdown the repository in
It says
/**
* rep:versionStorage
*/
public static final Name REP_NODETYPES = FACTORY.create(Name.NS_REP_URI,
nodeTypes);
when it should say rep:nodeTypes.
Regards,
Esteban Franqueiro
[EMAIL PROTECTED]
Notice: This email message, together with any attachments, may contain
information of BEA
Namespace not registered yet prevent BundleDbPersistenceManager to detect
already existing root node and leads to workspace initialization failure in a
cluster environment
Null Pointer Exception while looking for a DavProperty that hasn't been set
---
Key: JCR-1559
URL: https://issues.apache.org/jira/browse/JCR-1559
Project: Jackrabbit
18 matches
Mail list logo
