Note JSF trunk is inactive until JSF.next is being developed.
If you intend to test JSF 2.2 please be aware it is NOT supported on GF
3.1.
Note the correct branch for 2.2 is
https://svn.java.net/svn/mojarra~svn/branches/MOJARRA_2_2X_ROLLING/
<
https://svn.java.net/svn/mojarra%7Esvn/branches/MOJARRA_2_2X_ROLLING/>
Please use GF 3.1.2.2 or GF 4.0 if you are trying to build Mojarra 2.2.
Thanks!
Manfred
On 6/19/2013 9:59 AM, Anthony wrote:
>
> Thanks Manfred,
>
> I'm in the process of trying it now, it normally takes around 18 mins
> before error (I'm currently on my laptop).
>
> I'm running it with Glassfish 3.1 Final. I'm not too familiar with
> Glassfish or Ant as I normally use Tomcat and Maven, therefore I'm not
> sure if it's significant but after checking the applications folder of
> the Glassfish installation directory I've noticed that the
> jsf-systest.war hasn't fully expanded and only the WEB-INF/lib/ folder
> along with the jars is in the applications folder.
>
> All the best,
>
> Anthony.
>
> *From:*Manfred Riem [mailto:manfred.riem_at_oracle.com]
> *Sent:* 19 June 2013 15:50
> *To:* dev_at_javaserverfaces.java.net
> *Cc:* Anthony
> *Subject:* Re: Cannot get tests to run from JSF trunk
>
> Can you try to do the following:
>
> ant main clean main test.with.container.refresh
>
> Note which container did you set up?
>
> Manfred
>
> On 6/19/2013 9:07 AM, Anthony wrote:
>
> One of my validators? I'm running the JSF trunk!
>
> *From:*Manfred Riem [mailto:manfred.riem_at_oracle.com]
> *Sent:* 19 June 2013 14:21
> *To:* dev_at_javaserverfaces.java.net
> <mailto:dev_at_javaserverfaces.java.net>
> *Cc:* Anthony
> *Subject:* Re: Cannot get tests to run from JSF trunk
>
> Looks like one of your Validators is missing its value.
>
> Manfred
>
> On 6/19/2013 7:33 AM, Anthony wrote:
>
> Hi,
>
> I finally managed to get a little more time to take a look
> into some JSF issues that our project has been having.
> Previously (around 2.1.6) I managed to connect to the JSF
> trunk and successfully run the 'ant clean main
> test.with.container.refresh' command.
>
> Now when I try to run the same command with the latest code
> from the trunk I hit this issue I can't find a fix for. The
> error is below:
>
> java.lang.annotation.IncompleteAnnotationException:
> javax.faces.validator.FacesValidator missing element value
>
> at
> sun.reflect.annotation.AnnotationInvocationHandler.invoke(AnnotationInvocationHandler.java:72)
>
> at com.sun.proxy.$Proxy106.value(Unknown Source)
>
> at
> com.sun.faces.application.annotation.ValidatorConfigHandler.collect(ValidatorConfigHandler.java:95)
>
> at
> com.sun.faces.application.annotation.AnnotationManager.applyConfigAnnotations(AnnotationManager.java:197)
>
> at
> com.sun.faces.config.processor.AbstractConfigProcessor.processAnnotations(AbstractConfigProcessor.java:326)
>
> at
> com.sun.faces.config.processor.ValidatorConfigProcessor.process(ValidatorConfigProcessor.java:101)
>
> at
> com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
>
> at
> com.sun.faces.config.processor.ConverterConfigProcessor.process(ConverterConfigProcessor.java:126)
>
> at
> com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
>
> at
> com.sun.faces.config.processor.ComponentConfigProcessor.process(ComponentConfigProcessor.java:117)
>
> at
> com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
>
> at
> com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:337)
>
> at
> com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
>
> at
> com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116)
>
> at
> com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
>
> at
> com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:222)
>
> at
> com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:360)
>
> at
> com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:225)
>
> at
> org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:4690)
>
> at
> com.sun.enterprise.web.WebModule.contextListenerStart(WebModule.java:534)
>
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:5305)
>
> at
> com.sun.enterprise.web.WebModule.start(WebModule.java:500)
>
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:917)
>
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:901)
>
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:755)
>
> at
> com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1980)
>
> at
> com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1630)
>
> at
> com.sun.enterprise.web.WebApplication.start(WebApplication.java:100)
>
> at
> org.glassfish.internal.data.EngineRef.start(EngineRef.java:130)
>
> at
> org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:269)
>
> at
> org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:286)
>
> at
> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
>
> at
> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
>
> at
> org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:370)
>
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:355)
>
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:370)
>
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1067)
>
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:96)
>
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1247)
>
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235)
>
> at
> com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:465)
>
> at
> com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:222)
>
> at
> com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168)
>
> at
> com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
>
> at
> com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:234)
>
> at
> com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822)
>
> at
> com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719)
>
> at
> com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)
>
> at
> com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
>
> at
> com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
>
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
>
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
>
> at
> com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
>
> at
> com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
>
> at
> com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
>
> at
> com.sun.grizzly.ContextTask.run(ContextTask.java:71)
>
> at
> com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
>
> at
> com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
>
> at java.lang.Thread.run(Thread.java:722)
>
> |#]
>
> Is there anyone who knows what is causing this issue?
>
> With our own applications I'd have it set up so that I can run
> it in debug mode. This allows me to find solutions for issues
> like this. Do you know if this is possible with the way that
> this project is configured, it would be really helpful for me
> to get to know the system in more depth,
>
> Many thanks,
>
> Anthony.
>