Error Authentication failed [Understood]

[Alessandro Domanico]

I've just build and deployed service.war and editor.war in my Tomcat Server.

I receive that message by accessing: http://localhost:8080/editor/editor.html

or http://localhost:8080/editor/editor.html?documentID=1

or as well http://localhost:8080/editor/editor.html?documentID=[URL]

or also http://localhost:8080/editor/amendment.html?documentID=[URL]

[Philip Luppens]

Hi Alessandro,

You're probably on the /dev branch, right? I've recently added (JAAS) authentication because of a request for a prototype installation, hence the reason it requires authentication now. In order to enable this (provided you work on a Tomcat installation), is to add a user with the role ROLE_USER or ROLE_ADMIN in your conf/tomcat-users.xml file, or to use whatever JAAS authentication mechanism you want.

HTH, if not, just ask away :)

Phil

[Alessandro Domanico]

Hi Philip, thanks for the answer.

I've cloned the master branch, I don't know if I'm on dev branch... but according with what you suggest I'm required this authentication too.

In my tomcat I already set up a user to deploy the application with following roles (Tomcat7): <user name="alessandro" password="ale" roles="admin-gui,manager-gui" />

is it enough?

Thanks

[Philip Luppens]

If you make that roles="admin-gui,manager-gui,ROLE_USER,ROLE_ADMIN", then it should work after a restart.

[Alessandro Domanico]

Oh... tried right now: changed roles, restarted tomcat, but still same message... :(

[Philip Luppens]

Wait, I think I misunderstood: you're talking about a popup message while being on editor page, or a message from the Tomcat server before even seeing the NSESA toolbar?

[Alessandro Domanico]

I'm talking about the popup message on the editor page.

At every request I can see in tomcat log: giu 16, 2014 10:50:00 AM org.apache.catalina.core.ApplicationContext log Grave: Exception while dispatching incoming RPC call java.lang.OutOfMemoryError: PermGen space

[Philip Luppens]

Aha! Ok, it makes sense now. Sorry, I was confused by the authentication failure because I thought you were on the /develop branch and had issues with JAAS.

Ok, this means your Tomcat doesn't have enough memory assigned. What platform are you on? Windows, Linux or OSX?

[Alessandro Domanico]

I'm on Windows, I'm trying to increase the PermGen space with: --JvmOptions=-Xmx2g -Xms1g -XX:MaxPermSize=512m

It solved the OutOfMemory, but the popup is not gone

[Alessandro Domanico]

if I access editor.html logs are very silent, everything seems ok.

But if I access amendment.html nsesa.log says:

2014-06-16 11:25:28,851 WARN [http-bio-8080-exec-6] phase.PhaseInterceptorChain: Interceptor for {http://api.service.server.nsesa.org/}PersonServiceService#{http://api.service.server.nsesa.org/}getPersonByUsername has thrown exception, unwinding now
java.lang.RuntimeException: Cannot create a secure XMLInputFactory
    at org.apache.cxf.staxutils.StaxUtils.createXMLInputFactory(StaxUtils.java:312)
    at org.apache.cxf.staxutils.StaxUtils.getXMLInputFactory(StaxUtils.java:262)
    at org.apache.cxf.staxutils.StaxUtils.createXMLStreamReader(StaxUtils.java:1441)
    at org.apache.cxf.interceptor.StaxInInterceptor.handleMessage(StaxInInterceptor.java:112)
    at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
    at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:835)
    at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1614)
    at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1504)
    at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1310)
    at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
    at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:628)
    at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
    at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
    at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:565)
    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:474)
    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:377)
    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:330)
    at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
    at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
    at com.sun.proxy.$Proxy55.getPersonByUsername(Unknown Source)
    at org.nsesa.editor.gwt.an.common.server.service.gwt.GWTServiceImpl.authenticate(GWTServiceImpl.java:55)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:561)
    at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:208)
    at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:248)
    at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
    at org.nsesa.editor.gwt.an.common.server.service.gwt.SpringRemoteServiceServlet.handleRequest(SpringRemoteServiceServlet.java:42)
    at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:900)
    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:827)
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
    at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
    at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
    at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
    at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:314)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
    at java.lang.Thread.run(Unknown Source)

