Hi,
Sorry i couldn't send the warning in net beans 5.0 for my second question.
It is in the attachment screenshot.

regards ,
janandith.

On Wed, Apr 16, 2008 at 2:01 PM, janandith jayawardena <[EMAIL PROTECTED]>
wrote:

> Hi ,
>
> I have two questions.
> First is about starting a new bundle manually. Second is about a warning
> message shown by net beans 5.0.
>
> This is a lenghty description but i think it is necessary.
> *
> First question*
>
> I wrote two skeleton classes  ScalaScriptEngineFactory and
> ScalaScriptEngine with out any logic only implementing the required
> interfaces referring the Velocity , Ruby , Freemarker & Rhino modules.
>
> I saved them under
> sling\scripting\scala\src\main\java\org\apache\sling\scripting\scala.
>
> then i modified the pom.xml generated by maven as follows
>
> <project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance";
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>   <modelVersion>4.0.0</modelVersion>
>
>     <parent>
>         <groupId>org.apache.sling</groupId>
>         <artifactId>sling</artifactId>
>         <version>1-incubator-SNAPSHOT</version>
>         <relativePath>../../parent/pom.xml</relativePath>
>     </parent>
>
>     <artifactId>org.apache.sling.scripting.scala</artifactId>
>     <version>2.0.0-incubator-SNAPSHOT</version>
>     <packaging>bundle</packaging>
>
>     <name>Sling - Scripting - Scala Support</name>
>     <description>Support for Scala scripting</description>
>
>     <build>
>         <plugins>
>             <plugin>
>                 <groupId>org.apache.felix</groupId>
>                 <artifactId>maven-bundle-plugin</artifactId>
>                 <extensions>true</extensions>
>                 <configuration>
>                     <instructions>
>
>                         <Private-Package>
>                             org.apache.sling.scripting.scala
>                         </Private-Package>
>
>                         <ScriptEngine-Name>${pom.name}</ScriptEngine-Name>
>
> <ScriptEngine-Version>${pom.version}</ScriptEngine-Version>
>
>                     </instructions>
>                 </configuration>
>             </plugin>
>         </plugins>
>     </build>
>
>
>     <dependencies>
>         <dependency>
>             <groupId>org.apache.sling</groupId>
>             <artifactId>org.apache.sling.api</artifactId>
>             <version>2.0.0-incubator-SNAPSHOT</version>
>         </dependency>
>         <dependency>
>             <groupId>org.apache.sling</groupId>
>             <artifactId>org.apache.sling.scripting.api</artifactId>
>             <version>2.0.0-incubator-SNAPSHOT</version>
>         </dependency>
>         <dependency>
>             <groupId>javax.jcr</groupId>
>             <artifactId>jcr</artifactId>
>         </dependency>
>           <dependency>
>             <groupId>junit</groupId>
>             <artifactId>junit</artifactId>
>             <version>3.8.1</version>
>             <scope>test</scope>
>           </dependency>
>   </dependencies>
> </project>
>
> *After adding the line  "<module>scripting/scala</module>" under "<!--
> Scripting Support -->" in the main pom.xml I rebuilt sling using command
> "mvn install"
> Once the build is complete it was possible to add the created jar using
> the launchpad web interface. When I click start it shows that the new bundle
> has started.
>
> But I didn't write any logic.
> So how is it possible for the bundle to load and start. How can i really
> check whether it is started ?.*
>
> *Second question*
>
> when i wrote the code using net beans 5.0 IDE there is this warning.
>
>
>
> but the get methods in the Script Engine Factory classes for other
> scripting languges have similar META DATA get methods as shown in JSR 223
> spec.
>
> why is this warning telling AbstractScriptEngineFactory cannot implement
> getMethodCallSyntax in javax.script.ScriptEngineFactory. Will it create an
> issue for the execution of the bundle. ?
>
> regards,
>
> janandith.
>
>
>
>

Reply via email to