[jira] Commented: (AXIS2-1714) AXIS2 V1.1: java2wsdl.bat does not work.
[ https://issues.apache.org/jira/browse/AXIS2-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463913 ] Carsten Ziegeler commented on AXIS2-1714: - I have the same problems with all Axis2 versions (including 1.1.1) - at least on my windows machine the problem is that the classpath is too long which causes either the error "command line too long" or strange looking class not found exceptions as the shell is in some cases "resetting" the classpath environment variable. My temporary solution is to extract all jar files into a classes directory and use this classes directory as the classpathit would be good if the tools would use correct manifest entries for all jars, so they could be run with "java -jar ..." or the scripts need to be changed somehow. > AXIS2 V1.1: java2wsdl.bat does not work. > - > > Key: AXIS2-1714 > URL: https://issues.apache.org/jira/browse/AXIS2-1714 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: wsdl >Affects Versions: 1.1 > Environment: Win XP, IBM JDK 1.5 >Reporter: Michael Moser > > The wsdl2java.bat does not work for me. I spiced it up with a few more > "echo ..." statements and all names, the paths and the command line > looks fine to me, but all it ever produced so far was: > "An error occured while generating codejava.lang.ClassNotFoundException: > org.dailymoon.classifieds.ClassifiedService" (I'm going through the > "classified ads" example in the tutorial at > http://www-128.ibm.com/developerworks/edu/ws-dw-ws-understand-web-services2.html). > How to regenerate: > 1.) I extracted the axis2 bin distribution to "C:\Java_Extensions\axis2-1.1"' > 2.) My example is located under > "C:\JavaDevt\tutorials\webservices\ClassifiedAds\src", > 3.) The actual .java file to be translated is > C:\JavaDevt\tutorials\webservices\ClassifiedAds\src\org\dailymoon\classifieds\ClassifiedService.java > 4.) I created a two-line .bat file: > set AXIS2_HOME=C:\Java_Extensions\axis2-1.1 > %AXIS2_HOME%\bin\java2wsdl.bat -cn > org.dailymoon.classifieds.ClassifiedService -o . > When I excute this I get: > C:\JavaDevt\tutorials\webservices\ClassifiedAds\src>generateWSDL.bat > C:\JavaDevt\tutorials\webservices\ClassifiedAds\src>set > AXIS2_HOME=C:\Java_Extensions\axis2-1.1 > C:\JavaDevt\tutorials\webservices\ClassifiedAds\src>C:\Java_Extensions\axis2-1.1\bin\java2wsdl.bat > -cn org.dailymoon.classifieds.ClassifiedService -o . > Using AXIS2_HOME: C:\Java_Extensions\axis2-1.1 > Using JAVA_HOME:C:\IBMJSDK1.5.0 > Using AXIS2_CLASS_PATH: > "C:\Java_Extensions\axis2-1.1;C:\Java_Extensions\axis2-1.1\lib\activation-1.1.jar;C:\Java_Extensions\axis2-1 > .1\lib\annogen-0.1.0.jar;C:\Java_Extensions\axis2-1.1\lib\axiom-api-1.2.jar;C:\Java_Extensions\axis2-1.1\lib\axiom-dom-1.2.jar;C:\Ja > va_Extensions\axis2-1.1\lib\axiom-impl-1.2.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-adb-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\a > xis2-adb-codegen-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-codegen-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-java2wsdl-1.1 > .jar;C:\Java_Extensions\axis2-1.1\lib\axis2-jibx-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-kernel-1.1.jar;C:\Java_Extensions\ax > is2-1.1\lib\axis2-saaj-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-soapmonitor-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-spr > ing-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-tools-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-xmlbeans-1.1.jar;C:\Java_Ext > ensions\axis2-1.1\lib\backport-util-concurrent-2.2.jar;C:\Java_Extensions\axis2-1.1\lib\commons-codec-1.3.jar;C:\Java_Extensions\axi > s2-1.1\lib\commons-fileupload-1.1.1.jar;C:\Java_Extensions\axis2-1.1\lib\commons-httpclient-3.0.1.jar;C:\Java_Extensions\axis2-1.1\l > ib\commons-io-1.2.jar;C:\Java_Extensions\axis2-1.1\lib\commons-logging-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\geronimo-spec-jms-1. > 1-rc4.jar;C:\Java_Extensions\axis2-1.1\lib\jakarta-httpcore-4.0-alpha2.jar;C:\Java_Extensions\axis2-1.1\lib\jaxen-1.1-beta-10.jar;C: > \Java_Extensions\axis2-1.1\lib\jibx-bind-1.1.2.jar;C:\Java_Extensions\axis2-1.1\lib\jibx-run-1.1.2.jar;C:\Java_Extensions\axis2-1.1\ > lib\mail-1.4.jar;C:\Java_Extensions\axis2-1.1\lib\neethi-2.0.jar;C:\Java_Extensions\axis2-1.1\lib\servletapi-2.3.jar;C:\Java_Extensi > ons\axis2-1.1\lib\stax-api-1.0.1.jar;C:\Java_Extensions\axis2-1.1\lib\woden-1.0.0M6.jar;C:\Java_Extensions\axis2-1.1\lib\wsdl4j-1.6. > 1.jar;C:\Java_Extensions\axis2-1.1\lib\wstx-asl-3.0.1.jar;C:\Java_Extensions\axis2-1.1\lib\xalan-2.7.0.jar;C:\Java_Extensions\axis
[jira] Created: (AXIS2-1025) Better Implement for getProperties in MessageContext
Better Implement for getProperties in MessageContext - Key: AXIS2-1025 URL: http://issues.apache.org/jira/browse/AXIS2-1025 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: core Reporter: Carsten Ziegeler Attachments: patch.txt The implementation of the getProperties() method is not taking the different environments into account. The applied patch fixes this problem. The patch has been discussed some weeks ago in the mailing list, but got never applied. So I'm now submitting this here, so it doesn't get lost. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Resolved: (AXIS2-1008) Reopen bug AXIS-987
Are you sure that this is fixed? I can't find the patch in the latest code from svn. Carsten Davanum Srinivas (JIRA) wrote: > [ http://issues.apache.org/jira/browse/AXIS2-1008?page=all ] > > Davanum Srinivas resolved AXIS2-1008. > - > > Resolution: Fixed > > reopened AXIS2-987 :) > >> Reopen bug AXIS-987 >> --- >> >> Key: AXIS2-1008 >> URL: http://issues.apache.org/jira/browse/AXIS2-1008 >> Project: Apache Axis 2.0 (Axis2) >> Issue Type: Bug >> Components: wsdl >>Reporter: Fabian Christ >> >> Hi, >> I want to reopen bug AXIS-987. This bug was solved at revision 429647 but at >> revision 430196 the bug reappeared an the patching code was removed. Please >> add the patch from AXIS-987 to fix this bug again. >> thanks, >> Fabian > -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1009) org.apache.axis2.databinding.utils.ConverterUtil.convertToOMAttribute is missing
[ http://issues.apache.org/jira/browse/AXIS2-1009?page=all ] Carsten Ziegeler updated AXIS2-1009: Attachment: sample-wsdl.zip Sure :) > org.apache.axis2.databinding.utils.ConverterUtil.convertToOMAttribute is > missing > > > Key: AXIS2-1009 > URL: http://issues.apache.org/jira/browse/AXIS2-1009 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: databinding >Reporter: Carsten Ziegeler > Attachments: sample-wsdl.zip > > > The current svn generates calls to > org.apache.axis2.databinding.utils.ConverterUtil.convertToOMAttribute() which > is missing in the class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1009) org.apache.axis2.databinding.utils.ConverterUtil.convertToOMAttribute is missing
org.apache.axis2.databinding.utils.ConverterUtil.convertToOMAttribute is missing Key: AXIS2-1009 URL: http://issues.apache.org/jira/browse/AXIS2-1009 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Reporter: Carsten Ziegeler The current svn generates calls to org.apache.axis2.databinding.utils.ConverterUtil.convertToOMAttribute() which is missing in the class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Updated: (AXIS2-963) Problems with complex xml schemas in wsdl2java
Thilo Frotscher schrieb: > Carsten, > > The schema location URL in your WSDL does not point to a document. > Perhaps that's already the problem: the code generator just can't > load the schema. > Hi Thilo, the schema location points to "http://schemas.xmlsoap.org/ws/2005/02/trust/ws-trust.xsd"; which is a valid schema. Or do you mean something different? Thanks Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-963) Problems with complex xml schemas in wsdl2java
[ http://issues.apache.org/jira/browse/AXIS2-963?page=all ] Carsten Ziegeler updated AXIS2-963: --- Attachment: authentication.wsdl > Problems with complex xml schemas in wsdl2java > -- > > Key: AXIS2-963 > URL: http://issues.apache.org/jira/browse/AXIS2-963 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: wsdl > Reporter: Carsten Ziegeler > Attachments: authentication.wsdl > > > When trying to generate a service code using wsdl2java (latest svn), I get > different errors depending on the databinding used. With "-d none" I get: > xception in thread "main" > org.apache.axis2.wsdl.codegen.CodeGenerationException > : org.apache.axis2.wsdl.codegen.CodeGenerationException: > org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No type was mapped > to the name > RequestSecurityToken with namespace > http://schemas.xmlsoap.org/ws/2005/02/trust at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:235) > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) > at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) > Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: > org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No type was mapped > to the name RequestSecurityToken with namespace > http://schemas.xmlsoap.org/ws/2005/02/trust at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:796) > at > With "-d adb" I get this exception: > Caused by: org.apache.axis2.schema.SchemaCompilationException: > Unsupported content Simple Content Extension ! at > org.apache.axis2.schema.SchemaCompiler.processSimpleContent(SchemaCom > piler.java:979) > With "-d xmlbeans" I get the following exception: > ... > Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: > http://schemas.xmlsoap.org/ws/2004/08/addressing/:4:1571: error: > cvc-enumeration-valid: > string value 'none' is not a valid enumeration value for type of > processContents attribute in xs:wildcard > at > org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGe > nerationUtility.java:235) > ... 8 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-963) Problems with complex xml schemas in wsdl2java
Problems with complex xml schemas in wsdl2java -- Key: AXIS2-963 URL: http://issues.apache.org/jira/browse/AXIS2-963 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Reporter: Carsten Ziegeler Attachments: authentication.wsdl When trying to generate a service code using wsdl2java (latest svn), I get different errors depending on the databinding used. With "-d none" I get: xception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException : org.apache.axis2.wsdl.codegen.CodeGenerationException: org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No type was mapped to the name RequestSecurityToken with namespace http://schemas.xmlsoap.org/ws/2005/02/trust at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:235) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No type was mapped to the name RequestSecurityToken with namespace http://schemas.xmlsoap.org/ws/2005/02/trust at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:796) at With "-d adb" I get this exception: Caused by: org.apache.axis2.schema.SchemaCompilationException: Unsupported content Simple Content Extension ! at org.apache.axis2.schema.SchemaCompiler.processSimpleContent(SchemaCom piler.java:979) With "-d xmlbeans" I get the following exception: ... Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: http://schemas.xmlsoap.org/ws/2004/08/addressing/:4:1571: error: cvc-enumeration-valid: string value 'none' is not a valid enumeration value for type of processContents attribute in xs:wildcard at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGe nerationUtility.java:235) ... 8 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Problems with MessageContext
Deepal Jayasinghe wrote:
> If you are happy with unmodifiable map then I have no objection , any
> way if some one want to modify property (or properties) he can easily do
> that no need to call the getProperties and then modify the map.
>
> So lets keep what we have now :)
>
You mean with my patch :) (Because the current impl always returns an
empty map).
I updated the patch to create an unmodifiable map and added some javadocs.
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Index:
D:/dev/workspace/axis2/modules/core/src/org/apache/axis2/context/MessageContext.java
===
---
D:/dev/workspace/axis2/modules/core/src/org/apache/axis2/context/MessageContext.java
(revision 421208)
+++
D:/dev/workspace/axis2/modules/core/src/org/apache/axis2/context/MessageContext.java
(working copy)
@@ -30,6 +30,9 @@
import javax.xml.namespace.QName;
import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.Map;
/**
* MessageContext holds service specific state information.
@@ -471,6 +474,42 @@
}
/**
+ * Retrieves all property values. The order of search is as follows:
search in
+ * my own options and then look in my context hierarchy. Since its possible
+ * that the entire hierarchy is not present, it will start at whatever
level
+ * has been set and start there.
+ * The returned map is unmodifiable, so any changes to the properties have
+ * to be done by calling [EMAIL PROTECTED] #setProperty(String, Object)}.
In addition,
+ * any changes to the properties are not reflected on this map.
+ *
+ * @return An unmodifiable map containing the combination of all available
+ * properties or an empty map.
+ */
+public Map getProperties() {
+final Map resultMap = new HashMap();
+
+// My own context hierarchy may not all be present. So look for
whatever
+// nearest level is present and add the properties
+// We have to access the contexts in reverse order, in order to allow
+// a nearer context to overwrite values from a more distant context
+if (configurationContext != null) {
+resultMap.putAll(configurationContext.getProperties());
+}
+if (serviceGroupContext != null) {
+resultMap.putAll(serviceGroupContext.getProperties());
+}
+if (serviceContext != null) {
+resultMap.putAll(serviceContext.getProperties());
+}
+if (operationContext != null) {
+resultMap.putAll(operationContext.getProperties());
+}
+// and now add options
+resultMap.putAll(options.getProperties());
+return Collections.unmodifiableMap(resultMap);
+}
+
+/**
* @return Returns RelatesTo array.
*/
public RelatesTo[] getRelationships() {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Problems with MessageContext
Carsten Ziegeler schrieb: > Deepal Jayasinghe wrote: >> Hi Carsten; >> >> I went through your patch and realized that , you are giving read only >> access to the properties . So if someone want to change the value of >> property (properties) then he wont be able to do that. I think we need >> to provide way to change them as well . >> > Hmm, but in this case has the MessageContext no control about what has > been changed, because it happens outside of its context. > > But I will come up with another patch which will handle put and remove > as well. > Ok, I look at a possible solution - but I think it's not worth the effort :) In order to be able to change the map, it's requrired to provide a map implementation which acts as a wrapepr around all the other maps. Simple operations like put,get,remove etc. are simple to implement - but complex ones, like values(), entrySet() etc. require a lot of code. We could use commons-collections and their CompositeMap for that - at least partically. Before I implement this, I would like to know if adding a dependency to commons collections just for this simple feature is fine. Personally I think the getProperties() method should return an unmodifiable map. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Problems with MessageContext
Deepal Jayasinghe wrote: > Hi Carsten; > > I went through your patch and realized that , you are giving read only > access to the properties . So if someone want to change the value of > property (properties) then he wont be able to do that. I think we need > to provide way to change them as well . > Hmm, but in this case has the MessageContext no control about what has been changed, because it happens outside of its context. But I will come up with another patch which will handle put and remove as well. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Problems with MessageContext
Sanjiva Weerawarana wrote:
> On Tue, 2006-07-11 at 08:19 +0200, Carsten Ziegeler wrote:
>>> So in effect the properties hashtable inherited from the superclass is
>>> not used by the MessageContext class.
>>>
>> Yes, except in the getProperties() method. If you do a setProperty("A",
>> "B") on the message context and then do a getProperties().get("A"), you
>> end up with getting null and not "B". So I think it should be fixed.
>
> Oops, you're right of course! Send a patch? :)
Sure, here we go :)
The implementation is adding the properties from the various contexts
into a map (reversing the search order) and returns the combined map.
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Index:
D:/dev/workspace/axis2/modules/core/src/org/apache/axis2/context/MessageContext.java
===
---
D:/dev/workspace/axis2/modules/core/src/org/apache/axis2/context/MessageContext.java
(revision 420740)
+++
D:/dev/workspace/axis2/modules/core/src/org/apache/axis2/context/MessageContext.java
(working copy)
@@ -30,6 +30,8 @@
import javax.xml.namespace.QName;
import java.util.ArrayList;
+import java.util.HashMap;
+import java.util.Map;
/**
* MessageContext holds service specific state information.
@@ -471,6 +473,42 @@
}
/**
+ * Retrieves all property values. The order of search is as follows:
search in
+ * my own options and then look in my context hierarchy. Since its possible
+ * that the entire hierarchy is not present, I will start at whatever level
+ * has been set and start there.
+ *
+ * @return the combination of all available properties or an empty map
+ */
+public Map getProperties() {
+final Map resultMap = new HashMap();
+
+// My own context hierarchy may not all be present. So look for
whatever
+// nearest level is present and add the properties
+// We have to access the contexts in reverse order, in order to allow
+// a nearer context to overwrite values from a more distant context
+if (configurationContext != null) {
+resultMap.putAll(configurationContext.getProperties());
+}
+if (serviceGroupContext != null) {
+resultMap.putAll(serviceGroupContext.getProperties());
+}
+if (serviceContext != null) {
+resultMap.putAll(serviceContext.getProperties());
+}
+if (operationContext != null) {
+resultMap.putAll(operationContext.getProperties());
+}
+
+// and now add options, or if the map is empty so far just return them
+if ( resultMap.isEmpty() ) {
+return options.getProperties();
+}
+resultMap.putAll(options.getProperties());
+return resultMap;
+}
+
+/**
* @return Returns RelatesTo array.
*/
public RelatesTo[] getRelationships() {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Problems with MessageContext
Sanjiva Weerawarana wrote:
> On Mon, 2006-07-10 at 11:33 +0200, Carsten Ziegeler wrote:
>> While playing around with implementing my own handler, I found out,
>> that the getProperties() method of the MessageContext is not implemented
>> correctly: MessageContext overrides the property handling of the parent
>> class by setting/getting properties from the Options object. But
>> getProperties() is passed on to the parent class which then always
>> returns an empty map. (Using getOptions().getProperties() of course works).
>> If you need an implementation for getProperties() which uses the Options
>> object I can provide it.
>
> IIRC, the behavior desired was for just the message context to use
> options' properties instead of using the local hashtable. This has
> something to do with allowing users to set stuff from outside via
> options and having them take effect at the various contexts.
>
Ah, thanks for the info.
> So if the property is not found via options.getProperty() then we cross
> over to whatever level of other context is around (operation or service
> or .. etc.) and ask there.
>
> Note that setProperty() too has been overridden to match this behavior.
>
> So in effect the properties hashtable inherited from the superclass is
> not used by the MessageContext class.
>
Yes, except in the getProperties() method. If you do a setProperty("A",
"B") on the message context and then do a getProperties().get("A"), you
end up with getting null and not "B". So I think it should be fixed.
>> In addition it seems that the outgoing MessageContext objects do not
>> contain the servlet context. Is this by mistake or by design? If it's
>> the latter, how can I access the servlet context?
>
> Its by design- you have to get the operation context from the outgoing
> MC and then get the incoming MC from that and look there for the servlet
> context and any other "incoming" info.
>
Ok, thanks!
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Problems with MessageContext
While playing around with implementing my own handler, I found out, that the getProperties() method of the MessageContext is not implemented correctly: MessageContext overrides the property handling of the parent class by setting/getting properties from the Options object. But getProperties() is passed on to the parent class which then always returns an empty map. (Using getOptions().getProperties() of course works). If you need an implementation for getProperties() which uses the Options object I can provide it. In addition it seems that the outgoing MessageContext objects do not contain the servlet context. Is this by mistake or by design? If it's the latter, how can I access the servlet context? Thanks Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Commented: (AXIS-1825) Use WSDL to validate incomming messages
Davanum Srinivas (JIRA) wrote: [ http://issues.apache.org/jira/browse/AXIS-1825?page=comments#action_59525 ] Davanum Srinivas commented on AXIS-1825: Can we make this as an enhancement request? thanks, dims Damn, I thought I'd choose enhancement request. Sorry! Now the issue is closed and I can't change anything :( Can you - as admin - change it? Thanks Carsten Use WSDL to validate incomming messages --- Key: AXIS-1825 URL: http://issues.apache.org/jira/browse/AXIS-1825 Project: Axis Type: Improvement Reporter: Carsten Ziegeler Currently Axis doesn't use a WSDL file; even if you already have one you use wsdl2java and then deploy the result into Axis. During this deployment the wsdl file is not deployed as well. The main problem with this is that some validation rules defined in the wsdl file are not checked by axis anymore, for example if you use patterns for strings etc. So, it would be great if it would be possible to deploy a WSDL file as well and Axis would use that to validate incomming messages. The validation can be done by using WSDL4J to read the WSDL file and then create an XML Schema out of the in memory representation you get from WSDL4J; just add a new schema element for each incomming message to the schema and then you can validate the incomming request using this schema. -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
[jira] Created: (AXIS-1825) Use WSDL to validate incomming messages
Use WSDL to validate incomming messages --- Key: AXIS-1825 URL: http://issues.apache.org/jira/browse/AXIS-1825 Project: Axis Type: Improvement Reporter: Carsten Ziegeler Currently Axis doesn't use a WSDL file; even if you already have one you use wsdl2java and then deploy the result into Axis. During this deployment the wsdl file is not deployed as well. The main problem with this is that some validation rules defined in the wsdl file are not checked by axis anymore, for example if you use patterns for strings etc. So, it would be great if it would be possible to deploy a WSDL file as well and Axis would use that to validate incomming messages. The validation can be done by using WSDL4J to read the WSDL file and then create an XML Schema out of the in memory representation you get from WSDL4J; just add a new schema element for each incomming message to the schema and then you can validate the incomming request using this schema. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: [Fwd: Validating a document using WSDL?]
Davanum Srinivas wrote: We use WSDL4J and that has support to extract information from wsdl. Thanks Dims! Will look into that. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [Fwd: Validating a document using WSDL?]
Davanum Srinivas wrote: You can always use XMLBeans or Castor as the data-binding layer and let them handle the validation part. Hmm, yes, but how easy is it to extract the schema from the wsdl? Is there anything that supports this task? Thanks Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [Fwd: Validating a document using WSDL?]
Davanum Srinivas wrote: Do you mean validating the xml inside the soap message against the schema specified in the wsdl? Yes :) Carsten -- dims On Sun, 13 Feb 2005 14:47:02 +0100, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: Forwarding to dev list, perhaps someone has an idea? Thanks! Carsten -- Forwarded message -- From: Carsten Ziegeler <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Date: Fri, 11 Feb 2005 10:02:53 +0100 Subject: Validating a document using WSDL? I'm searching for an easy way of validating an XML document against a WSDL file. This is in order to test if the document is a valid request for the service. Does Axis provide some classes/functionalitity I could use? Or is there something else I can do? I read somewhere that Axis currently doesn't valid ws against the wsdl if document style is used. Is this true? Thanks Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
[Fwd: Validating a document using WSDL?]
Forwarding to dev list, perhaps someone has an idea? Thanks! Carsten --- Begin Message --- I'm searching for an easy way of validating an XML document against a WSDL file. This is in order to test if the document is a valid request for the service. Does Axis provide some classes/functionalitity I could use? Or is there something else I can do? I read somewhere that Axis currently doesn't valid ws against the wsdl if document style is used. Is this true? Thanks Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ --- End Message ---