[Philip Luppens]

I've never seen this error, but it looks like a missing library problem (check out http://stackoverflow.com/questions/16903216/cxf-2-7-x-woodstox-compatibility-via-maven).

[Alessandro Domanico]

I've tried to replace those dependencies but with no success...

the only thing I've noticed are the following warnings in the pom.xml installation:

[WARNING] Some problems were encountered while building the effective model for org.nsesa:editor-an:war:0.11
[WARNING] 'dependencies.dependency.exclusions.exclusion.groupId' for org.springframework.security:spring-security-web:jar with value '*' does not match a valid id pattern. @ line 129, column 30
[WARNING] 'dependencies.dependency.exclusions.exclusion.artifactId' for org.springframework.security:spring-security-web:jar with value '*' does not match a valid id pattern. @ line 130, column 33
[WARNING] 'dependencies.dependency.exclusions.exclusion.groupId' for org.springframework.security:spring-security-taglibs:jar with value '*' does not match a valid id pattern. @ line 203, column 30
[WARNING] 'dependencies.dependency.exclusions.exclusion.artifactId' for org.springframework.security:spring-security-taglibs:jar with value '*' does not match a valid id pattern. @ line 204, column 33
[WARNING] 'dependencies.dependency.exclusions.exclusion.groupId' for org.springframework.security:spring-security-config:jar with value '*' does not match a valid id pattern. @ line 250, column 30
[WARNING] 'dependencies.dependency.exclusions.exclusion.artifactId' for org.springframework.security:spring-security-config:jar with value '*' does not match a valid id pattern. @ line 251, column 33
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING] 

[Philip Luppens]

Ok, try the following standalone distribution then, just to see if this one works: http://nsesa.org/uploads/nsesa-standalone/1.0-SNAPSHOT/nsesa-standalone-1.0-SNAPSHOT-distribution.zip

Regarding the warning: can you try to build with Maven 3? I think you're still on Maven 2, no?

[Philip Luppens]

Or, perhaps try to use a Tomcat 6 instead of 7?

[Alessandro Domanico]

with the standalone distro still the same popup!

I think I should try to solve the problem in the standalone first, then in my develop environment, isn't it?

[Philip Luppens]

Well, you'll need the project to work in your development environment at the end, but indeed, at least the libraries should be available in the standalone download.

What version of Java (JDK) are you using?

[Alessandro Domanico]

java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)

[Philip Luppens]

Strange, that should work afaik ...

java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)

Windows version?

[Alessandro Domanico]

Windows 7 Home Premium 64bit
Service Pack 1

But let me ask you, what the authentication popup error refers to?

[Philip Luppens]

Ok, that should totally work ... sigh

The final thing I could suggest is to try to find the same version that I have.

Or, perhaps, check the logs - maybe there is another error earlier in the logs that we skipped over.

[Philip Luppens]

The nsesa-server.properties is an override, you don't need it for development. How did you deploy the two wars? There should be 2, called editor.war and services.war. Try to drop services.war first into the webapps folder and see if it starts correctly by going to /services/ws.

[Alessandro Domanico]

I was talking about the standalone behaviour. Anyway in my system I've deployed both, editor and service.

'/services/ws' with the standalone distro is up and running fine: i get a CXF - Service list page. Same thing with the one deployed by myself. The problem is given by the editor.war only.

But let me ask you, what the authentication popup error refers to?

[Philip Luppens]

It seems you're unable to create the clients for the webservices in the editor.war. But it's strange that you get a 404 response, since you managed to deploy the war, but you simply cannot use the services at runtime.

The authentication isn't exactly a failure to authenticate; it simply means that the backend service couldn't retrieve a valid Person object via the passed in username. Since this throws an exception, the default behaviour is to say that the authentication failed.

I'll see if I can get something running on a local VM.

[Alessandro Domanico]

I see, but it's also strange that it happens in the standalone version too...

I'll try and try again.

Thank you very much for now

[Philip Luppens]

