Skip to content
This repository has been archived by the owner on Sep 4, 2019. It is now read-only.

Ripple standalone: ripple service log is not available anywhere #123

Open
danielesegato opened this issue Jul 4, 2012 · 3 comments
Open

Comments

@danielesegato
Copy link

I don't know if this is the right place for bugs on Ripple.. couldn't find any bug tracker for that.

Using the Ripple service + chrome extension you could execute the service from command line (osx in my case) and then see what was going on if something failed with weird exception like: "RAPC exception occurred" that give you no hint on what's happening.

Sometimes the log could be helpful to discover the issue.

I found no way of seeing this log in the Ripple Stand Alone and since you are going to remove the chrome plugin I'm wandering how will be possible to see it.
Actually I preferred the service + chrome solution. It also allowed to have a window server somewhere with blackberry sdk and using the chrome extension from osx or even Linux.

I think this is a big mistake: you are going back on something that was better designed that what you are now doing.

@kwallis
Copy link
Member

kwallis commented Jul 4, 2012

Hi mastro. I am not actually sure what the service is that you are referring to, I assume the services that provide the build and deploy options. You should still be able to run those separately from the Ripple standalone tool, and Ripple standalone also runs on osx. All that said however, we are pushing forward with the Chrome extension approach in the future, so I believe you should be all right.

@danielesegato
Copy link
Author

I'm exactly talking about the build / deploy service

on osx is called something like ripple_service.sh and is found somewhere in /Applications/<app_path>/bin/ripple_service.sh (I'm reporting this second handed, so I don't know the exact path).

Anyway, using the standalone apparently you don't need to execute any service:
https://developer.blackberry.com/html5/documentation/ww_getting_started/use_the_standalone_ripple_emulator_2007541_11.html

so how do you see the service log, and how do you configure your "remote" service instead? couldn't find this information.

thanks

@kwallis
Copy link
Member

kwallis commented Jul 4, 2012

For the standalone, assuming you have installed with the default location, the ripple service is located here:
/Applications/Research In Motion/Ripple 0.9.0.16/services/bin

You should be able to run from there.

Ken Wallis

Product Manager – BlackBerry WebWorks

Research In Motion

(905) 629-4746 x14369


From: mastro [[email protected]]
Sent: Wednesday, July 04, 2012 10:04 AM
To: Ken Wallis
Subject: Re: [WebWorks] Ripple standalone: ripple service log is not available anywhere (#123)

I'm exactly talking about the build / deploy service

on osx is called something like ripple_service.sh and is found somewhere in /Applications/<app_path>/bin/ripple_service.sh (I'm reporting this second handed, so I don't know the exact path).

Anyway, using the standalone apparently you don't need to execute any service:
https://developer.blackberry.com/html5/documentation/ww_getting_started/use_the_standalone_ripple_emulator_2007541_11.html

so how do you see the service log, and how do you configure your "remote" service instead? couldn't find this information.

thanks


Reply to this email directly or view it on GitHub:
#123 (comment)


This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants