[JBossWS] - Re: Exception while deploying a webservice with attachment (
by mnsharif
People post their problems here when they run short of ideas on their own and they expect others to help. Anyway, thanks for all the help that was provided (my issue is still unresolved though).
RomeuFigueira!
As you mentioned about the files required for dealing with attachments in JBoss WS, i have created them all (but havent tweaked any of them manually).
It looks like that http://jira.jboss.com/jira/browse/JBWS-269 suggest that wstools (the tool from JBoss) does not currently support attachments. In either case, i am using wscompile (from JWSDPv1.6) to generate SEI and mapping file from a hand-written WSDL file. Then i write a web.xml and webservices.xml file by hand as well to complete the deployment package.
So, technically i have everything in place and i used same WSDL file to generate artifacts and published web service successfully on tomcat using JWSDP.
To frustrate me enough, the error that i get is
org.jboss.ws.WSException:
| Cannot obtain java/xml type mapping for: {http://www.w3.org/2001/XMLSchema}string
where we all know that the given schema DOES contain a data type with the name string
So, what's wrong with my implementation? any clues? anyone?
mnsharif
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985784#3985784
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985784
19Â years, 7Â months
[News & Announcements] - JBossCache 1.4.1.Beta released
by rrajesh
JBossCache 1.4.1.Beta has been released and is available for download from Sourceforge at the following URL.
http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=10...
Release 1.4.1.BETA (November 13, 2006)
======================================
** Bug
* [JBCACHE-690] - TcpCacheServer never gets out of STARTING state, and doesn't shut down socket when stop() is called.
* [JBCACHE-739] - Exception in a CacheLoader throws ChainingCacheLoader calling method and prevent the call to the next CacheLoaders
* [JBCACHE-755] - Potential bug when using (async) replication queue and region based marshalling
* [JBCACHE-756] - Marshaller breaks with Strings of length greater than 32767
* [JBCACHE-760] - TreeCacheListener in PojoCache gets nodeModify events for invalid objects
* [JBCACHE-763] - Transaction rollback does not restore contents of collection of cached collections
* [JBCACHE-765] - implementation of equals() in collections is incorrect
* [JBCACHE-767] - Fail more silently when setting node versions
* [JBCACHE-769] - JDBCCacheLoader should not directly serialize a map passed to put
* [JBCACHE-776] - EvictionPolicyProvider WARN message is noisy and misleading
* [JBCACHE-777] - Creating a custom cache loader which delegates to a standard cache loader, can generate misleading WARN messages
* [JBCACHE-785] - InvocationContext and suspended transactions
* [JBCACHE-792] - ChainingCacheLoader method get(Fqn) - unecessary call of the next CacheLoader
* [JBCACHE-794] - Eviction Queue hard limit can cause deadlocks
* [JBCACHE-795] - listIterator in a cached list throws exception on empty list
* [JBCACHE-799] - Bug in RmiDelegatingCacheLoader class
* [JBCACHE-806] - Invalidation causes problems with otimistic data versioning and certain edge cases
* [JBCACHE-808] - Add serialVersionUID to ReplicationException
* [JBCACHE-810] - TCP Delegating Cache Loader not multithreaded
* [JBCACHE-825] - PassivationInterceptor emits notification even if the node isn't loaded
* [JBCACHE-836] - TreeCache isCoordinator() returns incorrect value after clean shutdown of coordinator
* [JBCACHE-843] - Data versions do not replicate properly alongside data
* [JBCACHE-844] - Correct handling of partial state transfer re-try logic
** Feature Request
* [JBCACHE-813] - BaseRpcInterceptor to call callRemoteMethod() instead of callRemoteMethods() when sending to a single recipient
* [JBCACHE-829] - Add JBoss EULA
* [JBCACHE-842] - Optimistic Locking improvements - validation on read-only transactions
** Patch
* [JBCACHE-766] - Don't return unnecessary values from _replicate, avoiding need for marshalling
* [JBCACHE-786] - errors from "OK" putFailFast replications
** Task
* [JBCACHE-680] - TreeCache demo gui to update view instanteously
* [JBCACHE-761] - Make connecting the channel and state transfer an atomic part of startup
* [JBCACHE-793] - hibernate-recommended-config.xml incorrectly specifies INVALIDATION_SYNC
* [JBCACHE-798] - Use ConcurrentHashMap for lock_table
* [JBCACHE-800] - Performance problem with TCP & RMI Cache loaders
* [JBCACHE-812] - Enable JGroups multiplexer integration in a 1.4.x release
* [JBCACHE-815] - Eliminate need for jboss-serialization.jar if it's not used
* [JBCACHE-824] - Don't call Channel.getView() in viewAccepted() callback
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985783#3985783
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985783
19Â years, 7Â months
[JBoss Portal] - Re: JBoss Portal Stress Results
by roy.russoï¼ jboss.com
Sohil found two things in the 2.6 codebase and they've been fixed (and backported to 2.4):
1. CMS regexp I added for removal of everything except *. The regexp was being run every time, over the cached object, regardless if the tag existed.
2. Portal ResourceBundle loader seemed to be buggy/slow.
He ran the windows test tool on 2.6 and now has this (WITH the CMS):
| Overview
|
| ================================================================================
|
| Report name: 11/13/2006 8:35:32 PM
|
| Run on: 11/13/2006 8:35:32 PM
|
| Run length: 00:02:51
|
|
|
| Web Application Stress Tool Version:1.1.293.1
|
|
|
| Number of test clients: 1
|
|
|
| Number of hits: 2713
|
| Requests per Second: 22.57
|
|
|
| Socket Statistics
|
| --------------------------------------------------------------------------------
|
| Socket Connects: 2713
|
| Total Bytes Sent (in KB): 643.81
|
| Bytes Sent Rate (in KB/s): 5.35
|
| Total Bytes Recv (in KB): 42361.48
|
| Bytes Recv Rate (in KB/s): 352.35
|
|
|
| Socket Errors
|
| --------------------------------------------------------------------------------
|
| Connect: 0
|
| Send: 0
|
| Recv: 0
|
| Timeouts: 0
|
|
|
| RDS Results
|
| --------------------------------------------------------------------------------
|
| Successful Queries: 0
|
|
|
|
|
| Script Settings
|
| ================================================================================
|
| Server: localhost
|
| Number of threads: 1
|
|
|
| Test length: 00:02:00
|
| Warmup: 00:00:25
|
| Cooldown: 00:00:25
|
|
|
| Use Random Delay: No
|
|
|
| Follow Redirects: Yes
|
| Max Redirect Depth: 15
|
|
|
|
|
| Clients used in test
|
| ================================================================================
|
| localhost
|
|
|
| Clients not used in test
|
| ================================================================================
|
|
|
|
|
| Result Codes
|
| Code Description Count
|
| ================================================================================
|
| 200 OK 2713
|
|
|
|
|
| Page Summary
|
| Page Hits TTFB Avg TTLB Avg Auth Query
|
| ================================================================================
|
| GET /portal 2713 39.32 42.92 No No
|
|
As we get closer to 2.6Beta, expect throughput to increase.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985778#3985778
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985778
19Â years, 7Â months
[JBossWS] - base64Binary: jbossws client serialize problem
by vbatista
Hello!
I am using JBoss 4.0.4 with jbossws 1.0.3GA. I am developing a WS DII client which talks with a third party Web Service. I am having problems serializing one field which is specified as "base64Binary" on the WSDL:
<xsd:complexType name="BinaryData">
<xsd:sequence>
<xsd:element name="data" type="xsd:base64Binary"
nillable="true"/>
<xsd:element name="mimeType" type="xsd:string"
nillable="true"/>
<xsd:element name="URL" type="xsd:string" nillable="true"/>
<xsd:element name="removeOnUpdate" type="xsd:boolean"
nillable="false"/>
</xsd:sequence>
The "data" field should be sent as a Base64 String. Although, the Request SOAP message has the following data:
<ns1:data xmlns:ns1="urn:drm/ingest-ex/IngestService/SchemaTypes">
<ns1:data>-1</ns1:data>
<ns1:data>-40</ns1:data>
<ns1:data>-1</ns1:data>
<ns1:data>-32</ns1:data>
......
<ns1:mimeType>image/jpeg</ns1:mimeType>
<ns1:URL xsi:nil="1"/>
<ns1:removeOnUpdate>false</ns1:removeOnUpdate>
</ns1:data>
I have implemented a client using jboss.net (org.jboss.axis...) and I have the same problem.
I have implemented a standalone client using axis (org.apache.axis...) and I can call the Web Service correctly. The Request SOAP message contains:
< data>
< data>j/4AAQSkZ.....
< mimeType>image/gif
< URL xsi:nil="true"/>
< removeOnUpdate>false
< /data>
In this case, the "data" field is correctly encoded as a Base64 String.
Am i missing any configuration with jbossws? What must I do to have the correct behavior?
Any help would really be appreciated.
Thanks in advance,
Victor Batista
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985777#3985777
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985777
19Â years, 7Â months