[jira] Updated: (AXIS2-4631) getOMElement() of StubClass: ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter.
[ https://issues.apache.org/jira/browse/AXIS2-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Regula updated AXIS2-4631: - Description: Inside get getOMElement(): ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter. It is overriding the serialize method with org.apache.axis2.databinding.utils.writer.MTOMAwareXserializeMLStreamWriter as parameter. I generated the StubClass using the command wsdl2java -uri http://localhost:8080/axis2/services/EchoService?wsdl -O . from command prompt. I havent used any IDE. I even tried axis2 1.4.1 still the same problem. I am using jdk 1.6 was: Inside get getOMElement(): ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter. It is overriding the serialize method with org.apache.axis2.databinding.utils.writer.MTOMAwareXserializeMLStreamWriter as parameter. I generated the StubClass using the command wsdl2java -uri http://localhost:8080/axis2/services/EchoService?wsdl -O . I even tried axis2 1.4.1 still the same problem Environment: JDK1.6, Axis2, XP Home, DellDimension 2400 (was: XP Home DellDimension 2400) > getOMElement() of StubClass: ADBDataSource not overriding serialize method > with MTOMAwareXMLStreamWriter. > - > > Key: AXIS2-4631 > URL: https://issues.apache.org/jira/browse/AXIS2-4631 > Project: Axis2 > Issue Type: Bug > Components: wsdl >Affects Versions: 1.5.1 > Environment: JDK1.6, Axis2, XP Home, DellDimension 2400 >Reporter: Prasad Regula >Priority: Blocker > > Inside get getOMElement(): > ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter. > It is overriding the serialize method with > org.apache.axis2.databinding.utils.writer.MTOMAwareXserializeMLStreamWriter > as parameter. I generated the StubClass using the command > wsdl2java -uri http://localhost:8080/axis2/services/EchoService?wsdl -O . > from command prompt. I havent used any IDE. > I even tried axis2 1.4.1 still the same problem. > I am using jdk 1.6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-4631) getOMElement() of StubClass: ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter.
[ https://issues.apache.org/jira/browse/AXIS2-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Regula updated AXIS2-4631: - Component/s: wsdl Priority: Blocker (was: Major) > getOMElement() of StubClass: ADBDataSource not overriding serialize method > with MTOMAwareXMLStreamWriter. > - > > Key: AXIS2-4631 > URL: https://issues.apache.org/jira/browse/AXIS2-4631 > Project: Axis2 > Issue Type: Bug > Components: wsdl >Affects Versions: 1.5.1 > Environment: XP Home DellDimension 2400 >Reporter: Prasad Regula >Priority: Blocker > > Inside get getOMElement(): > ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter. > It is overriding the serialize method with > org.apache.axis2.databinding.utils.writer.MTOMAwareXserializeMLStreamWriter > as parameter. I generated the StubClass using the command wsdl2java -uri > http://localhost:8080/axis2/services/EchoService?wsdl -O . > I even tried axis2 1.4.1 still the same problem -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (AXIS2-4631) getOMElement() of StubClass: ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter.
getOMElement() of StubClass: ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter. - Key: AXIS2-4631 URL: https://issues.apache.org/jira/browse/AXIS2-4631 Project: Axis2 Issue Type: Bug Affects Versions: 1.5.1 Environment: XP Home DellDimension 2400 Reporter: Prasad Regula Inside get getOMElement(): ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter. It is overriding the serialize method with org.apache.axis2.databinding.utils.writer.MTOMAwareXserializeMLStreamWriter as parameter. I generated the StubClass using the command wsdl2java -uri http://localhost:8080/axis2/services/EchoService?wsdl -O . I even tried axis2 1.4.1 still the same problem -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (AXIS2-4630) ADB generates code that doesn't compile when WSDL has abstract types.
ADB generates code that doesn't compile when WSDL has abstract types. - Key: AXIS2-4630 URL: https://issues.apache.org/jira/browse/AXIS2-4630 Project: Axis2 Issue Type: Bug Components: adb Affects Versions: 1.5.1 Reporter: Aaron Gourley In ADBBeanTemplate.xsl, occurrences of the following exist without taking into consideration the fact that the class may have been declared as abstract: new (); Classes are declared abstract if @isAbstract='true' here (also in ADBBeanTemplate.xsl): abstract Obviously, abstract classes can not be instantiated directly. Specifically I am seeing the problem in the generated Factory.fromString() method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[Axis2 1.4.1 with Rampart 1.4] - No user value in the rampart configuration policy
Hello everybody,
I have a Web Application wich interacts
with a Axis2 Web Service. The requests to WS are both free and with
secure policy. Web App creates 2 client for my service: first one ("free
client") call the WS in http without security header; the second
("secure client") engages rampart module and adds UsernameToken header
to soap message.
Consider this situation:
- a logged user does a request
to WS using "secure client" => success
- immediately
after user receive responce, system do:
+ stub._getServiceClient().getOptions().setUserName("");
+ stub._getServiceClient().getOptions().setPassword("");
+
stub._getServiceClient().cleanupTransport();
+
stub._getServiceClient().cleanup();
- user logout and does a request to WS using "free client" => ERROR:
No user value in the rampart configuration policy!!!
Why does it
happen if user calls the WS through
"free client"?
If I use forever the same client and engage and disengage rampart
when needed, axis2 stack loads on java heap space 2 modules (mex and
rampart jars) at any secure request. The garbage collection never
deletes these modules and I am obligated to restart Tomcat regularly
because heap space is full!!!
Have you any solution for my problem?
Many thanks in advance
and sorry for my bad bad english! :)
*
F. Giuseppe Atzeni
Mail: giuseppe.atz...@gmail.com
*
Presentaci un amico! Invita i tuoi amici a scoprire i servizi Tiscali: per ogni
amico che attiverà un servizio Tiscali, potrai avere 30 euro di sconto e lo
stesso sconto di 30 euro verrà poi offerto al tuo amico.
Scopri come! http://abbonati.tiscali.it/presentaci_un_amico/?WT.mc_id=01fw
[jira] Created: (AXIS-2822) Content-Length calculation issue.
Content-Length calculation issue. - Key: AXIS-2822 URL: https://issues.apache.org/jira/browse/AXIS-2822 Project: Axis Issue Type: Bug Components: Basic Architecture Affects Versions: 1.4 Environment: This is the clients environment: Red Hat Enterprise Linux AS release 4 (Nahant Update 4) With kernel: Linux 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:27:17 EDT 2006 i686 i686 i386 GNU/Linux Java Env: Java(TM) SE Runtime Environment (build 1.6.0_13-b03) Java HotSpot(TM) Server VM (build 11.3-b02, mixed mode) Reporter: Vasili Bledar While 99.9% the axis is working perfectly, when trying to send a request of 1.500.000 bytes approximately, the server fails to acknowledge it. While trying to send the same request a few times in a row, it is always sent with different content-length. The element's indexes in the xml file we sent may differ each time, but the actual data are always the same. For example: 1st time we transmit: blabla gluglu The 2nd time we transmit may be found like this: gluglu blabla By using a packet sniffer on the server side we can see that our request is successfully transmitted. The soap request is reassembled through the packets recieved and the request body is checked against an xml parser which reveals that everything is ok with the xml data pasted in it. This xml body is different each time, but the length of the body should be the same (I'm not 100% sure on this and I may be missing something essential here). Another fact is that, the content-length parameter could say for example that the content-length is 1.456.321 bytes, but the number of packets size summed together for the specific communication is 1.255.456 or it could be slightly above the content-length which is not correct since there are definetely more data in communication which should increase the bytes sent in the communication much above the content-length. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Can not commit to the trunk
hi, I am getting this error when try to commit to the trunk. svn: Commit failed (details follow): svn: Server sent unexpected return value (403 Forbidden) in response to CHECKOUT request for '/repos/asf/!svn/ver/909680/axis/axis2/java/core/trunk/modules/adb/src/org/apache/axis2/databinding/utils/writer/MTOMAwareOMBuilder.java' svn: Your commit message was left in a temporary file: but seems that others can commit to the trunk. what could be the reason for this? thanks, Amila. -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