Doesn't matter - it's a classpath problem that somehow stops your webservice client proxies in editor.war from being created, and this is normally caused by having conflicting libraries on your classpath. You could try to use 2 different tomcat servers, and then create an nsesa-editor-an.properties file in your home directory to override the location of the webservices via the 'services.url=http://localhost:8080/services/ws' setting, but that would require that you change the port at which running. And that's quite a bit of work as well.

[Alessandro Domanico]

sorry, I'm not understanding the explanation: which classpath should I check? In the standalone version all the libs required should be there, and the built war should take in account only those, isn't it?

Maybe I need external libraries in my JDK installation? Or I need some system variables to be defined? (at the moment I have JAVA_HOME and JRE_HOME)

[Philip Luppens]

Ok, it looks like this is a problem with a different Stax parser. Somehow there's a conflict in the runtime classpath where another dependency shadows the CXF Stax parser, which results in an exception because CXF believes its own parser is more secure.

Could you try to add the following system configuration (in addition to the -Xmx and -Xms parameter): -Dorg.apache.cxf.stax.allowInsecureParser=true and restart the server?

[Alessandro Domanico]

No way... tried on my local Tomcat. And tried on the standalone distro by adding in setenv.bat.

Found that (with or without allowInsecureParser=true) I get this error in localhost.log when accessing /services/ws:

Grave: Servlet.service() for servlet [CXFServlet] in context with path [/services] threw exception
java.lang.IllegalStateException: getWriter() has already been called for this response
    at org.apache.catalina.connector.Response.getOutputStream(Response.java:602)
    at org.apache.catalina.connector.ResponseFacade.getOutputStream(ResponseFacade.java:196)
    at org.apache.cxf.transport.servlet.servicelist.ServiceListGeneratorServlet.renderStyleSheet(ServiceListGeneratorServlet.java:174)
    at org.apache.cxf.transport.servlet.servicelist.ServiceListGeneratorServlet.service(ServiceListGeneratorServlet.java:89)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:170)
    at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
    at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:167)
    at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
    at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:211)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
    at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:262)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
    at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
    at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
    at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:315)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

[Alessandro Domanico]

last error solved by updating cxf-bundle-minimal-2.7.10 --> cxf-bundle-minimal-2.7.11 as explained here.

[Philip Luppens]

Thanks for reporting back - does that mean the error is resolved and you can access the services via the clients? Or are you still seeing the 'Cannot create a secure XMLInputFactory' error message?

If so, we would need to see if there's another stax parser on your classpath shadowing the woodstock one. Perhaps the JDK version is to blame ...

[Alessandro Domanico]

I solved the error when accessing /service/ws:

Grave: Servlet.service() for servlet [CXFServlet] in context with path [/services] threw exception
java.lang.IllegalStateException: getWriter() has already been called for this response

the 'Cannot create a secure XMLInputFactory' error was on my local deploy, no trace of it in the standalone version.

I would prefer to solve first in the standalone, that should be fine as build, dependencies, classpath and deployment.

At the moment I have no errors in logs, except the 404s, and still that popup window when accessing editor or amendment

[Philip Luppens]

Ok, so let's focus on the editor deployment then; can you post the logs somewhere (nsesa.log, catalina.out, ...)? Preferably after you removed all of them and did a single restart so there's not too much noise. I'll see if there's anything else that I can find.

[Alessandro Domanico]

ok, after starting the standalone version and contacting http://localhost:8080/editor/amendment.html?documentID=http://at4amos.bitbucket.org/nsesa-examples/Act_Kenya_1980-01-01%401989-12-15.xml

I got (the only ones written by web-container):

• http://pastebin.com/UB01nRXj

• http://pastebin.com/1xYDv49x

• http://pastebin.com/yqnxdQcT

• http://pastebin.com/W7vdRUD4

If I contact http://localhost:8080/editor/editor.html?documentID=1 (or an URL as parameter) it gives 404 on /editor/editor.html!!! :/

[Philip Luppens]

Strange, I would have expected it to at least attempt to deploy the war file or the exploded directory, with a clear indication of what went wrong. The 404 is the result of a non-succeeding deployment, so Tomcat responds with a 404 for that war file (/editor).

