|
|
Re: [ECP][CDO] connect to cdo repository without branching support [message #1066417 is a reply to message #1066385] |
Tue, 02 July 2013 14:57 |
|
Am 02.07.2013 14:01, schrieb Erdal Karaca:
> Hi all
> I am getting the following exception when connecting to a remote CDO repository in the EMFClient:
>
> Caused by: java.lang.UnsupportedOperationException
> at
> org.eclipse.emf.cdo.server.internal.hibernate.HibernateStoreAccessor.loadSubBranches(HibernateStoreAccessor.java:439)
> at org.eclipse.emf.cdo.internal.server.Repository.loadSubBranches(Repository.java:412)
> at org.eclipse.emf.cdo.internal.common.branch.CDOBranchImpl.getBranches(CDOBranchImpl.java:175)
> at org.eclipse.emf.cdo.internal.common.branch.CDOBranchImpl.getBranches(CDOBranchImpl.java:189)
> at
> org.eclipse.emf.cdo.server.internal.net4j.protocol.LoadSubBranchesIndication.responding(LoadSubBranchesIndication.java:45)
> at org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServerIndication.responding(CDOServerIndication.java:134)
> at org.eclipse.net4j.signal.IndicationWithResponse.doExtendedOutput(IndicationWithResponse.java:98)
> at org.eclipse.net4j.signal.Signal.doOutput(Signal.java:298)
> at org.eclipse.net4j.signal.IndicationWithResponse.execute(IndicationWithResponse.java:67)
> at org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServerReadIndication.execute(CDOServerReadIndication.java:36)
>
>
> We are using the hibernate store which does not support branching. Is it possible to connect without branching?
This could be a pure UI issue but I'm not sure. If the CDO repo is configured without branching support the ECP UI
should not try to request sub branches of the MAIN branch. I could also imagine to relax the CDO server such that it
returns an empty collection instead of throwing an exception. I leave it to you where you report a bugzilla ;-)
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
|
|
Re: [ECP][CDO] connect to cdo repository without branching support [message #1066895 is a reply to message #1066481] |
Fri, 05 July 2013 05:45 |
|
Am 02.07.2013 21:51, schrieb Jonas Helming:
> Hi,
>
> do you mean, the CDO Repository node in the repository browser has no children? It is intended to select one of these
> and check them out as projects.
> The UI of the CDO provider currently does not allow to create projects in the model explorer, which are not connected
> to any repository.
I tried it out yesterday and I can confirm: There is no Checkout action anymore on the branches that are displayed
inside the CDO repo. I checked the sources (and the Git history) for quite some while but couldn't figure out how/when
something changed that caused this. I'm pretty sure that I didn't touch ECP or its CDO provider for more than a year, so
someone else must have caused this regression.
I checked that CDOBranchWrapper properly implements ECPCheckoutSource and that there's a command handler contributed in
the framework's plugin.xml. Where else should I look? How can I debug why that contribution does not lead to a visible
action in the popup menu?
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
> The other option you are refering to is provided by the file provider.
>
> Regards
>
> Jonas
>
>
> Am 02.07.2013 17:04, schrieb Erdal Karaca:
>> I did exactly that and got no more exceptions, but I still cannot
>> "browse" the repository: UI has no option to create a new CDO project (I
>> can only create a new empty project and select an existing xmi file).
>>
>> Eike Stepper wrote on Tue, 02 July 2013 16:57
>>> I could also imagine to relax the CDO server such that it returns an
>>> empty collection instead of throwing an exception.
>>
>>
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Re: [ECP][CDO] connect to cdo repository without branching support [message #1066948 is a reply to message #1066895] |
Fri, 05 July 2013 08:38 |
Jonas Helming Messages: 699 Registered: July 2009 |
Senior Member |
|
|
Hi,
I just checked, I have a check-out action either in latest develop state
and in 1.0.0. I did not check the functionality, though.
Can you describe where you tested this?
Regards
Jonas
Am 05.07.2013 07:45, schrieb Eike Stepper:
> Am 02.07.2013 21:51, schrieb Jonas Helming:
>> Hi,
>>
>> do you mean, the CDO Repository node in the repository browser has no
>> children? It is intended to select one of these and check them out as
>> projects.
>> The UI of the CDO provider currently does not allow to create projects
>> in the model explorer, which are not connected to any repository.
> I tried it out yesterday and I can confirm: There is no Checkout action
> anymore on the branches that are displayed inside the CDO repo. I
> checked the sources (and the Git history) for quite some while but
> couldn't figure out how/when something changed that caused this. I'm
> pretty sure that I didn't touch ECP or its CDO provider for more than a
> year, so someone else must have caused this regression.
>
> I checked that CDOBranchWrapper properly implements ECPCheckoutSource
> and that there's a command handler contributed in the framework's
> plugin.xml. Where else should I look? How can I debug why that
> contribution does not lead to a visible action in the popup menu?
>
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
>
>> The other option you are refering to is provided by the file provider.
>>
>> Regards
>>
>> Jonas
>>
>>
>> Am 02.07.2013 17:04, schrieb Erdal Karaca:
>>> I did exactly that and got no more exceptions, but I still cannot
>>> "browse" the repository: UI has no option to create a new CDO project (I
>>> can only create a new empty project and select an existing xmi file).
>>>
>>> Eike Stepper wrote on Tue, 02 July 2013 16:57
>>>> I could also imagine to relax the CDO server such that it returns an
>>>> empty collection instead of throwing an exception.
>>>
>>>
>>
>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04879 seconds