Technical production setup guide update

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Technical production setup guide update

Jacques Le Roux
Administrator
Hi,

While working on the "technical production setup guide" update I noticed some inconsistencies related to the "java -jar ofbiz.jar" commands.

The help gives you:

c:\projectsASF\ofbiz>java -jar ofbiz.jar -help

Usage: java -jar ofbiz.jar [command] [arguments]
-both    -----> Run simultaneously the POS (Point of Sales) application and OFBiz standard
-help, -? ----> This screen
-install -----> Run install (create tables/load data)
-pos     -----> Run the POS (Point of Sales) application
-setup -------> Run external application server setup
-start -------> Start the server
-status ------> Status of the server
-shutdown ----> Shutdown the server
-test --------> Run the JUnit test script
[no config] --> Use default config
[no command] -> Start the server w/ default config

But actually only the -help, -status and -shutdown command need a dash.
So I suggest that we change the -help command to return the other commands without dashes, or?
Also should we not rename install to load-demo?
The setup or -setup command starts but fails
And while at it I'm not sure what
     [no config] --> Use default config
means

Thanks

Jacques
Reply | Threaded
Open this post in threaded view
|

Re: Technical production setup guide update

Jacopo Cappellato-4
Hi Jacques,

thanks for looking at this; the OFBiz bootstrap class clearly need some love; see inline:

On Nov 11, 2014, at 9:05 AM, Jacques Le Roux <[hidden email]> wrote:

> Hi,
>
> While working on the "technical production setup guide" update I noticed some inconsistencies related to the "java -jar ofbiz.jar" commands.
>
> The help gives you:
>
> c:\projectsASF\ofbiz>java -jar ofbiz.jar -help
>
> Usage: java -jar ofbiz.jar [command] [arguments]
> -both    -----> Run simultaneously the POS (Point of Sales) application and OFBiz standard
> -help, -? ----> This screen
> -install -----> Run install (create tables/load data)
> -pos     -----> Run the POS (Point of Sales) application
> -setup -------> Run external application server setup
> -start -------> Start the server
> -status ------> Status of the server
> -shutdown ----> Shutdown the server
> -test --------> Run the JUnit test script
> [no config] --> Use default config
> [no command] -> Start the server w/ default config
>
> But actually only the -help, -status and -shutdown command need a dash.
> So I suggest that we change the -help command to return the other commands without dashes, or?

yes, or we could change the code to accept dashed arguments

> Also should we not rename install to load-demo?

load-data would be a better choice

> The setup or -setup command starts but fails

I suspect that the external app server setup component doesn't work and the thread that I started some time ago in the user list seems to confirm my assumption; in my opinion we should get rid of it and of this startup argument.

> And while at it I'm not sure what
>    [no config] --> Use default config
> means

I think it means that if you don't specify a startup properties file, some default values (hardcoded) will be applied.

>
> Thanks
>
> Jacques

Reply | Threaded
Open this post in threaded view
|

Re: Technical production setup guide update

Jacques Le Roux
Administrator

Le 11/11/2014 10:07, Jacopo Cappellato a écrit :