Btw, I'll be travelling back to Romania tomorrow, so I will be (even) slow(er) in responding - apologies.

-Phil

[Alessandro Domanico]

I can see that the editor is actually deployed and exploded in webapps/. I agree that in case of errors in the deployment Tomcat should have said something... :(

I'll be waiting for some more suggestions. Stupid question: the standalone version you sent to me is working fine for you?

Don't worry, you're giving me a lot of help! Thank you!

[Philip Luppens]

Ok, I tried it with Windows 7 Professional, 64 bit. Clean OS install, installed JDK-1.7.0_60, set JAVA_HOME to the JDK folder, downloaded the standalone zip file, extracted it and ran 'startup.bat'. Everything worked beautifully.

Damn. That makes it even harder to figure out what's wrong on your system. Did you try uninstalling Java and installing a completely new JDK?

[Alessandro Domanico]

I'm a Java developer, I've all JDK for all versions, from 5 to 7, 32 and 64bit...

JAVA_HOME = C:\Program Files\Java\jdk1.7.0\bin

That is the one posted before:

java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)

I'll try with your same identical version... just to be sure... unless Windows that is Home Premium and not Professional

[Alessandro Domanico]

Nothing... still the same and no new informations in logs... :((((((

java version "1.7.0_60"
Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)

[Philip Luppens]

(Just a quick notice: your JAVA_HOME points to your JDK directory, not the JDK/bin, right?)

Just for gigs, try to use another application server (Jetty, JBoss) to see if perhaps some more info is available there.

[Philip Luppens]

I wanted you to find out the classpath when running the application server, but that wouldn't explain why it doesn't work in the standalone version (its classpath should be clean and thus not give the error).

You can change the logging for Tomcat to the maximum level, but it wouldn't help much in the case of a classpath error. And I don't understand how your classpath can get polluted in case of the standalone version, unless you somehow execute Tomcat with the wrong JDK version.

[Philip Luppens]

Also, when you run the Tomcat server - is this from the command line, or from within an IDE (IntelliJ, Eclipse, ...)?

[Alessandro Domanico]

Hi Philip, my JAVA_HOME is set to JDK/bin... but even setting to JDK/ it doesn't work.

I changed the log level to ALL but, as you stated, I don't see more informations.

I run the Tomcat server included in the standalone version (startup.bat), so the IDE is not involved in the operation.

I would like to show you the output of startup.bat but then it launches catalina.bat and this give me problem in redirecting the standard output properly, at the moment...

[Alessandro Domanico]

This is the stout of tomcat in the standalone version:

http://pastebin.com/Q2xawRj0

[Philip Luppens]

Ok, what's the output of the nsesa.log file in the standalone log directory?

[Alessandro Domanico]

nsesa.log is silent, not event created. The only one created is nsesa-server.log, that says always the same thing (in standalone and in my local deployment):

2014-06-20 12:44:51,703 WARN [localhost-startStop-1] support.PropertySourcesPlaceholderConfigurer: Could not load properties from URL [file:/C:/Users/Nanni/nsesa-server.properties]: C:\Users\Nanni\nsesa-server.properties (Impossibile trovare il file specificato)

[Philip Luppens]

I'm really running out of ideas - I would suggest you clean up your java.library.path, and remove anything that is not elementary (meaning your JDK path only - without the bin suffix). RIght now I see there are a bunch of MySQL extensions that load some classes, and perhaps one of them is responsible. That would be the only thing that would influence the startup of the standalone version.

[Alessandro Domanico]

Done, without success.... now the java.library.path seen by startup.bat is:

giu 20, 2014 10:29:49 PM org.apache.catalina.core.AprLifecycleListener init
INFORMAZIONI: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre7\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Java\jre7\bin;C:\Program Files\Java\jdk1.7.0_60;.

But the problem is not solved... I'll try to do it in a VM from scratch... I'm totally lost... :(

[Philip Luppens]

Well, this is mine in the VM:

Jun 19, 2014 2:13:30 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.7.0_60\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;.

The only difference I can point out is that your JRE is coming before your JDK, whereas for me it's the opposite way. Not sure if that's going to make a difference.

[Alessandro Domanico]

No, I thing we're going in the alchemy's field... :P

Let me try to do everything in a LinuxVM, I want to let it work!

Thanks for the help, in case of news I'll update you on this issue. ;)

[Philip Luppens]

No problem; I'm also intrigued. I created the standalone version to exactly overcome issues like this, but perhaps I should see if I can include a fully self-contained distribution with JVM instead, that completely ignores the classpath.

[Alessandro Domanico]

Tried the standalone version in a VM with Ubuntu12.10... it seems exaclty the same behaviour... I'll perform all the checks done up to know on this new configuration

[Philip Luppens]

I know it sounds stupid, but are these Italian versions? Maybe somehow that is of importance?

[Alessandro Domanico]

negative, the Ubuntu in VM is in english.

But let me ask you: this repo, and the standalone version as well, carries the default documents? The ones accessible with:

http://localhost:8080/editor/editor.html?documentID=1

http://localhost:8080/editor/editor.html?documentID=2

http://localhost:8080/editor/editor.html?documentID=...

http://localhost:8080/editor/editor.html?documentID=8

And the document I'm testing is:

http://localhost:8080/editor/editor.html?documentID=http://at4amos.bitbucket.org/nsesa-examples/Act_Kenya_1980-01-01%401989-12-15.xml

or

http://localhost:8080/editor/amendment.html?documentID=http://at4amos.bitbucket.org/nsesa-examples/Act_Kenya_1980-01-01%401989-12-15.xml

Is that right?

With editor.html I get resource not found (404), with amendment.html I get the popup message of this issue.

[Philip Luppens]

Indeed, you should use 'amendment.html', not editor.html (which has been renamed). The files should be available locally, yes, so the documentID=1 should work.

[Alessandro Domanico]

Ok, that's why the resource not found (404) message... anyway I always tried both, with no success. No way...

[Philip Luppens]

Ok, I'll see if I can get a chance today to try it with a ubuntu 12.10. If that works fine for me, then I'm officially retiring from programming and start a career in cave dwelling or sheep herding.

[Alessandro Domanico]

LOL... anyway, there's something different from amendment.html that I may test on the deployed editor.war?

[Philip Luppens]

Well, there's the drafter.html and markup.html, but drafter is mostly keyboard oriented (think VI) and markup is just a POC. Both are mostly done to show how easy it is to create new applications that need to support XSDs.

[Alessandro Domanico]

Ok, just tried:

• drafter.html answers with the same error message
• markup.html answers with a blank page, but the source is this http://pastebin.com/yYH2WFjW

[Philip Luppens]

Sorry about the late response - I've had a lot on my plate in the last 3 days. I hope to verify it this weekend.

[Philip Luppens]

Ok, tried it. It works like a charm here:

• Downloaded 12.10, installed via easy-install under VMWare Fusion
• sudo apt-get update
• sudo apt-get upgrade
• sudo apt-get dist-upgrade
• sudo apt-get install openjdk-7-jdk
• sudo apt-get install tomcat7
• sudo apt-get install vim && openssh
• sudo vi /etc/tomcat7/tomcat-users.xml (added user)
• sudo service tomcat7 restart
• cp /home/phil/temp/* /var/lib/tomcat7/webapps (contains both editor.war and services.war)

15 seconds later everything is up and running, and it works fine.

I'm out of ideas & will be retiring into the wild shortly.

[Alessandro Domanico]

Hi Philip, unfortunately I will not be able to re-try this for a month... anyway I'm wondering if the problem is due to a wrong usage of the tool.

Could you please list the steps after those 15 seconds?

Thank you.

[Philip Luppens]

Hi Alessandro - there are no further steps; I just copy the editor.war and services.war files into the /webapps directory. They get unpacked, and I end up with 2 running webapps (other than some errors in the log about not being able to find the designated log files).

The only thing that I can imagine is that your build process somehow doesn't create the correct war files. Can you copy the ones you get from the standalone edition into the VM?