Re: AspectJ and WebObjects?

From: Ulrich Köster (ulric..bjectstyle.org)
Date: Tue Dec 23 2003 - 04:03:29 EST

  • Next message: Ulrich Köster: "Re: Servlet Single Directory Deployment"

    Hi Kaelin,

    Am 23.12.2003 um 08:53 schrieb Kaelin Colclasure:

    > It has occurred to me on several occasions that AspectJ might be an
    > invaluable tool for learning the ins and outs of WebObjects. Has
    > anyone on these lists experimented with this? I've just tried
    > installing the latest (1.1.4) AJDT Eclipse plugin, but it
    > unfortunately does not seem to play well with WOLips.:
    >
    > !ENTRY org.eclipse.ajdt.ui 4 0 Dec 22, 2003 21:22:08.892
    > !MESSAGE Compile failed.
    > !STACK 0
    > java.lang.NullPointerException
    > at
    > org.eclipse.ajdt.internal.ui.ajde.ProjectProperties.getClasspath(Projec
    > tProperties.java:206)
    > at org.eclipse.ajdt.internal.builder.Builder.build(Builder.java:150)
    > at
    > org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:
    > 427)
    > at
    > org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform
    > .java:1006)
    > at org.eclipse.core.runtime.Platform.run(Platform.java:413)
    > at
    > org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.j
    > ava:125)
    > at
    > org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.j
    > ava:181)
    > at
    > org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.j
    > ava:191)
    > at
    > org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:
    > 151)
    > at
    > org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform
    > .java:1006)
    > at org.eclipse.core.runtime.Platform.run(Platform.java:413)
    > at
    > org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.j
    > ava:165)
    > at
    > org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:
    > 265)
    > at org.eclipse.core.internal.resources.Project.build(Project.java:85)
    > at
    > org.eclipse.ajdt.internal.ui.PulldownBuildselectorMenu$1.run(PulldownBu
    > ildselectorMenu.java:295)
    > at
    > org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalCo
    > ntext.java:101)
    >
    > I suspect that this is because WOLips has its own Builder classes (I
    > believe) which (presumably) handle classpath metadata differently from
    > the standard Eclipse Builder.
    No, fully standard compliant. We use two builder in a WOLips project.
    1. The standard Eclipse JavaBuilder without any changes. 2. The Ant
    Builder. The .classpath is the same for all java projects in Eclipse.
    WOLips does not make a difference.
    >
    > Using the AspectJ Ant tasks also seems to be a non-starter. It's
    > designed as essentially a drop-in replacement for the javac Ant task
    > -- but again, WOProject Ant build files do not use the javac task.
    > Compiling is apparently all handled in the bowels of the woapplication
    > or woframework tasks instead. While this does make the build files
    > substantially more concise, it would appear to also make it impossible
    > to use alternative Java compilers in conjunction with WOProject... Or
    > is there (hopefully) something I'm missing?
    No, the compiling is done by Eclipse. WOProject just graps the output
    from the compiler (the content of the bin dir) and creates a jar from
    it.

    Is it possible that you use the wrong combination of versions?

    Ulrich

    PS. Please do not post to different mailing list at once.
    >
    > -- Kaelin
    >



    This archive was generated by hypermail 2.0.0 : Tue Dec 23 2003 - 04:03:10 EST