[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrp-interop] BEA's producer/consumer now online
This is the comment I was about to make. The Consumer gets the choice of whether to parse the multipart mime into an array of UploadContext structures (one per mime part) or simply pass through the multipart message using a single UploadContext structure. The last discussion of this I remember thought that most Consumers would choose the array of UploadContext structures as they likely will have already parsed the multipart message anyway, but we left the option in for the Consumer to recognize that it did not need to do the parsing and therefore pass it straight through to the Producer.
Rich
David Ward <david.ward@oracle.com> 09/11/2003 09:49 AM
Subbu Allamaraju <subbu@bea.com> wsrp-interop@lists.oasis-open.org Re: [wsrp-interop] BEA's producer/consumer now online
I think the spec was left flexible so that it was valid to send a single multipart MIME message as a single UploadContext or multiple MIME parts as multiple UploadContexts. In the case of JSR 168, when the upload data is only available as an InputStream, it doesn't make sense for the consumer to split out all the individual MIME parts and then for the producer to join them all back together.
Subbu Allamaraju wrote:
David,
My interpretation of the spec is that each MIME part corresponds to an UploadContext. For example, if a form has two parameters and two files for upload, there would be four UploadContext elements (two for fields and two for files), each with its own content type and set of mimeAttributes.
The producer is then responsible for aggregating the parts into a single InputStream. So, I would not be concerned about boundary attributes.
It seems to me that some of these details are underspecified in the spec.
Regards,
Subbu
David Ward wrote:
All I'm saying is that it's important that you keep the full content type of a multipart form message intact, including its boundary attribute. So the mimeType field would require an attribute part. Is this legal?
The Oracle consumer is forwarding a single UploadContext corresponding to the multipart mime message, rather than multiple upload contexts corresponding to each message part (this makes it much easier to map straight to a JSR 168 request input stream) So it's important that the boundary attribute (and when I say attribute I mean in the MIME sense) is communicated.
Dave
Andre Kramer wrote:
Content-Disposition would be good to support but Content-Type as a MIME attribute would be redundant.
e.g.
Content-Disposition: form-data; name="files"; filename="file1.txt".
for file1.txt posted using the files input.
thanks,
Andre
-----Original Message-----
*From:* David Ward [mailto:david.ward@oracle.com]
*Sent:* 11 September 2003 11:58
*To:* Andre Kramer
*Cc:* Subbu Allamaraju; wsrp-interop@lists.oasis-open.org
*Subject:* Re: [wsrp-interop] BEA's producer/consumer now online
Andre Kramer wrote:
The name mimeAttributes was perhaps unfortunate as the MIME spec
uses "attribute" for the name part of a content-Type's
name=value parameter pairs. Such attributes should be part
of the UploadContext.mimeType string.
So I agree our mimeAttributes are primarily for MIME headers -
but these should be optional and extensible. The only required
MIME header is the content-type which we carry in
UploadContext.mimeType. We should not depend on others
(MIME-Version) or re-define standard ones (those starting with
"content-").
Our consumer does not add any standard (content-) headers to a
posted data value other than MIMEtype.
Also, I add a "filename" as an additional attribute as well as a
"fieldname" to supply additional (hopefully useful) information
which producers are free to ignore.
But there's already a standard way of transmitting the filename
in the Content-Disposition header as an attribute. See
http://www.w3.org/TR/html401/interact/forms.html#h-17.13.4.2 By
the way, it's important that you forward on the
Content-Disposition headers as they also carry the name of the
form field from which the file was submitted. Otherwise you don't
know which file corresponds to which field.
It looks like Content-Type (including boundary attribute) and
Content-Disposition (with name and optional filename attributes)
are the only headers our upload portlet relies on.
MIME interpreters are allowed to not handle inputs but, in the
interest of interop testing, I was asking if this was the case
with your portlets/producer (i.e. what standard headers, if
any, you expect)?
regards,
Andre
-----Original Message-----
*From:* David Ward [mailto:david.ward@oracle.com]
*Sent:* 10 September 2003 19:30
*To:* Subbu Allamaraju
*Cc:* wsrp-interop@lists.oasis-open.org
*Subject:* Re: [wsrp-interop] BEA's producer/consumer now online
Yes I agree - mimeAttributes should have MIME header semantics.
Subbu Allamaraju wrote:
Andre,
Since there is no way to advertise to required
mimeAttributes, we could agree to interpret mimeAttributes
to be MIME headers for that part (and clarify in 1.1).
Atleast, this assumption allowed our consumer to automate
the creation of UploadContext without concerning about the
meaning of each mimeAttribute.
Dave - do you agree?
Regards,
Subbu
Andre Kramer wrote:
We have no way for a portlet to advertise required
attributes. Should we agree on a minimal set for interop?
regards,
Andre
-----Original Message-----
From: Subbu Allamaraju [mailto:subbu@bea.com]
Sent: 10 September 2003 18:19
To: wsrp-interop@lists.oasis-open.org
Subject: Re: [wsrp-interop] BEA's producer/consumer now
online
Eric,
We should have a fix ready today/tomorrow to handle the
incorrect
mimeAttributes. Essentially, with our fix, our producer
runtime will not
fail due to incorrect mimeAttributes, but the portlet will
fail to
process the request (which is valid).
Thanks
Subbu
Eric Xu wrote:
>Oh, I see the problem now. The portlet takes the entire
mime-headers (i.e. content-disposition, and content-type)
as mime attributes. I, instead, put content-type in the
UploadContext.mimetype field, and further parsed
content-disposition, and put its attributes in the
UploadContext.mimeAttribute field.
>
>Btw, the monitoring tool is cute. =) Thanks, Subbu.
>Eric
>
>-----Original Message-----
>From: Subbu Allamaraju [mailto:subbu@bea.com]
>Sent: Tuesday, September 09, 2003 6:40 PM
>To: wsrp-interop@lists.oasis-open.org
>Subject: Re: [wsrp-interop] BEA's producer/consumer now
online
>
>
>Eric,
>
>You can debug this from our consumer
>(http://wsrp.avitek.com:8001/consumer/portal.portal). The
portlet is on
>the second page. Just before uploading the files, open
>http://wsrp.avitek.com:8001/consumer/monitor to view the
traffic. You
>can see the outgoing message.
>
>Regards,
>
>Subbu
>
>Eric Xu wrote:
>
> >
>>Oh, forgot to ask. Has anyone successfully uploaded a
file? Subbu, if possible, can I have a trace of a request
that works, so I know what I'm missing?
>>
>>Thanks,
>>Eric
>>
>>-----Original Message-----
>>From: Eric Xu
>>Sent: Tuesday, September 09, 2003 3:57 PM
>>To: 'Subbu Allamaraju'; wsrp-interop@lists.oasis-open.org
>>Subject: RE: [wsrp-interop] BEA's producer/consumer now
online
>>
>>
>>Thanks everyone for your response. Just to clarify,
yes, I was trying to forward the name/value pairs in
multipart headers. I'm using Orielly's MultipartParser
api. This api parses the multipart http headers and omits
some params, such as creation-date etc, and for "filename"
and "name" params in FilePart, it doesn't give you the
original pair, but provides getFilePath and getName
methods. That's the reason I have to hardcode "filename"
in order to preserve the original pair. As a summer
intern, I'm not brave enough to invent my own way yet. =)
>>
>>Anyways, my request saves all the parameters now, but
I'm still getting the same npe. >>
>>Subbu, see if this trace can help us identify the
problem. Based on rfc1867, for multiparts that do not
contain a content-type, I'm sending text/plain mimetype. Thanks for noticing the problem of my filedata encoding. Yes, I was calling a wrong encoding method.
>>
>>Thanks,
>>Eric
>>
>>-----Original Message-----
>>From: Subbu Allamaraju [mailto:subbu@bea.com]
>>Sent: Tuesday, September 09, 2003 8:58 AM
>>To: wsrp-interop@lists.oasis-open.org
>>Subject: Re: [wsrp-interop] BEA's producer/consumer now
online
>>
>>
>>Our interpretation is that mimeAttributes are the MIME
headers, and
>>since the request does not have these headers, the
producer is probably
>>getting the NPE. We're looking into the NPE.
>>
>>Eric,
>>
>>I also noticed that the data you're sending looks like
plain text and
>>not base64 encoded.
>>
>>Regards,
>>
>>Subbu
>>
>>
>>Rich Thompson wrote:
>>
>> >>
>>>What would this mean on a SOAP message? The
mimeAttributes array was
>>>introduced as an unambiguous way to get the mime data
to the Producer.
>>>
>>>Rich
>>>
>>>
>>>*David Ward <david.ward@oracle.com>*
>>>
>>>09/09/2003 06:51 AM
>>>
>>> >>>To
>>> Andre Kramer <andre.kramer@eu.citrix.com>
>>>cc
>>> "'Eric Xu'" <Eric.Xu@plumtree.com>, Subbu
Allamaraju <subbu@bea.com>,
>>>wsrp-interop@lists.oasis-open.org
>>>Subject
>>> Re: [wsrp-interop] BEA's producer/consumer now online
>>>
>>>
>>> >>>
>>>
>>>
>>>
>>>
>>>I had assumed clients would just forward all the
original headers from
>>>the multipart mime message intact. Why invent a new way
of carrying the
>>>filename?
>>>
>>>David
>>>
>>>Andre Kramer wrote:
>>>
>>>I'm also using a mime attribute to carry the filename.
>>>
>>>regards,
>>>Andre
>>>
>>>-----Original Message-----
>>>From: Eric Xu [_mailto:Eric.Xu@plumtree.com_]
>>>Sent: 09 September 2003 02:29
>>>To: Subbu Allamaraju; Andre Kramer;
_wsrp-interop@lists.oasis-open.org_
>>><mailto:wsrp-interop@lists.oasis-open.org>
>>>Subject: RE: [wsrp-interop] BEA's producer/consumer now
online
>>>
>>>Hi, Subbu and all,
>>> This is regarding to the file upload portlet and the
>>>uploadContext structure. I'm getting the same error as
Andre's.
>>>However, my soap request is a bit different. I didn't
find a good
>>>place in the UploadContext structure to put fileName. In my request, I
>>>just had NamedString("filename", fileName) as one of
the MimeAttributes,
>>>where "filename" is a constant. I put "filename"
there, since this is
>>>how it appears in http header. I'm not sure if this is
the correct way
>>>of doing it as the spec doesn't mention this. How is
everyone handling
>>>this issue?
>>>
>>> Attached is my request, the response is a
NullPointerException.
>>>
>>>Thanks,
>>>Eric
>>>
>>>-----Original Message-----
>>>From: Subbu Allamaraju [_mailto:subbu@bea.com_]
>>>Sent: Tuesday, September 02, 2003 9:06 AM
>>>To: Andre Kramer; _wsrp-interop@lists.oasis-open.org_
>>><mailto:wsrp-interop@lists.oasis-open.org>
>>>Subject: Re: [wsrp-interop] BEA's producer/consumer now
online
>>>
>>>Andre,
>>>
>>>Thanks for the test results. The portlet description as
well as the
>>>fault type returned by our producer are wrong. I'm also
looking into the
>>>failure with upload.
>>>
>>>Regards,
>>>
>>>Subbu
>>>
>>>Andre Kramer wrote:
>>> >>>
>>>>I've now been able to test against BEA's producer and
am able to report
>>>>that the portlets are displaying and interacting with
our consumer (see
>>>>below for some issues and observations).
>>>>
>>>>I've also placed one portlet from each producer on a
test Web page:
>>>>
>>>>_http://andrek.dyndns.org/NETlets/Page.aspx?page=multi_
>>>>
>>>>[This page takes some time in loading due to 4 *
>>>>getServiceDescription/register/getSD/initCookie/getMarkup
(on each
>>>>initial load, as I have our db turned off when our
prototype is on the
>>>>Internet). The Oracle portlet still has connectivity
problems and I've
>>>>used the Citrix graph portlet rather than Oracle's on
the principle that
>>>>it does not use cookies ;-)]
>>>>
>>>>I saw two SOAP faults testing with the BEA portlets:
>>>>
>>>> - Switching the helloWorldPortlet to edit and
help mode (see
>>>>attached trace 1)
>>>> - Uploading a file to multipartRequest1 (see
attached trace 2)
>>>>
>>>>I was unable to get the login and create account
portlets to work
>>>>together (i.e. could not log in after creating an
acount). The title of
>>>>the loginPortlet is "Create a User Account" so maybe
this is work in
>>>>progress?
>>>>
>>>>I was unable to fully test the secure portlet (no
secure bindings in the
>>>>service wsdl) but noticed that the secure resource
image did not display
>>>>as the cert was not verifiable my end (also, the gif
urls end in a ?).
>>>>
>>>>regards,
>>>>Andre
>>>>
>>>>-----Original Message-----
>>>>From: Subbu Allamaraju [_mailto:subbu@bea.com_]
>>>>Sent: 11 August 2003 22:12
>>>>To: _wsrp-interop@lists.oasis-open.org_
>>>> >>>>
>>><mailto:wsrp-interop@lists.oasis-open.org>
>>> >>>
>>>>Cc: William Cox
>>>>Subject: [wsrp-interop] BEA's producer/consumer now
online
>>>>
>>>>
>>>>
>>>>BEA's WSRP producer and consumer are now available
online for interop
>>>>testing.
>>>>
>>>>WSDL:
>>>>
>>>> >>>>
>>>_http://wsrp.avitek.com:7001/producer/wsdl/wlp_wsrp_v1_markup_service.wsdl_
>>> >>>
>>>>Producer:
>>>>
>>>>The portlets for this producer are hosted in
>>>>_http://wsrp.avitek.com:7001/producer_, and can be
invoked directly
>>>>(without a portal) for testing purposes. Please refer to
>>>>_http://wsrp.avitek.com:7001/producer/index.jsp_ for
the list of
>>>> >>>>
>>>portlets
>>> >>>
>>>>currently deployed. You can follow the hyperlinks to
test those
>>>>portlets.
>>>>
>>>>Please note that this producer does not support
registration and portlet
>>>>management ports.
>>>>
>>>>Consumer:
>>>>
>>>>A read-only consumer is hosted at
>>>>_http://wsrp.avitek.com:8001/consumer/portal.portal_.
This consumer
>>>>includes pages that include portlets from BEA's and
IBM's producers.
>>>>
>>>>Please let me know if you're able to use these
producers successfully.
>>>>If you have a producer online, we'll be happy to
include those portlets
>>>>in our test consumer.
>>>>
>>>>We'll try to keep these servers online to the extent
possible (except
>>>>during updates).
>>>>
>>>>Regards,
>>>>
>>>>Subbu
>>>>
>>>>
>>>>
>>>>
>>>>You may leave a Technical Committee at any time by
visiting
>>>>
>>>> >>>>
>>>_http://www.oasis-open.org/apps/org/workgroup/wsrp-interop/members/leave_workgroup.php_
>>>
>>> >>>
>>>>
>>>>
>>>>------------------------------------------------------------------------
>>>>
>>>>Subject:
>>>>bea trace 1
>>>>From:
>>>>Andre Kramer _<andre.kramer@eu.citrix.com>_
>>>> >>>>
>>><mailto:andre.kramer@eu.citrix.com>
>>> >>>
>>>>Date:
>>>>Fri, 29 Aug 2003 11:46:49 +0100
>>>>To:
>>>>Andre Kramer _<andre.kramer@eu.citrix.com>_
>>>> >>>>
>>><mailto:andre.kramer@eu.citrix.com>
>>> >>>
>>>>
>>>>request: getMarkup with edit:
>>>>
>>>>User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web
Services Client
>>>>Protocol 1.1.4322.573) Content-Type: text/xml;
charset=utf-8 SOAPAction:
>>>>"urn:oasis:names:tc:wsrp:v1:getMarkup" Content-Length:
1781 Expect:
>>>>100-continue Host: localhost:9090 Cookie:
>>>>
>>>> >>>>
>>>JSESSIONID=1Pve49VcO1BBV3clAHSiWGpyqqUDZJDgmPoTW9WWvK11l4g78NsR!1079735209
>>> >>>
>>>><?xml version="1.0" encoding="utf-8"?><soap:Envelope
>>>>xmlns:soap="_http://schemas.xmlsoap.org/soap/envelope/_"
>>>>xmlns:xsi="_http://www.w3.org/2001/XMLSchema-instance_"
>>>>xmlns:xsd="_http://www.w3.org/2001/XMLSchema_"
>>>>xmlns:wsa="_http://schemas.xmlsoap.org/ws/2003/03/addressing_"
>>>>
>>>> >>>>
>>>xmlns:wsu="_http://schemas.xmlsoap.org/ws/2002/07/utility_"><soap:Header><wsa:Action>urn:oasis:names:tc:wsrp:v1:getMarkup</wsa:Action><wsa:From><wsa:Address>_http://schemas.xmlsoap.org/ws/2003/03/addressing/role/anonymous_</wsa:Address></wsa:From><wsa:MessageID>uuid:b6a56dd7-1661-434a-a40b-e3877cb3aedb</wsa:MessageID><wsa:To>_http://knowth:8080/WSRPService_</wsa:To><wsu:Timestamp><wsu:Created>2003-08-29T10:40:30Z</wsu:Created><wsu:Expires>2003-08-29T10:45:30Z</wsu:Expires></wsu:! Ti!
>>>mestamp></soap:Header><soap:Body><getMarkup
>>>
>>> >>>
>>>>xmlns="urn:oasis:names:tc:wsrp:v1:types"><registrationContext
>>>>xsi:nil="true"
>>>>
>>>> >>>>
>>>/><portletContext><portletHandle>helloWorldPortlet</portletHandle></portletContext><runtimeContext><userAuthentication>wsrp:password</userAuthentication><portletInstanceKey>3F4aJF%2bSFnjQQw5xTiwuyKNgl7w%3d</portletInstanceKey><namespacePrefix>netlet0</namespacePrefix><sessionID>1Pve49VcO1BBV3clAHSiWGpyqqUDZJDgmPoTW9WWvK11l4g78NsR!1079735209</sessionID></runtimeContext><userContext><userContextKey>12345</userContextKey></userContext><markupParams><secureClientCommunication>false</secureClientCommunication><locales>en</locales><locales>de</locales><mimeTypes>text/html</mimeTypes><mode>wsrp:edit</mode><windowState>wsrp:normal</windowState><clientData><userAgent>Mozilla/4.0
>>>
>>>
>>> >>>
>>>>(compatible; MSIE 6.0; Windows NT 5.1; .NET CLR
>>>>
>>>> >>>>
>>>1.1.4322)</userAgent></clientData><markupCharacterSets>UTF-8</markupCharacterSets><markupCharacterSets>UTF-16</markupCharacterSets></markupParams></getMarkup></soap:Body></soap:Envelope>
>>>
>>>
>>> >>>
>>>>response from helloWorldPortlet when getMarkup with edit:
>>>>
>>>>
>>>>HTTP/1.1 200 OK Date: Fri, 29 Aug 2003 10:47:18 GMT
Server: WebLogic
>>>>Server 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009
with Content-Length:
>>>>2546 Content-Type: text/xml; charset=UTF-8 <?xml
version="1.0"
>>>>encoding="UTF-8"?>
>>>>
>>>><soapenv:Envelope
>>>>
>>>> >>>>
>>>xmlns:soapenv="_http://schemas.xmlsoap.org/soap/envelope/_"><soapenv:Body><soapenv:Fault
>>>
>>> >>>
>>>xmlns:urn="urn:oasis:names:tc:wsrp:v1:types"><faultcode>urn:OperationFailed</faultcode><faultstring
>>>
>>> >>>
>>>>xsi:nil="true"
>>>>
>>>> >>>>
>>>xmlns:xsi="_http://www.w3.org/2001/XMLSchema-instance_"/><detail><detail>com.bea.wsrp.faults.OperationFailedException
>>>
>>> >>>
>>>> at
>>>>
>>>> >>>>
>>>com.bea.wsrp.producer.adapter.pageflow.PageflowPortletContainer.getMarkup(PageflowPortletContainer.java:209)
>>>
>>> >>>
>>>> at
>>>>
>>>> >>>>
>>>com.bea.wsrp.producer.handlers.markup.MarkupServiceHandler.doGetMarkup(MarkupServiceHandler.java:250)
>>>
>>> >>>
>>>> at
>>>>
>>>> >>>>
>>>com.bea.wsrp.producer.handlers.markup.MarkupServiceHandler.doService(MarkupServiceHandler.java:166)
>>>
>>> >>>
>>>> at
>>>> >>>>
>>>com.bea.wsrp.producer.WsrpServer.doService(WsrpServer.java:301)
>>> >>>
>>>> at
>>>>com.bea.wsrp.producer.WsrpServer.internalService(WsrpServer.java:222)
>>>> at
com.bea.wsrp.producer.WsrpServer.doPost(WsrpServer.java:209)
>>>> at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
>>>> at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
>>>> at
>>>>
>>>> >>>>
>>>weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
>>>
>>> >>>
>>>> at
>>>>
>>>> >>>>
>>>weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
>>>
>>> >>>
>>>> at
>>>>weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
>>>> at
>>>>
>>>> >>>>
>>>weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>>> >>>
>>>> at
>>>>
>>>> >>>>
>>>com.bea.wsrp.producer.adapter.pageflow.WsrpPageflowFilter.doFilter(WsrpPageflowFilter.java:73)
>>>
>>> >>>
>>>> at
>>>>
>>>> >>>>
>>>weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>>> >>>
>>>> at
>>>>
>>>> >>>>
>>>weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6316)
>>>
>>> >>>
>>>> at
>>>>
>>>> >>>>
>>>weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
>>>
>>> >>>
>>>> at
>>>>
>>>> >>>>
>>>weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
>>> >>>
>>>> at
>>>>
>>>> >>>>
>>>weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
>>>
>>> >>>
>>>> at
>>>>
>>>> >>>>
>>>weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
>>>
>>> >>>
>>>> at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
>>>> at
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>>>>Caused by: java.lang.IllegalStateException: Pageflow
invalid:
>>>>helloWorld.Controller
>>>> at
>>>>
>>>> >>>>
>>>com.bea.wsrp.producer.adapter.pageflow.PageflowPortletContainer.invokePageflowRender(PageflowPortletContainer.java:474)
>>>
>>>
>>> >>>
>>>> at
>>>>
>>>> >>>>
>>>com.bea.wsrp.producer.adapter.pageflow.PageflowPortletContainer.getMarkup(PageflowPortletContainer.java:202)
>>>
>>> >>>
>>>> ... 20 more
>>>></detail></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>
>>>>
>>>>
>>>>------------------------------------------------------------------------
>>>>
>>>>Subject:
>>>>bea trace 2
>>>>From:
>>>>Andre Kramer _<andre.kramer@eu.citrix.com>_
>>>> >>>>
>>><mailto:andre.kramer@eu.citrix.com>
>>> >>>
>>>>Date:
>>>>Fri, 29 Aug 2003 12:40:15 +0100
>>>>To:
>>>>Andre Kramer _<andre.kramer@eu.citrix.com>_
>>>> >>>>
>>><mailto:andre.kramer@eu.citrix.com>
>>> >>>
>>>>request (pbia with uploaddata):
>>>>
>>>>SOAPAction:
"urn:oasis:names:tc:wsrp:v1:performBlockingInteraction"
>>>>Content-Length: 4615 Expect: 100-continue Host:
localhost:9090 Cookie:
>>>>
>>>> >>>>
>>>JSESSIONID=1P7qhT0JnLj9Mz0kAqJHzS9oUtBlUMFT1Ykse4RcnCSO89e1xJbe!1079735209
>>> >>>
>>>><?xml version="1.0" encoding="utf-8"?><soap:Envelope
>>>>xmlns:soap="_http://schemas.xmlsoap.org/soap/envelope/_"
>>>>xmlns:xsi="_http://www.w3.org/2001/XMLSchema-instance_"
>>>>xmlns:xsd="_http://www.w3.org/2001/XMLSchema_"
>>>>xmlns:wsa="_http://schemas.xmlsoap.org/ws/2003/03/addressing_"
>>>>
>>>> >>>>
>>>xmlns:wsu="_http://schemas.xmlsoap.org/ws/2002/07/utility_"><soap:Header><wsa:Action>urn:oasis:names:tc:wsrp:v1:performBlockingInteraction</wsa:Action><wsa:From><wsa:Address>_http://schemas.xmlsoap.org/ws/2003/03/addressing/role/anonymous_</wsa:Address></wsa:From><wsa:MessageID>uuid:30cdd411-213f-4d4f-b931-573de9f38eab</wsa:MessageID><wsa:To>_http://knowth:8080/WSRPService_</wsa:To><wsu:Timestamp><wsu:Created>2003-08-29T11:32:52Z</wsu:Created><wsu:Expires>2003-08-29T11:37:52Z</wsu:Exp! ir!
>>>es></wsu:Timestamp></soap:Header><soap:Body><performBlockingInteraction
>>>
>>> >>>
>>>>xmlns="urn:oasis:names:tc:wsrp:v1:types"><registrationContext
>>>>xsi:nil="true"
>>>>
>>>> >>>>
>>>/><portletContext><portletHandle>multipartRequest1</portletHandle></portletContext><runtimeContext><userAuthentication>wsrp:password</userAuthentication><portletInstanceKey>P1ZWiWkVV8Iu%2b2ygJG9AJah%2f3j8%3d</portletInstanceKey><namespacePrefix>netlet0</namespacePrefix><sessionID>1P7qhT0JnLj9Mz0kAqJHzS9oUtBlUMFT1Ykse4RcnCSO89e1xJbe!1079735209</sessionID></runtimeContext><userContext><userContextKey>12345</userContextKey></userContext><markupParams><secureClientCommunication>false</secureClientCommunication><locales>en</locales><locales>de</locales><mimeTypes>text/html</mimeTypes><mode>wsrp:view</mode><windowState>wsrp:normal</windowState><clientData><userAgent>Mozilla/4.0
>>>
>>>
>>> >>>
>>>>(compatible; MSIE 6.0; Windows NT 5.1; .NET CLR
>>>>1.1.4322)</userAgent></clientData><navigationalState
>>>>
>>>> >>>>
>>>/><markupCharacterSets>UTF-8</markupCharacterSets><markupCharacterSets>UTF-16</markupCharacterSets></markupParams><interactionParams><portletStateChange>cloneBeforeWrite</portletStateChange><interactionState>multipartUpload</interactionState><formParameters
>>>
>>>
>>> >>>
>>>name="P1ZWiWkVV8Iu%2b2ygJG9AJah%2f3j8%3d{actionForm.text1}"><value>test</value></formParameters><formParameters
>>>
>>> >>>
>>>>name="P1ZWiWkVV8Iu%2b2ygJG9AJah%2f3j8%3d{actionForm.text2}"><value
>>>>
>>>> >>>>
>>>/></formParameters><uploadContexts><mimeType>text/xml</mimeType><uploadData>PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KCjx3c2RsOmRlZmluaXRpb25z
>>>
>>>
>>> >>>
>>>IHRhcmdldE5hbWVzcGFjZT0idXJuOm9hc2lzOm5hbWVzOnRjOndzcnA6djE6d3NkbCIKCiAgICB4
>>>
>>> >>>
>>>bWxuczpiaW5kPSJ1cm46b2FzaXM6bmFtZXM6dGM6d3NycDp2MTpiaW5kIgoKCgogICAgeG1sbnM9
>>>
>>> >>>
>>>Imh0dHA6Ly9zY2hlbWFzLnhtbHNvYXAub3JnL3dzZGwvIgoKCgogICAgeG1sbnM6d3NkbD0iaHR0
>>>
>>> >>>
>>>cDovL3NjaGVtYXMueG1sc29hcC5vcmcvd3NkbC8iCgogICAgeG1sbnM6c29hcD0iaHR0cDovL3Nj
>>>
>>> >>>
>>>aGVtYXMueG1sc29hcC5vcmcvd3NkbC9zb2FwLyI+CgoKCiAgICA8aW1wb3J0IG5hbWVzcGFjZT0i
>>>
>>> >>>
>>>dXJuOm9hc2lzOm5hbWVzOnRjOndzcnA6djE6YmluZCIKCiAgICAgICAgbG9jYXRpb249IndzcnBf
>>>
>>> >>>
>>>djFfYmluZGluZ3Mud3NkbCIvPgoKCgogICAgPCEtLSBXTFAgQmluZGluZ3MgLS0+CgogICAgPHdz
>>>
>>> >>>
>>>ZGw6c2VydmljZSBuYW1lPSJXU1JQU2VydmljZSI+CgogICAgICAgIDx3c2RsOnBvcnQgYmluZGlu
>>>
>>> >>>
>>>Zz0iYmluZDpXU1JQX3YxX01hcmt1cF9CaW5kaW5nX1NPQVAiIG5hbWU9IldTUlBCYXNlU2Vydmlj
>>>
>>> >>>
>>>ZSI+CgogICAgICAgICAgICA8c29hcDphZGRyZXNzIGxvY2F0aW9uPSJodHRwOi8vd3NycC5hdml0
>>>
>>> >>>
>>>ZWsuY29tOjcwMDEvcHJvZHVjZXIvcHJvZHVjZXIiLz4KCiAgICAgICAgPC93c2RsOnBvcnQ+Cgog
>>>
>>> >>>
>>>ICAgICAgIDx3c2RsOnBvcnQgYmluZGluZz0iYmluZDpXU1JQX3YxX1NlcnZpY2VEZXNjcmlwdGlv
>>>
>>> >>>
>>>bl9CaW5kaW5nX1NPQVAiIG5hbWU9IldTUlBTZXJ2aWNlRGVzY3JpcHRpb25TZXJ2aWNlIj4KCiAg
>>>
>>> >>>
>>>ICAgICAgICAgIDxzb2FwOmFkZHJlc3MgbG9jYXRpb249Imh0dHA6Ly93c3JwLmF2aXRlay5jb206
>>>
>>> >>>
>>>NzAwMS9wcm9kdWNlci9wcm9kdWNlciIvPgoKICAgICAgICA8L3dzZGw6cG9ydD4KCiAgICAgICAg
>>>
>>> >>>
>>>PCEtLSBOb3Qgc3VwcG9ydGVkCgogICAgICAgIDx3c2RsOnBvcnQgYmluZGluZz0iYmluZDpXU1JQ
>>>
>>> >>>
>>>X3YxX1JlZ2lzdHJhdGlvbl9CaW5kaW5nX1NPQVAiIG5hbWU9IldTUlBSZWdpc3RyYXRpb25TZXJ2
>>>
>>> >>>
>>>aWNlIj4KCiAgICAgICAgICAgIDxzb2FwOmFkZHJlc3MgbG9jYXRpb249Imh0dHA6Ly93c3JwLmF2
>>>
>>> >>>
>>>aXRlay5jb206NzAwMS9wcm9kdWNlci9wcm9kdWNlciIvPgoKICAgICAgICA8L3dzZGw6cG9ydD4K
>>>
>>> >>>
>>>CiAgICAgICAgLS0+CgogICAgICAgIDwhLS0gTm90IHN1cHBvcnRlZAoKICAgICAgICA8d3NkbDpw
>>>
>>> >>>
>>>b3J0IGJpbmRpbmc9ImJpbmQ6V1NSUF92MV9Qb3J0bGV0TWFuYWdlbWVudF9CaW5kaW5nX1NPQVAi
>>>
>>> >>>
>>>IG5hbWU9IldTUlBQb3J0bGV0TWFuYWdlbWVudFNlcnZpY2UiPgoKICAgICAgICAgICAgPHNvYXA6
>>>
>>> >>>
>>>YWRkcmVzcyBsb2NhdGlvbj0iaHR0cDovL3dzcnAuYXZpdGVrLmNvbTo3MDAxL3Byb2R1Y2VyL3By
>>>
>>> >>>
>>>b2R1Y2VyIi8+CgogICAgICAgIDwvd3NkbDpwb3J0PgoKICAgICAgICAtLT4KCiAgICA8L3dzZGw6
>>>
>>> >>>
>>>>c2VydmljZT4KCjwvd3NkbDpkZWZpbml0aW9ucz4KCgoK</uploadData><mimeAttributes
>>>>
>>>> >>>>
>>>name="filename"><value>C:\Inetpub\wwwroot\NETlets\services\bea.wsdl</value></mimeAttributes></uploadContexts><uploadContexts><mimeType>application/octet-stream</mimeType><uploadData
>>>
>>>
>>> >>>
>>>>/><mimeAttributes
>>>>
>>>> >>>>
>>>name="fieldname"><value>P1ZWiWkVV8Iu%2b2ygJG9AJah%2f3j8%3d{actionForm.file2}</value></mimeAttributes></uploadContexts></interactionParams></performBlockingInteraction></soap:Body></soap:Envelope>
>>>
>>>
>>> >>>
>>>>soap fault response from pfi:
>>>>
>>>>HTTP/1.1 200 OK Date: Fri, 29 Aug 2003 11:39:41 GMT
Server: WebLogic
>>>>Server 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009
with Content-Length:
>>>>396 Content-Type: text/xml; charset=UTF-8 <?xml
version="1.0"
>>>>encoding="UTF-8"?>
>>>>
>>>><soapenv:Envelope
>>>>
>>>> >>>>
>>>xmlns:soapenv="_http://schemas.xmlsoap.org/soap/envelope/_"><soapenv:Body><soapenv:Fault
>>>
>>> >>>
>>>xmlns:soapenv="_http://schemas.xmlsoap.org/soap/envelope/_"><faultcode>soapenv:java.lang.NullPointerException</faultcode><faultstring
>>>
>>>
>>> >>>
>>>>xsi:nil="true"
>>>>
>>>> >>>>
>>>xmlns:xsi="_http://www.w3.org/2001/XMLSchema-instance_"/></soapenv:Fault></soapenv:Body></soapenv:Envelope>
>>>
>>> >>>
>>>>------------------------------------------------------------------------
>>>>
>>>>To unsubscribe from this mailing list (and be removed
from the roster
>>>> >>>>
>>>of the OASIS TC), go to
>>>_http://www.oasis-open.org/apps/org/workgroup/wsrp-interop/members/leave_workgroup.php_.
>>>
>>>
>>>
>>>To unsubscribe from this mailing list (and be removed
from the roster of
>>>the OASIS TC), go to
>>>_http://www.oasis-open.org/apps/org/workgroup/wsrp-interop/members/leave_workgroup.php_.
>>>
>>>
>>>
>>>--
>>>
>>>------------------------------------------------------------------------
>>>*David Ward*
>>>Principal Software Engineer
>>>Portlet Technologies
>>>Oracle Portal
>>> Oracle European Development Centre
>>>520 Oracle Parkway
>>>Thames Valley Park
>>>Reading
>>>Berkshire RG6 1RA
>>>UK >>>*Email:*
>>> _david.ward@oracle.com_
<mailto:david.ward@oracle.com>
>>>*Tel:*
>>> +44 118 924 5079
>>>*Fax:*
>>> +44 118 924 5005
>>>
>>>
>>>
>>>
>>> >>>
>>
>>
>>To unsubscribe from this mailing list (and be removed
from the roster of the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsrp-interop/members/leave_workgroup.php.
>>
>>
>>To unsubscribe from this mailing list (and be removed
from the roster of the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsrp-interop/members/leave_workgroup.php.
>>
>> >>
>
>
>
>To unsubscribe from this mailing list (and be removed
from the roster of the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsrp-interop/members/leave_workgroup.php.
>
> >
To unsubscribe from this mailing list (and be removed from
the roster of the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsrp-interop/members/leave_workgroup.php.
To unsubscribe from this mailing list (and be removed from
the roster of the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsrp-interop/members/leave_workgroup.php.
-- ------------------------------------------------------------------------
*David Ward*
Principal Software Engineer
Portlet Technologies
Oracle Portal
Oracle European Development Centre
520 Oracle Parkway
Thames Valley Park
Reading
Berkshire RG6 1RA
UK
*Email:* david.ward@oracle.com <mailto:david.ward@oracle.com>
*Tel:* +44 118 924 5079
*Fax:* +44 118 924 5005
-- ------------------------------------------------------------------------
*David Ward*
Principal Software Engineer
Portlet Technologies
Oracle Portal
Oracle European Development Centre
520 Oracle Parkway
Thames Valley Park
Reading
Berkshire RG6 1RA
UK
*Email:* david.ward@oracle.com <mailto:david.ward@oracle.com>
*Tel:* +44 118 924 5079
*Fax:* +44 118 924 5005
--
------------------------------------------------------------------------
*David Ward*
Principal Software Engineer
Portlet Technologies
Oracle Portal
Oracle European Development Centre
520 Oracle Parkway
Thames Valley Park
Reading
Berkshire RG6 1RA
UK
*Email:* david.ward@oracle.com <mailto:david.ward@oracle.com>
*Tel:* +44 118 924 5079
*Fax:* +44 118 924 5005
To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsrp-interop/members/leave_workgroup.php.
--
Principal Software Engineer
Portlet Technologies
Oracle PortalOracle European Development Centre
520 Oracle Parkway
Thames Valley Park
Reading
Berkshire RG6 1RA
UK
david.ward@oracle.com +44 118 924 5079 +44 118 924 5005
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]