Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

Sanjiva Weerawarana wrote: > Keith Chapman wrote: >> Hi all, >> >> The change is done. We now have the service available at >> /services/username/serviceName. The actual name of the axisService is >> username-serviceName but this is hidden from the user. I have added a > > Cool! > >> new dispatch

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

Keith Chapman wrote: Hi all, The change is done. We now have the service available at /services/username/serviceName. The actual name of the axisService is username-serviceName but this is hidden from the user. I have added a Cool! new dispatcher and our own transport listener (In order to t

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

Hi all, The change is done. We now have the service available at /services/username/serviceName. The actual name of the axisService is username-serviceName but this is hidden from the user. I have added a new dispatcher and our own transport listener (In order to take control of the EPR in the wsd

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

> Two options for that: > > 1. don't store the service in AxisConfig at all .. store it elsewhere > and have the dispatcher look there. > > 2. store it in the AxisConfig with a mangled name - call it > "{user}/{service}" say (use a join character which is not valid in a > service name). I prefer

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

Keith Chapman wrote: We can take control of the EPR by providing our own listener that extends the WSAS listener. The piece that left in the puzzle is to have two services with the same name in Axis2. Any clue what this configuration parameter is? Two options for that: 1. don't store the servi

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

Sanjiva Weerawarana wrote: > Keith Chapman wrote: >> >> How can I have 2 axis services both with the name sudoku? Axis disallows >> this at present which pushes us to use something like jonathan-soduku >> and keith-sudoku. > > Nahh .. you can control all of that in Axis2. We can take control of th

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

Sanjiva Weerawarana wrote: > Keith Chapman wrote: >> >> How can I have 2 axis services both with the name sudoku? Axis disallows >> this at present which pushes us to use something like jonathan-soduku >> and keith-sudoku. > > Nahh .. you can control all of that in Axis2. > >> I can have jonathan

Re: [Fwd: Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls]

Jonathan Marsh wrote: >>> Deepal- there's no difference between having multiple configs and a >> single >>> config in terms of the cost of having the WSDLs in memory etc.. If >> there >>> are n services there are n WSDLs - This is not an issue for the Mashup Server (At least at the moment) because

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

Keith Chapman wrote: How can I have 2 axis services both with the name sudoku? Axis disallows this at present which pushes us to use something like jonathan-soduku and keith-sudoku. Nahh .. you can control all of that in Axis2. I can have jonathan-soduku and keith-sudoku as the actual servic

RE: [Fwd: Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls]

> > Deepal- there's no difference between having multiple configs and a > single > > config in terms of the cost of having the WSDLs in memory etc.. If > there > > are n services there are n WSDLs - > The problem is each single config will have n number of wsdls so , if > we > have m number of use

[Fwd: Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls]

gt;>>> what >>>> we need to do is use the user name as a key to pick the configuration. >>>> >>>> Sanjiva. >>>> >>>> Jonathan Marsh wrote: >>>>> We can use "-" as a splitter if we preclude it from mashup na

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

>>>> Let me know if you guys need help to figure out the details of that- >>>> what >>>> we need to do is use the user name as a key to pick the configuration. >>>> >>>> Sanjiva. >>>> >>>> Jonathan Marsh wrote: >>>>

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

aces.live.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Glen Daniels Sent: Saturday, December 08, 2007 6:17 AM To: mashup-dev@wso2.org Subject: Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls Jonathan Marsh wrote: to differentiate

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

>> http://auburnmarshes.spaces.live.com >>> >>>> -Original Message- >>>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >>>> On Behalf Of Glen Daniels >>>> Sent: Saturday, December 08, 2007 6:17 AM >>>> To: mash

RE: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

ance of Axis2 per user sounds good. Having an > >> option > >> to turn off the "services" segment is good too. > >> > >> Jonathan Marsh - http://www.wso2.com - > >> http://auburnmarshes.spaces.live.com > >> > >>> -Ori

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

t; Jonathan Marsh - http://www.wso2.com - >> http://auburnmarshes.spaces.live.com >> >>> -Original Message- >>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >>> On Behalf Of Glen Daniels >>> Sent: Saturday, December 08, 2007 6:17 AM >>> To:

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

Sanjiva Weerawarana wrote: > Keith Chapman wrote: >> Sanjiva Weerawarana wrote: >>> The right solution is to use a different Axis2 configuration for each >>> user- there's absolutely no problem doing that. >> Will that scale well? (Say we have a 100 users) > > Its just an object with a bunch of ha

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

Keith Chapman wrote: Sanjiva Weerawarana wrote: The right solution is to use a different Axis2 configuration for each user- there's absolutely no problem doing that. Will that scale well? (Say we have a 100 users) Its just an object with a bunch of hashtables .. it'll be fine! Sanjiva. -- Sa

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

Message- >>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >>> On Behalf Of Glen Daniels >>> Sent: Saturday, December 08, 2007 6:17 AM >>> To: mashup-dev@wso2.org >>> Subject: Re: [mashup-dev] Some thoughts on the scripts folder, paths, >>&

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

h - http://www.wso2.com - http://auburnmarshes.spaces.live.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Glen Daniels Sent: Saturday, December 08, 2007 6:17 AM To: mashup-dev@wso2.org Subject: Re: [mashup-dev] Some thoughts on the scripts folder, paths, and u

RE: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

ttp://www.wso2.com - http://auburnmarshes.spaces.live.com > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Glen Daniels > Sent: Saturday, December 08, 2007 6:17 AM > To: mashup-dev@wso2.org > Subject: Re: [mashup-dev] Some thoughts on the scri

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

Jonathan Marsh wrote: to differentiate between two services with the same service name (channa/sudoku and jonathan/sudoku). You mean we'd need to do some front-end rewriting of the url: /jonathan/Sudoku to something like /services/jonathan;Sudoku ? I'd steer away from semicolon since that

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Some comments inline; >> >> 0) More on user provisioning: >> >> a. On startup, several accounts are created: >> >> i. System. The system account is the “author” of the built-in >> foundational services. The system account is of type Guest but for >> s

RE: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

> > c. Each of the above folders is a virtual directory, with mashups > > available from the urls http://:7762/system/ > > and > > http://:7762/samples/ > > respectively. > > > The virtual directory can simply be

Re: [mashup-dev] Some thoughts on the scripts folder, paths, and urls

*On Behalf Of *Jonathan Marsh *Sent:* Wednesday, October 24, 2007 2:46 PM *To:* mashup-dev@wso2.org *Subject:* [mashup-dev] Some thoughts on the scripts folder, paths, and urls We have a number of bugs related to the virtual directory system for mashups MASHUP-6: Need virtual directory