Hey Paolo, Mike

Hmm... I guess both normal and lowercase works, at least for me. Is there some specification somewhere that states it isn't the lowercase version? I'll put the feature request into Jira using the normal class name.

Also, I have slightly modified my work-around until the feature can be added. The full instructions for the workaround are as follows:

1) Create a directory named "Java" in your project "WebServerResources" directory.
2) Right-click -> WOLips Tools -> Include as WebServerResource
3) Add the follwing jar command to the javaclient target in the build.xml : <jar basedir="${classes.dir}" includes="**/client/**/*.class,**/ common/**/*.class"
                        jarfile="WebServerResources/Java/${project.name}.jar">
                </jar>

4) Always do an Install of you application prior to clicking the run button. Step 3 copies the current version of the client-side .jar into the project so the incremental builder will pick it up.

Dave


On Jan 12, 2008, at 5:33 AM, Paolo Sommaruga wrote:

Hi David,

good idea, I did not dare to ask to the wolips guys including such features.

I have two remarks:

- when one need to extend a EOGenericRecord frequently it need to have one version client side and one server side of the class. It is practical common that both can extend a common class, which will have therefore to make part both of the jar in Resources and the jar in WebServerResources. Therefore I suggest to place the more general

<jar basedir="${classes.dir}" includes="**/client/**/*.class,**/ common/**/*.class"

instead of

        <jar basedir="${classes.dir}" includes="**/client/**/*.class"

with the convention that the common classes are in a package that include somewhere in its path the word common and that the client classes are in a package that include somewhere in its path the word client

- the lowercase nome for the jar have to be under the Resources folder, not in the WebServerResources. Therefore I suggest to place

jarfile="${dest.dir}/${project.name}.woa/Contents/ WebServerResources/Java/${project.name}.jar">

instead of

jarfile="${dest.dir}/${project.name}.woa/Contents/ WebServerResources/Java/${project.name.lowercase}.jar">

After all I think it's better to have

<mkdir dir="${dest.dir}/${project.name}.woa/Contents/ WebServerResources/Java"/> <jar basedir="${classes.dir}" includes="**/client/**/*.class,**/ common/**/*.class" jarfile="${dest.dir}/${project.name}.woa/Contents/ WebServerResources/Java/${project.name}.jar">
        </jar>


Paolo

Il giorno 11/gen/08, alle ore 18:12, Mike Schrag ha scritto:

I would log a WOLips request in Jira for this ...

ms

On Jan 11, 2008, at 11:50 AM, David Avendasora wrote:

Okay. I'm not ready to give up yet, so please humor me?

Is it possible for you to modify the incremental builder to do the same thing as this portion of my build.xml?

<mkdir dir="${dest.dir}/${project.name}.woa/Contents/ WebServerResources/Java"/>
<jar basedir="${classes.dir}" includes="**/client/**/*.class"
jarfile="${dest.dir}/${project.name}.woa/Contents/ WebServerResources/Java/${project.name.lowercase}.jar">
</jar>

This would be helpful to anyone trying to build Java Client applications, and likely would have no effect on anyone not building Java client applications. All client-side classes must be in the WebServerResources directory in order for WO to pass them to the Java Client.

Thanks.

Dave

On Jan 11, 2008, at 11:15 AM, Mike Schrag wrote:

Is the compiled code in the Project/build folder what Eclipse runs when you select "Run"?
yes

If so, can how the contents of that are built be controlled (a hidden build.xml file or something)? I have some special requirements for the "WebServerResources" directory on my project.
It's built by the incremental builder, which is written in code ... it's not something that you can probably easily hook into.

ms






--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/psomma% 40jpaso.com

This email sent to [EMAIL PROTECTED]


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to