Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
No SproutCore Bundle registered at this location
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  3 messages - Expand all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Ian Joyner  
View profile  
 More options Jun 2 2008, 11:46 pm
From: Ian Joyner <i.joy...@acm.org>
Date: Mon, 2 Jun 2008 20:46:45 -0700 (PDT)
Local: Mon, Jun 2 2008 11:46 pm
Subject: No SproutCore Bundle registered at this location
I have set up SproutCore using gem as in the hello world tutorial.
Following the other trivial steps, when I go to http://localhost:4020/hello_world,
I get the "No SproutCore Bundle registered at this location" message.
In Terminal I get:

ian:hello_world ian 13:35 520> pwd
/Volumes/User/Users/ian/Development/Web/SproutCore/hello_world/clients/
hello_world
ian:hello_world ian 13:35 521> sc-server
Running SproutCore Build Tools v0.9.7
Welcome to SproutCore
 ~ Not Using Sessions
 ~ Using Mongrel adapter
 ~ Request: /hello_world
 ~ Routed to:
{:controller=>"sprout_core_bundle_controller_0", :action=>"main"}
 ~ Params: {"action"=>"main",
"controller"=>"sprout_core_bundle_controller_0"}
 ~ No SproutCore Bundle registered at this location. -
(Merb::ControllerExceptions::NotFound)
/Library/Ruby/Gems/1.8/gems/sproutcore-0.9.7/lib/sproutcore/merb/
bundle_controller.rb:35:in `main'
/Library/Ruby/Gems/1.8/gems/merb-core-0.9.3/lib/merb-core/controller/
abstract_controller.rb:221:in `send'
/Library/Ruby/Gems/1.8/gems/merb-core-0.9.3/lib/merb-core/controller/
abstract_controller.rb:221:in `_call_action'
/Library/Ruby/Gems/1.8/gems/merb-core-0.9.3/lib/merb-core/controller/
abstract_controller.rb:201:in `_dispatch'
/Library/Ruby/Gems/1.8/gems/merb-core-0.9.3/lib/merb-core/controller/
merb_controller.rb:189:in `_dispatch'
/Library/Ruby/Gems/1.8/gems/merb-core-0.9.3/lib/merb-core/dispatch/
dispatcher.rb:126:in `dispatch_action'
/Library/Ruby/Gems/1.8/gems/merb-core-0.9.3/lib/merb-core/dispatch/
dispatcher.rb:126:in `synchronize'
/Library/Ruby/Gems/1.8/gems/merb-core-0.9.3/lib/merb-core/dispatch/
dispatcher.rb:126:in `dispatch_action'
/Library/Ruby/Gems/1.8/gems/merb-core-0.9.3/lib/merb-core/dispatch/
dispatcher.rb:73:in `handle'
/Library/Ruby/Gems/1.8/gems/merb-core-0.9.3/lib/merb-core/rack/
application.rb:53:in `call'
/Library/Ruby/Gems/1.8/gems/merb-core-0.9.3/lib/merb-core/rack/handler/
mongrel.rb:72:in `process'
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:159:in
`process_client'
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in `each'
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in
`process_client'
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run'
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in
`initialize'
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `new'
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run'
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in
`initialize'
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `new'
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `run'
/Library/Ruby/Gems/1.8/gems/merb-core-0.9.3/lib/merb-core/rack/adapter/
mongrel.rb:22:in `start'
/Library/Ruby/Gems/1.8/gems/merb-core-0.9.3/lib/merb-core/server.rb:
44:in `start'
/Library/Ruby/Gems/1.8/gems/merb-core-0.9.3/lib/merb-core.rb:36:in
`start'
/Library/Ruby/Gems/1.8/gems/sproutcore-0.9.7/bin/sc-server:66
/usr/bin/sc-server:19:in `load'
/usr/bin/sc-server:19
 ~

I am using OS X 10.5.3 with developer tools and Ruby installed. What
have I missed?

Thanks
Ian


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Joshua Dickens  
View profile  
(1 user)  More options Jun 3 2008, 12:25 am
From: Joshua Dickens <jdick...@apple.com>
Date: Mon, 2 Jun 2008 21:25:16 -0700
Local: Tues, Jun 3 2008 12:25 am
Subject: Re: [sproutcore] No SproutCore Bundle registered at this location

On Jun 2, 2008, at 8:46 PM, Ian Joyner wrote:

> /Volumes/User/Users/ian/Development/Web/SproutCore/hello_world/
> clients/
> hello_world
> ian:hello_world ian 13:35 521> sc-server

It looks like you are starting up sc-server from the wrong location.  
You should start sc-server from the main directory of your Sproutcore  
project directory  --

instead of
cd /Volumes/User/Users/ian/Development/Web/SproutCore/hello_world/
clients/hello_world
sc-server

try

cd /Volumes/User/Users/ian/Development/Web/SproutCore/hello_world
sc-server

then when you go to
http://localhost:4020/hello_world it should work, where hello_world  
now is the name of the particular client app you want to run; if you  
create a new client at

/Volumes/User/Users/ian/Development/Web/SproutCore/hello_world/clients/
my_new_app

then you'd access it at
http://localhost:4020/my_new_app

Hope that helps!

Joosh


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
TomD  
View profile  
 More options Jun 17 2008, 12:46 pm
From: TomD <t...@mactom.com>
Date: Tue, 17 Jun 2008 09:46:13 -0700 (PDT)
Local: Tues, Jun 17 2008 12:46 pm
Subject: Re: No SproutCore Bundle registered at this location
I just downloaded and installed SproutCore on OS 10.5.3.

I found a way to very easily produce the problem:

1) Generate a new example app as per http://www.sproutcore.com/documentation/getting-started/

2) Start the server, and all is well UNTIL ...

3) Replace the contents of body.rhtml with this:

<% content_for('body') do %>
<img src="/fubar.gif" />
<% end %>

where "/fubar.gif" can be just about anything so long as the image
does not really exist.

4) Refresh the web page, see the stack trace.

If you point it to an image that does exist, then the stack trace does
not occur.

I am considering rewriting an app using SproutCore. I hope this is
example is not indicative of an overall fragility of the framework.

Best regards,
Tom


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google