|
Home > Archive > WebSphere Portal Server > February 2007 > Portal 6 XMLAccess deploy portlet script issue -
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Portal 6 XMLAccess deploy portlet script issue -
|
|
| marc_dauncey 2007-02-28, 1:18 pm |
| Hi everyone, I have a problem with an XMLAccess script I am trying to use to deploy a custom portlet to a WebSphere Portal 6.0.0.1 server. Essentially XMLAccess is having problems parsing what I assume is the XMLAccess script and throws a sun.io.Malformed
InputException.
Am I right in thinking this could be a file format or locale issue?
Heres the stack trace:
[28/02/07 14:40:48:066 GMT] 00000036 XmlCommandSer E com.ibm.wps.command.xml.XmlCommandServlet doPost EJPFB0002E: Exception occurred.
com.ibm.wps.command.CommandFailedException: EJPFB0005E: An unexpected exception occurred.
WrappedException is: com.ibm.wps.command.xml.XmlCommandException: EJPXA0001E: An error occurred while processing the XML configuration request. unknown
StackTrace of the WrappedException:
com.ibm.wps.command.xml.XmlCommandException: EJPXA0001E: An error occurred while processing the XML configuration request. unknown
at com.ibm.wps.command.xml.XmlAccessReader. getRequestSchemaDefinition(XmlAccessRead
er.java:280)
at com.ibm.wps.command.xml.XmlUtils.getEngine(XmlUtils.java:145)
at com.ibm.wps.command.xml.XmlCommand.execute(XmlCommand.java:154)
at com.ibm.wps.command.xml.XmlCommandServlet.processInternal(XmlCommandServlet.java:272)
at com.ibm.wps.command.xml.XmlCommandServlet.process(XmlCommandServlet.java:260)
at com.ibm.wps.command.xml.XmlCommandServlet.doPost(XmlCommandServlet.java:214)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1282)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:673)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:89)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1897)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:84)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:472)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:411)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:288)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback. sendToDiscriminaters(NewConnectionInitia
lReadCallback.java:207)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback. complete(NewConnectionInitialReadCallbac
k.java:109)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
Caused by: sun.io.MalformedInputException
at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java(Compiled Code))
at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java(Inlined Compiled Code))
at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java(Compiled Code))
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java(Compiled Code))
at java.io.InputStreamReader.read(InputStreamReader.java(Compiled Code))
at com.ibm.wps.command.xml.XmlAccessReader.appendBuffer(XmlAccessReader.java:298)
at com.ibm.wps.command.xml.XmlAccessReader. getRequestSchemaDefinition(XmlAccessRead
er.java:214)
... 22 more
And here is the script:
<?xml version="1.0" encoding="UTF-8"?>
<request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PortalConfig_1.3.1.xsd" type="update" create-oids="true">
<portal action="locate">
<!-- As jsr168 portlets don't have a uid defined in the portlet.xml use "projectname.war.webmod" as uid value -->
<web-app action="update" active='true' uid="deploytest.war.webmod">
<url>file:///c:/deploy/deploytest.war</url>
<portlet-app action="update" active="true" uid="deploytest.war">
<portlet action="update" active="true" name="deploytest" />
</portlet-app>
</web-app>
</portal>
</request>
Many thanks if anyone could shed some light!
Marc
| |
|
| The only obvious problem I see is that you're using an old xsd-file as namespace.
You should use PortalConfig_1.4.0.1.xsd for WPS 6.0.0.1 but I guess that PortalConfig_1.4.xsd would work as well.
Here's a reference link for you:
http://publib.boulder.ibm.com/infoc...s/adxmlchg.html
/Jonas V
| |
| marc_dauncey 2007-02-28, 1:18 pm |
| Thank you, changed that as per your message.
Still having the same problem - got to be something specific to my portal server, as I think I've eliminated all the obvious things, such as removing trailing spaces and saving files as UTF-8 UNIX format.
When my colleague runs the script from the same war, XMLAccess script and batch file, it works right away. I'm wondering whether I need to patch my portal server. I recently brought it up to 6.0.0.1 which appeared to be successful. Theres nothing specific
in the logs apart from that stack trace.
Marc
|
|
|
|
|