I am coming back here after many years... :D
Will post my performance engineering and testing experience.
Will post my performance engineering and testing experience.
Tuesday, February 23, 2016
Tuesday, July 28, 2009
Getting rid from error "setProperty must be overridden by all subclasses of SOAPMessage" in JBoss 4.2.3
I am using JBoss 4.2.3 with JDK 1.6.0_11 and had the following error while running client to call webservice as following:
ERROR [SOAPFaultHelperJAXWS] SOAP request exception
java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
at javax.xml.soap.SOAPMessage.setProperty(Unknown Source)
at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:83)
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:217)
Solution: https://jira.jboss.org/jira/browse/JBWS-1439
ERROR [SOAPFaultHelperJAXWS] SOAP request exception
java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
at javax.xml.soap.SOAPMessage.setProperty(Unknown Source)
at org.jboss.ws.core.soap.SOAPMessageImpl.
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:217)
Solution: https://jira.jboss.org/jira/browse/JBWS-1439
Thursday, July 09, 2009
Simple eclipse problem screwed me up..
I imported an ear file and since this file did not have java source file so i copied all source file in src folder generated by eclipse.
what is next...I needed to modify in source code and deploye on JBoss server.
So, i tried to deploy it on JBoss server but message was showing..."Publish failed using Ant publisher".
I tried to fix this issue by changing so many configuration but i couldn't :(
even i tried to googling this problem but i did not find any luck.
so i tried to copy the message from details and when i copied and paste in text editor there was more messge as following.
Publish failed using Ant publisher
unable to assemble module
duplicate entry: org/jboss/seam/example/registration/test/RegisterTest.class
ohhh...this was silly problem... later I realised that there was and imported classes that should be deleted so I deleted all modified class from ImportedClasses and this got fixed :-)
what is next...I needed to modify in source code and deploye on JBoss server.
So, i tried to deploy it on JBoss server but message was showing..."Publish failed using Ant publisher".
I tried to fix this issue by changing so many configuration but i couldn't :(
even i tried to googling this problem but i did not find any luck.
so i tried to copy the message from details and when i copied and paste in text editor there was more messge as following.
Publish failed using Ant publisher
unable to assemble module
duplicate entry: org/jboss/seam/example/registration/test/RegisterTest.class
ohhh...this was silly problem... later I realised that there was and imported classes that should be deleted so I deleted all modified class from ImportedClasses and this got fixed :-)
Monday, April 06, 2009
Sunday, April 05, 2009
Choosing among JCA, JMS, and Web services for EAI
http://www.ibm.com/developerworks/webservices/library/ws-jcajms.html
Saturday, March 14, 2009
Thursday, March 12, 2009
XML DTDs vs schemas
XML DTDs vs schemas
Takeaway: Developers familiar with XML know that DTDs and schemas serve a similar purpose, but the debate over which one to use shows no signs of settling down. Find out what XML newsletter columnist Brian Schaffner thinks.
Every technology has its share of controversial topics, and XML is not immune to debate—especially when it comes to document type definitions (DTDs) and schemas. Both of these XML technologies perform similar functions, but the argument over which you should use rages on. Let’s look at some of the pros and cons of each.
The role of DTDs and schemas
Essentially, DTDs and schemas fulfill the same purpose: helping XML developers describe the structure and data within their XML documents. Without DTDs and schemas, it would be difficult to determine whether an XML document is valid in terms of it meeting certain structural and data type criteria.
The DTD or schema provides the XML parser with a description of what a particular type of XML document should look like. For example, it will say whether a <City> element can be contained within an <Address> element. It will also say how many <City> elements the parser should expect to find in the <Address> element, and it can describe the type of data within the element.
The DTD argument
DTDs, which have been around longer than XML, describe the type of document you're dealing with. When XML arrived as a specification, certain concepts were considered to help protect against mistakes within the document. One concept, validation, is the process of comparing an XML document to its DTD.
Takeaway: Developers familiar with XML know that DTDs and schemas serve a similar purpose, but the debate over which one to use shows no signs of settling down. Find out what XML newsletter columnist Brian Schaffner thinks.
Every technology has its share of controversial topics, and XML is not immune to debate—especially when it comes to document type definitions (DTDs) and schemas. Both of these XML technologies perform similar functions, but the argument over which you should use rages on. Let’s look at some of the pros and cons of each.
The role of DTDs and schemas
Essentially, DTDs and schemas fulfill the same purpose: helping XML developers describe the structure and data within their XML documents. Without DTDs and schemas, it would be difficult to determine whether an XML document is valid in terms of it meeting certain structural and data type criteria.
The DTD or schema provides the XML parser with a description of what a particular type of XML document should look like. For example, it will say whether a <City> element can be contained within an <Address> element. It will also say how many <City> elements the parser should expect to find in the <Address> element, and it can describe the type of data within the element.
The DTD argument
DTDs, which have been around longer than XML, describe the type of document you're dealing with. When XML arrived as a specification, certain concepts were considered to help protect against mistakes within the document. One concept, validation, is the process of comparing an XML document to its DTD.
Subscribe to:
Posts (Atom)