WLI2.1

I've just installed WLS6.1 and WLI2.1, and I'm trying to work through the
BPM samples that were part of the install. However, when I go to
Configuration >> Business Operations and double click on any of the sample
beans, I get a Class Not Found Exception.
Do I need to define a CLASSPATH or some other system variable for all of the
samples to be found?

Hi.
You might try posting this question to one of the WLI newsgroups -
weblogic.integration.interest or weblogic.integration.developer. Someone there
may be better able to answer your question.
Thanks,
Michael
Ron Pragides wrote:
I've just installed WLS6.1 and WLI2.1, and I'm trying to work through the
BPM samples that were part of the install. However, when I go to
Configuration >> Business Operations and double click on any of the sample
beans, I get a Class Not Found Exception.
Do I need to define a CLASSPATH or some other system variable for all of the
samples to be found?--
Michael Young
Developer Relations Engineer
BEA Support

Similar Messages

Migration from WLI2.0 to WLI2.1 - problems and solutions

We have experienced a number of issues when migrating from WLI2.0 (no service packs)
to WLI2.1 - We are only using the WLPI (BPM) part of WLI. We decided to publish
these issues in case they can be of help to others.
Problems:
1. The documentation (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#998197)
says the migration process works from WLPI 1.2.1 and from WLI 2.0 (SP2, 3, 4).
What about WLI2.0 with no service packs - I don't see why BEA should have left
out migration from that platform. We decided to follow the process and see what
happened.
2. There is no indication in the documentation of how to run the GUI based migration
tools on Unix, only for Windows so we had to follow the manual route.
3. The Manual process refers (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#999969)
to the DB variable setting scripts. It then says to run "migratedb.sh". None of
these files have extensions ".sh" - the files that were installed have no extension.
Obviously that did not stop us running them but the documentation needs correcting.
4. The migratedb scripts calls "WLI_HOME/setenv.sh" - it is confusing that there
is a second copy of this file in the bin folder called "setenv". Why are there
2 copies. Also I note that the one in bin is executable and the other is not.
All very confusing!!
5. The migratedb script fails to run because we have not previously run setDomain.
This is not documented.
6. Running setDomain on a domain moved from a WLI2.0 installaion fails since it
does not contain the expected folders. That basically means you cannot migrate
such a domain. We carried on with the process using the bpmdomain so that we could
at least migrate our database automatically.
7. Having run setDomain, we tried migratedb again but it failed because we had
not run switchdb. Again, this is not documented. We ran switchdb successfully.
8. Now running migratedb creates a file called "migrate.sh". Unfortunately the
script migratedb then attempts to run a file called "migrate". This is evidence
that no-one has ever tested this script at BEA and we are very disconcerted by
this fact!! We renamed the script and ran migratedb again - this time it ran the
migrate script.
9. This still fails with the following errors (when calling migrateCommonRep)
     -v (No such file or directory)
     null
     java.lang.NullPointerException
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:120)
     at com.bea.eci.migration.Migrate.getConnection(Migrate.java:207)
     at com.bea.eci.migration.Migrate.main(Migrate.java:73)
     java.lang.NullPointerException
     at com.bea.eci.migration.Migrate.main(Migrate.java:192)
10. It also fails because it cannot find "sqlplus" - a fatal problem - we do not
have sqlplus installed on the same machine as WLI and yet again this requirement
is not documented. At this point we gave up trying to run the migrate script as
there seemed to be no route forward.
The process we took to move from WLI2.0 (WLPI only) was as follows:
a. Since we had done no changes to filerealm.properties we simply copied the one
fron bpmdomain into our own domain.
b. We have been unable to run the step to migrate the common repository (see note
9). If this is referring to the XML repository then that should not be a problem
to us as we have not used it.
c. We moved the "migrate/BPM_20SP3-21.sql" script to an NT machine and ran that
script on our database. This seems to have successfully updated the database.
Lastly, having completed the migration process we tried to run the server but
it fails. This is because the startWeblogic script fails to call checkdomain properly.
We modified the line to become:
     ". $WLI_HOME/bin/checkdomain"     # the '.' was missing
Does anyone else have any experiences with this that would help us all?
Pete

Pete,
Please post this to the weblogic.integration.interest and weblogic.integration.developer newsgroups?
Pete Edwards wrote:
We have experienced a number of issues when migrating from WLI2.0 (no service packs)
to WLI2.1 - We are only using the WLPI (BPM) part of WLI. We decided to publish
these issues in case they can be of help to others.
Problems:
1. The documentation (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#998197)
says the migration process works from WLPI 1.2.1 and from WLI 2.0 (SP2, 3, 4).
What about WLI2.0 with no service packs - I don't see why BEA should have left
out migration from that platform. We decided to follow the process and see what
happened.
2. There is no indication in the documentation of how to run the GUI based migration
tools on Unix, only for Windows so we had to follow the manual route.
3. The Manual process refers (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#999969)
to the DB variable setting scripts. It then says to run "migratedb.sh". None of
these files have extensions ".sh" - the files that were installed have no extension.
Obviously that did not stop us running them but the documentation needs correcting.
4. The migratedb scripts calls "WLI_HOME/setenv.sh" - it is confusing that there
is a second copy of this file in the bin folder called "setenv". Why are there
2 copies. Also I note that the one in bin is executable and the other is not.
All very confusing!!
5. The migratedb script fails to run because we have not previously run setDomain.
This is not documented.
6. Running setDomain on a domain moved from a WLI2.0 installaion fails since it
does not contain the expected folders. That basically means you cannot migrate
such a domain. We carried on with the process using the bpmdomain so that we could
at least migrate our database automatically.
7. Having run setDomain, we tried migratedb again but it failed because we had
not run switchdb. Again, this is not documented. We ran switchdb successfully.
8. Now running migratedb creates a file called "migrate.sh". Unfortunately the
script migratedb then attempts to run a file called "migrate". This is evidence
that no-one has ever tested this script at BEA and we are very disconcerted by
this fact!! We renamed the script and ran migratedb again - this time it ran the
migrate script.
9. This still fails with the following errors (when calling migrateCommonRep)
-v (No such file or directory)
null
java.lang.NullPointerException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:120)
at com.bea.eci.migration.Migrate.getConnection(Migrate.java:207)
at com.bea.eci.migration.Migrate.main(Migrate.java:73)
java.lang.NullPointerException
at com.bea.eci.migration.Migrate.main(Migrate.java:192)
10. It also fails because it cannot find "sqlplus" - a fatal problem - we do not
have sqlplus installed on the same machine as WLI and yet again this requirement
is not documented. At this point we gave up trying to run the migrate script as
there seemed to be no route forward.
The process we took to move from WLI2.0 (WLPI only) was as follows:
a. Since we had done no changes to filerealm.properties we simply copied the one
fron bpmdomain into our own domain.
b. We have been unable to run the step to migrate the common repository (see note
9). If this is referring to the XML repository then that should not be a problem
to us as we have not used it.
c. We moved the "migrate/BPM_20SP3-21.sql" script to an NT machine and ran that
script on our database. This seems to have successfully updated the database.
Lastly, having completed the migration process we tried to run the server but
it fails. This is because the startWeblogic script fails to call checkdomain properly.
We modified the line to become:
". $WLI_HOME/bin/checkdomain" # the '.' was missing
Does anyone else have any experiences with this that would help us all?
Pete--
Developer Relations Engineer
BEA Support

Problem when migrate from WLI2.1 to WLI7

I met this problem when migrating my program from WLI2.1 to WLI7.
It report the following exception in WLI7:
<2002-10-21 下午05时05分15秒> <Error> <HTTP> <101019>
<[ServletContext(id=5904188,name=dkh
,context-path=/dkh)] Servlet failed with IOException
java.rmi.AccessException: Security Violation: User: 'admin' has insufficient permission
to
access EJB: type=<ejb>, application=WebLogic Integration, module=WLI-BPM Server,
ejb=WLPI
Principal, method=getRolesForUser, methodInterface=Remote, signature={java.lang.String,jav
a.lang.String,boolean}.
But it's fine in WLI2.1? Who can tell me why and how to solve it?
Thanks

####<13 oct. 2004 17 h 05 CEST> <Info> <JMS> <ucwwe2> ><ucwls81> <WrapperSimpleAppMain> <<WLS Kernel>> <> <BEA->040114> <JMSServer "JMSServer", Finished scan of file >store "persistence" in directory "c:\bin\bea\jmsstore".                     >Found 2 025 records totalling 21 205 248 bytes.>
          >####<13 oct. 2004 17 h 05 CEST> <Info> <JMS> <ucwwe2> ><ucwls81> <WrapperSimpleAppMain> <<WLS Kernel>> <> <BEA->?040056> <JMSServer "JMSServer". Deleting 2025 messages(s) with no matching destination.>
          My JMS experience on WLS 8.1 ain't great, purley from these error messages it looks like the destination of these messages is the problem. Can you double check the destination exists and is configured correctly.
          Hoos
          www.orbism.com

Problem with BPM tutorial in WLI2.1

Hi all,
I got a problem while running the BPM Tutorial in WLI2.1 which is
about Purchase Order. I have import Tutorial.jar and set active to the
workflow. When the workflow start and flow to the node "Check
Inventory", an exception threw as shown:
The server was unable to complete your request.
System error: Unable to load class object for remote interface of type
"com.bea.wlpi.tour.po.PurchaseOrderHome";
java.lang.ClassNotFoundException:
com.bea.wlpi.tour.po.PurchaseOrderHome.
Workflow error: com.bea.wlpi.common.WorkflowException: Unable to load
class object for remote interface of type
"com.bea.wlpi.tour.po.PurchaseOrderHome";
java.lang.ClassNotFoundException:
com.bea.wlpi.tour.po.PurchaseOrderHome.
<<no stack trace available>>
I used the domain "bpmdomain" in WLI2.1. It seems to me that the
Business operation was set properly and the related EJB can be called by
writing an EJB client. But why the BPM can't call that EJB create()? Is
there anything I have missed to set?
Thx a lot.
Regards,
Karen

Sounds like something's messed up. Make sure pobean.jar is in
$WLI_HOME/lib, and deployed in config/bpmdomain/config.xml as part of the
WLI Application.
"Karen Law" <[email protected]> wrote in message
news:[email protected]..
Hi all,
I got a problem while running the BPM Tutorial in WLI2.1 which is
about Purchase Order. I have import Tutorial.jar and set active to the
workflow. When the workflow start and flow to the node "Check
Inventory", an exception threw as shown:
The server was unable to complete your request.
System error: Unable to load class object for remote interface of type
"com.bea.wlpi.tour.po.PurchaseOrderHome";
java.lang.ClassNotFoundException:
com.bea.wlpi.tour.po.PurchaseOrderHome.
Workflow error: com.bea.wlpi.common.WorkflowException: Unable to load
class object for remote interface of type
"com.bea.wlpi.tour.po.PurchaseOrderHome";
java.lang.ClassNotFoundException:
com.bea.wlpi.tour.po.PurchaseOrderHome.
<<no stack trace available>>
I used the domain "bpmdomain" in WLI2.1. It seems to me that the
Business operation was set properly and the related EJB can be called by
writing an EJB client. But why the BPM can't call that EJB create()? Is
there anything I have missed to set?
Thx a lot.
Regards,
Karen

[q] WLI2.0 on WL6.1

hI,
Can I run WLI2.0 on WL6.1, If Yes, How ?
Thanxs,
Ronen Yaari

Ronen
NO a release is due out shortly that addresses the 6.1 release.
Tony
"Ronen Yaari" <[email protected]> wrote in message
news:[email protected]..
>
hI,
Can I run WLI2.0 on WL6.1, If Yes, How ?
Thanxs,
Ronen Yaari

Install of WLI2.1 with exising WLS6.1 domains

Hi - I am looking for information about how to install/configure WLI2.1 to use an existing WLS6.1 installation.
I already have a wls6.1 domain configured and running, and I want to configure WLI2.1 to use this existing domain (ie I don't want to use the WLI supplied example domains).
This seems like an obvious thing to do although I can't find any details in the documentation?
Thanks, Kevin

kevin,
Please post this to the weblogic.integration.interest and weblogic.integration.developer newsgroups?
Kevin Hooke wrote:
Hi - I am looking for information about how to install/configure WLI2.1 to use an existing WLS6.1 installation.
I already have a wls6.1 domain configured and running, and I want to configure WLI2.1 to use this existing domain (ie I don't want to use the WLI supplied example domains).
This seems like an obvious thing to do although I can't find any details in the documentation?
Thanks, Kevin--
Developer Relations Engineer
BEA Support

WLAN | wireless PCI card | Buffalo WLI2-PCI-G54S

I need a WLAN solution for my old and beloved smurf...
I have read about the Buffalo WLI2-PCI-G54S and a compatible Broadcom chipset...
This card is still available... but does it still have the broadcom chip these days? And is it really working-out-of-the-box?
Anyone with experiences?
TIA!

Belkin Wireless G Gaming Adapter
May be this is an alternative, cause there is no driver issue, or am i wrong?
Any wireless Ethernet bridge device should work well. Examples include Belkin F5D7330 (please note that there are two variants, one with one and one with two antennas), D-Link DWL-G810 or DWL-G820, Linksys WET54G and Netgear WGE111. Also, Linksys has introduced an N model (WGA600N), which appears to be something similar. Normally, wireless Ethernet bridge devices do not require special drivers at all, and can thus be used under almost any operating system.
The various models (or versions of a model) may or may not support WPA security. A firmware update (which, typically, has to be carried out on a PC) may be sufficient. So, check the specifications (and the firmware download sites).
Jan

Multiple Servers for Development Team in WLI2.1 on wlidomain

Has anyone tried to create multiple servers so that a development team can share
the resources of a domain with WLI 2.1? If so, how did it work. I have done this
with WLS but would like to try it with WLI.
I tried to create multiple servers, but, had difficulty as there seems to many
resources that are tied to the server name and default port. Also, I tried to
change the port and that caused alot of problems on the myserver.

Thanks John.
I was not looking for something which is scaling out Hyperion Planning(via load balancer)/Horizontal clustering.
But was looking for some thing like Vertical clustering(multiple JVMs/nodes of Hyperion Planning within a single planning server) which was applicable in 11.1.1.3.
Came to know that with 11.1.2.2 vertical clustering not more supported.
Thanks

Defining Business Operations using remote session EJBs for WLI2.1

Hello all,
I'm having a deployment issue with WLI 2.1. Is it true that in order to define
a Business Operation in WLI 2.1 that uses a session EJB, the EJB MUST be deployed
in the same JNDI tree (WLS instance) that WLI is running on? Is everyone just
running one admin server that hosts WLI and all other applications on the same
instance?
I'd like to have WLI running on one machine and have my applications running on
another, but at this point seems unobtainable because you cant supply a t3 URL
to that separate machine when defining Business Operations...
Any help would be appreciated,
Jon

I am new to WLPI and have run across this problem as well. Could you
provide more detail your proxy session bean and maybe include some
example code? Thanks.
Regards,
Rick H.
"Paul Rooney" <[email protected]> wrote:
>
I have come accross the same problem - solved it by using a "proxy" session
bean
that knows how to call out to all the Remote EJBS that I need. This "proxy"
session
bean is deployed with wlpi application.
"Erik Godding Boye" <[email protected]> wrote:
We would like to define business operations in WLI calling EJBs on a
remote machine.
It seems like the EJB have to be deployed locally to appear in the (JNDI)
drop-down
list when defining the business operation.
Is the only way to achieve this functionality to write (or generate)
some kind
of wrapper EJB that will be deployed locally, or do you have other suggestions?
Regards,
E
PS: We're using WLI 2.1 running on WLS 6.1 SP1

WLI2.1 Timed workflow is executing in a loop

In Wbelogic Integrator 2.1 I have created a scheduled workflow.
If you go to the start Task properties and click on the timed radio button and
put a start date for the execution of the workflow.
The worklfow starts at that particular time but never ends.
It keeps on executing the workflow again and again.
Please help.

The problem seems to have resolved itself.

WLI2.1 Install script error?

The bpmdomain startweblogic.cmd script refers to %WLSERVERCP% unlike all
other domains which refer to %SVRCP% - is this an error?

Hi.
Most of our scripts set this environment variable earlier in the script.
This is probably ok if the start script sets WLSERVERCP prior to using it.
Regards,
Michael
Bob Radcliffe wrote:
The bpmdomain startweblogic.cmd script refers to %WLSERVERCP% unlike all
other domains which refer to %SVRCP% - is this an error?--
Michael Young
Developer Relations Engineer
BEA Support

WebLogic Error : Registered more than one instance with the same objectName

HI there, I'm facing a big problem. I have two environments installed on the same physical machine.
I have ALSB and WLI servers running out there.
Environment 1 - WLI port running at 7011 domain name : stp_wli_domain and ALSB port running at 8011 domain name: stp_alsb_homo1 - folders- stp_wli_domain / stp_bea_alsb_homo
Environmnet 2 - WLI port running at 7211 domain name : stp_wli_domain2 and ALSB port tunning at 8211 domain name : stp-alsb_homo2 - folders - stp_wli_domain2 / stp_bea-alsb_homo2
Everything was working fine, but these days I had install new deployments on both environment and I got this error :
java.lang.IllegalArgumentException: Registered more than one instance with the same objectName : stp_wli_domain:ServerRuntime=wli_wls01,Name=stp_wli_domain,Location=wli_wls01,Type=AIRuntime new:com.bea.wlai.management.AIRuntimeMBeanImpl@bcf22dc existing com.bea.wlai.management.AIRuntimeMBeanImpl@de02e6c
The weird is : There is no same object name, as you can see, domains are different, folders are different and ports are diferrent, including multicast addresses.
Have you guys seen this before ?
I'm under pressure here, 'cause some projects had stopped to work.
Please I would appreciate any help.
Tks.
Edson

HI there, thanks for attention..
See ...
There's a lot of confusion with these env's .
I did not built this, so... I'm cleaning my hands.... anyway... :)
I must fix....
Well basically if we have two env's, so we have different project each one right ?
Ok, but I was told that if you have on the same network and same physical machine the name of AdminServer as "AdminServer" in all domains, so it goes with problems... I never heard about it... but is a good practice you put the names for example :
WLI - WLIAdminServer
ALSB - AlsbAdminServer
WLI2 - WLiadminServer2
ALSB2 - ALsbAdminServer2
I would do it.. this way..
But how it wasn't me...
We got..
WLI - WliAdminServer
ALsb - AdminServer
WLI2 - AdminServer
ALsb2 - AdminServer
Have you got it ?
So... I was told that this could be a problem, almost all AdminServers with the same name... guess what ?Some Projects are back to work. but not at all.. only some.. so I 'm breathing better now... but I would like to know if you seen this before ?
I would appreciate your help again.
Unfortunately there's no detailed stack trace to track this
Tks.

Adding SimpleContent to a schema results in error

Hi,
Am using WLI2.1 for developing adapter. While creating the Request and
Response schema for my adapter, am adding 'SimpleContent' element to it
using ADK. But adding this gives me an error, as
the schema formed is not syntactically correct, so the parsing gives an
error and so WLI is not able to save the schema in the repository.
The part of the code I have written is something like this :
SOMAttribute attrb = new SOMAttribute ("xsi:nil");
attrb.setFixed ("true");
attrb.setUse (SOMAttribute.OPTIONAL);
SOMExtension ext = new SOMExtension (SOMType.getType ("long"));
ext.addAttribute (attrb);
SOMComplexType complexType = element.addComplexType ();
blankComplexType.addSimpleContent (ext);
The schema that it produces is this :
<xsd:element name="EMPID">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:long">
<xsd:attribute name="xsi:nil" type="xsd:string"/>
</xsd:extension>
<xsd:simpleContent/>
</xsd:complexType> <<<-------------------- This
is where the error is !!!
</xsd:element>
If you look at the closing tag of xsd:simpleContent, then its not well
formed. It should be </xsd:simpleContent> instead of <xsd:simpleContent/>.
The stack trace is pasted below.
I think this is a bug, can anyone confirm this. If not then please let me
know what am doing wrong.
The same happens for complexContent too.
The stack trace is :
Document Parse Exception: com.bea.document.DocumentParseException:
Couldn't fromXML(InputSource) - The element type "xsd:simpleContent" must be
terminated by the matching end-tag "</xsd:simpleContent>".
Linked Exception...
org.xml.sax.SAXParseException: The element type "xsd:simpleContent"
must be terminated by the matching end-tag "</xsd:simpleContent>".
Public ID: null
System ID: null
Line: 18
Column: 34
Public ID: null
System ID: null
Line: 18
Column: 34
at com.bea.document.internal.Document.fromXML(Document.java:465)
at com.bea.document.internal.Document.<init>(Document.java:113)
at com.bea.document.internal.Document.<init>(Document.java:101)
at
com.bea.wlai.repository.SchemaPersistence.updateSchema(SchemaPersistence.jav
a:228)
at
com.bea.wlai.client.bean.SchemaManagerImpl.updateSchema(SchemaManagerImpl.ja
va:175)
at
com.bea.wlai.client.bean.SchemaManagerBean.updateSchema(SchemaManagerBean.ja
va:139)
at
com.bea.wlai.client.bean.SchemaManagerBean_meazej_EOImpl.updateSchema(Schema
ManagerBean_meazej_EOImpl.java:259)
at
com.bea.adapter.web.AbstractDesignTimeRequestHandler.updateSchemaInRepositor
y(AbstractDesignTimeRequestHandler.java:2500)
at
peoplesoft.web.DesignTimeRequestHandler.editServiceDescriptor(DesignTimeRequ
estHandler.java:353)
at
com.bea.adapter.web.AbstractDesignTimeRequestHandler.edtservc(AbstractDesign
TimeRequestHandler.java:2112)
at java.lang.reflect.Method.invoke(Native Method)
at
com.bea.web.ControllerServlet.processRequest(ControllerServlet.java:356)
at
com.bea.web.ControllerServlet.doAction(ControllerServlet.java:282)
at com.bea.web.ControllerServlet.doPost(ControllerServlet.java:175)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2456)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Thanks
Amit

Thanks Chris,
Does BEA maintain list of bugs on its site, so that we can go and check
there. That will really save a lot of time.
Thanks always for the replies.
Amit Chauhan
Chris Stead <[email protected]> wrote in message
news:[email protected]...
Amit,
Yes, that is a known bug in WLI 2.1 and is fixed in Service Pack 1. Sorryfor
the inconvenience.
Cheers,
Chris
Amit wrote:
Sorry, the blankComplexType is basically compleType :
Read
complexType.addSimpleContent (ext);
instead of
blankComplexType.addSimpleContent (ext);
Thanks
Amit
Amit <[email protected]> wrote in message
news:[email protected]...
Hi,
Am using WLI2.1 for developing adapter. While creating the Request and
Response schema for my adapter, am adding 'SimpleContent' element to
it
using ADK. But adding this gives me an error, as
the schema formed is not syntactically correct, so the parsing givesan
error and so WLI is not able to save the schema in the repository.
The part of the code I have written is something like this :
SOMAttribute attrb = new SOMAttribute ("xsi:nil");
attrb.setFixed ("true");
attrb.setUse (SOMAttribute.OPTIONAL);
SOMExtension ext = new SOMExtension (SOMType.getType ("long"));
ext.addAttribute (attrb);
SOMComplexType complexType = element.addComplexType ();
blankComplexType.addSimpleContent (ext);
The schema that it produces is this :
<xsd:element name="EMPID">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:long">
<xsd:attribute name="xsi:nil"type="xsd:string"/>
</xsd:extension>
<xsd:simpleContent/>
</xsd:complexType><<<--------------------
This
is where the error is !!!
</xsd:element>
If you look at the closing tag of xsd:simpleContent, then its not well
formed. It should be </xsd:simpleContent> instead of
<xsd:simpleContent/>.
>>>
The stack trace is pasted below.
I think this is a bug, can anyone confirm this. If not then please letme
know what am doing wrong.
The same happens for complexContent too.
The stack trace is :
Document Parse Exception:com.bea.document.DocumentParseException:
Couldn't fromXML(InputSource) - The element type "xsd:simpleContent"must
be
terminated by the matching end-tag "</xsd:simpleContent>".
Linked Exception...
org.xml.sax.SAXParseException: The element type"xsd:simpleContent"
must be terminated by the matching end-tag "</xsd:simpleContent>".
Public ID: null
System ID: null
Line: 18
Column: 34
Public ID: null
System ID: null
Line: 18
Column: 34
at
com.bea.document.internal.Document.fromXML(Document.java:465)
atcom.bea.document.internal.Document.<init>(Document.java:113)
atcom.bea.document.internal.Document.<init>(Document.java:101)
at
com.bea.wlai.repository.SchemaPersistence.updateSchema(SchemaPersistence.jav
a:228)
at
com.bea.wlai.client.bean.SchemaManagerImpl.updateSchema(SchemaManagerImpl.ja
va:175)
at
com.bea.wlai.client.bean.SchemaManagerBean.updateSchema(SchemaManagerBean.ja
va:139)
at
com.bea.wlai.client.bean.SchemaManagerBean_meazej_EOImpl.updateSchema(Schema
ManagerBean_meazej_EOImpl.java:259)
at
com.bea.adapter.web.AbstractDesignTimeRequestHandler.updateSchemaInRepositor
y(AbstractDesignTimeRequestHandler.java:2500)
at
peoplesoft.web.DesignTimeRequestHandler.editServiceDescriptor(DesignTimeRequ
estHandler.java:353)
at
com.bea.adapter.web.AbstractDesignTimeRequestHandler.edtservc(AbstractDesign
TimeRequestHandler.java:2112)
at java.lang.reflect.Method.invoke(Native Method)
at
com.bea.web.ControllerServlet.processRequest(ControllerServlet.java:356)
at
com.bea.web.ControllerServlet.doAction(ControllerServlet.java:282)
atcom.bea.web.ControllerServlet.doPost(ControllerServlet.java:175)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
atjavax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2456)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2039)
atweblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Thanks
Amit

Xml into war file

How I can read an xml file with SAX or DOM into a war file?. I have WLS 6.1 SP4
with WLI2.1 SP2.
I can read a xml file, but when I create a war file, the aplication does not find
the xml file. When it tries to find it, it looks on the path but not on the war
which contains the xml file needed.
This is the instruction given:
String uri = "Menu.xml";
DocumentBuilderFactory factory =DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
Document doc = builder.parse( uri );
And the error message displayed is:
File "file:///c:/bea/wli21/Memu.xml" not found
Coments please!!
Edy

The error is calss org.xml.sa.SAXParseException: File "localhost:7001/Menu.xml"
not found
I change localhost by the correct IP.
Tks.
Edy
"Karthik V" <[email protected]> wrote:
What error message are you getting now?
Can you produce the trace?
Try using File or InputStream while Parsing.
That will help you to narrow down the error.
/k
"Edith Barra" <[email protected]> wrote in message
news:3ea594cc$[email protected]..
The error persist.
Help me!!
Tks.
Edy
"Karthik V" <[email protected]> wrote:
Try modifying your uri value to http://localhost:7001/Menu.xml
Substitute correct port and docroot for the xml location.
/k
"Edith Barra" <[email protected]> wrote in message
news:3ea572aa$[email protected]..
How I can read an xml file with SAX or DOM into a war file?. I haveWLS
6.1 SP4
with WLI2.1 SP2.
I can read a xml file, but when I create a war file, the aplicationdoes
not find
the xml file. When it tries to find it, it looks on the path but
not
on
the war
which contains the xml file needed.
This is the instruction given:
String uri = "Menu.xml";
DocumentBuilderFactory factory =DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
Document doc = builder.parse( uri );
And the error message displayed is:
File "file:///c:/bea/wli21/Memu.xml" not found
Coments please!!
Edy

Parse problem using SOMSchema reading an .xsd file

          Platform: windowsXP, WLI2.1, WLS6.1sp1
          The following is extracted from a log of the sample WLI server.
          I used it as a platform for an adapter under development.
          The log shows an erronous SOMSchema after a failed creation of an application
          view.
          The cause is long before. During a parse of a schema.xsd from a file into a SOMSchema
          it loses a '/'.
          <xsd:element name="Value">
          <xsd:complexType>
          <xsd:complexContent>
          <xsd:extension base="xsd:complexType">
          <xsd:attribute name="col" use="required"/>
          <xsd:attribute name="row" use="required"/>
          </xsd:extension>
          --> <xsd:complexContent/>
          </xsd:complexType>
          </xsd:element>
          Of course I worked around by dropping the tag </xsd:complexContent/>. Without
          all parses allright.
          From the erronous SOMSchema you can derive valid DocumentRecords.
          For that reason I guess the problem is to be found in the schema package.


          Platform: windowsXP, WLI2.1, WLS6.1sp1
          The following is extracted from a log of the sample WLI server.
          I used it as a platform for an adapter under development.
          The log shows an erronous SOMSchema after a failed creation of an application
          view.
          The cause is long before. During a parse of a schema.xsd from a file into a SOMSchema
          it loses a '/'.
          <xsd:element name="Value">
          <xsd:complexType>
          <xsd:complexContent>
          <xsd:extension base="xsd:complexType">
          <xsd:attribute name="col" use="required"/>
          <xsd:attribute name="row" use="required"/>
          </xsd:extension>
          --> <xsd:complexContent/>
          </xsd:complexType>
          </xsd:element>
          Of course I worked around by dropping the tag </xsd:complexContent/>. Without
          all parses allright.
          From the erronous SOMSchema you can derive valid DocumentRecords.
          For that reason I guess the problem is to be found in the schema package.

WLI2.1

Similar Messages

Maybe you are looking for