You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Fabian Christ <ch...@googlemail.com> on 2012/11/08 10:54:59 UTC
Contenthub release
Hi,
I started to check the Contenthub for releasability. The RAT check is fine
now and the resulting source package, too.
I had a look at the SNAPSHOT deps and found the ones below. Could the
authors of the Contenthub please check if these SNAPSHOT deps are correct
and required? I just wanted to make sure that there are only required
SNAPSHOTs used. Otherwise please change to stable releases if possible.
org.apache.stanbol:org.apache.stanbol.commons.jsonld:jar:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.commons.web.base:jar:0.10.1-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.bundlelist:partialbundlelist:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.ldpath:bundle:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.parent:pom:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.reactor:pom:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.search.featured:bundle:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.search.reactor:pom:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.search.related:bundle:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.search.solr:bundle:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.servicesapi:bundle:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.servicesapi:jar:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.store.clerezza:bundle:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.store.inmemory:bundle:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.store.reactor:pom:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.store.solr:bundle:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.contenthub.web:bundle:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.enhancer.core:jar:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.enhancer.servicesapi:jar:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.enhancer.test:jar:0.10.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.entityhub.core:jar:0.11.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.entityhub.ldpath:jar:0.11.0-SNAPSHOT
org.apache.stanbol:org.apache.stanbol.entityhub.servicesapi:jar:0.11.0-SNAPSHOT
--
Fabian
http://twitter.com/fctwitt
Re: contenthub access
Posted by Reto Bachmann-Gmür <re...@apache.org>.
Hi Melanie
The username/passsword are the same for all services. So it seems very
strange that the same tokens work in some places but not in other. Would be
ideal if you could open an issue with the network transcript for a failing
request.
Cheers,
Reto
On Sat, Jan 19, 2013 at 12:08 PM, Melanie Reiplinger <
melanie.reiplinger@dfki.de> wrote:
> Hi Reto and all,
>
> ok so I added authentication to my interface. I had a design in mind that
> would be most convenient to the user, namely that he sets his login data
> once and for all, the username and password are then set as global
> variables, and in each jQuery.ajax call that will be done, the
> authentication data is sent. I do this for all services, not only the
> contenthub, because the idea is that access will still work even if the
> Stanbol people should decide to require authentication on services other
> than the contenthub in the future.
>
> That seems to work in most cases, but there are a few exceptions where I
> get a
> 401 Unauthorized, and a
> WWW-Authenticate:Basic realm="Apache Stanbol authentication needed"
> in the response header. This error occurs only when I DO send
> authentication data; access works fine as long as I do NOT try to authorize
> my access.
>
> The cases where this happens are:
> GET on entityhub/sites/referenced/
> GET on entityhub/lookup/
> POST on ontonet/session/
> and when I try to GET all the registered session on the ontonet.
>
> (for the factstore and rules I don't know, since the first is not there
> presently and the latter does not allow for CORS access.)
>
> Do these services have a different username and password (meaning:
> different from the default admin-admin that works for the other services)?
>
> Best,
> Melanie
>
>
> Am 08.01.2013 20:13, schrieb Reto Bachmann-Gmür:
>
> Hi Melanie and all
>>
>> We should discus ehich permission should be needed for the contenthub. As
>> it allows adding data it shouldn't be allowed to anonymous users.
>>
>> On the demo server you mention there's currently only the admin user. I
>> think it would make sense to have a user to test which can access all
>> services but the system console and another user with priviledges to
>> access
>> the system console.
>>
>> Cheers,
>> Reto
>>
>> On Wed, Jan 2, 2013 at 12:10 PM, Melanie Reiplinger <
>> melanie.reiplinger@dfki.de> wrote:
>>
>> Hi Stanbol developers!
>>>
>>> (Happy new year, by the way :) )
>>>
>>> Suddenly, the contenthub on dev.iks-project.eu:8081/ asks me for a user
>>> name and password. Do you intend to have users of the demo server
>>> register
>>> in order to test it? Or is this because auf the in-progress release?
>>>
>>>
>>> Best,
>>> Melanie
>>>
>>>
>
Re: contenthub access
Posted by Melanie Reiplinger <me...@dfki.de>.
Hi Reto and all,
ok so I added authentication to my interface. I had a design in mind
that would be most convenient to the user, namely that he sets his login
data once and for all, the username and password are then set as global
variables, and in each jQuery.ajax call that will be done, the
authentication data is sent. I do this for all services, not only the
contenthub, because the idea is that access will still work even if the
Stanbol people should decide to require authentication on services other
than the contenthub in the future.
That seems to work in most cases, but there are a few exceptions where I
get a
401 Unauthorized, and a
WWW-Authenticate:Basic realm="Apache Stanbol authentication needed"
in the response header. This error occurs only when I DO send
authentication data; access works fine as long as I do NOT try to
authorize my access.
The cases where this happens are:
GET on entityhub/sites/referenced/
GET on entityhub/lookup/
POST on ontonet/session/
and when I try to GET all the registered session on the ontonet.
(for the factstore and rules I don't know, since the first is not there
presently and the latter does not allow for CORS access.)
Do these services have a different username and password (meaning:
different from the default admin-admin that works for the other services)?
Best,
Melanie
Am 08.01.2013 20:13, schrieb Reto Bachmann-Gmür:
> Hi Melanie and all
>
> We should discus ehich permission should be needed for the contenthub. As
> it allows adding data it shouldn't be allowed to anonymous users.
>
> On the demo server you mention there's currently only the admin user. I
> think it would make sense to have a user to test which can access all
> services but the system console and another user with priviledges to access
> the system console.
>
> Cheers,
> Reto
>
> On Wed, Jan 2, 2013 at 12:10 PM, Melanie Reiplinger <
> melanie.reiplinger@dfki.de> wrote:
>
>> Hi Stanbol developers!
>>
>> (Happy new year, by the way :) )
>>
>> Suddenly, the contenthub on dev.iks-project.eu:8081/ asks me for a user
>> name and password. Do you intend to have users of the demo server register
>> in order to test it? Or is this because auf the in-progress release?
>>
>>
>> Best,
>> Melanie
>>
Re: contenthub access
Posted by Reto Bachmann-Gmür <re...@apache.org>.
Hi Melanie and all
We should discus ehich permission should be needed for the contenthub. As
it allows adding data it shouldn't be allowed to anonymous users.
On the demo server you mention there's currently only the admin user. I
think it would make sense to have a user to test which can access all
services but the system console and another user with priviledges to access
the system console.
Cheers,
Reto
On Wed, Jan 2, 2013 at 12:10 PM, Melanie Reiplinger <
melanie.reiplinger@dfki.de> wrote:
> Hi Stanbol developers!
>
> (Happy new year, by the way :) )
>
> Suddenly, the contenthub on dev.iks-project.eu:8081/ asks me for a user
> name and password. Do you intend to have users of the demo server register
> in order to test it? Or is this because auf the in-progress release?
>
>
> Best,
> Melanie
>
contenthub access
Posted by Melanie Reiplinger <me...@dfki.de>.
Hi Stanbol developers!
(Happy new year, by the way :) )
Suddenly, the contenthub on dev.iks-project.eu:8081/ asks me for a user
name and password. Do you intend to have users of the demo server
register in order to test it? Or is this because auf the in-progress
release?
Best,
Melanie
Re: Contenthub release
Posted by Suat Gonul <su...@gmail.com>.
Hi Fabian,
My intention is also to go on like that.
Best,
Suat
On 11/8/2012 1:35 PM, Fabian Christ wrote:
> Hi Suat,
>
> thanks. I think it would be great to have a Contenthub release before the
> branch of the 2-layer architecture is merged to the trunk.
>
> Best,
> - Fabian
>
>
> 2012/11/8 Suat Gonul <su...@gmail.com>
>
>> Hi Fabian,
>>
>> Ok, I will go over the dependency versions. Currently, I have some local
>> changes and there are some other minor issues that I would like take
>> care before the release. Once those changes are done, we can go for a
>> release.
>>
>> Best,
>> Suat
>>
>> On 11/8/2012 11:54 AM, Fabian Christ wrote:
>>> Hi,
>>>
>>> I started to check the Contenthub for releasability. The RAT check is
>> fine
>>> now and the resulting source package, too.
>>>
>>> I had a look at the SNAPSHOT deps and found the ones below. Could the
>>> authors of the Contenthub please check if these SNAPSHOT deps are correct
>>> and required? I just wanted to make sure that there are only required
>>> SNAPSHOTs used. Otherwise please change to stable releases if possible.
>>>
>>> org.apache.stanbol:org.apache.stanbol.commons.jsonld:jar:0.10.0-SNAPSHOT
>>>
>> org.apache.stanbol:org.apache.stanbol.commons.web.base:jar:0.10.1-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.bundlelist:partialbundlelist:0.10.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.ldpath:bundle:0.10.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.parent:pom:0.10.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.reactor:pom:0.10.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.search.featured:bundle:0.10.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.search.reactor:pom:0.10.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.search.related:bundle:0.10.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.search.solr:bundle:0.10.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.servicesapi:bundle:0.10.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.servicesapi:jar:0.10.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.store.clerezza:bundle:0.10.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.store.inmemory:bundle:0.10.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.store.reactor:pom:0.10.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.store.solr:bundle:0.10.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.contenthub.web:bundle:0.10.0-SNAPSHOT
>>> org.apache.stanbol:org.apache.stanbol.enhancer.core:jar:0.10.0-SNAPSHOT
>>>
>> org.apache.stanbol:org.apache.stanbol.enhancer.servicesapi:jar:0.10.0-SNAPSHOT
>>> org.apache.stanbol:org.apache.stanbol.enhancer.test:jar:0.10.0-SNAPSHOT
>>> org.apache.stanbol:org.apache.stanbol.entityhub.core:jar:0.11.0-SNAPSHOT
>>>
>> org.apache.stanbol:org.apache.stanbol.entityhub.ldpath:jar:0.11.0-SNAPSHOT
>> org.apache.stanbol:org.apache.stanbol.entityhub.servicesapi:jar:0.11.0-SNAPSHOT
>>>
>>
>
Re: Contenthub release
Posted by Fabian Christ <ch...@googlemail.com>.
Hi Suat,
thanks. I think it would be great to have a Contenthub release before the
branch of the 2-layer architecture is merged to the trunk.
Best,
- Fabian
2012/11/8 Suat Gonul <su...@gmail.com>
> Hi Fabian,
>
> Ok, I will go over the dependency versions. Currently, I have some local
> changes and there are some other minor issues that I would like take
> care before the release. Once those changes are done, we can go for a
> release.
>
> Best,
> Suat
>
> On 11/8/2012 11:54 AM, Fabian Christ wrote:
> > Hi,
> >
> > I started to check the Contenthub for releasability. The RAT check is
> fine
> > now and the resulting source package, too.
> >
> > I had a look at the SNAPSHOT deps and found the ones below. Could the
> > authors of the Contenthub please check if these SNAPSHOT deps are correct
> > and required? I just wanted to make sure that there are only required
> > SNAPSHOTs used. Otherwise please change to stable releases if possible.
> >
> > org.apache.stanbol:org.apache.stanbol.commons.jsonld:jar:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.commons.web.base:jar:0.10.1-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.bundlelist:partialbundlelist:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.ldpath:bundle:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.parent:pom:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.reactor:pom:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.search.featured:bundle:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.search.reactor:pom:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.search.related:bundle:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.search.solr:bundle:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.servicesapi:bundle:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.servicesapi:jar:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.store.clerezza:bundle:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.store.inmemory:bundle:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.store.reactor:pom:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.store.solr:bundle:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.contenthub.web:bundle:0.10.0-SNAPSHOT
> > org.apache.stanbol:org.apache.stanbol.enhancer.core:jar:0.10.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.enhancer.servicesapi:jar:0.10.0-SNAPSHOT
> > org.apache.stanbol:org.apache.stanbol.enhancer.test:jar:0.10.0-SNAPSHOT
> > org.apache.stanbol:org.apache.stanbol.entityhub.core:jar:0.11.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.entityhub.ldpath:jar:0.11.0-SNAPSHOT
> >
> org.apache.stanbol:org.apache.stanbol.entityhub.servicesapi:jar:0.11.0-SNAPSHOT
> >
> >
>
>
--
Fabian
http://twitter.com/fctwitt
Re: Contenthub release
Posted by Suat Gonul <su...@gmail.com>.
Hi Fabian,
Ok, I will go over the dependency versions. Currently, I have some local
changes and there are some other minor issues that I would like take
care before the release. Once those changes are done, we can go for a
release.
Best,
Suat
On 11/8/2012 11:54 AM, Fabian Christ wrote:
> Hi,
>
> I started to check the Contenthub for releasability. The RAT check is fine
> now and the resulting source package, too.
>
> I had a look at the SNAPSHOT deps and found the ones below. Could the
> authors of the Contenthub please check if these SNAPSHOT deps are correct
> and required? I just wanted to make sure that there are only required
> SNAPSHOTs used. Otherwise please change to stable releases if possible.
>
> org.apache.stanbol:org.apache.stanbol.commons.jsonld:jar:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.commons.web.base:jar:0.10.1-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.bundlelist:partialbundlelist:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.ldpath:bundle:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.parent:pom:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.reactor:pom:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.search.featured:bundle:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.search.reactor:pom:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.search.related:bundle:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.search.solr:bundle:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.servicesapi:bundle:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.servicesapi:jar:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.store.clerezza:bundle:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.store.inmemory:bundle:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.store.reactor:pom:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.store.solr:bundle:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.contenthub.web:bundle:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.enhancer.core:jar:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.enhancer.servicesapi:jar:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.enhancer.test:jar:0.10.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.entityhub.core:jar:0.11.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.entityhub.ldpath:jar:0.11.0-SNAPSHOT
> org.apache.stanbol:org.apache.stanbol.entityhub.servicesapi:jar:0.11.0-SNAPSHOT
>
>