> Hi Jacques,
>
> thanks for looking at this; the OFBiz bootstrap class clearly need some love; see inline:
>
> On Nov 11, 2014, at 9:05 AM, Jacques Le Roux <[hidden email]> wrote:
>
>> Hi,
>>
>> While working on the "technical production setup guide" update I noticed some inconsistencies related to the "java -jar ofbiz.jar" commands.
>>
>> The help gives you:
>>
>> c:\projectsASF\ofbiz>java -jar ofbiz.jar -help
>>
>> Usage: java -jar ofbiz.jar [command] [arguments]
>> -both    -----> Run simultaneously the POS (Point of Sales) application and OFBiz standard
>> -help, -? ----> This screen
>> -install -----> Run install (create tables/load data)
>> -pos     -----> Run the POS (Point of Sales) application
>> -setup -------> Run external application server setup
>> -start -------> Start the server
>> -status ------> Status of the server
>> -shutdown ----> Shutdown the server
>> -test --------> Run the JUnit test script
>> [no config] --> Use default config
>> [no command] -> Start the server w/ default config
>>
>> But actually only the -help, -status and -shutdown command need a dash.
>> So I suggest that we change the -help command to return the other commands without dashes, or?
> yes, or we could change the code to accept dashed arguments
I believe it would be better (consistent), also because it would restore the previous behaviour. Of course it needs more work (that's why I suggested
the lazy solution)
>> Also should we not rename install to load-demo?
> load-data would be a better choice
+1
>
>> The setup or -setup command starts but fails
> I suspect that the external app server setup component doesn't work and the thread that I started some time ago in the user list seems to confirm my assumption; in my opinion we should get rid of it and of this startup argument.
I don't even know what is this "external app server setup component" :D
So I'm all to get rid of it if nobody care
>
>> And while at it I'm not sure what
>>     [no config] --> Use default config
>> means
> I think it means that if you don't specify a startup properties file, some default values (hardcoded) will be applied.
But how is it different from [no command]?

Jacques
>
>> Thanks
>>
>> Jacques
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Technical production setup guide update

Jacopo Cappellato-4

On Nov 11, 2014, at 2:12 PM, Jacques Le Roux <[hidden email]> wrote:

>
> Le 11/11/2014 10:07, Jacopo Cappellato a écrit :
>> Hi Jacques,
>>
>> thanks for looking at this; the OFBiz bootstrap class clearly need some love; see inline:
>>
>> On Nov 11, 2014, at 9:05 AM, Jacques Le Roux <[hidden email]> wrote:
>>
>>> Hi,
>>>
>>> While working on the "technical production setup guide" update I noticed some inconsistencies related to the "java -jar ofbiz.jar" commands.
>>>
>>> The help gives you:
>>>
>>> c:\projectsASF\ofbiz>java -jar ofbiz.jar -help
>>>
>>> Usage: java -jar ofbiz.jar [command] [arguments]
>>> -both    -----> Run simultaneously the POS (Point of Sales) application and OFBiz standard
>>> -help, -? ----> This screen
>>> -install -----> Run install (create tables/load data)
>>> -pos     -----> Run the POS (Point of Sales) application
>>> -setup -------> Run external application server setup
>>> -start -------> Start the server
>>> -status ------> Status of the server
>>> -shutdown ----> Shutdown the server
>>> -test --------> Run the JUnit test script
>>> [no config] --> Use default config
>>> [no command] -> Start the server w/ default config
>>>
>>> But actually only the -help, -status and -shutdown command need a dash.
>>> So I suggest that we change the -help command to return the other commands without dashes, or?
>> yes, or we could change the code to accept dashed arguments
> I believe it would be better (consistent), also because it would restore the previous behaviour. Of course it needs more work (that's why I suggested the lazy solution)

Of course if you don't have time fixing this it will be ok if you fix the output only.

>>> Also should we not rename install to load-demo?
>> load-data would be a better choice
> +1
>>
>>> The setup or -setup command starts but fails
>> I suspect that the external app server setup component doesn't work and the thread that I started some time ago in the user list seems to confirm my assumption; in my opinion we should get rid of it and of this startup argument.
> I don't even know what is this "external app server setup component" :D

I was actually referring to the specialpurpose/appserver component :-)

> So I'm all to get rid of it if nobody care
>>
>>> And while at it I'm not sure what
>>>    [no config] --> Use default config
>>> means
>> I think it means that if you don't specify a startup properties file, some default values (hardcoded) will be applied.
> But how is it different from [no command]?

I don't know... maybe [no command] actually "starts" the application but yeah... I am not sure about these too.

>
> Jacques
>>
>>> Thanks
>>>
>>> Jacques

Reply | Threaded
Open this post in threaded view
|

Re: Technical production setup guide update

Jacques Le Roux
Administrator
I have created https://issues.apache.org/jira/browse/OFBIZ-5872 for that

Inline..

Le 11/11/2014 15:03, Jacopo Cappellato a écrit :

