× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I would guess then that maybe the record is not converting for some 
reason, are there any error messages in the conversion log that comes up 
after the conversion is complete?

If you look for the generated jsp's and their corresponding data 
definition xml files do they exist in the project ?

Mike

Mike Hockings, P.Eng.
WebSphere Development Tools for AS/400  -  CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory 
hockings@xxxxxxxxxx 




"randys" <randys@xxxxxxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces+hockings=ca.ibm.com@xxxxxxxxxxxx
2004-09-24 13:42
Please respond to
Websphere Development Studio Client for iSeries 


To
wdsci-l@xxxxxxxxxxxx
cc

Subject
RE: [WDSCI-L] Webfacing DDS Issue







Mike,

Thanks for the resonse. I tried that, re-deployed, and it still didn't 
work. 
The DSPF is named BL8202DF and the record format is named BL820201.

Below is the entire additional Info:

Additional information :

     WF0100: The record data bean was either not found or was inconsistent 

with the DDS record in the display file. Try re-converting and deploying 
your 
DDS.

Details : 

com.ibm.as400ad.webfacing.runtime.core.WebfacingLevelCheckException: 
WF0015: 
The specified class or definition file 
{BOSS.QDDSSRC.BL8202DF.BL820201Data} 
could not be found. 
at java/lang/Throwable.(Throwable.java:195) 
at java/lang/Exception.(Exception.java:41) 
at com/ibm/as400ad/webfacing/runtime/core/WFException.(Unknown Source) 
at com/ibm/as400ad/webfacing/runtime/core/WebfacingLevelCheckException.
(Unknown Source) 
at 
com/ibm/as400ad/webfacing/runtime/controller/RecordDefinitionFetcher.loadClass
(Unknown Source) 
at 
com/ibm/as400ad/webfacing/runtime/controller/RecordDefinitionFetcher.loadJavaD
efinition(Unknown Source) 
at 
com/ibm/as400ad/webfacing/runtime/controller/CachingRecordDefinitionFetcher.re
questFromCache(Unknown Source) 
at 
com/ibm/as400ad/webfacing/runtime/controller/CachingRecordDefinitionFetcher.re
questDataDefinition(Unknown Source) 
at 
com/ibm/as400ad/webfacing/runtime/controller/RecordBeanFactory.loadRecordDataD
efinition(Unknown Source) 
at 
com/ibm/as400ad/webfacing/runtime/controller/RecordBeanFactory.loadRecordDataD
efinition(Unknown Source) 
at 
com/ibm/as400ad/webfacing/runtime/controller/RecordBeanFactory.createRecordDat
aBean(Unknown Source) 
at 
com/ibm/as400ad/webfacing/runtime/host/ADBDOutputBuffer.initializeFromOutputBu
ffer(Unknown Source) 
at com/ibm/as400ad/webfacing/runtime/host/ADBDOutputBuffer.(Unknown 
Source) 
at 
com/ibm/as400ad/webfacing/runtime/controller/ApplicationRequest.processApplica
tionRequests(Unknown Source) 
at 
com/ibm/as400ad/webfacing/runtime/controller/ApplicationRequest.handleApplicat
ionRequest(Unknown Source) 
at 
com/ibm/as400ad/webfacing/runtime/controller/ApplicationRequest.processHostDat
a(Unknown Source) 
at com/ibm/as400ad/webfacing/runtime/controller/WFState.processRequest
(Unknown Source) 
at 
com/ibm/as400ad/webfacing/runtime/controller/struts/actions/WebFacingAction.ex
ecute(Unknown Source) 
at org/apache/struts/action/RequestProcessor.processActionPerform
(RequestProcessor.java:484) 
at org/apache/struts/action/RequestProcessor.process
(RequestProcessor.java:217) 
at org/apache/struts/action/ActionServlet.process(ActionServlet.java:1481) 

at org/apache/struts/action/ActionServlet.doPost(ActionServlet.java:525) 
at javax/servlet/http/HttpServlet.service(HttpServlet.java:733) 
at javax/servlet/http/HttpServlet.service(HttpServlet.java:848) 
at org/mortbay/jetty/servlet/ServletHolder.handle(ServletHolder.java:328) 
at org/mortbay/jetty/servlet/WebApplicationHandler$Chain.doFilter
(WebApplicationHandler.java:312) 
at 
com/ibm/etools/iseries/webfacing/runtime/filters/WFCharacterEncodingFilter.doF
ilter(Unknown Source) 
at org/mortbay/jetty/servlet/WebApplicationHandler$Chain.doFilter
(WebApplicationHandler.java:312) 
at 
com/ibm/etools/iseries/webfacing/runtime/filters/CompressionFilter.doFilter
(Unknown Source) 
at org/mortbay/jetty/servlet/WebApplicationHandler$Chain.doFilter
(WebApplicationHandler.java:312) 
at org/mortbay/jetty/servlet/WebApplicationHandler.dispatch
(WebApplicationHandler.java:188) 
at 
org/mortbay/jetty/servlet/ServletHandler.handle(ServletHandler.java:499) 
at org/mortbay/http/HttpContext.handle(HttpContext.java:1695) 
at org/mortbay/jetty/servlet/WebApplicationContext.handle
(WebApplicationContext.java:545) 
at org/mortbay/http/HttpContext.handle(HttpContext.java:1590) 
at org/mortbay/http/HttpServer.service(HttpServer.java:827) 
at org/jboss/jetty/Jetty.service(Jetty.java:497) 
at org/mortbay/http/HttpConnection.service(HttpConnection.java:757) 
at org/mortbay/http/HttpConnection.handleNext(HttpConnection.java:828) 
at org/mortbay/http/HttpConnection.handle(HttpConnection.java:775) 
at 
org/mortbay/http/SocketListener.handleConnection(SocketListener.java:174) 
at org/mortbay/util/ThreadedServer.handle(ThreadedServer.java:286) 
at org/mortbay/util/ThreadPool$PoolThread.run(ThreadPool.java:442) 



-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Mike Hockings
Sent: Thursday, September 23, 2004 5:46 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Webfacing DDS Issue


If that is the case then maybe just go to the DSPF mapping page of the 
project properties and edit in the missing text?  Are there any special 
characters or something in the name, though I have not heard of any 
problems in this area.

Mike



Mike Hockings, P.Eng.
WebSphere Development Tools for AS/400  -  CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory 
hockings@xxxxxxxxxx 



All,

I'm having an issue adding a DSPF to a V5.2.1 webfacing project and 
deploying 
it to JBoss. I keep receiving WF0096 and WF0100 eventhough I've added and 
removed and added the DSPF back several time.
 When I add the display to my project and test it using WAS Test on my PC 
it 
works fine. If I have one of our web team members test it on their PC 
using 
JBoss V5.2.* it works fine. However, when I deploy it to our 400 and test 
it 
on JBoss V 5.0.* it doesn't work. All the other displays that were in the 
project before I added the last one still work but this one doesn't. The 
only 
difference I've noticed is that in the webfacing perspective properties 
window for this DDS is that for this one it just has a value of 
*LIB/DSPNAME 
whereas the others have *LIB/DSPNAME = /MYLIB/MYSRCF/DSPNAME.

Any help would be greatly appreciated.

TIA
Randy S.

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L) 
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L) 
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.