http://issues.apache.org/jira/browse/SLING-1752
http://issues.apache.org/jira/browse/SLING-1751

latter is almost fixed in my local workspace; I imagine the former is
something relatively simple.

On 9/10/10 3:40 PM, Tom Barber wrote:
> Hey Justin,
> 
> You want to give me a heads up on whatelse might not work? ;)
> 
> Tom
> 
> 
> 
> On 10 Sep 2010, at 15:12, [email protected] wrote:
> 
>>  BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px;Don't
>> ask, crappy webmail cause I'm stuck behind a corporate firewall.
>> Thanks for your help Justin and Jos, much appreciated.
>> On Fri 10/09/10  3:06 PM , Justin Edelson [email protected]
>> sent:
>> Yes. Please create a JIRA.
>> I've gotta ask... what's up with your email client putting CSS in a
>> plain text email?
>> Justin
>> On 9/10/10 10:04 AM, [email protected] [1] wrote:
>>>  BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px;
>>> }Thanks Justin, I've fixed this locally for now, should I file it
>> as
>>> a jira?
>>> Thanks
>>> Tom
>>> On Fri 10/09/10  2:44 PM , Justin Edelson [email protected]
>> [2]
>>> sent:
>>> There's some code in sling.js that tries to set up the base url.
>>> Perhaps
>>> that's buggy. Since you have this set up and Firebug open, can
>> you
>>> set a
>>> breakpoint on line 413 of sling.js and see if you can see the
>> issue?
>>> On line 415, Sling.baseurl should be set to "/sling" whereas it
>>> sounds
>>> like it's being set to ""
>>> Justin
>>> On 9/10/10 9:29 AM, [email protected] [3] [1] wrote:
>>>>  BODY { font-family:Arial, Helvetica,
>> sans-serif;font-size:12px;
>>>> }Thanks for the reply Jos,
>>>> Thanks the thing (I don't think I'm completely derranged)
>>>> in my tomcat/webapps folder I have a folder called sling that
>>>> contained the webapp.
>>>> So obviously the docroot is http://localhost:8080/sling/ [1]
>>>> And if I go to
>> http://localhost:8080/sling/system/console/bundles
>>>> [2] that works.
>>>> And if I go to http://loclahost:8080/sling/content/tom.html,
>> [3]
>>>> that also works.
>>>> But I can either put an absolute path or relative path to the
>>>> sling.js file:
>>>> and I can see in firebug that the file is loaded, but then the
>>> call
>>>> to info.sessioninfo.json fails because the url is wrong
>> (missing
>>> the
>>>> /sling/)
>>>> I know whatever it is, is something dumb, I just dunno what :)
>>>> Thanks
>>>> Tom
>>>> On Fri 10/09/10  2:22 PM , Jos Snellings
>> [email protected] [4]
>>> [2]
>>>> sent:
>>>> Hi Tom,
>>>> Just rename sling webapp to whatever you want the top of your
>>> webapp
>>>> to be.
>>>> Tomcat will pick that up.
>>>> your urls will look like:
>>>> http://localhost:8080/{yourtopname}/{pathtoresource}
>>>> Jos
>>>> On 09/10/2010 02:51 PM, [email protected] [5] [3] [4]
>> wrote:
>>>>>   BODY { font-family:Arial, Helvetica,
>>> sans-serif;font-size:12px;
>>>> }Hi
>>>>> Guys,
>>>>>  I've been playing around with sling on and off for a few
>>> weeks
>>>> and
>>>>> in development jetty mode my app runs fine, but I want to
>>> deploy
>>>> to
>>>>> tomcat where my sling install no longer resides on root.
>>>>>  Is it possible to set a base url of some sort, so if I do
>>> import
>>>>> sling.js in my esp it knows where to look for resources?
>>>>>  At the moment when I import it it looks to the root :)
>>>>>  http://localhost:8080/system/sling/info.sessionInfo.json
>>>>>  Sorry, noob question, still trying to get my head around
>> all
>>> of
>>>>> this..
>>>>>  Thanks
>>>>>  Tom
>>>>>
>>>>>
>>>>
>>>>
>>>> Links:
>>>> ------
>>>> [1] http://localhost:8080/sling/
>>>> [2] http://localhost:8080/sling/system/console/bundles
>>>> [3] http://loclahost:8080/sling/content/tom.html,
>>>> [4] [email protected] [6] [4]
>>>>
>>>
>>>
>>> Links:
>>> ------
>>> [1] [email protected] [7]
>>> [2] [email protected] [8]
>>> [3] [email protected] [9]
>>> [4] [email protected] [10]
>>>
>>
>>
>> Links:
>> ------
>> [1] mailto:[email protected]
>> [2] mailto:[email protected]
>> [3] mailto:[email protected]
>> [4] mailto:[email protected]
>> [5] mailto:[email protected]
>> [6] mailto:[email protected]
>> [7] mailto:[email protected]
>> [8] mailto:[email protected]
>> [9] mailto:[email protected]
>> [10] mailto:[email protected]
> 

Reply via email to