You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Suat Gonul <su...@gmail.com> on 2011/12/09 12:57:54 UTC
Re: full-war launcher
Hi Alex,
I have made some improvements regarding the war launcher. First, when
the war file is deployed on Tomcat, it starts automatically. Also,
static resources e.g css, images are displayed correctly. As far as I
tried, HTTP service for SOLR cores is also working. For example, I
executed a query like {stanbolhost}/solr/default/dbpedia/select?q=Paris
and was able to obtain results.
BTW, I used Tomcat 7.0.23 to test the changes.
Best,
Suat
On 11/25/2011 05:43 PM, Alex Lopez wrote:
> Thanks Suat for clarifications, :) no problem I'll go on with the jar
> launcher and switch to war into my Tomcat later.
>
>> Hi Alex,
>>
>> First of all, I am still working on this launcher and it's not fully
>> tested yet. I just gave a break as I had to focus on other issues.
>> Please see my other comments inline.
>>
>> On 11/25/2011 05:00 PM, Alex Lopez wrote:
>>> Hi,
>>>
>>> I've been trying to run Stanbol using the full-war launcher (into a
>>> Tomcat 7.0.21, using the /stanbol context).
>>>
>>> The app deployed fine, but after it showed several problems:
>>>
>>> - The first visit to host/stanbol to check if everything was OK
>>> yielded an error (404 if I remember right). Then tomcat log start to
>>> show some "initiating Jersey app" messages, then after some seconds a
>>> subsequent visit to host/stanbol works. So it behaves like it needed a
>>> first request to wake up.
>>
>> Yes, this case was same for me.
>>
>>> - No CSS or images displayed (no /stanbol context added to path of
>>> static resources).
>>
>> This is related about deployment location of static resources. I was
>> working on this but I didn't complete yet. I will inform you when I
>> commit the change that fixes this issue.
>>
>>> - SOLR search not working at host/stanbol/solr anymore (I've had
>>> problems before with SOLR + Tomcat7, could it be this?)
>>>
>>
>> I didn't check the new updates on SOLR yet, so I don't have a clear idea
>> on this. As I said, I didn't finish the work on full-war launcher yet
>> and will inform through the list when finished. Sorry for the
>> inconvenience.
>>
>> Best,
>> Suat
>>
>>> Are these expected or I am doing something wrong? (I'm running Stanbol
>>> svn revision 1202633)
>>>
>>> Regards,
>>> Alex
>>>
>>
>
Re: full-war launcher
Posted by Olivier Grisel <ol...@ensta.org>.
2011/12/9 Suat Gonul <su...@gmail.com>:
> Hi Alex,
>
> I have made some improvements regarding the war launcher. First, when
> the war file is deployed on Tomcat, it starts automatically. Also,
> static resources e.g css, images are displayed correctly. As far as I
> tried, HTTP service for SOLR cores is also working. For example, I
> executed a query like {stanbolhost}/solr/default/dbpedia/select?q=Paris
> and was able to obtain results.
Good work Suat!
--
Olivier
http://twitter.com/ogrisel - http://github.com/ogrisel
Re: full-war launcher
Posted by Alex Lopez <al...@flordeutopia.pt>.
> Yes, I also tried to set "sling.home" property manually resulting no
> success. But within web.xml of full-war module, it is possible to set
> sling output folder with init-param configuration as follows.
I found this:
http://old.nabble.com/Re%3A-Default-web-app-integration-behavior-p25819120.html
which says:
"There is such a property. It is named "sling.ignoreSystemProperties"
and defaults to true in the Servlet container case and to false in the
standalone application case."
Now I could swear I saw that property somewhere in stanbol trunk or in
the generated files (set to true), but grepped for it now and found
nothing. This might be the reason sling.home is not picked up. However,
I have an idea why it is turned on by default in a servlet environment
and I think it would be better to ignore system properties (aside from
unambiguous properties starting with stanbol.{whatever}, and set sling
and derby etc from these as you propose).
Re: full-war launcher
Posted by Suat Gonul <su...@gmail.com>.
Hi Alex,
See my response inline.
On 12/20/2011 05:50 PM, Alex Lopez wrote:
> Suat,
>
> I managed to deploy and use successfully the full-war into Tomcat :)
> (as you said, I had old sling and derby files lying around from
> previous version, I just missed to spot it at first. The thing is, I
> did a 'cd' into another dir from my Tomcat init script so the user dir
> was not in fact the bin folder in Tomcat.).
Glad to hear that.
>
> So now I wonder now what parameters can I pass to Tomcat to explicitly
> change the location where Sling and Derby write their things. As for
> derby, I added -Dderby.system.home=$MY_STANBOL_HOME to JAVA_OPTS and
> it gets picked up, creating factstore and derby.log. But I had no
> success changing Sling location (tried -Dsling.home=$MY_STANBOL_HOME
> without success), it still goes to the current user dir.
Yes, I also tried to set "sling.home" property manually resulting no
success. But within web.xml of full-war module, it is possible to set
sling output folder with init-param configuration as follows.
<servlet>
<display-name>Sling Servlet</display-name>
<servlet-name>sling</servlet-name>
<servlet-class>org.apache.sling.launchpad.webapp.SlingServlet</servlet-class>
* <init-param>
<param-name>sling.home</param-name>
<param-value>{sling.output.path}</param-value>
</init-param>*
<load-on-startup>100</load-on-startup>
</servlet>
>
> To put it another way, I would be great to be able to pass Tomcat a
> single parameter (like stanbol.dir) so it gets propagated to sling and
> derby; suppose I have been using stanbol stand-alone from location 'A'
> (where I built it), I could then just drop the war file into my
> container, setting stanbol.dir='A', and get a Stanbol instance running
> in the same state as before. I think from the use-case of integrating
> stanbol to a container as part of a webapp it makes sense to have a
> single parameter to set "stanbol home".
>
+1
@All,
To my knowledge, we may check for a property like "stanbol.dir" and
reset both "sling.home" and "derby.system.home" properties based on
"stanbol.dir" in the beginning of initialization of OSGi environment.
However, I'm not sure whether this is an elegant way to configure such
parameters or it would work at all. If you have any other idea, I would
be glad to hear them.
> Best,
> Alex
>
Best,
Suat
Re: full-war launcher
Posted by Alex Lopez <al...@flordeutopia.pt>.
Suat,
I managed to deploy and use successfully the full-war into Tomcat :) (as
you said, I had old sling and derby files lying around from previous
version, I just missed to spot it at first. The thing is, I did a 'cd'
into another dir from my Tomcat init script so the user dir was not in
fact the bin folder in Tomcat.).
So now I wonder now what parameters can I pass to Tomcat to explicitly
change the location where Sling and Derby write their things. As for
derby, I added -Dderby.system.home=$MY_STANBOL_HOME to JAVA_OPTS and it
gets picked up, creating factstore and derby.log. But I had no success
changing Sling location (tried -Dsling.home=$MY_STANBOL_HOME without
success), it still goes to the current user dir.
To put it another way, I would be great to be able to pass Tomcat a
single parameter (like stanbol.dir) so it gets propagated to sling and
derby; suppose I have been using stanbol stand-alone from location 'A'
(where I built it), I could then just drop the war file into my
container, setting stanbol.dir='A', and get a Stanbol instance running
in the same state as before. I think from the use-case of integrating
stanbol to a container as part of a webapp it makes sense to have a
single parameter to set "stanbol home".
Best,
Alex
Em 16-12-2011 15:22, Alex Lopez escreveu:
> Still no joy :(
>
> I have deleted older files, even tried with a fresh Stanbol without
> custom indexes, and to the same results. I have other work to do now but
> will keep trying next week and I let you know.
>
> Em 14-12-2011 14:48, Suat Gonul escreveu:
>> Hi Alex,
>>
>> If it starts automatically, you should be using the updated version.
>> But, the other cause may be the older Stanbol related
>> files(sling,factstore,derby.log) that are created in bin folder of
>> tomcat. I wasn't able to use newer version of war file, until I had
>> deleted those files and redeploy the war.
>>
>> It is enough to drop the war file under webapps as you said. For
>> aliasing, you don't need to set any configuration. Name of the war file
>> becomes the context e.g if you deploy stanbol.war, Stanbol root should
>> be available under {host}/stanbol and static files should be referenced
>> with {host}/stanbol/static/...
>>
>> Best,
>> Suat
>>
>> On 12/14/2011 04:24 PM, Alex Lopez wrote:
>>> Suat,
>>>
>>> I had some problems deploying to Tomcat 7.0.23 as /stanbol context.
>>> I'm now updating and will try again. I could see that now it starts
>>> automatically but I'm still getting wrong static url {host}/static/...
>>> instead of {host}/{stanbolcontext}/static/...
>>>
>>> Just to be sure I'm doing this right, am I just supposed to build
>>> stanbol like mvn clean install and "drop the war"
>>> (launchers/full-war/target/stanbol.war) inside tomcat's webapps? Right
>>> now I'm passing tomcat one property for stanbol (stanbol.dir), I see
>>> in your notes references to web.static.url and web.alias. Do I have to
>>> set these for tomcat too?
>>>
>>> Thanks,
>>> Alex
>>>
>>> Em 12-12-2011 09:54, Alex Lopez escreveu:
>>>> Great, I should get back to it, update and test, thanks for letting me
>>>> know.
>>>>
>>>> Em 09-12-2011 14:03, Fabian Christ escreveu:
>>>>> Hi,
>>>>>
>>>>> yes nice - good to hear ;)
>>>>>
>>>>> Best
>>>>> - Fabian
>>>>>
>>>>> Am Freitag, 9. Dezember 2011 schrieb Suat Gonul :
>>>>>
>>>>>> Hi Alex,
>>>>>>
>>>>>> I have made some improvements regarding the war launcher. First, when
>>>>>> the war file is deployed on Tomcat, it starts automatically. Also,
>>>>>> static resources e.g css, images are displayed correctly. As far as I
>>>>>> tried, HTTP service for SOLR cores is also working. For example, I
>>>>>> executed a query like
>>>>>> {stanbolhost}/solr/default/dbpedia/select?q=Paris
>>>>>> and was able to obtain results.
>>>>>>
>>>>>> BTW, I used Tomcat 7.0.23 to test the changes.
>>>>>>
>>>>>> Best,
>>>>>> Suat
>>>>>>
>>>>>>
>>>>>> On 11/25/2011 05:43 PM, Alex Lopez wrote:
>>>>>>> Thanks Suat for clarifications, :) no problem I'll go on with the
>>>>>>> jar
>>>>>>> launcher and switch to war into my Tomcat later.
>>>>>>>
>>>>>>>> Hi Alex,
>>>>>>>>
>>>>>>>> First of all, I am still working on this launcher and it's not
>>>>>>>> fully
>>>>>>>> tested yet. I just gave a break as I had to focus on other issues.
>>>>>>>> Please see my other comments inline.
>>>>>>>>
>>>>>>>> On 11/25/2011 05:00 PM, Alex Lopez wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I've been trying to run Stanbol using the full-war launcher
>>>>>>>>> (into a
>>>>>>>>> Tomcat 7.0.21, using the /stanbol context).
>>>>>>>>>
>>>>>>>>> The app deployed fine, but after it showed several problems:
>>>>>>>>>
>>>>>>>>> - The first visit to host/stanbol to check if everything was OK
>>>>>>>>> yielded an error (404 if I remember right). Then tomcat log
>>>>>>>>> start to
>>>>>>>>> show some "initiating Jersey app" messages, then after some
>>>>>>>>> seconds a
>>>>>>>>> subsequent visit to host/stanbol works. So it behaves like it
>>>>>>>>> needed a
>>>>>>>>> first request to wake up.
>>>>>>>>
>>>>>>>> Yes, this case was same for me.
>>>>>>>>
>>>>>>>>> - No CSS or images displayed (no /stanbol context added to path of
>>>>>>>>> static resources).
>>>>>>>>
>>>>>>>> This is related about deployment location of static resources. I
>>>>>>>> was
>>>>>>>> working on this but I didn't complete yet. I will inform you when I
>>>>>>>> commit the change that fixes this issue.
>>>>>>>>
>>>>>>>>> - SOLR search not working at host/stanbol/solr anymore (I've had
>>>>>>>>> problems before with SOLR + Tomcat7, could it be this?)
>>>>>>>>>
>>>>>>>>
>>>>>>>> I didn't check the new updates on SOLR yet, so I don't have a clear
>>>>>>>> idea
>>>>>>>> on this. As I said, I didn't finish the work on full-war launcher
>>>>>>>> yet
>>>>>>>> and will inform through the list when finished. Sorry for the
>>>>>>>> inconvenience.
>>>>>>>>
>>>>>>>> Best,
>>>>>>>> Suat
>>>>>>>>
>>>>>>>>> Are these expected or I am doing something wrong? (I'm running
>>>>>>>>> Stanbol
>>>>>>>>> svn revision 1202633)
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Alex
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>
>>
Re: full-war launcher
Posted by Alex Lopez <al...@flordeutopia.pt>.
Still no joy :(
I have deleted older files, even tried with a fresh Stanbol without
custom indexes, and to the same results. I have other work to do now but
will keep trying next week and I let you know.
Em 14-12-2011 14:48, Suat Gonul escreveu:
> Hi Alex,
>
> If it starts automatically, you should be using the updated version.
> But, the other cause may be the older Stanbol related
> files(sling,factstore,derby.log) that are created in bin folder of
> tomcat. I wasn't able to use newer version of war file, until I had
> deleted those files and redeploy the war.
>
> It is enough to drop the war file under webapps as you said. For
> aliasing, you don't need to set any configuration. Name of the war file
> becomes the context e.g if you deploy stanbol.war, Stanbol root should
> be available under {host}/stanbol and static files should be referenced
> with {host}/stanbol/static/...
>
> Best,
> Suat
>
> On 12/14/2011 04:24 PM, Alex Lopez wrote:
>> Suat,
>>
>> I had some problems deploying to Tomcat 7.0.23 as /stanbol context.
>> I'm now updating and will try again. I could see that now it starts
>> automatically but I'm still getting wrong static url {host}/static/...
>> instead of {host}/{stanbolcontext}/static/...
>>
>> Just to be sure I'm doing this right, am I just supposed to build
>> stanbol like mvn clean install and "drop the war"
>> (launchers/full-war/target/stanbol.war) inside tomcat's webapps? Right
>> now I'm passing tomcat one property for stanbol (stanbol.dir), I see
>> in your notes references to web.static.url and web.alias. Do I have to
>> set these for tomcat too?
>>
>> Thanks,
>> Alex
>>
>> Em 12-12-2011 09:54, Alex Lopez escreveu:
>>> Great, I should get back to it, update and test, thanks for letting me
>>> know.
>>>
>>> Em 09-12-2011 14:03, Fabian Christ escreveu:
>>>> Hi,
>>>>
>>>> yes nice - good to hear ;)
>>>>
>>>> Best
>>>> - Fabian
>>>>
>>>> Am Freitag, 9. Dezember 2011 schrieb Suat Gonul :
>>>>
>>>>> Hi Alex,
>>>>>
>>>>> I have made some improvements regarding the war launcher. First, when
>>>>> the war file is deployed on Tomcat, it starts automatically. Also,
>>>>> static resources e.g css, images are displayed correctly. As far as I
>>>>> tried, HTTP service for SOLR cores is also working. For example, I
>>>>> executed a query like
>>>>> {stanbolhost}/solr/default/dbpedia/select?q=Paris
>>>>> and was able to obtain results.
>>>>>
>>>>> BTW, I used Tomcat 7.0.23 to test the changes.
>>>>>
>>>>> Best,
>>>>> Suat
>>>>>
>>>>>
>>>>> On 11/25/2011 05:43 PM, Alex Lopez wrote:
>>>>>> Thanks Suat for clarifications, :) no problem I'll go on with the jar
>>>>>> launcher and switch to war into my Tomcat later.
>>>>>>
>>>>>>> Hi Alex,
>>>>>>>
>>>>>>> First of all, I am still working on this launcher and it's not fully
>>>>>>> tested yet. I just gave a break as I had to focus on other issues.
>>>>>>> Please see my other comments inline.
>>>>>>>
>>>>>>> On 11/25/2011 05:00 PM, Alex Lopez wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I've been trying to run Stanbol using the full-war launcher (into a
>>>>>>>> Tomcat 7.0.21, using the /stanbol context).
>>>>>>>>
>>>>>>>> The app deployed fine, but after it showed several problems:
>>>>>>>>
>>>>>>>> - The first visit to host/stanbol to check if everything was OK
>>>>>>>> yielded an error (404 if I remember right). Then tomcat log
>>>>>>>> start to
>>>>>>>> show some "initiating Jersey app" messages, then after some
>>>>>>>> seconds a
>>>>>>>> subsequent visit to host/stanbol works. So it behaves like it
>>>>>>>> needed a
>>>>>>>> first request to wake up.
>>>>>>>
>>>>>>> Yes, this case was same for me.
>>>>>>>
>>>>>>>> - No CSS or images displayed (no /stanbol context added to path of
>>>>>>>> static resources).
>>>>>>>
>>>>>>> This is related about deployment location of static resources. I was
>>>>>>> working on this but I didn't complete yet. I will inform you when I
>>>>>>> commit the change that fixes this issue.
>>>>>>>
>>>>>>>> - SOLR search not working at host/stanbol/solr anymore (I've had
>>>>>>>> problems before with SOLR + Tomcat7, could it be this?)
>>>>>>>>
>>>>>>>
>>>>>>> I didn't check the new updates on SOLR yet, so I don't have a clear
>>>>>>> idea
>>>>>>> on this. As I said, I didn't finish the work on full-war launcher
>>>>>>> yet
>>>>>>> and will inform through the list when finished. Sorry for the
>>>>>>> inconvenience.
>>>>>>>
>>>>>>> Best,
>>>>>>> Suat
>>>>>>>
>>>>>>>> Are these expected or I am doing something wrong? (I'm running
>>>>>>>> Stanbol
>>>>>>>> svn revision 1202633)
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Alex
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>
>
Re: full-war launcher
Posted by Suat Gonul <su...@gmail.com>.
Hi Alex,
If it starts automatically, you should be using the updated version.
But, the other cause may be the older Stanbol related
files(sling,factstore,derby.log) that are created in bin folder of
tomcat. I wasn't able to use newer version of war file, until I had
deleted those files and redeploy the war.
It is enough to drop the war file under webapps as you said. For
aliasing, you don't need to set any configuration. Name of the war file
becomes the context e.g if you deploy stanbol.war, Stanbol root should
be available under {host}/stanbol and static files should be referenced
with {host}/stanbol/static/...
Best,
Suat
On 12/14/2011 04:24 PM, Alex Lopez wrote:
> Suat,
>
> I had some problems deploying to Tomcat 7.0.23 as /stanbol context.
> I'm now updating and will try again. I could see that now it starts
> automatically but I'm still getting wrong static url {host}/static/...
> instead of {host}/{stanbolcontext}/static/...
>
> Just to be sure I'm doing this right, am I just supposed to build
> stanbol like mvn clean install and "drop the war"
> (launchers/full-war/target/stanbol.war) inside tomcat's webapps? Right
> now I'm passing tomcat one property for stanbol (stanbol.dir), I see
> in your notes references to web.static.url and web.alias. Do I have to
> set these for tomcat too?
>
> Thanks,
> Alex
>
> Em 12-12-2011 09:54, Alex Lopez escreveu:
>> Great, I should get back to it, update and test, thanks for letting me
>> know.
>>
>> Em 09-12-2011 14:03, Fabian Christ escreveu:
>>> Hi,
>>>
>>> yes nice - good to hear ;)
>>>
>>> Best
>>> - Fabian
>>>
>>> Am Freitag, 9. Dezember 2011 schrieb Suat Gonul :
>>>
>>>> Hi Alex,
>>>>
>>>> I have made some improvements regarding the war launcher. First, when
>>>> the war file is deployed on Tomcat, it starts automatically. Also,
>>>> static resources e.g css, images are displayed correctly. As far as I
>>>> tried, HTTP service for SOLR cores is also working. For example, I
>>>> executed a query like
>>>> {stanbolhost}/solr/default/dbpedia/select?q=Paris
>>>> and was able to obtain results.
>>>>
>>>> BTW, I used Tomcat 7.0.23 to test the changes.
>>>>
>>>> Best,
>>>> Suat
>>>>
>>>>
>>>> On 11/25/2011 05:43 PM, Alex Lopez wrote:
>>>>> Thanks Suat for clarifications, :) no problem I'll go on with the jar
>>>>> launcher and switch to war into my Tomcat later.
>>>>>
>>>>>> Hi Alex,
>>>>>>
>>>>>> First of all, I am still working on this launcher and it's not fully
>>>>>> tested yet. I just gave a break as I had to focus on other issues.
>>>>>> Please see my other comments inline.
>>>>>>
>>>>>> On 11/25/2011 05:00 PM, Alex Lopez wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I've been trying to run Stanbol using the full-war launcher (into a
>>>>>>> Tomcat 7.0.21, using the /stanbol context).
>>>>>>>
>>>>>>> The app deployed fine, but after it showed several problems:
>>>>>>>
>>>>>>> - The first visit to host/stanbol to check if everything was OK
>>>>>>> yielded an error (404 if I remember right). Then tomcat log
>>>>>>> start to
>>>>>>> show some "initiating Jersey app" messages, then after some
>>>>>>> seconds a
>>>>>>> subsequent visit to host/stanbol works. So it behaves like it
>>>>>>> needed a
>>>>>>> first request to wake up.
>>>>>>
>>>>>> Yes, this case was same for me.
>>>>>>
>>>>>>> - No CSS or images displayed (no /stanbol context added to path of
>>>>>>> static resources).
>>>>>>
>>>>>> This is related about deployment location of static resources. I was
>>>>>> working on this but I didn't complete yet. I will inform you when I
>>>>>> commit the change that fixes this issue.
>>>>>>
>>>>>>> - SOLR search not working at host/stanbol/solr anymore (I've had
>>>>>>> problems before with SOLR + Tomcat7, could it be this?)
>>>>>>>
>>>>>>
>>>>>> I didn't check the new updates on SOLR yet, so I don't have a clear
>>>>>> idea
>>>>>> on this. As I said, I didn't finish the work on full-war launcher
>>>>>> yet
>>>>>> and will inform through the list when finished. Sorry for the
>>>>>> inconvenience.
>>>>>>
>>>>>> Best,
>>>>>> Suat
>>>>>>
>>>>>>> Are these expected or I am doing something wrong? (I'm running
>>>>>>> Stanbol
>>>>>>> svn revision 1202633)
>>>>>>>
>>>>>>> Regards,
>>>>>>> Alex
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>
Re: full-war launcher
Posted by Alex Lopez <al...@flordeutopia.pt>.
Suat,
I had some problems deploying to Tomcat 7.0.23 as /stanbol context. I'm
now updating and will try again. I could see that now it starts
automatically but I'm still getting wrong static url {host}/static/...
instead of {host}/{stanbolcontext}/static/...
Just to be sure I'm doing this right, am I just supposed to build
stanbol like mvn clean install and "drop the war"
(launchers/full-war/target/stanbol.war) inside tomcat's webapps? Right
now I'm passing tomcat one property for stanbol (stanbol.dir), I see in
your notes references to web.static.url and web.alias. Do I have to set
these for tomcat too?
Thanks,
Alex
Em 12-12-2011 09:54, Alex Lopez escreveu:
> Great, I should get back to it, update and test, thanks for letting me
> know.
>
> Em 09-12-2011 14:03, Fabian Christ escreveu:
>> Hi,
>>
>> yes nice - good to hear ;)
>>
>> Best
>> - Fabian
>>
>> Am Freitag, 9. Dezember 2011 schrieb Suat Gonul :
>>
>>> Hi Alex,
>>>
>>> I have made some improvements regarding the war launcher. First, when
>>> the war file is deployed on Tomcat, it starts automatically. Also,
>>> static resources e.g css, images are displayed correctly. As far as I
>>> tried, HTTP service for SOLR cores is also working. For example, I
>>> executed a query like {stanbolhost}/solr/default/dbpedia/select?q=Paris
>>> and was able to obtain results.
>>>
>>> BTW, I used Tomcat 7.0.23 to test the changes.
>>>
>>> Best,
>>> Suat
>>>
>>>
>>> On 11/25/2011 05:43 PM, Alex Lopez wrote:
>>>> Thanks Suat for clarifications, :) no problem I'll go on with the jar
>>>> launcher and switch to war into my Tomcat later.
>>>>
>>>>> Hi Alex,
>>>>>
>>>>> First of all, I am still working on this launcher and it's not fully
>>>>> tested yet. I just gave a break as I had to focus on other issues.
>>>>> Please see my other comments inline.
>>>>>
>>>>> On 11/25/2011 05:00 PM, Alex Lopez wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I've been trying to run Stanbol using the full-war launcher (into a
>>>>>> Tomcat 7.0.21, using the /stanbol context).
>>>>>>
>>>>>> The app deployed fine, but after it showed several problems:
>>>>>>
>>>>>> - The first visit to host/stanbol to check if everything was OK
>>>>>> yielded an error (404 if I remember right). Then tomcat log start to
>>>>>> show some "initiating Jersey app" messages, then after some seconds a
>>>>>> subsequent visit to host/stanbol works. So it behaves like it
>>>>>> needed a
>>>>>> first request to wake up.
>>>>>
>>>>> Yes, this case was same for me.
>>>>>
>>>>>> - No CSS or images displayed (no /stanbol context added to path of
>>>>>> static resources).
>>>>>
>>>>> This is related about deployment location of static resources. I was
>>>>> working on this but I didn't complete yet. I will inform you when I
>>>>> commit the change that fixes this issue.
>>>>>
>>>>>> - SOLR search not working at host/stanbol/solr anymore (I've had
>>>>>> problems before with SOLR + Tomcat7, could it be this?)
>>>>>>
>>>>>
>>>>> I didn't check the new updates on SOLR yet, so I don't have a clear
>>>>> idea
>>>>> on this. As I said, I didn't finish the work on full-war launcher yet
>>>>> and will inform through the list when finished. Sorry for the
>>>>> inconvenience.
>>>>>
>>>>> Best,
>>>>> Suat
>>>>>
>>>>>> Are these expected or I am doing something wrong? (I'm running
>>>>>> Stanbol
>>>>>> svn revision 1202633)
>>>>>>
>>>>>> Regards,
>>>>>> Alex
>>>>>>
>>>>>
>>>>
>>>
>>>
>>
Re: full-war launcher
Posted by Alex Lopez <al...@flordeutopia.pt>.
Great, I should get back to it, update and test, thanks for letting me know.
Em 09-12-2011 14:03, Fabian Christ escreveu:
> Hi,
>
> yes nice - good to hear ;)
>
> Best
> - Fabian
>
> Am Freitag, 9. Dezember 2011 schrieb Suat Gonul :
>
>> Hi Alex,
>>
>> I have made some improvements regarding the war launcher. First, when
>> the war file is deployed on Tomcat, it starts automatically. Also,
>> static resources e.g css, images are displayed correctly. As far as I
>> tried, HTTP service for SOLR cores is also working. For example, I
>> executed a query like {stanbolhost}/solr/default/dbpedia/select?q=Paris
>> and was able to obtain results.
>>
>> BTW, I used Tomcat 7.0.23 to test the changes.
>>
>> Best,
>> Suat
>>
>>
>> On 11/25/2011 05:43 PM, Alex Lopez wrote:
>>> Thanks Suat for clarifications, :) no problem I'll go on with the jar
>>> launcher and switch to war into my Tomcat later.
>>>
>>>> Hi Alex,
>>>>
>>>> First of all, I am still working on this launcher and it's not fully
>>>> tested yet. I just gave a break as I had to focus on other issues.
>>>> Please see my other comments inline.
>>>>
>>>> On 11/25/2011 05:00 PM, Alex Lopez wrote:
>>>>> Hi,
>>>>>
>>>>> I've been trying to run Stanbol using the full-war launcher (into a
>>>>> Tomcat 7.0.21, using the /stanbol context).
>>>>>
>>>>> The app deployed fine, but after it showed several problems:
>>>>>
>>>>> - The first visit to host/stanbol to check if everything was OK
>>>>> yielded an error (404 if I remember right). Then tomcat log start to
>>>>> show some "initiating Jersey app" messages, then after some seconds a
>>>>> subsequent visit to host/stanbol works. So it behaves like it needed a
>>>>> first request to wake up.
>>>>
>>>> Yes, this case was same for me.
>>>>
>>>>> - No CSS or images displayed (no /stanbol context added to path of
>>>>> static resources).
>>>>
>>>> This is related about deployment location of static resources. I was
>>>> working on this but I didn't complete yet. I will inform you when I
>>>> commit the change that fixes this issue.
>>>>
>>>>> - SOLR search not working at host/stanbol/solr anymore (I've had
>>>>> problems before with SOLR + Tomcat7, could it be this?)
>>>>>
>>>>
>>>> I didn't check the new updates on SOLR yet, so I don't have a clear idea
>>>> on this. As I said, I didn't finish the work on full-war launcher yet
>>>> and will inform through the list when finished. Sorry for the
>>>> inconvenience.
>>>>
>>>> Best,
>>>> Suat
>>>>
>>>>> Are these expected or I am doing something wrong? (I'm running Stanbol
>>>>> svn revision 1202633)
>>>>>
>>>>> Regards,
>>>>> Alex
>>>>>
>>>>
>>>
>>
>>
>
Re: full-war launcher
Posted by Fabian Christ <ch...@googlemail.com>.
Hi,
yes nice - good to hear ;)
Best
- Fabian
Am Freitag, 9. Dezember 2011 schrieb Suat Gonul :
> Hi Alex,
>
> I have made some improvements regarding the war launcher. First, when
> the war file is deployed on Tomcat, it starts automatically. Also,
> static resources e.g css, images are displayed correctly. As far as I
> tried, HTTP service for SOLR cores is also working. For example, I
> executed a query like {stanbolhost}/solr/default/dbpedia/select?q=Paris
> and was able to obtain results.
>
> BTW, I used Tomcat 7.0.23 to test the changes.
>
> Best,
> Suat
>
>
> On 11/25/2011 05:43 PM, Alex Lopez wrote:
> > Thanks Suat for clarifications, :) no problem I'll go on with the jar
> > launcher and switch to war into my Tomcat later.
> >
> >> Hi Alex,
> >>
> >> First of all, I am still working on this launcher and it's not fully
> >> tested yet. I just gave a break as I had to focus on other issues.
> >> Please see my other comments inline.
> >>
> >> On 11/25/2011 05:00 PM, Alex Lopez wrote:
> >>> Hi,
> >>>
> >>> I've been trying to run Stanbol using the full-war launcher (into a
> >>> Tomcat 7.0.21, using the /stanbol context).
> >>>
> >>> The app deployed fine, but after it showed several problems:
> >>>
> >>> - The first visit to host/stanbol to check if everything was OK
> >>> yielded an error (404 if I remember right). Then tomcat log start to
> >>> show some "initiating Jersey app" messages, then after some seconds a
> >>> subsequent visit to host/stanbol works. So it behaves like it needed a
> >>> first request to wake up.
> >>
> >> Yes, this case was same for me.
> >>
> >>> - No CSS or images displayed (no /stanbol context added to path of
> >>> static resources).
> >>
> >> This is related about deployment location of static resources. I was
> >> working on this but I didn't complete yet. I will inform you when I
> >> commit the change that fixes this issue.
> >>
> >>> - SOLR search not working at host/stanbol/solr anymore (I've had
> >>> problems before with SOLR + Tomcat7, could it be this?)
> >>>
> >>
> >> I didn't check the new updates on SOLR yet, so I don't have a clear idea
> >> on this. As I said, I didn't finish the work on full-war launcher yet
> >> and will inform through the list when finished. Sorry for the
> >> inconvenience.
> >>
> >> Best,
> >> Suat
> >>
> >>> Are these expected or I am doing something wrong? (I'm running Stanbol
> >>> svn revision 1202633)
> >>>
> >>> Regards,
> >>> Alex
> >>>
> >>
> >
>
>
--
Fabian
http://twitter.com/fctwitt