You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@beehive.apache.org by Alexander Smirnoff <as...@vistar.ca> on 2004/08/05 15:29:40 UTC
error on apt compilation
Hi,
I'm trying to compile one of the simple tests from DRT in my own
environment. Why am I getting this error?
[apt] warning on annotation value "Begin.jsp": File "Begin.jsp" could
not be found in the web application.
[apt] warning on annotation value "Begin.jsp": File "Begin.jsp" could
not be found in the web application.
[apt] warning on annotation value "Begin.jsp": File "Begin.jsp" could
not be found in the web application.
[apt] __input:29: The package must be
"WEB-INF.tmp.miniTests.buttonSubmit".
[apt] (source unavailable)
[apt] 1 error
it looks like apt tries to compile from tmp directory, but cannot resolve
the package. Here is by built.xml:
<project default="all" basedir=".">
<property name="src.dir" value="src"/>
<property name="web.dir" value="WebRoot"/>
<property name="lib.common" value="lib/common"/>
<property name="lib.web" value="${web.dir}/WEB-INF/lib"/>
<property name="lib.beehive" value="lib/beehive"/>
<property name="tmp.dir" value="${web.dir}/WEB-INF/tmp"/>
<path id="webapp.build.classpath">
<pathelement location="${web.dir}/WEB-INF/classes" />
<fileset dir="${lib.web}">
<include name="*.jar" />
</fileset>
<fileset dir="${lib.common}">
<include name="*.jar" />
</fileset>
</path>
<target name="all">
<delete dir="${tmp.dir}" includeEmptyDirs="true"/>
<javac srcdir="${src.dir}"
destdir="${web.dir}/WEB-INF/classes"
classpathref="webapp.build.classpath"/>
<taskdef name="apt"
classname="org.apache.beehive.controls.runtime.generator.AptTask"
classpath="${lib.beehive}/controls.jar;${lib.beehive}/beehive-netui-compiler
.jar" onerror="report"/>
<mkdir dir="${tmp.dir}"/>
<path id="pageflow.build.classpath">
<path refid="webapp.build.classpath"/>
<fileset file="${lib.beehive}/beehive-netui-compiler.jar"/>
</path>
<apt srcdir="${web.dir}"
destdir="${web.dir}/WEB-INF/classes"
gendir="${tmp.dir}"
classpathref="pageflow.build.classpath"
srcExtensions="*.app,*.jpf">
</apt>
</target>
</project>
Thanks,
Alex.
RE: error on apt compilation
Posted by Alexander Smirnoff <as...@vistar.ca>.
Thanks Carl,
I have the feeling that this is a runtime setup issue.
Alex.
> -----Original Message-----
> From: Carl McConnell [mailto:carl_mcconnell@instantiations.com]
> Sent: August 5, 2004 3:38 PM
> To: Beehive Users
> Subject: RE: error on apt compilation
>
>
> Hi Alex,
>
> I've been working along the same lines as you in trying to create a
> stand-alone compilation script, but the script isn't yet as
> isolated from
> beehive as yours is, which is probably why the buttonSubmit example
> compiles for me. In case it's useful, I've attached the
> script, which
> assumes environment variables are set as in the beehive build.
>
> Carl McConnell
> Instantiations, Inc.
> Eclipse Pollinate Project
>
> At 07:02 AM 8/5/2004, Alexander Smirnoff wrote:
> >The environment is Eclipse (3.1 integration). But the compilation
> >is made by normal ant process. I've even tried it without Eclipse
> >in command line - the same result.
> >
> >I tried to reproduce almost the same ant project as found in
> >test\ant\buildWebapp.xml, but I have feeling that I missed
> >something... At least [apt] task is identical...
> >
> >Alex.
> >
> > > -----Original Message-----
> > > From: Sebastian Gozin [mailto:some@gamepoint.net]
> > > Sent: August 5, 2004 9:56 AM
> > > To: Beehive Users
> > > Subject: Re: error on apt compilation
> > >
> > >
> > > Could you tell us a bit more about this environment? Like
> > > what IDE are
> > > you using to edit source?
> > > I find it strange to read the following
> > >
> > > [apt] __input:29: The package must be
> > > "WEB-INF.tmp.miniTests.buttonSubmit"
> > >
> > > Makes me think a bit of netbeans changing the package
> > > statements if you
> > > opened the source file from the wrong filesystem.
> > >
> > > Sebastian
> > >
> > >
> > > .Alexander Smirnoff wrote:
> > >
> > > >Hi,
> > > >
> > > >I'm trying to compile one of the simple tests from DRT
> in my own
> > > >environment. Why am I getting this error?
> > > >
> > > > [apt] warning on annotation value "Begin.jsp": File
> > > "Begin.jsp" could
> > > >not be found in the web application.
> > > > [apt] warning on annotation value "Begin.jsp": File
> > > "Begin.jsp" could
> > > >not be found in the web application.
> > > > [apt] warning on annotation value "Begin.jsp": File
> > > "Begin.jsp" could
> > > >not be found in the web application.
> > > > [apt] __input:29: The package must be
> > > >"WEB-INF.tmp.miniTests.buttonSubmit".
> > > > [apt] (source unavailable)
> > > > [apt] 1 error
> > > >
> > > >it looks like apt tries to compile from tmp directory, but
> > > cannot resolve
> > > >the package. Here is by built.xml:
> > > >
> > > ><project default="all" basedir=".">
> > > >
> > > > <property name="src.dir" value="src"/>
> > > > <property name="web.dir" value="WebRoot"/>
> > > > <property name="lib.common" value="lib/common"/>
> > > > <property name="lib.web"
> value="${web.dir}/WEB-INF/lib"/>
> > > > <property name="lib.beehive" value="lib/beehive"/>
> > > > <property name="tmp.dir"
> value="${web.dir}/WEB-INF/tmp"/>
> > > >
> > > > <path id="webapp.build.classpath">
> > > > <pathelement
> > > location="${web.dir}/WEB-INF/classes" />
> > > > <fileset dir="${lib.web}">
> > > > <include name="*.jar" />
> > > > </fileset>
> > > > <fileset dir="${lib.common}">
> > > > <include name="*.jar" />
> > > > </fileset>
> > > > </path>
> > > > <target name="all">
> > > > <delete dir="${tmp.dir}"
> includeEmptyDirs="true"/>
> > > >
> > > > <javac srcdir="${src.dir}"
> > > >destdir="${web.dir}/WEB-INF/classes"
> > > >
> > > classpathref="webapp.build.classpath"/>
> > > > <taskdef name="apt"
> > >
> >classname="org.apache.beehive.controls.runtime.generator.AptTask"
> > > >
> > > >classpath="${lib.beehive}/controls.jar;${lib.beehive}/beehi
> > > ve-netui-compiler
> > > >.jar" onerror="report"/>
> > > > <mkdir dir="${tmp.dir}"/>
> > > >
> > > > <path id="pageflow.build.classpath">
> > > > <path refid="webapp.build.classpath"/>
> > > > <fileset
> > > file="${lib.beehive}/beehive-netui-compiler.jar"/>
> > > > </path>
> > > >
> > > > <apt srcdir="${web.dir}"
> > > >destdir="${web.dir}/WEB-INF/classes"
> > > > gendir="${tmp.dir}"
> > > > classpathref="pageflow.build.classpath"
> > > >srcExtensions="*.app,*.jpf">
> > > > </apt>
> > > > </target>
> > > ></project>
> > > >
> > > >Thanks,
> > > >
> > > >Alex.
> > > >
> > > >
> > > >
> > >
> > >
>
RE: error on apt compilation
Posted by Carl McConnell <ca...@instantiations.com>.
Hi Alex,
I've been working along the same lines as you in trying to create a
stand-alone compilation script, but the script isn't yet as isolated from
beehive as yours is, which is probably why the buttonSubmit example
compiles for me. In case it's useful, I've attached the script, which
assumes environment variables are set as in the beehive build.
Carl McConnell
Instantiations, Inc.
Eclipse Pollinate Project
At 07:02 AM 8/5/2004, Alexander Smirnoff wrote:
>The environment is Eclipse (3.1 integration). But the compilation
>is made by normal ant process. I've even tried it without Eclipse
>in command line - the same result.
>
>I tried to reproduce almost the same ant project as found in
>test\ant\buildWebapp.xml, but I have feeling that I missed
>something... At least [apt] task is identical...
>
>Alex.
>
> > -----Original Message-----
> > From: Sebastian Gozin [mailto:some@gamepoint.net]
> > Sent: August 5, 2004 9:56 AM
> > To: Beehive Users
> > Subject: Re: error on apt compilation
> >
> >
> > Could you tell us a bit more about this environment? Like
> > what IDE are
> > you using to edit source?
> > I find it strange to read the following
> >
> > [apt] __input:29: The package must be
> > "WEB-INF.tmp.miniTests.buttonSubmit"
> >
> > Makes me think a bit of netbeans changing the package
> > statements if you
> > opened the source file from the wrong filesystem.
> >
> > Sebastian
> >
> >
> > .Alexander Smirnoff wrote:
> >
> > >Hi,
> > >
> > >I'm trying to compile one of the simple tests from DRT in my own
> > >environment. Why am I getting this error?
> > >
> > > [apt] warning on annotation value "Begin.jsp": File
> > "Begin.jsp" could
> > >not be found in the web application.
> > > [apt] warning on annotation value "Begin.jsp": File
> > "Begin.jsp" could
> > >not be found in the web application.
> > > [apt] warning on annotation value "Begin.jsp": File
> > "Begin.jsp" could
> > >not be found in the web application.
> > > [apt] __input:29: The package must be
> > >"WEB-INF.tmp.miniTests.buttonSubmit".
> > > [apt] (source unavailable)
> > > [apt] 1 error
> > >
> > >it looks like apt tries to compile from tmp directory, but
> > cannot resolve
> > >the package. Here is by built.xml:
> > >
> > ><project default="all" basedir=".">
> > >
> > > <property name="src.dir" value="src"/>
> > > <property name="web.dir" value="WebRoot"/>
> > > <property name="lib.common" value="lib/common"/>
> > > <property name="lib.web" value="${web.dir}/WEB-INF/lib"/>
> > > <property name="lib.beehive" value="lib/beehive"/>
> > > <property name="tmp.dir" value="${web.dir}/WEB-INF/tmp"/>
> > >
> > > <path id="webapp.build.classpath">
> > > <pathelement
> > location="${web.dir}/WEB-INF/classes" />
> > > <fileset dir="${lib.web}">
> > > <include name="*.jar" />
> > > </fileset>
> > > <fileset dir="${lib.common}">
> > > <include name="*.jar" />
> > > </fileset>
> > > </path>
> > > <target name="all">
> > > <delete dir="${tmp.dir}" includeEmptyDirs="true"/>
> > >
> > > <javac srcdir="${src.dir}"
> > >destdir="${web.dir}/WEB-INF/classes"
> > >
> > classpathref="webapp.build.classpath"/>
> > > <taskdef name="apt"
> > >classname="org.apache.beehive.controls.runtime.generator.AptTask"
> > >
> > >classpath="${lib.beehive}/controls.jar;${lib.beehive}/beehi
> > ve-netui-compiler
> > >.jar" onerror="report"/>
> > > <mkdir dir="${tmp.dir}"/>
> > >
> > > <path id="pageflow.build.classpath">
> > > <path refid="webapp.build.classpath"/>
> > > <fileset
> > file="${lib.beehive}/beehive-netui-compiler.jar"/>
> > > </path>
> > >
> > > <apt srcdir="${web.dir}"
> > >destdir="${web.dir}/WEB-INF/classes"
> > > gendir="${tmp.dir}"
> > > classpathref="pageflow.build.classpath"
> > >srcExtensions="*.app,*.jpf">
> > > </apt>
> > > </target>
> > ></project>
> > >
> > >Thanks,
> > >
> > >Alex.
> > >
> > >
> > >
> >
> >
Re: error on apt compilation
Posted by Carl McConnell <ca...@instantiations.com>.
Eddie,
Thanks for jumping on this. The "self-contained directory" you describe is
just the ticket. I'd be happy to never again go crawling around the Beehive
dev tree trying to invent one myself. :-)
Carl
At 07:46 AM 8/9/2004, you wrote:
>Carl--
>
> I actually think that defining the distribution and getting the build
> producing it (even if we don't distribute it off of the website for the
> near term) is actually pretty critical to getting people using Beehive.
> To answer your questions, the best thing that Beehive could do is to
> just produce that distribution in $BEEHIVE_HOME/build/dist. This would
> need to be a self-contained directory that includes all of the pieces
> necessary to:
>
> - use controls
> - create / use a NetUI webapp
> - provide a build process that can handle each of these
>
> I'll strike up a thread on the dev list that starts to answer your four
> questions below and perhaps we can get something rolling this week.
>
>Eddie
>
>Carl McConnell wrote:
>
>>Eddie,
>>
>>Thanks for the info. A build file such as you describe (requiring only
>>the location of a Beehive distribution and the web app to be compiled) is
>>exactly what I want. Is such a thing in the offing? I'm sure the Beehive
>>developers have bigger fish to fry, but this is a critical issue for us
>>Beehive consumers to resolve so we can define our dev environment. It may
>>seem on the trivial side, but for a newbie like me the Beehive recipe
>>isn't obvious. Some of the questions I've come up with in this regard are:
>>
>> 1. What exactly is in the Beehive distribution (jar files, tld files,
>> and so on)?
>> 2. In the Beehive distribution, which items are needed at web app
>> compile-time, and which at web app run-time?
>> 3. What non-Beehive pieces are needed to compile a Beehive-enabled web
>> app?
>> 4. What steps are involved in compiling a Beehive-enabled web app?
>>
>>It would be nice if the Beehive build process answered these questions by
>>producing (for example) a folder containing the Beehive distribution as
>>well as the artifacts (build script, properties file, batch file, and so
>>on) necessary to compile a web app, with no references to a Beehive dev build.
>>
>> Carl
>>
>>>Alex and Carl--
>>>
>>> The intention is that the build file in
>>> $BEEHIVE_HOME/test/ant/buildWebapp.xml is included as part of the
>>> Beehive distribution and is used to compile a Beehive webapp. It
>>> should just require the location of a Beehive distribution (not dev
>>> build) and a Beehive enabled webapp in order to build a webapp. In
>>> general, the file is pretty close and with a bit of refactoring can be
>>> most of the way there. The motivation to do this is that if we're
>>> using the same build file for the dev build and user distribution, the
>>> latter is guaranteed to always be in sync with the actual Beehive
>>> webapp build process.
>>>
>>> Alex, to answer your question, there isn't any specific documentation
>>> on the Beehive webapp build process right now other than that in the
>>> build file itself; it will eventually be on the wiki. Assuming you've
>>> got a webapp with the Beehive runtime, the steps are to basically build
>>> XSDs into XMLBeans, build Java files in WEB-INF/src, compile Controls
>>> and JPFs, and copy XML and other resources to WEB-INF/classes. Once
>>> that's done, the webapp is built and can be deployed on Tomcat using
>>> the Tomcat Ant tasks, the manager UI, etc.
>>> Hope that helps.
>>>
>>>Eddie
>>>
>>>
>>>
>>>Alexander Smirnoff wrote:
>>>
>>>>Thanks Eddie,
>>>>
>>>>Interesting article, somehow I missed that one.
>>>>
>>>>WSW 8.1 hides many actions when deploying web application. What
>>>>puzzles me in Beehive is exactly it: what needed to be done during
>>>>building/deployment process of application?
>>>>
>>>>Is there any Beehive doc on this process, except of scattered ant
>>>>build files? It would be great for me and any other folks on
>>>>Pollinate project thoroughly investigate this issue and for
>>>>beginning have a sort of short description of runtime and involved
>>>>ant tasks in build/deploy.
>>>>
>>>>Thanks,
>>>>Alex.
>>>>
>>>>
>>>>
>>>>>-----Original Message-----
>>>>>From: Eddie O'Neil [mailto:ekoneil@bea.com]
>>>>>Sent: August 5, 2004 10:42 AM
>>>>>To: Beehive Users
>>>>>Subject: Re: error on apt compilation
>>>>>
>>>>>
>>>>>Alex--
>>>>>
>>>>> No, you don't need Global.app, though if you have it, it
>>>>>must be in:
>>>>>
>>>>> WEB-INF/src/global/Global.app
>>>>>
>>>>>It's a top-level controller file (sort of like a Page Flow)
>>>>>that is used
>>>>>to have global actions and to manage state for the duration
>>>>>of a user
>>>>>session.
>>>>>
>>>>>An article covering Global.app is here:
>>>>>
>>>>>
>>>>>http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp
>>>>>
>>>>>Keep in mind that this covered the Workshop 8.1.x version
>>>>>of Global.app,
>>>>>which used Javadoc based metadata. The Beehive Global.app
>>>>>uses JDK 1.5
>>>>>metadata instead. Other than that, the functionality provided by
>>>>>Beehive's Global.app is basically the same.
>>>>>
>>>>> Hope that helps.
>>>>>
>>>>>Eddie
>>>>>
>>>>>
>>>>>
>>>>>Alexander Smirnoff wrote:
>>>>>
>>>>>
>>>>>
>>>>>>BTW, Do I need Global.app to run this test? What it for anyway?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>-----Original Message-----
>>>>>>>From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
>>>>>>>Sent: August 5, 2004 10:03 AM
>>>>>>>To: Beehive Users
>>>>>>>Subject: RE: error on apt compilation
>>>>>>>
>>>>>>>
>>>>>>>The environment is Eclipse (3.1 integration). But the compilation
>>>>>>>is made by normal ant process. I've even tried it without Eclipse
>>>>>>>in command line - the same result.
>>>>>>>
>>>>>>>I tried to reproduce almost the same ant project as found in
>>>>>>>test\ant\buildWebapp.xml, but I have feeling that I missed
>>>>>>>something... At least [apt] task is identical...
>>>>>>>
>>>>>>>Alex.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>-----Original Message-----
>>>>>>>>From: Sebastian Gozin [mailto:some@gamepoint.net]
>>>>>>>>Sent: August 5, 2004 9:56 AM
>>>>>>>>To: Beehive Users
>>>>>>>>Subject: Re: error on apt compilation
>>>>>>>>
>>>>>>>>
>>>>>>>>Could you tell us a bit more about this environment? Like
>>>>>>>>what IDE are
>>>>>>>>you using to edit source?
>>>>>>>>I find it strange to read the following
>>>>>>>>
>>>>>>>> [apt] __input:29: The package must be
>>>>>>>>"WEB-INF.tmp.miniTests.buttonSubmit"
>>>>>>>>
>>>>>>>>Makes me think a bit of netbeans changing the package
>>>>>>>>statements if you
>>>>>>>>opened the source file from the wrong filesystem.
>>>>>>>>
>>>>>>>>Sebastian
>>>>>>>>
>>>>>>>>
>>>>>>>>.Alexander Smirnoff wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>Hi,
>>>>>>>>>
>>>>>>>>>I'm trying to compile one of the simple tests from DRT in my own
>>>>>>>>>environment. Why am I getting this error?
>>>>>>>>>
>>>>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>>>>
>>>>>>>>>
>>>>>>>>"Begin.jsp" could
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>not be found in the web application.
>>>>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>>>>
>>>>>>>>>
>>>>>>>>"Begin.jsp" could
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>not be found in the web application.
>>>>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>>>>
>>>>>>>>>
>>>>>>>>"Begin.jsp" could
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>not be found in the web application.
>>>>>>>>> [apt] __input:29: The package must be
>>>>>>>>>"WEB-INF.tmp.miniTests.buttonSubmit".
>>>>>>>>> [apt] (source unavailable)
>>>>>>>>> [apt] 1 error
>>>>>>>>>
>>>>>>>>>it looks like apt tries to compile from tmp directory, but
>>>>>>>>>
>>>>>>>>>
>>>>>>>>cannot resolve
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>the package. Here is by built.xml:
>>>>>>>>>
>>>>>>>>><project default="all" basedir=".">
>>>>>>>>>
>>>>>>>>> <property name="src.dir" value="src"/>
>>>>>>>>> <property name="web.dir" value="WebRoot"/>
>>>>>>>>> <property name="lib.common" value="lib/common"/>
>>>>>>>>> <property name="lib.web" value="${web.dir}/WEB-INF/lib"/>
>>>>>>>>> <property name="lib.beehive" value="lib/beehive"/>
>>>>>>>>> <property name="tmp.dir" value="${web.dir}/WEB-INF/tmp"/>
>>>>>>>>>
>>>>>>>>> <path id="webapp.build.classpath">
>>>>>>>>> <pathelement
>>>>>>>>>
>>>>>>>>>
>>>>>>>>location="${web.dir}/WEB-INF/classes" />
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> <fileset dir="${lib.web}">
>>>>>>>>> <include name="*.jar" />
>>>>>>>>> </fileset>
>>>>>>>>> <fileset dir="${lib.common}">
>>>>>>>>> <include name="*.jar" />
>>>>>>>>> </fileset>
>>>>>>>>> </path>
>>>>>>>>> <target name="all">
>>>>>>>>> <delete dir="${tmp.dir}"
>>>>>>>>>
>>>>>>>>>
>>>>>>>includeEmptyDirs="true"/>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>> <javac srcdir="${src.dir}"
>>>>>>>>>destdir="${web.dir}/WEB-INF/classes"
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>classpathref="webapp.build.classpath"/>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> <taskdef name="apt"
>>>>>>>>>classname="org.apache.beehive.controls.runtime.generator
>>>>>.AptTask"
>>>>>
>>>>>
>>>>>>>>>classpath="${lib.beehive}/controls.jar;${lib.beehive}/beehi
>>>>>>>>>
>>>>>>>>>
>>>>>>>>ve-netui-compiler
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>.jar" onerror="report"/>
>>>>>>>>> <mkdir dir="${tmp.dir}"/>
>>>>>>>>>
>>>>>>>>> <path id="pageflow.build.classpath">
>>>>>>>>> <path refid="webapp.build.classpath"/>
>>>>>>>>> <fileset
>>>>>>>>>
>>>>>>>>>
>>>>>>>>file="${lib.beehive}/beehive-netui-compiler.jar"/>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> </path>
>>>>>>>>>
>>>>>>>>> <apt srcdir="${web.dir}"
>>>>>>>>>destdir="${web.dir}/WEB-INF/classes"
>>>>>>>>> gendir="${tmp.dir}"
>>>>>>>>> classpathref="pageflow.build.classpath"
>>>>>>>>>srcExtensions="*.app,*.jpf">
>>>>>>>>> </apt>
>>>>>>>>> </target>
>>>>>>>>></project>
>>>>>>>>>
>>>>>>>>>Thanks,
>>>>>>>>>
>>>>>>>>>Alex.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>
>>
Re: error on apt compilation
Posted by Eddie O'Neil <ek...@bea.com>.
Carl--
I actually think that defining the distribution and getting the build
producing it (even if we don't distribute it off of the website for the
near term) is actually pretty critical to getting people using Beehive.
To answer your questions, the best thing that Beehive could do is to
just produce that distribution in $BEEHIVE_HOME/build/dist. This would
need to be a self-contained directory that includes all of the pieces
necessary to:
- use controls
- create / use a NetUI webapp
- provide a build process that can handle each of these
I'll strike up a thread on the dev list that starts to answer your
four questions below and perhaps we can get something rolling this week.
Eddie
Carl McConnell wrote:
> Eddie,
>
> Thanks for the info. A build file such as you describe (requiring only
> the location of a Beehive distribution and the web app to be compiled)
> is exactly what I want. Is such a thing in the offing? I'm sure the
> Beehive developers have bigger fish to fry, but this is a critical
> issue for us Beehive consumers to resolve so we can define our dev
> environment. It may seem on the trivial side, but for a newbie like me
> the Beehive recipe isn't obvious. Some of the questions I've come up
> with in this regard are:
>
> 1. What exactly is in the Beehive distribution (jar files, tld
> files, and so on)?
> 2. In the Beehive distribution, which items are needed at web app
> compile-time, and which at web app run-time?
> 3. What non-Beehive pieces are needed to compile a Beehive-enabled
> web app?
> 4. What steps are involved in compiling a Beehive-enabled web app?
>
> It would be nice if the Beehive build process answered these questions
> by producing (for example) a folder containing the Beehive
> distribution as well as the artifacts (build script, properties file,
> batch file, and so on) necessary to compile a web app, with no
> references to a Beehive dev build.
>
> Carl
>
>> Alex and Carl--
>>
>> The intention is that the build file in
>> $BEEHIVE_HOME/test/ant/buildWebapp.xml is included as part of the
>> Beehive distribution and is used to compile a Beehive webapp. It
>> should just require the location of a Beehive distribution (not dev
>> build) and a Beehive enabled webapp in order to build a webapp. In
>> general, the file is pretty close and with a bit of refactoring can
>> be most of the way there. The motivation to do this is that if we're
>> using the same build file for the dev build and user distribution,
>> the latter is guaranteed to always be in sync with the actual Beehive
>> webapp build process.
>>
>> Alex, to answer your question, there isn't any specific
>> documentation on the Beehive webapp build process right now other
>> than that in the build file itself; it will eventually be on the
>> wiki. Assuming you've got a webapp with the Beehive runtime, the
>> steps are to basically build XSDs into XMLBeans, build Java files in
>> WEB-INF/src, compile Controls and JPFs, and copy XML and other
>> resources to WEB-INF/classes. Once that's done, the webapp is built
>> and can be deployed on Tomcat using the Tomcat Ant tasks, the manager
>> UI, etc.
>> Hope that helps.
>>
>> Eddie
>>
>>
>>
>> Alexander Smirnoff wrote:
>>
>>> Thanks Eddie,
>>>
>>> Interesting article, somehow I missed that one.
>>>
>>> WSW 8.1 hides many actions when deploying web application. What
>>> puzzles me in Beehive is exactly it: what needed to be done during
>>> building/deployment process of application?
>>>
>>> Is there any Beehive doc on this process, except of scattered ant
>>> build files? It would be great for me and any other folks on
>>> Pollinate project thoroughly investigate this issue and for
>>> beginning have a sort of short description of runtime and involved
>>> ant tasks in build/deploy.
>>>
>>> Thanks,
>>> Alex.
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Eddie O'Neil [mailto:ekoneil@bea.com]
>>>> Sent: August 5, 2004 10:42 AM
>>>> To: Beehive Users
>>>> Subject: Re: error on apt compilation
>>>>
>>>>
>>>> Alex--
>>>>
>>>> No, you don't need Global.app, though if you have it, it
>>>> must be in:
>>>>
>>>> WEB-INF/src/global/Global.app
>>>>
>>>> It's a top-level controller file (sort of like a Page Flow)
>>>> that is used
>>>> to have global actions and to manage state for the duration
>>>> of a user
>>>> session.
>>>>
>>>> An article covering Global.app is here:
>>>>
>>>>
>>>> http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp
>>>>
>>>> Keep in mind that this covered the Workshop 8.1.x version
>>>> of Global.app,
>>>> which used Javadoc based metadata. The Beehive Global.app
>>>> uses JDK 1.5
>>>> metadata instead. Other than that, the functionality provided by
>>>> Beehive's Global.app is basically the same.
>>>>
>>>> Hope that helps.
>>>>
>>>> Eddie
>>>>
>>>>
>>>>
>>>> Alexander Smirnoff wrote:
>>>>
>>>>
>>>>
>>>>> BTW, Do I need Global.app to run this test? What it for anyway?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
>>>>>> Sent: August 5, 2004 10:03 AM
>>>>>> To: Beehive Users
>>>>>> Subject: RE: error on apt compilation
>>>>>>
>>>>>>
>>>>>> The environment is Eclipse (3.1 integration). But the compilation
>>>>>> is made by normal ant process. I've even tried it without Eclipse
>>>>>> in command line - the same result.
>>>>>>
>>>>>> I tried to reproduce almost the same ant project as found in
>>>>>> test\ant\buildWebapp.xml, but I have feeling that I missed
>>>>>> something... At least [apt] task is identical...
>>>>>>
>>>>>> Alex.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Sebastian Gozin [mailto:some@gamepoint.net]
>>>>>>> Sent: August 5, 2004 9:56 AM
>>>>>>> To: Beehive Users
>>>>>>> Subject: Re: error on apt compilation
>>>>>>>
>>>>>>>
>>>>>>> Could you tell us a bit more about this environment? Like
>>>>>>> what IDE are
>>>>>>> you using to edit source?
>>>>>>> I find it strange to read the following
>>>>>>>
>>>>>>> [apt] __input:29: The package must be
>>>>>>> "WEB-INF.tmp.miniTests.buttonSubmit"
>>>>>>>
>>>>>>> Makes me think a bit of netbeans changing the package
>>>>>>> statements if you
>>>>>>> opened the source file from the wrong filesystem.
>>>>>>>
>>>>>>> Sebastian
>>>>>>>
>>>>>>>
>>>>>>> .Alexander Smirnoff wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I'm trying to compile one of the simple tests from DRT in my own
>>>>>>>> environment. Why am I getting this error?
>>>>>>>>
>>>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> "Begin.jsp" could
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> not be found in the web application.
>>>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> "Begin.jsp" could
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> not be found in the web application.
>>>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> "Begin.jsp" could
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> not be found in the web application.
>>>>>>>> [apt] __input:29: The package must be
>>>>>>>> "WEB-INF.tmp.miniTests.buttonSubmit".
>>>>>>>> [apt] (source unavailable)
>>>>>>>> [apt] 1 error
>>>>>>>>
>>>>>>>> it looks like apt tries to compile from tmp directory, but
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> cannot resolve
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> the package. Here is by built.xml:
>>>>>>>>
>>>>>>>> <project default="all" basedir=".">
>>>>>>>>
>>>>>>>> <property name="src.dir" value="src"/>
>>>>>>>> <property name="web.dir" value="WebRoot"/>
>>>>>>>> <property name="lib.common" value="lib/common"/>
>>>>>>>> <property name="lib.web" value="${web.dir}/WEB-INF/lib"/>
>>>>>>>> <property name="lib.beehive" value="lib/beehive"/>
>>>>>>>> <property name="tmp.dir" value="${web.dir}/WEB-INF/tmp"/>
>>>>>>>>
>>>>>>>> <path id="webapp.build.classpath">
>>>>>>>> <pathelement
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> location="${web.dir}/WEB-INF/classes" />
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> <fileset dir="${lib.web}">
>>>>>>>> <include name="*.jar" />
>>>>>>>> </fileset>
>>>>>>>> <fileset dir="${lib.common}">
>>>>>>>> <include name="*.jar" />
>>>>>>>> </fileset>
>>>>>>>> </path>
>>>>>>>> <target name="all">
>>>>>>>> <delete dir="${tmp.dir}"
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>> includeEmptyDirs="true"/>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>> <javac srcdir="${src.dir}"
>>>>>>>> destdir="${web.dir}/WEB-INF/classes"
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> classpathref="webapp.build.classpath"/>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> <taskdef name="apt"
>>>>>>>> classname="org.apache.beehive.controls.runtime.generator
>>>>>>>>
>>>> .AptTask"
>>>>
>>>>
>>>>>>>> classpath="${lib.beehive}/controls.jar;${lib.beehive}/beehi
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> ve-netui-compiler
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> .jar" onerror="report"/>
>>>>>>>> <mkdir dir="${tmp.dir}"/>
>>>>>>>>
>>>>>>>> <path id="pageflow.build.classpath">
>>>>>>>> <path refid="webapp.build.classpath"/>
>>>>>>>> <fileset
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> file="${lib.beehive}/beehive-netui-compiler.jar"/>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> </path>
>>>>>>>>
>>>>>>>> <apt srcdir="${web.dir}"
>>>>>>>> destdir="${web.dir}/WEB-INF/classes"
>>>>>>>> gendir="${tmp.dir}"
>>>>>>>> classpathref="pageflow.build.classpath"
>>>>>>>> srcExtensions="*.app,*.jpf">
>>>>>>>> </apt>
>>>>>>>> </target>
>>>>>>>> </project>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Alex.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>
>
>
Re: error on apt compilation
Posted by Carl McConnell <ca...@instantiations.com>.
Eddie,
Thanks for the info. A build file such as you describe (requiring only the
location of a Beehive distribution and the web app to be compiled) is
exactly what I want. Is such a thing in the offing? I'm sure the Beehive
developers have bigger fish to fry, but this is a critical issue for us
Beehive consumers to resolve so we can define our dev environment. It may
seem on the trivial side, but for a newbie like me the Beehive recipe isn't
obvious. Some of the questions I've come up with in this regard are:
1. What exactly is in the Beehive distribution (jar files, tld files,
and so on)?
2. In the Beehive distribution, which items are needed at web app
compile-time, and which at web app run-time?
3. What non-Beehive pieces are needed to compile a Beehive-enabled web app?
4. What steps are involved in compiling a Beehive-enabled web app?
It would be nice if the Beehive build process answered these questions by
producing (for example) a folder containing the Beehive distribution as
well as the artifacts (build script, properties file, batch file, and so
on) necessary to compile a web app, with no references to a Beehive dev build.
Carl
>Alex and Carl--
>
> The intention is that the build file in
> $BEEHIVE_HOME/test/ant/buildWebapp.xml is included as part of the Beehive
> distribution and is used to compile a Beehive webapp. It should just
> require the location of a Beehive distribution (not dev build) and a
> Beehive enabled webapp in order to build a webapp. In general, the file
> is pretty close and with a bit of refactoring can be most of the way
> there. The motivation to do this is that if we're using the same build
> file for the dev build and user distribution, the latter is guaranteed to
> always be in sync with the actual Beehive webapp build process.
>
> Alex, to answer your question, there isn't any specific documentation on
> the Beehive webapp build process right now other than that in the build
> file itself; it will eventually be on the wiki. Assuming you've got a
> webapp with the Beehive runtime, the steps are to basically build XSDs
> into XMLBeans, build Java files in WEB-INF/src, compile Controls and
> JPFs, and copy XML and other resources to WEB-INF/classes. Once that's
> done, the webapp is built and can be deployed on Tomcat using the Tomcat
> Ant tasks, the manager UI, etc.
> Hope that helps.
>
>Eddie
>
>
>
>Alexander Smirnoff wrote:
>
>>Thanks Eddie,
>>
>>Interesting article, somehow I missed that one.
>>
>>WSW 8.1 hides many actions when deploying web application. What
>>puzzles me in Beehive is exactly it: what needed to be done during
>>building/deployment process of application?
>>
>>Is there any Beehive doc on this process, except of scattered ant
>>build files? It would be great for me and any other folks on
>>Pollinate project thoroughly investigate this issue and for
>>beginning have a sort of short description of runtime and involved
>>ant tasks in build/deploy.
>>
>>Thanks,
>>Alex.
>>
>>
>>
>>>-----Original Message-----
>>>From: Eddie O'Neil [mailto:ekoneil@bea.com]
>>>Sent: August 5, 2004 10:42 AM
>>>To: Beehive Users
>>>Subject: Re: error on apt compilation
>>>
>>>
>>>Alex--
>>>
>>> No, you don't need Global.app, though if you have it, it
>>>must be in:
>>>
>>> WEB-INF/src/global/Global.app
>>>
>>>It's a top-level controller file (sort of like a Page Flow)
>>>that is used
>>>to have global actions and to manage state for the duration
>>>of a user
>>>session.
>>>
>>>An article covering Global.app is here:
>>>
>>>
>>>http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp
>>>
>>>Keep in mind that this covered the Workshop 8.1.x version
>>>of Global.app,
>>>which used Javadoc based metadata. The Beehive Global.app
>>>uses JDK 1.5
>>>metadata instead. Other than that, the functionality provided by
>>>Beehive's Global.app is basically the same.
>>>
>>> Hope that helps.
>>>
>>>Eddie
>>>
>>>
>>>
>>>Alexander Smirnoff wrote:
>>>
>>>
>>>
>>>>BTW, Do I need Global.app to run this test? What it for anyway?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>-----Original Message-----
>>>>>From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
>>>>>Sent: August 5, 2004 10:03 AM
>>>>>To: Beehive Users
>>>>>Subject: RE: error on apt compilation
>>>>>
>>>>>
>>>>>The environment is Eclipse (3.1 integration). But the compilation
>>>>>is made by normal ant process. I've even tried it without Eclipse
>>>>>in command line - the same result.
>>>>>
>>>>>I tried to reproduce almost the same ant project as found in
>>>>>test\ant\buildWebapp.xml, but I have feeling that I missed
>>>>>something... At least [apt] task is identical...
>>>>>
>>>>>Alex.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>-----Original Message-----
>>>>>>From: Sebastian Gozin [mailto:some@gamepoint.net]
>>>>>>Sent: August 5, 2004 9:56 AM
>>>>>>To: Beehive Users
>>>>>>Subject: Re: error on apt compilation
>>>>>>
>>>>>>
>>>>>>Could you tell us a bit more about this environment? Like
>>>>>>what IDE are
>>>>>>you using to edit source?
>>>>>>I find it strange to read the following
>>>>>>
>>>>>> [apt] __input:29: The package must be
>>>>>>"WEB-INF.tmp.miniTests.buttonSubmit"
>>>>>>
>>>>>>Makes me think a bit of netbeans changing the package
>>>>>>statements if you
>>>>>>opened the source file from the wrong filesystem.
>>>>>>
>>>>>>Sebastian
>>>>>>
>>>>>>
>>>>>>.Alexander Smirnoff wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Hi,
>>>>>>>
>>>>>>>I'm trying to compile one of the simple tests from DRT in my own
>>>>>>>environment. Why am I getting this error?
>>>>>>>
>>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>"Begin.jsp" could
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>not be found in the web application.
>>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>"Begin.jsp" could
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>not be found in the web application.
>>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>"Begin.jsp" could
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>not be found in the web application.
>>>>>>> [apt] __input:29: The package must be
>>>>>>>"WEB-INF.tmp.miniTests.buttonSubmit".
>>>>>>> [apt] (source unavailable)
>>>>>>> [apt] 1 error
>>>>>>>
>>>>>>>it looks like apt tries to compile from tmp directory, but
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>cannot resolve
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>the package. Here is by built.xml:
>>>>>>>
>>>>>>><project default="all" basedir=".">
>>>>>>>
>>>>>>> <property name="src.dir" value="src"/>
>>>>>>> <property name="web.dir" value="WebRoot"/>
>>>>>>> <property name="lib.common" value="lib/common"/>
>>>>>>> <property name="lib.web" value="${web.dir}/WEB-INF/lib"/>
>>>>>>> <property name="lib.beehive" value="lib/beehive"/>
>>>>>>> <property name="tmp.dir" value="${web.dir}/WEB-INF/tmp"/>
>>>>>>>
>>>>>>> <path id="webapp.build.classpath">
>>>>>>> <pathelement
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>location="${web.dir}/WEB-INF/classes" />
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> <fileset dir="${lib.web}">
>>>>>>> <include name="*.jar" />
>>>>>>> </fileset>
>>>>>>> <fileset dir="${lib.common}">
>>>>>>> <include name="*.jar" />
>>>>>>> </fileset>
>>>>>>> </path>
>>>>>>> <target name="all">
>>>>>>> <delete dir="${tmp.dir}"
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>includeEmptyDirs="true"/>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>> <javac srcdir="${src.dir}"
>>>>>>>destdir="${web.dir}/WEB-INF/classes"
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>classpathref="webapp.build.classpath"/>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> <taskdef name="apt"
>>>>>>>classname="org.apache.beehive.controls.runtime.generator
>>>>>>>
>>>.AptTask"
>>>
>>>
>>>>>>>classpath="${lib.beehive}/controls.jar;${lib.beehive}/beehi
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>ve-netui-compiler
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>.jar" onerror="report"/>
>>>>>>> <mkdir dir="${tmp.dir}"/>
>>>>>>>
>>>>>>> <path id="pageflow.build.classpath">
>>>>>>> <path refid="webapp.build.classpath"/>
>>>>>>> <fileset
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>file="${lib.beehive}/beehive-netui-compiler.jar"/>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> </path>
>>>>>>>
>>>>>>> <apt srcdir="${web.dir}"
>>>>>>>destdir="${web.dir}/WEB-INF/classes"
>>>>>>> gendir="${tmp.dir}"
>>>>>>> classpathref="pageflow.build.classpath"
>>>>>>>srcExtensions="*.app,*.jpf">
>>>>>>> </apt>
>>>>>>> </target>
>>>>>>></project>
>>>>>>>
>>>>>>>Thanks,
>>>>>>>
>>>>>>>Alex.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>>
Re: error on apt compilation
Posted by Eddie O'Neil <ek...@bea.com>.
Alex--
The ".tmpbeansrc" directory is set as the Ant property
"tmp.sourcegen.dir" in $BEEHIVE_HOME/test/ant/buidlWebapp.xml. It's not
externalized right now from that build file, so external callers can't
override it presently. It's certainly something that should be done
when we start producing a distribution than just having a dev tree.
As far as the Ant below to get a NetUI webapp template, I'll spout a
little bit of build philosophy here. :) Because that target is buried
in a NetUI Ant file and isn't exposed at the
$BEEHIVE_HOME/netui/build.xml file level, we think of it as "internal"
to NetUI, so for your build's stability, it's often best to not take
dependencies on it. I'll add a target in the
$BEEHIVE_HOME/netui/build.xml file that does the same thing and
insulates the caller from the actual "webappTemplate.xml" build file.
One of the components of a Beehive distribution is a NetUI webapp
template that includes support for controls and XMLBeans along with
NetUI. To make a new webapp, you'll just need to copy the directory
somewhere and give it a name.
Hope that helps.
Eddie
Alexander Smirnoff wrote:
>Thanks to all who helped me resolve the first problems
>with Beehive.
>
>I've finally find the reason why my simple application
>was not compiling: there is some hardcoded dependency
>to the name of temporary directory "gendir" attribute
>in apt task (if the name is not .tmpbeansrc you'll
>get a problem during compilation). Try to change it
>so something else like ".tmp" for example. Looks
>like a bug to me.
>
>To all Pollinate and other folks: there is a neat ant
>project file "webappTemplate.xml" that you can use to
>populate your first projects with Beehive runtime.
>
>Here is how to use it:
>
>1. cd to: <beehive_home>/netui/ant
>2. run:
>ant -f webappTemplate.xml
> -Dwebapp.dist.dir=<your_web_root_directory_path>
>
>This will populate your isolated Web root directory
>with Beehive runtime libraries.
>
>I was finally able to run the application on Tomcat 5
>It worked even with Eclipse 3.0 under MyEclipseIDE
>plugin...
>
>Regards,
>Alex.
>
>
>
>
>>-----Original Message-----
>>From: Eddie O'Neil [mailto:ekoneil@bea.com]
>>Sent: August 5, 2004 11:44 PM
>>To: Beehive Users
>>Subject: Re: error on apt compilation
>>
>>
>>Alex and Carl--
>>
>> The intention is that the build file in
>>$BEEHIVE_HOME/test/ant/buildWebapp.xml is included as part of the
>>Beehive distribution and is used to compile a Beehive
>>webapp. It should
>>just require the location of a Beehive distribution (not
>>dev build) and
>>a Beehive enabled webapp in order to build a webapp. In
>>general, the
>>file is pretty close and with a bit of refactoring can be
>>most of the
>>way there. The motivation to do this is that if we're
>>using the same
>>build file for the dev build and user distribution, the latter is
>>guaranteed to always be in sync with the actual Beehive
>>webapp build
>>process.
>>
>> Alex, to answer your question, there isn't any specific
>>documentation
>>on the Beehive webapp build process right now other than
>>that in the
>>build file itself; it will eventually be on the wiki.
>>Assuming you've
>>got a webapp with the Beehive runtime, the steps are to
>>basically build
>>XSDs into XMLBeans, build Java files in WEB-INF/src,
>>compile Controls
>>and JPFs, and copy XML and other resources to
>>WEB-INF/classes. Once
>>that's done, the webapp is built and can be deployed on
>>Tomcat using the
>>Tomcat Ant tasks, the manager UI, etc.
>>
>> Hope that helps.
>>
>>Eddie
>>
>>
>>
>>Alexander Smirnoff wrote:
>>
>>
>>
>>>Thanks Eddie,
>>>
>>>Interesting article, somehow I missed that one.
>>>
>>>WSW 8.1 hides many actions when deploying web application. What
>>>puzzles me in Beehive is exactly it: what needed to be done during
>>>building/deployment process of application?
>>>
>>>Is there any Beehive doc on this process, except of scattered ant
>>>build files? It would be great for me and any other folks on
>>>Pollinate project thoroughly investigate this issue and for
>>>beginning have a sort of short description of runtime and involved
>>>ant tasks in build/deploy.
>>>
>>>Thanks,
>>>Alex.
>>>
>>>
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Eddie O'Neil [mailto:ekoneil@bea.com]
>>>>Sent: August 5, 2004 10:42 AM
>>>>To: Beehive Users
>>>>Subject: Re: error on apt compilation
>>>>
>>>>
>>>>Alex--
>>>>
>>>> No, you don't need Global.app, though if you have it, it
>>>>must be in:
>>>>
>>>> WEB-INF/src/global/Global.app
>>>>
>>>>It's a top-level controller file (sort of like a Page Flow)
>>>>that is used
>>>>to have global actions and to manage state for the duration
>>>>of a user
>>>>session.
>>>>
>>>>An article covering Global.app is here:
>>>>
>>>>
>>>>http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp
>>>>
>>>>Keep in mind that this covered the Workshop 8.1.x version
>>>>of Global.app,
>>>>which used Javadoc based metadata. The Beehive Global.app
>>>>uses JDK 1.5
>>>>metadata instead. Other than that, the functionality provided by
>>>>Beehive's Global.app is basically the same.
>>>>
>>>> Hope that helps.
>>>>
>>>>Eddie
>>>>
>>>>
>>>>
>>>>Alexander Smirnoff wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>BTW, Do I need Global.app to run this test? What it for anyway?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>-----Original Message-----
>>>>>>From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
>>>>>>Sent: August 5, 2004 10:03 AM
>>>>>>To: Beehive Users
>>>>>>Subject: RE: error on apt compilation
>>>>>>
>>>>>>
>>>>>>The environment is Eclipse (3.1 integration). But the
>>>>>>
>>>>>>
>>compilation
>>
>>
>>>>>>is made by normal ant process. I've even tried it
>>>>>>
>>>>>>
>>without Eclipse
>>
>>
>>>>>>in command line - the same result.
>>>>>>
>>>>>>I tried to reproduce almost the same ant project as found in
>>>>>>test\ant\buildWebapp.xml, but I have feeling that I missed
>>>>>>something... At least [apt] task is identical...
>>>>>>
>>>>>>Alex.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>-----Original Message-----
>>>>>>>From: Sebastian Gozin [mailto:some@gamepoint.net]
>>>>>>>Sent: August 5, 2004 9:56 AM
>>>>>>>To: Beehive Users
>>>>>>>Subject: Re: error on apt compilation
>>>>>>>
>>>>>>>
>>>>>>>Could you tell us a bit more about this environment? Like
>>>>>>>what IDE are
>>>>>>>you using to edit source?
>>>>>>>I find it strange to read the following
>>>>>>>
>>>>>>> [apt] __input:29: The package must be
>>>>>>>"WEB-INF.tmp.miniTests.buttonSubmit"
>>>>>>>
>>>>>>>Makes me think a bit of netbeans changing the package
>>>>>>>statements if you
>>>>>>>opened the source file from the wrong filesystem.
>>>>>>>
>>>>>>>Sebastian
>>>>>>>
>>>>>>>
>>>>>>>.Alexander Smirnoff wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>Hi,
>>>>>>>>
>>>>>>>>I'm trying to compile one of the simple tests from
>>>>>>>>
>>>>>>>>
>>DRT in my own
>>
>>
>>>>>>>>environment. Why am I getting this error?
>>>>>>>>
>>>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>"Begin.jsp" could
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>not be found in the web application.
>>>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>"Begin.jsp" could
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>not be found in the web application.
>>>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>"Begin.jsp" could
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>not be found in the web application.
>>>>>>>> [apt] __input:29: The package must be
>>>>>>>>"WEB-INF.tmp.miniTests.buttonSubmit".
>>>>>>>> [apt] (source unavailable)
>>>>>>>> [apt] 1 error
>>>>>>>>
>>>>>>>>it looks like apt tries to compile from tmp directory, but
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>cannot resolve
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>the package. Here is by built.xml:
>>>>>>>>
>>>>>>>><project default="all" basedir=".">
>>>>>>>>
>>>>>>>> <property name="src.dir" value="src"/>
>>>>>>>> <property name="web.dir" value="WebRoot"/>
>>>>>>>> <property name="lib.common" value="lib/common"/>
>>>>>>>> <property name="lib.web"
>>>>>>>>
>>>>>>>>
>>value="${web.dir}/WEB-INF/lib"/>
>>
>>
>>>>>>>> <property name="lib.beehive" value="lib/beehive"/>
>>>>>>>> <property name="tmp.dir"
>>>>>>>>
>>>>>>>>
>>value="${web.dir}/WEB-INF/tmp"/>
>>
>>
>>>>>>>> <path id="webapp.build.classpath">
>>>>>>>> <pathelement
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>location="${web.dir}/WEB-INF/classes" />
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> <fileset dir="${lib.web}">
>>>>>>>> <include name="*.jar" />
>>>>>>>> </fileset>
>>>>>>>> <fileset dir="${lib.common}">
>>>>>>>> <include name="*.jar" />
>>>>>>>> </fileset>
>>>>>>>> </path>
>>>>>>>> <target name="all">
>>>>>>>> <delete dir="${tmp.dir}"
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>includeEmptyDirs="true"/>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>> <javac srcdir="${src.dir}"
>>>>>>>>destdir="${web.dir}/WEB-INF/classes"
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>classpathref="webapp.build.classpath"/>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> <taskdef name="apt"
>>>>>>>>classname="org.apache.beehive.controls.runtime.generator
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>.AptTask"
>>>>
>>>>
>>>>
>>>>
>>>>>>>>classpath="${lib.beehive}/controls.jar;${lib.beehive}/beehi
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>ve-netui-compiler
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>.jar" onerror="report"/>
>>>>>>>> <mkdir dir="${tmp.dir}"/>
>>>>>>>>
>>>>>>>> <path id="pageflow.build.classpath">
>>>>>>>> <path refid="webapp.build.classpath"/>
>>>>>>>> <fileset
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>file="${lib.beehive}/beehive-netui-compiler.jar"/>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> </path>
>>>>>>>>
>>>>>>>> <apt srcdir="${web.dir}"
>>>>>>>>destdir="${web.dir}/WEB-INF/classes"
>>>>>>>> gendir="${tmp.dir}"
>>>>>>>> classpathref="pageflow.build.classpath"
>>>>>>>>srcExtensions="*.app,*.jpf">
>>>>>>>> </apt>
>>>>>>>> </target>
>>>>>>>></project>
>>>>>>>>
>>>>>>>>Thanks,
>>>>>>>>
>>>>>>>>Alex.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>>>
>
>
>
>
>
RE: error on apt compilation
Posted by Alexander Smirnoff <as...@vistar.ca>.
Thanks to all who helped me resolve the first problems
with Beehive.
I've finally find the reason why my simple application
was not compiling: there is some hardcoded dependency
to the name of temporary directory "gendir" attribute
in apt task (if the name is not .tmpbeansrc you'll
get a problem during compilation). Try to change it
so something else like ".tmp" for example. Looks
like a bug to me.
To all Pollinate and other folks: there is a neat ant
project file "webappTemplate.xml" that you can use to
populate your first projects with Beehive runtime.
Here is how to use it:
1. cd to: <beehive_home>/netui/ant
2. run:
ant -f webappTemplate.xml
-Dwebapp.dist.dir=<your_web_root_directory_path>
This will populate your isolated Web root directory
with Beehive runtime libraries.
I was finally able to run the application on Tomcat 5
It worked even with Eclipse 3.0 under MyEclipseIDE
plugin...
Regards,
Alex.
> -----Original Message-----
> From: Eddie O'Neil [mailto:ekoneil@bea.com]
> Sent: August 5, 2004 11:44 PM
> To: Beehive Users
> Subject: Re: error on apt compilation
>
>
> Alex and Carl--
>
> The intention is that the build file in
> $BEEHIVE_HOME/test/ant/buildWebapp.xml is included as part of the
> Beehive distribution and is used to compile a Beehive
> webapp. It should
> just require the location of a Beehive distribution (not
> dev build) and
> a Beehive enabled webapp in order to build a webapp. In
> general, the
> file is pretty close and with a bit of refactoring can be
> most of the
> way there. The motivation to do this is that if we're
> using the same
> build file for the dev build and user distribution, the latter is
> guaranteed to always be in sync with the actual Beehive
> webapp build
> process.
>
> Alex, to answer your question, there isn't any specific
> documentation
> on the Beehive webapp build process right now other than
> that in the
> build file itself; it will eventually be on the wiki.
> Assuming you've
> got a webapp with the Beehive runtime, the steps are to
> basically build
> XSDs into XMLBeans, build Java files in WEB-INF/src,
> compile Controls
> and JPFs, and copy XML and other resources to
> WEB-INF/classes. Once
> that's done, the webapp is built and can be deployed on
> Tomcat using the
> Tomcat Ant tasks, the manager UI, etc.
>
> Hope that helps.
>
> Eddie
>
>
>
> Alexander Smirnoff wrote:
>
> >Thanks Eddie,
> >
> >Interesting article, somehow I missed that one.
> >
> >WSW 8.1 hides many actions when deploying web application. What
> >puzzles me in Beehive is exactly it: what needed to be done during
> >building/deployment process of application?
> >
> >Is there any Beehive doc on this process, except of scattered ant
> >build files? It would be great for me and any other folks on
> >Pollinate project thoroughly investigate this issue and for
> >beginning have a sort of short description of runtime and involved
> >ant tasks in build/deploy.
> >
> >Thanks,
> >Alex.
> >
> >
> >
> >>-----Original Message-----
> >>From: Eddie O'Neil [mailto:ekoneil@bea.com]
> >>Sent: August 5, 2004 10:42 AM
> >>To: Beehive Users
> >>Subject: Re: error on apt compilation
> >>
> >>
> >>Alex--
> >>
> >> No, you don't need Global.app, though if you have it, it
> >>must be in:
> >>
> >> WEB-INF/src/global/Global.app
> >>
> >>It's a top-level controller file (sort of like a Page Flow)
> >>that is used
> >>to have global actions and to manage state for the duration
> >>of a user
> >>session.
> >>
> >>An article covering Global.app is here:
> >>
> >>
> >>http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp
> >>
> >>Keep in mind that this covered the Workshop 8.1.x version
> >>of Global.app,
> >>which used Javadoc based metadata. The Beehive Global.app
> >>uses JDK 1.5
> >>metadata instead. Other than that, the functionality provided by
> >>Beehive's Global.app is basically the same.
> >>
> >> Hope that helps.
> >>
> >>Eddie
> >>
> >>
> >>
> >>Alexander Smirnoff wrote:
> >>
> >>
> >>
> >>>BTW, Do I need Global.app to run this test? What it for anyway?
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>>-----Original Message-----
> >>>>From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
> >>>>Sent: August 5, 2004 10:03 AM
> >>>>To: Beehive Users
> >>>>Subject: RE: error on apt compilation
> >>>>
> >>>>
> >>>>The environment is Eclipse (3.1 integration). But the
> compilation
> >>>>is made by normal ant process. I've even tried it
> without Eclipse
> >>>>in command line - the same result.
> >>>>
> >>>>I tried to reproduce almost the same ant project as found in
> >>>>test\ant\buildWebapp.xml, but I have feeling that I missed
> >>>>something... At least [apt] task is identical...
> >>>>
> >>>>Alex.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>-----Original Message-----
> >>>>>From: Sebastian Gozin [mailto:some@gamepoint.net]
> >>>>>Sent: August 5, 2004 9:56 AM
> >>>>>To: Beehive Users
> >>>>>Subject: Re: error on apt compilation
> >>>>>
> >>>>>
> >>>>>Could you tell us a bit more about this environment? Like
> >>>>>what IDE are
> >>>>>you using to edit source?
> >>>>>I find it strange to read the following
> >>>>>
> >>>>> [apt] __input:29: The package must be
> >>>>>"WEB-INF.tmp.miniTests.buttonSubmit"
> >>>>>
> >>>>>Makes me think a bit of netbeans changing the package
> >>>>>statements if you
> >>>>>opened the source file from the wrong filesystem.
> >>>>>
> >>>>>Sebastian
> >>>>>
> >>>>>
> >>>>>.Alexander Smirnoff wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Hi,
> >>>>>>
> >>>>>>I'm trying to compile one of the simple tests from
> DRT in my own
> >>>>>>environment. Why am I getting this error?
> >>>>>>
> >>>>>> [apt] warning on annotation value "Begin.jsp": File
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>"Begin.jsp" could
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>not be found in the web application.
> >>>>>> [apt] warning on annotation value "Begin.jsp": File
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>"Begin.jsp" could
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>not be found in the web application.
> >>>>>> [apt] warning on annotation value "Begin.jsp": File
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>"Begin.jsp" could
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>not be found in the web application.
> >>>>>> [apt] __input:29: The package must be
> >>>>>>"WEB-INF.tmp.miniTests.buttonSubmit".
> >>>>>> [apt] (source unavailable)
> >>>>>> [apt] 1 error
> >>>>>>
> >>>>>>it looks like apt tries to compile from tmp directory, but
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>cannot resolve
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>the package. Here is by built.xml:
> >>>>>>
> >>>>>><project default="all" basedir=".">
> >>>>>>
> >>>>>> <property name="src.dir" value="src"/>
> >>>>>> <property name="web.dir" value="WebRoot"/>
> >>>>>> <property name="lib.common" value="lib/common"/>
> >>>>>> <property name="lib.web"
> value="${web.dir}/WEB-INF/lib"/>
> >>>>>> <property name="lib.beehive" value="lib/beehive"/>
> >>>>>> <property name="tmp.dir"
> value="${web.dir}/WEB-INF/tmp"/>
> >>>>>>
> >>>>>> <path id="webapp.build.classpath">
> >>>>>> <pathelement
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>location="${web.dir}/WEB-INF/classes" />
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> <fileset dir="${lib.web}">
> >>>>>> <include name="*.jar" />
> >>>>>> </fileset>
> >>>>>> <fileset dir="${lib.common}">
> >>>>>> <include name="*.jar" />
> >>>>>> </fileset>
> >>>>>> </path>
> >>>>>> <target name="all">
> >>>>>> <delete dir="${tmp.dir}"
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>includeEmptyDirs="true"/>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>> <javac srcdir="${src.dir}"
> >>>>>>destdir="${web.dir}/WEB-INF/classes"
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>classpathref="webapp.build.classpath"/>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> <taskdef name="apt"
> >>>>>>classname="org.apache.beehive.controls.runtime.generator
> >>>>>>
> >>>>>>
> >>.AptTask"
> >>
> >>
> >>>>>>classpath="${lib.beehive}/controls.jar;${lib.beehive}/beehi
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>ve-netui-compiler
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>.jar" onerror="report"/>
> >>>>>> <mkdir dir="${tmp.dir}"/>
> >>>>>>
> >>>>>> <path id="pageflow.build.classpath">
> >>>>>> <path refid="webapp.build.classpath"/>
> >>>>>> <fileset
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>file="${lib.beehive}/beehive-netui-compiler.jar"/>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> </path>
> >>>>>>
> >>>>>> <apt srcdir="${web.dir}"
> >>>>>>destdir="${web.dir}/WEB-INF/classes"
> >>>>>> gendir="${tmp.dir}"
> >>>>>> classpathref="pageflow.build.classpath"
> >>>>>>srcExtensions="*.app,*.jpf">
> >>>>>> </apt>
> >>>>>> </target>
> >>>>>></project>
> >>>>>>
> >>>>>>Thanks,
> >>>>>>
> >>>>>>Alex.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >
> >
> >
> >
> >
>
Re: error on apt compilation
Posted by Eddie O'Neil <ek...@bea.com>.
Alex and Carl--
The intention is that the build file in
$BEEHIVE_HOME/test/ant/buildWebapp.xml is included as part of the
Beehive distribution and is used to compile a Beehive webapp. It should
just require the location of a Beehive distribution (not dev build) and
a Beehive enabled webapp in order to build a webapp. In general, the
file is pretty close and with a bit of refactoring can be most of the
way there. The motivation to do this is that if we're using the same
build file for the dev build and user distribution, the latter is
guaranteed to always be in sync with the actual Beehive webapp build
process.
Alex, to answer your question, there isn't any specific documentation
on the Beehive webapp build process right now other than that in the
build file itself; it will eventually be on the wiki. Assuming you've
got a webapp with the Beehive runtime, the steps are to basically build
XSDs into XMLBeans, build Java files in WEB-INF/src, compile Controls
and JPFs, and copy XML and other resources to WEB-INF/classes. Once
that's done, the webapp is built and can be deployed on Tomcat using the
Tomcat Ant tasks, the manager UI, etc.
Hope that helps.
Eddie
Alexander Smirnoff wrote:
>Thanks Eddie,
>
>Interesting article, somehow I missed that one.
>
>WSW 8.1 hides many actions when deploying web application. What
>puzzles me in Beehive is exactly it: what needed to be done during
>building/deployment process of application?
>
>Is there any Beehive doc on this process, except of scattered ant
>build files? It would be great for me and any other folks on
>Pollinate project thoroughly investigate this issue and for
>beginning have a sort of short description of runtime and involved
>ant tasks in build/deploy.
>
>Thanks,
>Alex.
>
>
>
>>-----Original Message-----
>>From: Eddie O'Neil [mailto:ekoneil@bea.com]
>>Sent: August 5, 2004 10:42 AM
>>To: Beehive Users
>>Subject: Re: error on apt compilation
>>
>>
>>Alex--
>>
>> No, you don't need Global.app, though if you have it, it
>>must be in:
>>
>> WEB-INF/src/global/Global.app
>>
>>It's a top-level controller file (sort of like a Page Flow)
>>that is used
>>to have global actions and to manage state for the duration
>>of a user
>>session.
>>
>>An article covering Global.app is here:
>>
>>
>>http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp
>>
>>Keep in mind that this covered the Workshop 8.1.x version
>>of Global.app,
>>which used Javadoc based metadata. The Beehive Global.app
>>uses JDK 1.5
>>metadata instead. Other than that, the functionality provided by
>>Beehive's Global.app is basically the same.
>>
>> Hope that helps.
>>
>>Eddie
>>
>>
>>
>>Alexander Smirnoff wrote:
>>
>>
>>
>>>BTW, Do I need Global.app to run this test? What it for anyway?
>>>
>>>
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
>>>>Sent: August 5, 2004 10:03 AM
>>>>To: Beehive Users
>>>>Subject: RE: error on apt compilation
>>>>
>>>>
>>>>The environment is Eclipse (3.1 integration). But the compilation
>>>>is made by normal ant process. I've even tried it without Eclipse
>>>>in command line - the same result.
>>>>
>>>>I tried to reproduce almost the same ant project as found in
>>>>test\ant\buildWebapp.xml, but I have feeling that I missed
>>>>something... At least [apt] task is identical...
>>>>
>>>>Alex.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>-----Original Message-----
>>>>>From: Sebastian Gozin [mailto:some@gamepoint.net]
>>>>>Sent: August 5, 2004 9:56 AM
>>>>>To: Beehive Users
>>>>>Subject: Re: error on apt compilation
>>>>>
>>>>>
>>>>>Could you tell us a bit more about this environment? Like
>>>>>what IDE are
>>>>>you using to edit source?
>>>>>I find it strange to read the following
>>>>>
>>>>> [apt] __input:29: The package must be
>>>>>"WEB-INF.tmp.miniTests.buttonSubmit"
>>>>>
>>>>>Makes me think a bit of netbeans changing the package
>>>>>statements if you
>>>>>opened the source file from the wrong filesystem.
>>>>>
>>>>>Sebastian
>>>>>
>>>>>
>>>>>.Alexander Smirnoff wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Hi,
>>>>>>
>>>>>>I'm trying to compile one of the simple tests from DRT in my own
>>>>>>environment. Why am I getting this error?
>>>>>>
>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>"Begin.jsp" could
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>not be found in the web application.
>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>"Begin.jsp" could
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>not be found in the web application.
>>>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>"Begin.jsp" could
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>not be found in the web application.
>>>>>> [apt] __input:29: The package must be
>>>>>>"WEB-INF.tmp.miniTests.buttonSubmit".
>>>>>> [apt] (source unavailable)
>>>>>> [apt] 1 error
>>>>>>
>>>>>>it looks like apt tries to compile from tmp directory, but
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>cannot resolve
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>the package. Here is by built.xml:
>>>>>>
>>>>>><project default="all" basedir=".">
>>>>>>
>>>>>> <property name="src.dir" value="src"/>
>>>>>> <property name="web.dir" value="WebRoot"/>
>>>>>> <property name="lib.common" value="lib/common"/>
>>>>>> <property name="lib.web" value="${web.dir}/WEB-INF/lib"/>
>>>>>> <property name="lib.beehive" value="lib/beehive"/>
>>>>>> <property name="tmp.dir" value="${web.dir}/WEB-INF/tmp"/>
>>>>>>
>>>>>> <path id="webapp.build.classpath">
>>>>>> <pathelement
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>location="${web.dir}/WEB-INF/classes" />
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> <fileset dir="${lib.web}">
>>>>>> <include name="*.jar" />
>>>>>> </fileset>
>>>>>> <fileset dir="${lib.common}">
>>>>>> <include name="*.jar" />
>>>>>> </fileset>
>>>>>> </path>
>>>>>> <target name="all">
>>>>>> <delete dir="${tmp.dir}"
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>includeEmptyDirs="true"/>
>>>>
>>>>
>>>>
>>>>
>>>>>> <javac srcdir="${src.dir}"
>>>>>>destdir="${web.dir}/WEB-INF/classes"
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>classpathref="webapp.build.classpath"/>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> <taskdef name="apt"
>>>>>>classname="org.apache.beehive.controls.runtime.generator
>>>>>>
>>>>>>
>>.AptTask"
>>
>>
>>>>>>classpath="${lib.beehive}/controls.jar;${lib.beehive}/beehi
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>ve-netui-compiler
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>.jar" onerror="report"/>
>>>>>> <mkdir dir="${tmp.dir}"/>
>>>>>>
>>>>>> <path id="pageflow.build.classpath">
>>>>>> <path refid="webapp.build.classpath"/>
>>>>>> <fileset
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>file="${lib.beehive}/beehive-netui-compiler.jar"/>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> </path>
>>>>>>
>>>>>> <apt srcdir="${web.dir}"
>>>>>>destdir="${web.dir}/WEB-INF/classes"
>>>>>> gendir="${tmp.dir}"
>>>>>> classpathref="pageflow.build.classpath"
>>>>>>srcExtensions="*.app,*.jpf">
>>>>>> </apt>
>>>>>> </target>
>>>>>></project>
>>>>>>
>>>>>>Thanks,
>>>>>>
>>>>>>Alex.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>
>
>
>
>
RE: error on apt compilation
Posted by Alexander Smirnoff <as...@vistar.ca>.
Thanks Eddie,
Interesting article, somehow I missed that one.
WSW 8.1 hides many actions when deploying web application. What
puzzles me in Beehive is exactly it: what needed to be done during
building/deployment process of application?
Is there any Beehive doc on this process, except of scattered ant
build files? It would be great for me and any other folks on
Pollinate project thoroughly investigate this issue and for
beginning have a sort of short description of runtime and involved
ant tasks in build/deploy.
Thanks,
Alex.
> -----Original Message-----
> From: Eddie O'Neil [mailto:ekoneil@bea.com]
> Sent: August 5, 2004 10:42 AM
> To: Beehive Users
> Subject: Re: error on apt compilation
>
>
> Alex--
>
> No, you don't need Global.app, though if you have it, it
> must be in:
>
> WEB-INF/src/global/Global.app
>
> It's a top-level controller file (sort of like a Page Flow)
> that is used
> to have global actions and to manage state for the duration
> of a user
> session.
>
> An article covering Global.app is here:
>
>
> http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp
>
> Keep in mind that this covered the Workshop 8.1.x version
> of Global.app,
> which used Javadoc based metadata. The Beehive Global.app
> uses JDK 1.5
> metadata instead. Other than that, the functionality provided by
> Beehive's Global.app is basically the same.
>
> Hope that helps.
>
> Eddie
>
>
>
> Alexander Smirnoff wrote:
>
> >BTW, Do I need Global.app to run this test? What it for anyway?
> >
> >
> >
> >>-----Original Message-----
> >>From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
> >>Sent: August 5, 2004 10:03 AM
> >>To: Beehive Users
> >>Subject: RE: error on apt compilation
> >>
> >>
> >>The environment is Eclipse (3.1 integration). But the compilation
> >>is made by normal ant process. I've even tried it without Eclipse
> >>in command line - the same result.
> >>
> >>I tried to reproduce almost the same ant project as found in
> >>test\ant\buildWebapp.xml, but I have feeling that I missed
> >>something... At least [apt] task is identical...
> >>
> >>Alex.
> >>
> >>
> >>
> >>>-----Original Message-----
> >>>From: Sebastian Gozin [mailto:some@gamepoint.net]
> >>>Sent: August 5, 2004 9:56 AM
> >>>To: Beehive Users
> >>>Subject: Re: error on apt compilation
> >>>
> >>>
> >>>Could you tell us a bit more about this environment? Like
> >>>what IDE are
> >>>you using to edit source?
> >>>I find it strange to read the following
> >>>
> >>> [apt] __input:29: The package must be
> >>>"WEB-INF.tmp.miniTests.buttonSubmit"
> >>>
> >>>Makes me think a bit of netbeans changing the package
> >>>statements if you
> >>>opened the source file from the wrong filesystem.
> >>>
> >>>Sebastian
> >>>
> >>>
> >>>.Alexander Smirnoff wrote:
> >>>
> >>>
> >>>
> >>>>Hi,
> >>>>
> >>>>I'm trying to compile one of the simple tests from DRT in my own
> >>>>environment. Why am I getting this error?
> >>>>
> >>>> [apt] warning on annotation value "Begin.jsp": File
> >>>>
> >>>>
> >>>"Begin.jsp" could
> >>>
> >>>
> >>>>not be found in the web application.
> >>>> [apt] warning on annotation value "Begin.jsp": File
> >>>>
> >>>>
> >>>"Begin.jsp" could
> >>>
> >>>
> >>>>not be found in the web application.
> >>>> [apt] warning on annotation value "Begin.jsp": File
> >>>>
> >>>>
> >>>"Begin.jsp" could
> >>>
> >>>
> >>>>not be found in the web application.
> >>>> [apt] __input:29: The package must be
> >>>>"WEB-INF.tmp.miniTests.buttonSubmit".
> >>>> [apt] (source unavailable)
> >>>> [apt] 1 error
> >>>>
> >>>>it looks like apt tries to compile from tmp directory, but
> >>>>
> >>>>
> >>>cannot resolve
> >>>
> >>>
> >>>>the package. Here is by built.xml:
> >>>>
> >>>><project default="all" basedir=".">
> >>>>
> >>>> <property name="src.dir" value="src"/>
> >>>> <property name="web.dir" value="WebRoot"/>
> >>>> <property name="lib.common" value="lib/common"/>
> >>>> <property name="lib.web" value="${web.dir}/WEB-INF/lib"/>
> >>>> <property name="lib.beehive" value="lib/beehive"/>
> >>>> <property name="tmp.dir" value="${web.dir}/WEB-INF/tmp"/>
> >>>>
> >>>> <path id="webapp.build.classpath">
> >>>> <pathelement
> >>>>
> >>>>
> >>>location="${web.dir}/WEB-INF/classes" />
> >>>
> >>>
> >>>> <fileset dir="${lib.web}">
> >>>> <include name="*.jar" />
> >>>> </fileset>
> >>>> <fileset dir="${lib.common}">
> >>>> <include name="*.jar" />
> >>>> </fileset>
> >>>> </path>
> >>>> <target name="all">
> >>>> <delete dir="${tmp.dir}"
> >>>>
> >>>>
> >>includeEmptyDirs="true"/>
> >>
> >>
> >>>> <javac srcdir="${src.dir}"
> >>>>destdir="${web.dir}/WEB-INF/classes"
> >>>>
> >>>>
> >>>>
> >>>classpathref="webapp.build.classpath"/>
> >>>
> >>>
> >>>> <taskdef name="apt"
> >>>>classname="org.apache.beehive.controls.runtime.generator
> .AptTask"
> >>>>
> >>>>classpath="${lib.beehive}/controls.jar;${lib.beehive}/beehi
> >>>>
> >>>>
> >>>ve-netui-compiler
> >>>
> >>>
> >>>>.jar" onerror="report"/>
> >>>> <mkdir dir="${tmp.dir}"/>
> >>>>
> >>>> <path id="pageflow.build.classpath">
> >>>> <path refid="webapp.build.classpath"/>
> >>>> <fileset
> >>>>
> >>>>
> >>>file="${lib.beehive}/beehive-netui-compiler.jar"/>
> >>>
> >>>
> >>>> </path>
> >>>>
> >>>> <apt srcdir="${web.dir}"
> >>>>destdir="${web.dir}/WEB-INF/classes"
> >>>> gendir="${tmp.dir}"
> >>>> classpathref="pageflow.build.classpath"
> >>>>srcExtensions="*.app,*.jpf">
> >>>> </apt>
> >>>> </target>
> >>>></project>
> >>>>
> >>>>Thanks,
> >>>>
> >>>>Alex.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
> >
> >
> >
>
Re: error on apt compilation
Posted by Eddie O'Neil <ek...@bea.com>.
Alex--
No, you don't need Global.app, though if you have it, it must be in:
WEB-INF/src/global/Global.app
It's a top-level controller file (sort of like a Page Flow) that is used
to have global actions and to manage state for the duration of a user
session.
An article covering Global.app is here:
http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp
Keep in mind that this covered the Workshop 8.1.x version of Global.app,
which used Javadoc based metadata. The Beehive Global.app uses JDK 1.5
metadata instead. Other than that, the functionality provided by
Beehive's Global.app is basically the same.
Hope that helps.
Eddie
Alexander Smirnoff wrote:
>BTW, Do I need Global.app to run this test? What it for anyway?
>
>
>
>>-----Original Message-----
>>From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
>>Sent: August 5, 2004 10:03 AM
>>To: Beehive Users
>>Subject: RE: error on apt compilation
>>
>>
>>The environment is Eclipse (3.1 integration). But the compilation
>>is made by normal ant process. I've even tried it without Eclipse
>>in command line - the same result.
>>
>>I tried to reproduce almost the same ant project as found in
>>test\ant\buildWebapp.xml, but I have feeling that I missed
>>something... At least [apt] task is identical...
>>
>>Alex.
>>
>>
>>
>>>-----Original Message-----
>>>From: Sebastian Gozin [mailto:some@gamepoint.net]
>>>Sent: August 5, 2004 9:56 AM
>>>To: Beehive Users
>>>Subject: Re: error on apt compilation
>>>
>>>
>>>Could you tell us a bit more about this environment? Like
>>>what IDE are
>>>you using to edit source?
>>>I find it strange to read the following
>>>
>>> [apt] __input:29: The package must be
>>>"WEB-INF.tmp.miniTests.buttonSubmit"
>>>
>>>Makes me think a bit of netbeans changing the package
>>>statements if you
>>>opened the source file from the wrong filesystem.
>>>
>>>Sebastian
>>>
>>>
>>>.Alexander Smirnoff wrote:
>>>
>>>
>>>
>>>>Hi,
>>>>
>>>>I'm trying to compile one of the simple tests from DRT in my own
>>>>environment. Why am I getting this error?
>>>>
>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>
>>>>
>>>"Begin.jsp" could
>>>
>>>
>>>>not be found in the web application.
>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>
>>>>
>>>"Begin.jsp" could
>>>
>>>
>>>>not be found in the web application.
>>>> [apt] warning on annotation value "Begin.jsp": File
>>>>
>>>>
>>>"Begin.jsp" could
>>>
>>>
>>>>not be found in the web application.
>>>> [apt] __input:29: The package must be
>>>>"WEB-INF.tmp.miniTests.buttonSubmit".
>>>> [apt] (source unavailable)
>>>> [apt] 1 error
>>>>
>>>>it looks like apt tries to compile from tmp directory, but
>>>>
>>>>
>>>cannot resolve
>>>
>>>
>>>>the package. Here is by built.xml:
>>>>
>>>><project default="all" basedir=".">
>>>>
>>>> <property name="src.dir" value="src"/>
>>>> <property name="web.dir" value="WebRoot"/>
>>>> <property name="lib.common" value="lib/common"/>
>>>> <property name="lib.web" value="${web.dir}/WEB-INF/lib"/>
>>>> <property name="lib.beehive" value="lib/beehive"/>
>>>> <property name="tmp.dir" value="${web.dir}/WEB-INF/tmp"/>
>>>>
>>>> <path id="webapp.build.classpath">
>>>> <pathelement
>>>>
>>>>
>>>location="${web.dir}/WEB-INF/classes" />
>>>
>>>
>>>> <fileset dir="${lib.web}">
>>>> <include name="*.jar" />
>>>> </fileset>
>>>> <fileset dir="${lib.common}">
>>>> <include name="*.jar" />
>>>> </fileset>
>>>> </path>
>>>> <target name="all">
>>>> <delete dir="${tmp.dir}"
>>>>
>>>>
>>includeEmptyDirs="true"/>
>>
>>
>>>> <javac srcdir="${src.dir}"
>>>>destdir="${web.dir}/WEB-INF/classes"
>>>>
>>>>
>>>>
>>>classpathref="webapp.build.classpath"/>
>>>
>>>
>>>> <taskdef name="apt"
>>>>classname="org.apache.beehive.controls.runtime.generator.AptTask"
>>>>
>>>>classpath="${lib.beehive}/controls.jar;${lib.beehive}/beehi
>>>>
>>>>
>>>ve-netui-compiler
>>>
>>>
>>>>.jar" onerror="report"/>
>>>> <mkdir dir="${tmp.dir}"/>
>>>>
>>>> <path id="pageflow.build.classpath">
>>>> <path refid="webapp.build.classpath"/>
>>>> <fileset
>>>>
>>>>
>>>file="${lib.beehive}/beehive-netui-compiler.jar"/>
>>>
>>>
>>>> </path>
>>>>
>>>> <apt srcdir="${web.dir}"
>>>>destdir="${web.dir}/WEB-INF/classes"
>>>> gendir="${tmp.dir}"
>>>> classpathref="pageflow.build.classpath"
>>>>srcExtensions="*.app,*.jpf">
>>>> </apt>
>>>> </target>
>>>></project>
>>>>
>>>>Thanks,
>>>>
>>>>Alex.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
>
>
>
RE: error on apt compilation
Posted by Alexander Smirnoff <as...@vistar.ca>.
BTW, Do I need Global.app to run this test? What it for anyway?
> -----Original Message-----
> From: Alexander Smirnoff [mailto:asmirnoff@vistar.ca]
> Sent: August 5, 2004 10:03 AM
> To: Beehive Users
> Subject: RE: error on apt compilation
>
>
> The environment is Eclipse (3.1 integration). But the compilation
> is made by normal ant process. I've even tried it without Eclipse
> in command line - the same result.
>
> I tried to reproduce almost the same ant project as found in
> test\ant\buildWebapp.xml, but I have feeling that I missed
> something... At least [apt] task is identical...
>
> Alex.
>
> > -----Original Message-----
> > From: Sebastian Gozin [mailto:some@gamepoint.net]
> > Sent: August 5, 2004 9:56 AM
> > To: Beehive Users
> > Subject: Re: error on apt compilation
> >
> >
> > Could you tell us a bit more about this environment? Like
> > what IDE are
> > you using to edit source?
> > I find it strange to read the following
> >
> > [apt] __input:29: The package must be
> > "WEB-INF.tmp.miniTests.buttonSubmit"
> >
> > Makes me think a bit of netbeans changing the package
> > statements if you
> > opened the source file from the wrong filesystem.
> >
> > Sebastian
> >
> >
> > .Alexander Smirnoff wrote:
> >
> > >Hi,
> > >
> > >I'm trying to compile one of the simple tests from DRT in my own
> > >environment. Why am I getting this error?
> > >
> > > [apt] warning on annotation value "Begin.jsp": File
> > "Begin.jsp" could
> > >not be found in the web application.
> > > [apt] warning on annotation value "Begin.jsp": File
> > "Begin.jsp" could
> > >not be found in the web application.
> > > [apt] warning on annotation value "Begin.jsp": File
> > "Begin.jsp" could
> > >not be found in the web application.
> > > [apt] __input:29: The package must be
> > >"WEB-INF.tmp.miniTests.buttonSubmit".
> > > [apt] (source unavailable)
> > > [apt] 1 error
> > >
> > >it looks like apt tries to compile from tmp directory, but
> > cannot resolve
> > >the package. Here is by built.xml:
> > >
> > ><project default="all" basedir=".">
> > >
> > > <property name="src.dir" value="src"/>
> > > <property name="web.dir" value="WebRoot"/>
> > > <property name="lib.common" value="lib/common"/>
> > > <property name="lib.web" value="${web.dir}/WEB-INF/lib"/>
> > > <property name="lib.beehive" value="lib/beehive"/>
> > > <property name="tmp.dir" value="${web.dir}/WEB-INF/tmp"/>
> > >
> > > <path id="webapp.build.classpath">
> > > <pathelement
> > location="${web.dir}/WEB-INF/classes" />
> > > <fileset dir="${lib.web}">
> > > <include name="*.jar" />
> > > </fileset>
> > > <fileset dir="${lib.common}">
> > > <include name="*.jar" />
> > > </fileset>
> > > </path>
> > > <target name="all">
> > > <delete dir="${tmp.dir}"
> includeEmptyDirs="true"/>
> > >
> > > <javac srcdir="${src.dir}"
> > >destdir="${web.dir}/WEB-INF/classes"
> > >
> > classpathref="webapp.build.classpath"/>
> > > <taskdef name="apt"
> > >classname="org.apache.beehive.controls.runtime.generator.AptTask"
> > >
> > >classpath="${lib.beehive}/controls.jar;${lib.beehive}/beehi
> > ve-netui-compiler
> > >.jar" onerror="report"/>
> > > <mkdir dir="${tmp.dir}"/>
> > >
> > > <path id="pageflow.build.classpath">
> > > <path refid="webapp.build.classpath"/>
> > > <fileset
> > file="${lib.beehive}/beehive-netui-compiler.jar"/>
> > > </path>
> > >
> > > <apt srcdir="${web.dir}"
> > >destdir="${web.dir}/WEB-INF/classes"
> > > gendir="${tmp.dir}"
> > > classpathref="pageflow.build.classpath"
> > >srcExtensions="*.app,*.jpf">
> > > </apt>
> > > </target>
> > ></project>
> > >
> > >Thanks,
> > >
> > >Alex.
> > >
> > >
> > >
> >
> >
>
>
RE: error on apt compilation
Posted by Alexander Smirnoff <as...@vistar.ca>.
The environment is Eclipse (3.1 integration). But the compilation
is made by normal ant process. I've even tried it without Eclipse
in command line - the same result.
I tried to reproduce almost the same ant project as found in
test\ant\buildWebapp.xml, but I have feeling that I missed
something... At least [apt] task is identical...
Alex.
> -----Original Message-----
> From: Sebastian Gozin [mailto:some@gamepoint.net]
> Sent: August 5, 2004 9:56 AM
> To: Beehive Users
> Subject: Re: error on apt compilation
>
>
> Could you tell us a bit more about this environment? Like
> what IDE are
> you using to edit source?
> I find it strange to read the following
>
> [apt] __input:29: The package must be
> "WEB-INF.tmp.miniTests.buttonSubmit"
>
> Makes me think a bit of netbeans changing the package
> statements if you
> opened the source file from the wrong filesystem.
>
> Sebastian
>
>
> .Alexander Smirnoff wrote:
>
> >Hi,
> >
> >I'm trying to compile one of the simple tests from DRT in my own
> >environment. Why am I getting this error?
> >
> > [apt] warning on annotation value "Begin.jsp": File
> "Begin.jsp" could
> >not be found in the web application.
> > [apt] warning on annotation value "Begin.jsp": File
> "Begin.jsp" could
> >not be found in the web application.
> > [apt] warning on annotation value "Begin.jsp": File
> "Begin.jsp" could
> >not be found in the web application.
> > [apt] __input:29: The package must be
> >"WEB-INF.tmp.miniTests.buttonSubmit".
> > [apt] (source unavailable)
> > [apt] 1 error
> >
> >it looks like apt tries to compile from tmp directory, but
> cannot resolve
> >the package. Here is by built.xml:
> >
> ><project default="all" basedir=".">
> >
> > <property name="src.dir" value="src"/>
> > <property name="web.dir" value="WebRoot"/>
> > <property name="lib.common" value="lib/common"/>
> > <property name="lib.web" value="${web.dir}/WEB-INF/lib"/>
> > <property name="lib.beehive" value="lib/beehive"/>
> > <property name="tmp.dir" value="${web.dir}/WEB-INF/tmp"/>
> >
> > <path id="webapp.build.classpath">
> > <pathelement
> location="${web.dir}/WEB-INF/classes" />
> > <fileset dir="${lib.web}">
> > <include name="*.jar" />
> > </fileset>
> > <fileset dir="${lib.common}">
> > <include name="*.jar" />
> > </fileset>
> > </path>
> > <target name="all">
> > <delete dir="${tmp.dir}" includeEmptyDirs="true"/>
> >
> > <javac srcdir="${src.dir}"
> >destdir="${web.dir}/WEB-INF/classes"
> >
> classpathref="webapp.build.classpath"/>
> > <taskdef name="apt"
> >classname="org.apache.beehive.controls.runtime.generator.AptTask"
> >
> >classpath="${lib.beehive}/controls.jar;${lib.beehive}/beehi
> ve-netui-compiler
> >.jar" onerror="report"/>
> > <mkdir dir="${tmp.dir}"/>
> >
> > <path id="pageflow.build.classpath">
> > <path refid="webapp.build.classpath"/>
> > <fileset
> file="${lib.beehive}/beehive-netui-compiler.jar"/>
> > </path>
> >
> > <apt srcdir="${web.dir}"
> >destdir="${web.dir}/WEB-INF/classes"
> > gendir="${tmp.dir}"
> > classpathref="pageflow.build.classpath"
> >srcExtensions="*.app,*.jpf">
> > </apt>
> > </target>
> ></project>
> >
> >Thanks,
> >
> >Alex.
> >
> >
> >
>
>
Re: error on apt compilation
Posted by Sebastian Gozin <so...@gamepoint.net>.
Could you tell us a bit more about this environment? Like what IDE are
you using to edit source?
I find it strange to read the following
[apt] __input:29: The package must be
"WEB-INF.tmp.miniTests.buttonSubmit"
Makes me think a bit of netbeans changing the package statements if you
opened the source file from the wrong filesystem.
Sebastian
.Alexander Smirnoff wrote:
>Hi,
>
>I'm trying to compile one of the simple tests from DRT in my own
>environment. Why am I getting this error?
>
> [apt] warning on annotation value "Begin.jsp": File "Begin.jsp" could
>not be found in the web application.
> [apt] warning on annotation value "Begin.jsp": File "Begin.jsp" could
>not be found in the web application.
> [apt] warning on annotation value "Begin.jsp": File "Begin.jsp" could
>not be found in the web application.
> [apt] __input:29: The package must be
>"WEB-INF.tmp.miniTests.buttonSubmit".
> [apt] (source unavailable)
> [apt] 1 error
>
>it looks like apt tries to compile from tmp directory, but cannot resolve
>the package. Here is by built.xml:
>
><project default="all" basedir=".">
>
> <property name="src.dir" value="src"/>
> <property name="web.dir" value="WebRoot"/>
> <property name="lib.common" value="lib/common"/>
> <property name="lib.web" value="${web.dir}/WEB-INF/lib"/>
> <property name="lib.beehive" value="lib/beehive"/>
> <property name="tmp.dir" value="${web.dir}/WEB-INF/tmp"/>
>
> <path id="webapp.build.classpath">
> <pathelement location="${web.dir}/WEB-INF/classes" />
> <fileset dir="${lib.web}">
> <include name="*.jar" />
> </fileset>
> <fileset dir="${lib.common}">
> <include name="*.jar" />
> </fileset>
> </path>
> <target name="all">
> <delete dir="${tmp.dir}" includeEmptyDirs="true"/>
>
> <javac srcdir="${src.dir}"
>destdir="${web.dir}/WEB-INF/classes"
> classpathref="webapp.build.classpath"/>
> <taskdef name="apt"
>classname="org.apache.beehive.controls.runtime.generator.AptTask"
>
>classpath="${lib.beehive}/controls.jar;${lib.beehive}/beehive-netui-compiler
>.jar" onerror="report"/>
> <mkdir dir="${tmp.dir}"/>
>
> <path id="pageflow.build.classpath">
> <path refid="webapp.build.classpath"/>
> <fileset file="${lib.beehive}/beehive-netui-compiler.jar"/>
> </path>
>
> <apt srcdir="${web.dir}"
>destdir="${web.dir}/WEB-INF/classes"
> gendir="${tmp.dir}"
> classpathref="pageflow.build.classpath"
>srcExtensions="*.app,*.jpf">
> </apt>
> </target>
></project>
>
>Thanks,
>
>Alex.
>
>
>