incubator-stonehenge-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Drew Baird <drew...@yahoo.com>
Subject Re: MetroDeploy_Troubleshoot_Walkthru.doc-QUERY
Date Sun, 16 Aug 2009 03:57:52 GMT
+1
 Drew 




________________________________
From: Selvaratnam Uthaiyashankar <uthaiyashankar@gmail.com>
To: stonehenge-dev@incubator.apache.org
Sent: Saturday, August 15, 2009 8:04:07 PM
Subject: Re: MetroDeploy_Troubleshoot_Walkthru.doc-QUERY

On Sat, Aug 15, 2009 at 9:32 PM, Ben Dewey<Ben.Dewey@26ny.com> wrote:
> Ming,
>
> +1 to changing both the WSAS and METRO codebases.   Additionally the Metro manual.doc
would have to be changed from using JAVA_* for Metro to METRO_*.
>
> Harold/Shankar,
>
> Thoughts?  Fair for nobody to use JAVA_*?

+1. Lets change it to METRO_* and WSAS_*. This will help us when there
is one more java platform (CXF? ) the names will be meaningful..

Regards,
Shankar

>
> -Ben Dewey
>
>
> ________________________________________
> From: Ming Jin [skyairmj@gmail.com]
> Sent: Saturday, August 15, 2009 11:12 AM
> To: stonehenge-dev@incubator.apache.org
> Subject: Re: MetroDeploy_Troubleshoot_Walkthru.doc-QUERY
>
> Hi Ben,
> We've noticed the naming conflict, that is the reason why there're three new
> service entries like WSO2_BS/WSO2_OPS/WSO2_OPSSEC in the config service
> table in manual.doc. And that's what we do in the Metro codebase.
>
> To solve this problem. we can change the metro codebase to use METRO_* and
> retain the wso2 codebase, or we can change the wso2 codebase to use WSO2_*
> and retain the metro codebase. To me, they are both OK.
>
> Anyway, I think it's a good idea to get Harold and Shankar involved in this
> discussion, what do you think?
>
> - Ming Jin
>
> On Sat, Aug 15, 2009 at 9:15 PM, Ben Dewey <Ben.Dewey@26ny.com> wrote:
>
>> We'll it seems we all may be having a problem with the naming conflict of
>> WSAS and METRO.  In my previous email I mentioned that the METRO is using
>> JAVA_CLIENT, JAVA_BS, and JAVA_OPS.  and WSAS is using JAVA_BS and JAVA_OPS.
>>
>> In our lab, Joby and I used METRO_BS and OPS, but since METRO is querying
>> getBsConfig using JAVA_BS, that's probably the errors that Joby is getting.
>>  Hopefully this also explains the confusion with the document.
>>
>> Ming,
>>
>> I'd really like you to weigh in on this and if you're okay with it I'll
>> rename the metro codebase to use METRO_BS and change the documentation.
>>
>> -Ben
>>
>> ________________________________________
>> From: Ranjitha V [ranjitha123@gmail.com]
>> Sent: Saturday, August 15, 2009 3:37 AM
>> To: stonehenge-dev@incubator.apache.org
>> Subject: Re: MetroDeploy_Troubleshoot_Walkthru.doc-QUERY
>>
>> Hi all,
>>
>> Even I faced the same error. The order was not carried out exactly.
>> The actual process of 'buy' and 'sell' did not happen.
>> Everytime I clicked on the link 'buy', I logged out automatically.
>>
>> -Ranjitha
>>
>> On Fri, Aug 14, 2009 at 10:59 PM, Vineet ghatge <vgh4uster@gmail.com>
>> wrote:
>>
>> > ---------- Forwarded message ----------
>> > From: Vineet ghatge <vgh4uster@gmail.com>
>> > Date: Fri, Aug 14, 2009 at 2:40 PM
>> > Subject: Fwd: MetroDeploy_Troubleshoot_Walkthru.doc-QUERY
>> > To: Ben Dewey <Ben.Dewey@26ny.com>
>> >
>> >
>> >
>> >
>> > ---------- Forwarded message ----------
>> > From: Vineet ghatge <vgh4uster@gmail.com>
>> > Date: Fri, Aug 14, 2009 at 2:40 PM
>> > Subject: MetroDeploy_Troubleshoot_Walkthru.doc-QUERY
>> > To: Ben Dewey <Ben.Dewey@26ny.com>
>> >
>> >
>> > Hello all,
>> >
>> > In the documentation "MetroDeploy_Troubleshoot_Walkthru.doc" the step
>> > number
>> > 21 says:-
>> >
>> > 21.    So, I manually updated the JAVA_BS record in the DB to METRO_OPS
>> >
>> > The above statement means
>> > -I should change the URL of JAVA_BS to METRO_BS in the "service table"
>> >
>> > Could please tell me if I am right?
>> >
>> > In th documentation "C:\Metro\documents" under Metro StockTrader
>> > Configuration there is a note:-
>> >
>> > Note 1:
>> >
>> > For JAVA_BS, JAVA_OPS and JAVA_OPSSEC, you should change the endpoint
>> > addresses according to the glassfish development environment, such as the
>> > port of glassfish.
>> >
>> > Is this Mandatory step ? The config part worked though I logged out every
>> > time tried buying shares.
>> >
>> > With Regards,
>> > Vineet Ghatge H
>> >
>>
>
>
>
> --
> Ming Jin
>
> Consultant
> Thoughtworks, Inc



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message