Frontman: commandsPath question

[Pat Farrell]

When using @Bear's frontman, there is a commandsPath parameter.
The examples show it containing only one directory.

Is it a real path? Can it hold multiple directories?
Does it use the Java System.property "path.separator" between them?

I'd like to have

        <init-param>
            <param-name>commandPackages</param-name>
            <param-value>com.pfarrell.bean:com.pfarrell.restrictedbean</param-value>
        </init-param>

[Bear Bibeault]

Are you using the FrontMan 2 beta? Or still using 1?

[Pat Farrell]

Bear Bibeault wrote:Are you using the FrontMan 2 beta? Or still using 1?

Beta 2. Which I think it probably out of beta, since I've been using it for what seems like years.

I have not recently grabbed any updates to Beta 2

[Bear Bibeault]

Pat Farrell wrote:Beta 2. Which I think it probably out of beta, since I've been using it for what seems like years.

The only thing the beta is lacking is finished documentation. I'm not anticipating any code changes, so I guess you can consider it final.

You can specify multiple packages separated by spaces. I like the idea of using the system "path.separator" better. Maybe for 2.1...

[Pat Farrell]

Bear Bibeault wrote:I like the idea of using the system "path.separator" better.

It seemed at least consistant to me. But, one of the claims is that you can write your WAR and run it anyway. If you developed on Windows and then deployed on Debian, the path.separator changes, so the programmer would have to change the source code (XML) to deploy. That seems to smell to me.

It would be a small matter of programming to use either of the two major path.separators known in the universe.