> On Nov 11, 2014, at 2:12 PM, Jacques Le Roux <[hidden email]> wrote:
>
>> Le 11/11/2014 10:07, Jacopo Cappellato a écrit :
>>> Hi Jacques,
>>>
>>> thanks for looking at this; the OFBiz bootstrap class clearly need some love; see inline:
>>>
>>> On Nov 11, 2014, at 9:05 AM, Jacques Le Roux <[hidden email]> wrote:
>>>
>>>> Hi,
>>>>
>>>> While working on the "technical production setup guide" update I noticed some inconsistencies related to the "java -jar ofbiz.jar" commands.
>>>>
>>>> The help gives you:
>>>>
>>>> c:\projectsASF\ofbiz>java -jar ofbiz.jar -help
>>>>
>>>> Usage: java -jar ofbiz.jar [command] [arguments]
>>>> -both    -----> Run simultaneously the POS (Point of Sales) application and OFBiz standard
>>>> -help, -? ----> This screen
>>>> -install -----> Run install (create tables/load data)
>>>> -pos     -----> Run the POS (Point of Sales) application
>>>> -setup -------> Run external application server setup
>>>> -start -------> Start the server
>>>> -status ------> Status of the server
>>>> -shutdown ----> Shutdown the server
>>>> -test --------> Run the JUnit test script
>>>> [no config] --> Use default config
>>>> [no command] -> Start the server w/ default config
>>>>
>>>> But actually only the -help, -status and -shutdown command need a dash.
>>>> So I suggest that we change the -help command to return the other commands without dashes, or?
>>> yes, or we could change the code to accept dashed arguments
>> I believe it would be better (consistent), also because it would restore the previous behaviour. Of course it needs more work (that's why I suggested the lazy solution)
> Of course if you don't have time fixing this it will be ok if you fix the output only.
>
>>>> Also should we not rename install to load-demo?
>>> load-data would be a better choice
>> +1
Do you know what it does exactly, does it load demo or seed data?
>>>> The setup or -setup command starts but fails
>>> I suspect that the external app server setup component doesn't work and the thread that I started some time ago in the user list seems to confirm my assumption; in my opinion we should get rid of it and of this startup argument.
>> I don't even know what is this "external app server setup component" :D
> I was actually referring to the specialpurpose/appserver component :-)

OK, I believe we can comment it out w/o regrets
I prefer to comment it out for now because if I vaguely remember it started me when I crafted the WASCE case in 2008, but not even sure.

>> So I'm all to get rid of it if nobody care
>>>> And while at it I'm not sure what
>>>>     [no config] --> Use default config
>>>> means
>>> I think it means that if you don't specify a startup properties file, some default values (hardcoded) will be applied.
>> But how is it different from [no command]?
> I don't know... maybe [no command] actually "starts" the application but yeah... I am not sure about these too.

Yes I guess it's that, if you simply use
java -jar ofbiz.jar
it starts the application. That's what [no command] means.

[no config] indeed means default config. But it's still unclear to me how you would use a config. For instance neither
java -jar ofbiz.jar start pos
nor
java -jar ofbiz.jar start -pos
start the pos when
java -jar ofbiz.jar pos
does
So I'd remove this help line which is a bit confusing and redundant

When we will be OK I will complete OFBIZ-5872

Jacques
Reply | Threaded
Open this post in threaded view
|

Re: Technical production setup guide update

Jacopo Cappellato-4

On Nov 12, 2014, at 11:08 AM, Jacques Le Roux <[hidden email]> wrote:

>>>>> Also should we not rename install to load-demo?
>>>> load-data would be a better choice
>>> +1
> Do you know what it does exactly, does it load demo or seed data?

It depends on other arguments; for example:

           $ java -jar ofbiz.jar -install -readers=seed,demo,ext -timeout=7200 -delegator=default -group=org.ofbiz
           $ java -jar ofbiz.jar -install -file=/tmp/dataload.xml

Jacopo

Reply | Threaded
Open this post in threaded view
|

Re: Technical production setup guide update

mandeepmavi
HI
If i add POS to new release or SVN. getting error with ant command.

Mandeep
Reply | Threaded
Open this post in threaded view
|

