X-Application Version: 3.1.1
Tamino Version : 3.1.2.1
Platform : Win2k
WebContainer : Tomcat 3.3
JDK Version : 1.3.1
When attempting to generate an x-application.
I get the following error (from x-app generator screen"
error reading c:\jakarta-tomcat-3.3\webapps\Employee1\WEB-INF\web.xml: Error in building: Operation timed out: no further information…aborted
Tomcat says…
[GuiServlet] Session isNew(): true
[GuiServlet] No schemaContainer created!
[GuiServlet] ############## attribute values ###############
[GuiServlet] TAMINO_COLLECTION: Emp
[GuiServlet] TOMCAT_HOME: c:\jakarta-tomcat-3.3
[GuiServlet] TARGET_DIR: c:\jakarta-tomcat-3.3\webapps\Employee1
[GuiServlet] TAMINO_SCHEMA_TEXT:
[GuiServlet] TAMINO_URL: http://localhost/tamino/welcome3_1_1_1
[GuiServlet] MODE: startgen
[GuiServlet] USER_ID: didataza/ncave
[GuiServlet] XAPP_HOME: C:\xapplication_311
[GuiServlet] TAMINO_SCHEMA_FILE:
[GuiServlet] TAMINO_AUTHORIZATION: on
[GuiServlet] TAMINO_SCHEMA: Employee
[GuiServlet] DOCTYPE: Employee
[GuiServlet] ################################################
[GuiServlet] Session isNew(): false
2003-03-24 15:15:04 - DecodeInterceptor: Charset from session ISO-8859-1
[GuiServlet] No schemaContainer created!
[GuiServlet] ############## attribute values ###############
[GuiServlet] TAMINO_COLLECTION: Emp
[GuiServlet] genType: generate
[GuiServlet] TOMCAT_HOME: c:\jakarta-tomcat-3.3
[GuiServlet] TAMINO_SCHEMA_TEXT:
[GuiServlet] TARGET_DIR: c:\jakarta-tomcat-3.3\webapps\Employee1
[GuiServlet] submitButton: Start Generation
[GuiServlet] TAMINO_URL: http://localhost/tamino/welcome3_1_1_1
[GuiServlet] MODE: startgen
[GuiServlet] USER_ID: didataza/ncave
[GuiServlet] XAPP_HOME: C:\xapplication_311
[GuiServlet] TAMINO_SCHEMA_FILE:
[GuiServlet] TAMINO_AUTHORIZATION: on
[GuiServlet] TAMINO_SCHEMA: Employee
[GuiServlet] DOCTYPE: Employee
[GuiServlet] PASSWORD: CONFIDENTIAL
[GuiServlet] ################################################
[GuiServlet] Generate target dir: c:\jakarta-tomcat-3.3\webapps\Employee1
[ConfigContainer] reading c:\jakarta-tomcat-3.3\webapps\Employee1\config.xml
[ConfigContainer] done reading c:\jakarta-tomcat-3.3\webapps\Employee1\config.xm
l
[ConfigContainer] reading c:\jakarta-tomcat-3.3\webapps\Employee1\WEB-INF\web.xm
l
My x-app used to work (ages ago), I may have used it last before installing 3.1.2.1 but the schema I’m trying to generate off is in the 3.1.1.1 db where the x-app schemas are defined.
What gives?
I must add that Tomcat creates Employee1 folder under webapps dirc. And there is a web.xml file under th web-inf folder. Which seems to be complete and looks like this…
<?xml version="1.0" encoding="ISO-8859-1" ?>
-
-
CODED
true
-
TAMINO_URL
http://localhost/tamino/welcome3_1_1_1
-
TAMINO_COLLECTION1
Emp
-
TAMINO_DOCTYPE1
Employee
-
USER_ID
didataza/ncave
-
PASSWORD
-
http://www.softwareag.com/xtools/xapplication
/WEB-INF/jsp/xapplication.tld
Hello,
if I understand you right: You used X-Application 3.1.1 and generated an application ‘Employee’. The directory that contains the application is
…\Employee1
Did you try to stop your Tomcat server and to invoke your application with
http://localhost:8080/Employee1/search.jsp
after a restart of Tomcat?
When I remember right the generator of X-Application 3.1.1 had problems to restart the second Tomcat process that loads the new application.
After a restart of the Tomcat the application should be available by default on port 8080 (while the generator started the second tomcat on 8081).
Does a restart solve your problem?
Bye,
Christian.
Hello,
please, remove the parameter value for USER. Currently, it set to
didataza/ncave
But, the password is not set. This should cause an error.
Bye,
Christian.
Hi Christian.
Seems restarting tomcat does allow you to start up the generated app. This never used to be the case.
I can get to the search screen, but any search or creation gives me the following…
(if this has been covered before please point me to the thread - thanks)
An error occurred in the application program. Please report the following problem to your webmaster.
Exception is: < JspException >
Exception error message: <For action type=create the ‘form’ attribute has to be supplied because the orginal 'a’nchor tag has no value in the href attribute.>
Stacktrace is:
<javax.servlet.jsp.JspTagException: For action type=create the ‘form’ attribute has to be supplied because the orginal 'a’nchor tag has no value in the href attribute.
at com.softwareag.xtools.xapplication.jsptaglib.ActionTag.processAction(ActionTag.java:143)
at com.softwareag.xtools.xapplication.jsptaglib.CommandTag.doAfterBodyCore(CommandTag.java:139)
at com.softwareag.xtools.xapplication.jsptaglib.XBodyTag.doAfterBody(XBodyTag.java:126)
at view_2._jspService(view_2.java:206)
at org.apache.jasper.runtime.HttpJspBase.service(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java)
at org.apache.tomcat.facade.ServletHandler.doService(Unknown Source)
at org.apache.tomcat.core.Handler.invoke(Unknown Source)
at org.apache.tomcat.core.Handler.service(Unknown Source)
at org.apache.tomcat.facade.ServletHandler.service(Unknown Source)
at org.apache.tomcat.core.ContextManager.internalService(Unknown Source)
at org.apache.tomcat.core.ContextManager.service(Unknown Source)
at org.apache.tomcat.modules.server.Http10Interceptor.processConnection(Unknown Source)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Unknown Source)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Unknown Source)
at java.lang.Thread.run(Thread.java:484)
Hello,
if you did not change the generated JSPs, I have no guess why this error could occur.
Sometimes when we observed strange effects which the apllication, the proposal was:
(1) stop Tomcat
(2) delete the content of Tomcat’s work directory
(3) restart the Tomcat
(4) Check the URL you are entering to start the application. URLs are case sensitive even if Tomcat returns a search page, the session object will not be found. Therefore, if your directory is ‘Employee1’, the URL to start must be
E[/b]mployee1/search.jsp]http://localhost:8080/Employee1/search.jsp
Please, check also the starting letter of the serach page whether it is Search.jsp or search.jsp.
In general 90% of the errors could be solved in this way. If your problem still exists, please zip your application (JSPs + web.xml + schema.tsd) and post it to the community. I will try to reproduce it on my machine.
Bye,
Christian.
[This message was edited by Christian Freytag on 24 Mar 2003 at 15:07.]
Hi Christian.
I’m now trying to generate from a different schema (which I’ll attach - the schema is inside the zipped webapp). When I generated an x-app off employee schema, I got as far as seeing the Search.jsp after bouncing Tomcat. Then I got the JSP exception. I could not resolve this. So I have tried another schema (PurchaseOrder). With this schema all the directory structures are created under Tomcat as they should be. But I can’t access even the search.jsp (after taking your recommendations into account). http://localhost:8080/PurchaseOrder/
reveals the directory structure. Ican selecet the gifs and stylesheetys no problem.
http://localhost:8080/PurchaseOrder/Search.jsp
upper or lower case s, gives me a http 404,
as does
http://localhost:8080/PurchaseOrder/create.jsp
http://localhost:8080/PurchaseOrder/Back.jsp
Gives me the following…
Error: 500
Location: /PurchaseOrder/Back.jsp
Internal Servlet Error:
javax.servlet.ServletException
at org.apache.jasper.runtime.PageContextImpl.handlePageException(Unknown Source)
at Back_2._jspService(Back_2.java:84)
at org.apache.jasper.runtime.HttpJspBase.service(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java)
at org.apache.tomcat.facade.ServletHandler.doService(Unknown Source)
at org.apache.tomcat.core.Handler.invoke(Unknown Source)
at org.apache.tomcat.core.Handler.service(Unknown Source)
at org.apache.tomcat.facade.ServletHandler.service(Unknown Source)
at org.apache.tomcat.core.ContextManager.internalService(Unknown Source)
at org.apache.tomcat.core.ContextManager.service(Unknown Source)
at org.apache.tomcat.modules.server.Http10Interceptor.processConnection(Unknown Source)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Unknown Source)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Unknown Source)
at java.lang.Thread.run(Thread.java:484)
Root cause:
java.lang.NullPointerException
at Back_2._jspService(Back_2.java:58)
at org.apache.jasper.runtime.HttpJspBase.service(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java)
at org.apache.tomcat.facade.ServletHandler.doService(Unknown Source)
at org.apache.tomcat.core.Handler.invoke(Unknown Source)
at org.apache.tomcat.core.Handler.service(Unknown Source)
at org.apache.tomcat.facade.ServletHandler.service(Unknown Source)
at org.apache.tomcat.core.ContextManager.internalService(Unknown Source)
at org.apache.tomcat.core.ContextManager.service(Unknown Source)
at org.apache.tomcat.modules.server.Http10Interceptor.processConnection(Unknown Source)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Unknown Source)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Unknown Source)
at java.lang.Thread.run(Thread.java:484)
PurchaseOrder.zip (2.1 MB)
Hello,
which kind of X-Application and Tomcat are you currently using?
If you are using Tomcat 3.3a. I recommend to switch to Tomcat 3.3.1 or 3.3.1a. Please check your version Tomcat. Version 3.3a has a lot of problems (bugs) with X-Application. We detected that in some cases the session object is not correctly retrieved.
Bye,
Christian.
Hola.
I’m using Xapplication_311 and Tomcat 3.3 Final. I used to have no problem with xapplication running on this version of Tomcat.
Hello,
is it necessary to use X-Application 3.1.1?
If you generate a new application and could run against a Tamino database of version 4, I would propose to switch to X-Application 4.1.1.
Or, do you have to run against a Tamino database version 3.
The error you are describing does not look like an X-Application problem if the JSPs are not available (Error code 404). The stacktrace does not realy help me to understand the problem. There is not X-Application class involved.
Therefore, I would please you to install the following version of Tomcat
http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3.1a/bin/
My hope is that we will get more information about the problem with this version. And, based on my experience with Tomcat versions, this version has less bugs than Tomcat 3.3a.
Thank you.
Bye,
Christian.
X-Application Version: 4.1.1, 3.1.3