[JBossWS] - Date, Time and DateTime
by gquintana
Hello,
I applied the wsconsume tool from JBoss 4.2.2 successfully on a WSDL. But when I deploy my WS implementation in JBoss, I get the following errors:
anonymous wrote : 2008-04-04 11:35:02,490 ERROR [org.jboss.ws.metadata.wsdl.xmlschema.JBossXSErrorHandler] JBossWS_datex2.eu_schema_1_0_1_048914.xsd[domain:http://www.w3.org/TR/xml...: The type 'DateTime' is atomic, so its {base type definition}, 'xs:anySimpleType', must be an atomic simple type definition or a built-in primitive datatype.
| 2008-04-04 11:35:02,493 ERROR [org.jboss.ws.metadata.wsdl.xmlschema.JBossXSErrorHandler] JBossWS_datex2.eu_schema_1_0_1_048914.xsd[domain:http://www.w3.org/TR/xml...: The type 'Time' is atomic, so its {base type definition}, 'xs:anySimpleType', must be an atomic simple type definition or a built-in primitive datatype.
| 2008-04-04 11:35:02,497 ERROR [org.jboss.ws.metadata.wsdl.xmlschema.JBossXSErrorHandler] JBossWS_datex2.eu_schema_1_0_1_048914.xsd[domain:http://www.w3.org/TR/xml...: The type 'Date' is atomic, so its {base type definition}, 'xs:anySimpleType', must be an atomic simple type definition or a built-in primitive datatype.
|
I don't understand what this error message says, but when I call the WS, I get the following error :
anonymous wrote : 2008-04-04 11:44:52,143 ERROR [org.jboss.wsf.stack.jbws.RequestHandlerImpl] Cannot close output stream
|
The Date/Time/DateTime type are defined like this:
<xs:complexType name="Date">
| <xs:simpleContent>
| <xs:extension base="xs:date" />
| </xs:simpleContent>
| </xs:complexType>
| <xs:complexType name="DateTime">
| <xs:simpleContent>
| <xs:extension base="xs:dateTime" />
| </xs:simpleContent>
| </xs:complexType>
| <xs:complexType name="Time">
| <xs:simpleContent>
| <xs:extension base="xs:time" />
| </xs:simpleContent>
| </xs:complexType>
|
In the WS impl, to instanciate the DateTime, I wrote:
DatatypeFactory.newInstance().newXMLGregorianCalendar(gregorianCalendar));
Could someone tell me where I am wrong?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141597#4141597
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141597
18 years
[JBoss Cache: Core Edition] - Re: Jdbc Cahce Loader Issue
by shanthi_jbosscache
Hi ,
Thanks for your suggestion. As you said, I have set fetchpersistantstate to FALSE. Now the records are NOT missing in the database during portal startup failure.
I want to know by setting fetchpersistentstate to FALSE, will this impact on cache clustering.
Please validate my understanding
1. I want to know the difference between fetchpersistentstate and fetchinmemorystate.
My understanding is below
(i). if fetchinmemorystate is TRUE - It acquires the initial state from the existing members in the cluster during startup
(ii). if fetchpersistent state is TRUE - Reads the data from database and loads the data into its cache
(iii). if fetchinmemorystate is TRUE and if fetchpersistent state is TRUE
a.it acquires the persistent state from the existing member in the cluster
b.Deletes the record(s) from the DB.
c.Persist the data fetched from the existing member in the cluster to DB
d.Retrieves the data from DB and reloads the data into its cache
Is my understanding on the above flow is correct?
2. Can we set both fetchpersistentstate and fetchinmemorystate to TRUE. If we can, please explain how it will work and the need(advantage) behind this setting.
3. What is the impact on cache clustering if fetchpersistentstate is set to FALSE?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141578#4141578
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141578
18 years