Re: Technical production setup guide update

Jacques Le Roux
Administrator
In reply to this post by Jacopo Cappellato-4

Le 12/11/2014 14:27, Jacopo Cappellato a écrit :

> On Nov 12, 2014, at 11:08 AM, Jacques Le Roux <[hidden email]> wrote:
>
>>>>>> Also should we not rename install to load-demo?
>>>>> load-data would be a better choice
>>>> +1
>> Do you know what it does exactly, does it load demo or seed data?
> It depends on other arguments; for example:
>
>             $ java -jar ofbiz.jar -install -readers=seed,demo,ext -timeout=7200 -delegator=default -group=org.ofbiz
>             $ java -jar ofbiz.jar -install -file=/tmp/dataload.xml

Ha great thanks, I think we should add this as an example in the help ! :)

Jacques

>
> Jacopo
>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Technical production setup guide update

mandeepmavi
In reply to this post by mandeepmavi
copy-derby-props:

ofbiz-init:

build:
     [echo] [build] ========== Start Building (Compile) ==========

build-framework:

init:

prepare:

classes:

jar:

init:

prepare:

gen-src:

classes:

jar:

init:

prepare:

gen-src:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

stubs:

main-jar:

rmi-jar:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

build-applications:

init:

prepare:

classes:
  [javac16] Compiling 1 source file to c:\ofbiz\applications\content\build\class
es

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

init:

prepare:

classes:

jar:

build-specialpurpose:

init:

prepare:

classes:

jar:

init:

prepare:

classes:
  [javac16] Compiling 62 source files to c:\ofbiz\specialpurpose\pos\build\class
es
  [javac16] c:\ofbiz\specialpurpose\pos\src\org\ofbiz\pos\PosTransaction.java:59
: cannot find symbol
  [javac16] symbol  : class EntityQuery
  [javac16] location: package org.ofbiz.entity.util
  [javac16] import org.ofbiz.entity.util.EntityQuery;
  [javac16]                             ^
  [javac16] c:\ofbiz\specialpurpose\pos\src\org\ofbiz\pos\PosTransaction.java:59
: cannot find symbol
  [javac16] symbol  : class EntityQuery
  [javac16] location: package org.ofbiz.entity.util
  [javac16] import org.ofbiz.entity.util.EntityQuery;
  [javac16]                             ^
  [javac16] c:\ofbiz\specialpurpose\pos\src\org\ofbiz\pos\PosTransaction.java:43
7: cannot find symbol
  [javac16] symbol  : variable EntityQuery
  [javac16] location: class org.ofbiz.pos.PosTransaction
  [javac16]             product = EntityQuery.use(delegator).from("Product").whe
re("productId", productId).cache().queryOne();
  [javac16]                       ^
  [javac16] c:\ofbiz\specialpurpose\pos\src\org\ofbiz\pos\PosTransaction.java:49
6: cannot find symbol
  [javac16] symbol  : variable EntityQuery
  [javac16] location: class org.ofbiz.pos.PosTransaction
  [javac16]             product = EntityQuery.use(delegator).from("Product").whe
re("productId", productId).cache().queryOne();
  [javac16]                       ^
  [javac16] c:\ofbiz\specialpurpose\pos\src\org\ofbiz\pos\config\ButtonEventConf
ig.java:55: warning: [deprecation] getXmlRootElement(java.lang.String) in org.of
biz.base.config.ResourceLoader has been deprecated
  [javac16]         Element root = ResourceLoader.getXmlRootElement(ButtonEventC
onfig.BUTTON_EVENT_CONFIG);
  [javac16]                                      ^
  [javac16] 3 errors
  [javac16] 1 warning

BUILD FAILED
c:\ofbiz\build.xml:230: The following error occurred while executing this line:
c:\ofbiz\build.xml:252: The following error occurred while executing this line:
c:\ofbiz\macros.xml:39: The following error occurred while executing this line:
c:\ofbiz\common.xml:91: Compile failed; see the compiler error output for detail
s.

Total time: 7 seconds
c:\ofbiz>