[jira] Updated: (AXIS2-3775) Register unmarshall info in DocLitBareMethodMarshaller
[ https://issues.apache.org/jira/browse/AXIS2-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takahide Nogayama updated AXIS2-3775: - Attachment: patch.txt > Register unmarshall info in DocLitBareMethodMarshaller > -- > > Key: AXIS2-3775 > URL: https://issues.apache.org/jira/browse/AXIS2-3775 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: jaxws > Environment: windows java > Reporter: Takahide Nogayama > Attachments: patch.txt > > Original Estimate: 168h > Remaining Estimate: 168h > > Currently DocLitWrappedMethodMarshaller can do unmarshalling fast by > regisntering UnmarshallInfo. This issue is opened to do the same optimization > in DocLitBareMethodMarshaller -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3775) Register unmarshall info in DocLitBareMethodMarshaller
[ https://issues.apache.org/jira/browse/AXIS2-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takahide Nogayama updated AXIS2-3775: - Remaining Estimate: 168h (was: 24h) Original Estimate: 168h (was: 24h) > Register unmarshall info in DocLitBareMethodMarshaller > -- > > Key: AXIS2-3775 > URL: https://issues.apache.org/jira/browse/AXIS2-3775 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: jaxws > Environment: windows java > Reporter: Takahide Nogayama > Original Estimate: 168h > Remaining Estimate: 168h > > Currently DocLitWrappedMethodMarshaller can do unmarshalling fast by > regisntering UnmarshallInfo. This issue is opened to do the same optimization > in DocLitBareMethodMarshaller -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3775) Register unmarshall info in DocLitBareMethodMarshaller
Register unmarshall info in DocLitBareMethodMarshaller -- Key: AXIS2-3775 URL: https://issues.apache.org/jira/browse/AXIS2-3775 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Environment: windows java Reporter: Takahide Nogayama Currently DocLitWrappedMethodMarshaller can do unmarshalling fast by regisntering UnmarshallInfo. This issue is opened to do the same optimization in DocLitBareMethodMarshaller -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3417) Modify BlockImpl to avoid double unmarshalling
[ https://issues.apache.org/jira/browse/AXIS2-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takahide Nogayama updated AXIS2-3417: - Attachment: patch.txt > Modify BlockImpl to avoid double unmarshalling > -- > > Key: AXIS2-3417 > URL: https://issues.apache.org/jira/browse/AXIS2-3417 > Project: Axis 2.0 (Axis2) > Issue Type: New Feature > Components: jaxws > Environment: Windows, java 1.5 > Reporter: Takahide Nogayama > Attachments: patch.txt > > > BlockImpl.getBusinessObject() creates an buisiness object from AXIOM. > I am trying to create buisiness object before JAXWSReceiver and set the > buisiness object into OMSoucedElement. But current > BlockImpl.getBuisinessObject() can not aware that. The BlockImpl wraps the > OMSourcedElement by OMStaXWrapper and create same buisiness object again. > This patch modifies BlockImpl to be able to aware such OMSoucedElement which > has buisiness object and set the buisiness object into BlockImpl. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3417) Modify BlockImpl to avoid double unmarshalling
Modify BlockImpl to avoid double unmarshalling -- Key: AXIS2-3417 URL: https://issues.apache.org/jira/browse/AXIS2-3417 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws Environment: Windows, java 1.5 Reporter: Takahide Nogayama BlockImpl.getBusinessObject() creates an buisiness object from AXIOM. I am trying to create buisiness object before JAXWSReceiver and set the buisiness object into OMSoucedElement. But current BlockImpl.getBuisinessObject() can not aware that. The BlockImpl wraps the OMSourcedElement by OMStaXWrapper and create same buisiness object again. This patch modifies BlockImpl to be able to aware such OMSoucedElement which has buisiness object and set the buisiness object into BlockImpl. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Request for XML Filter (AXIS2-1085)
BTW, In the original solution, filter is inserted like the follwoing code. // assume InputStream is given // create XML StAX parser XMLStreamReader rawReader = StAXUtils.createXMLStreamReader(in); // insert filter Filter filter = new FilterImpl(); filter.init(rawReader, msgctx); // create Builder. If xmlReader is implementation of BuilderAwareReader, builder is set to the xmlReader StAXSOAPModelBuilder builder = new StAXSOAPModelBuilder(filter, SOAP11Constants.SOAP_ENVELOPE_NAMESPACE_URI); // create SOAP envelope SOAPEnvelope soapEnvelope = builder.getSOAPEnvelope(); messageContext.setEnvelope(soapEnvelope); XMLStreamReader is replaced by filter before creating builder. This is simpler than replacing parser after creating builder. Can we move "creating builder code" to handler layer? if so, we can use this simple insertion in handler solution. Regards, --- Takahide Nogayama
Re: Request for XML Filter (AXIS2-1085)
In handler solution, I guess that new two handleres are added to handler chain. First handler inserts filter and second handler classifies envelope into normal or fault. To insert filter in the first handler, the following code is naive approach. // get builder SOAPEnvelope envelope = messageContext.getEnvelope(); StAXBuilder staxBuilder = (StAXBuilder) envelope.getBuilder(); // set cache flag false to get parser staxBuilder.setCache(false); XMLStreamReader rawReader = (XMLStreamReader) staxBuilder.getParser(); // insert filter Filter filter = new FilterImpl(); filter.init(rawReader, msgctx); // set filter again staxBuilder.setParser(filter); // This method is not supported now. The last line StAXBuilder.setParser(XMLStreamReader) is not supported and will not be supported in the future. This is first cons of my Email on 11/10 Regards, --- Takahide Nogayama
Re: Request for XML Filter (AXIS2-1085)
Hi Sanjiva, I am hoping to resume this discussion with you. Please give us comment about these alternative solution's pros and cons or let me know what is your concrete worry. Regards, --- Takahide Nogayama
Re: Request for XML Filter (AXIS2-1085)
And We also inspect another solution which uses XMLInputFactory. In this solution, Filter is inserted at XMLInputFactory which is written by us. The XMLInputFactory returns Filter instance. The filter wraps XMLStreamReader (Filter -> XMLStreamReader). And the filter goes into builder (StAXBuilder -> Filter -> XMLStreamReader). Here, filter configuration is stored in XMLInputFactory. We expect that the ode which pass MessageContext to XMLInputFactory will be too complex, because XMLInputFactory is wrapped by StAXUtils and StaxUtils reuses several XMLInputFactory. To avoid this complex, we can use ThreadLocal-Storage. We store MessageContext immediately to the ThreadLocal-Storage when it is created, then filter which is in the same thread can get MessageContext by the ThreadLocal-Storage. (In current implementation, MessageContext is stored on ThreadLocal-Storage at receiver layer. That is, MessageContext is not stored when the message processed in transport layer and handler layer. To archieve this XMLInputFactory solution, we have to change transport layer to store MC to TLS.) # We do not think this solution is good. because TLS is used. The points of XMLInputFactory solution are - Insert filter inside of XMLInputFactory - Filter configuration is stored in the XMLInputFactory - Pass MessageContext by using ThreadLocal-Storage pros) There are no filter related code in AXIS2. cons) Need to change to AXIS2 transport layer component to store MessageContext on ThreadLocal-Storage when it is created. cons) This seems contradict to MC design. We put context information in Axis Service/Operation/Message context because there is no control of when there is a thread switch. Regards, --- Takahide Nogayama
Re: Request for XML Filter (AXIS2-1085)
All, I inspect the Handler solution, the following is pros and cons. pros) There is no layer mixing. pros) There are no filter related code in AXIS2. cons) Need to change StAXBuilder to replace XMLStreamReader by Filter. To replace XMLStreamReader of builder by Filter, we have to add "setParser" method to "StAXBuilder". (we can get builder instance in handler by using ((OMElementImpl)msgctx.getEnvelope()).getBuilder() ) Apache community had already disscussed about this method ever. They concluded that they will never add this method to StAXBuilder. Because if some one tries to changes the parser, while the object model is being built or partially build, everything will get screwed. I heard this from Eran.http://issues.apache.org/jira/browse/WSCOMMONS-76#action_12434318 cons) Filter can not see SOAPHeader StAXEvents. SOAPHeader part is probably already built at the time by SOAPEnvelope.getBody(). For Example, (if we can add setParser to StAXBuilder) WSS specification says that two wsu:Id attributes within an XML document MUST NOT have the same value. So Id-Uniqueness-check-Filter must check Id-Uniqueness against entire XML document. However, at the top of Handler chain, the elements before have already been build by SOAPEnvelope.getBody(). That is, its StAX events are consumed and trashed. Id-Uniqueness-check-Filter which is inserted by handler can check the StAX events of and its descendant elements, but it can not check entire Id-Uniqueness. --- Takahide Nogayama
Re: Request for XML Filter (AXIS2-1085)
> OK then write a handler that turns off caching (so you get the pull > stream raw), eats whatever it wants and builds a new envelope and sticks > it onto the MC as the envelope. > > No expanding the tree, no architectural inconsistency and you get StAX > to play with. Problem solved? > > Sanjiva. > Yes, That is right. If we wrote handler which get parser and insert filter, at the top of handler chain, then we could avoid to change transport layer to insert filter. But we can not filter SOAP header part by the handler solution, because SOAP header part is already build in transport layer before handler layer by invoking envelope.getBody(). For example, envelope.getBody() is called on the bottom of HTTPTransportUtils.processHTTPPostRequest(), then the envelope is passed to AxisEngine. All StAXEvents of the SOAP header are already consumed by the handler gets envelope. Regards, --- Takahide Nogayama
Re: Request for XML Filter (AXIS2-1085)
Sanjiva said: >The second point is what's fundamentally inconsistent with Axis2's >architecture. If you want to introduce a StAX filter that one's thing. >But doing that and having access to the message context doesn't make >sense: we create an OMElement for the envelope giving just the StAX >stream and then create a message context using that envelope. Sorry I am not sure that I understand your point, but in my understanding, Message context is created at AxisServilet and many information are added by AxisServlet, TransportUtils (envelope is created here), AxisEngine, Dispatcher, and Handler while the message is propagated to message receiver. The information means AxisConfiguration, URL, character encoding type, SOAPAction, WSA-Action, AxisOperation, and so on. They will be used at Handler layer to provide QOS. Sanjiva said: >If you want a StAX filter then it must be a StAX filter: StAX in, StAX >out. I don't agree with the proposed change because its inconsistent >with the design and appears to mix layers of processing. Filter might not be clean design in terms of mixed layer processing. But handler with filter is good for performance/memory perspective. Filter enables us to have an option of doing some part of the job of the handler on StAX event layer or on handler layer. It might not be must-have but nice-to-have. I think that mix layers of processing and performance improvement are trade-off problem. Regards, --- Takahide Nogayama
Re: Request for XML Filter (AXIS2-1085)
>Henry said: > >One of the possible use cases for filter is for checking uniqness of a >piece of data, if this is implemented in using filter, the check and >enforcement can be done during the parsing of the message. This will save >the walking of the OM tree again. > > >A uniquenes check requires the inspection of the entire message. >If a uniquess check is performed with a handler solution, there are several undesirable outcomes: >1) the OM tree will be traversed, which is expensive. >2) the OM tree will be expanded and cached, which kills performance. > >If a uniquess check is performed with a filter and handler solution: >1) The filter can inspect the StAX events as they are read. The filter will not affect the caching of the OM tree. The filter will not pull StAX events. >2) The filter will store its results on the MessageContext. > >Handlers pull StAX events. > Filters don't pull StAX events. They intercept and propogate StAX events. > >Comments ? Takahide / Henry can you provide more justifications or feedback for this request ? Thanks, Let me add comment to the second outcomes of the handler solution, (2) the OM tree will be expanded and cached, which kills performance and consuming memory space Regards, --- Takahide Nogayama
[jira] Commented: (AXIS2-1085) StAX Filter [ Data conversion, extraction, or do something between XMLStreamReader and StAXBuilder]
[ http://issues.apache.org/jira/browse/AXIS2-1085?page=comments#action_1242 ] Takahide Nogayama commented on AXIS2-1085: -- Hi Eran, I am sorry for such a confusing example. ExtractMyActorSOAPHeaderFilter is not good example for AXIS2. I agree that other intermediary are not able to process, if previous node removes SOAP header. This filter may be useful in terms of avoiding to create fruitless OM Element, when ultimate receiver recieve others header. >2. If possible. please explain your reason behind putting this code "inside >Axis2"? Please see FilterDemo2 and PickUpFilter in patch ver 8. The filter finds the OMElement which meets some conditions specified by the user (in this example, the condition is "localName=e1") and saves the reference of the OMElement in List (, Map, Set, or something like that). The list is shared with handlers by using messageContext.set/getProperty. Then handler can access the element without traverse. > StAX Filter [ Data conversion, extraction, or do something between > XMLStreamReader and StAXBuilder] > --- > > Key: AXIS2-1085 > URL: http://issues.apache.org/jira/browse/AXIS2-1085 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: core > Environment: windows >Reporter: Takahide Nogayama > Assigned To: Rich Scheuerle > Attachments: patchAXIOM_to_moduleaxiom-apisrcmainjava.txt, > patchAXIS2_to_moduleskernelsrc.txt, src_demo.zip, > StAX_filter_architecture.ppt, > ver2_patch_to_axiom_modules_axiom-api_src_main_java_org_apache_axiom_om_impl_builder.txt, > ver2_patch_to_axis2_modules_kernel_src_org_apache_axis2_transport.txt, > ver5_patch_to_axis2_modules.txt, ver6_patch_to_axis2_modules.txt, > ver7_patch_to_axis2_modules.txt, ver8_patch_to_axis2_modules.txt > > > To use this Filter in AXIS2, we have to change AXIS2 alittle. > See > http://issues.apache.org/jira/browse/WSCOMMONS-76 -- 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] Updated: (AXIS2-1085) StAX Filter [ Data conversion, extraction, or do something between XMLStreamReader and StAXBuilder]
[ http://issues.apache.org/jira/browse/AXIS2-1085?page=all ] Takahide Nogayama updated AXIS2-1085: - Attachment: ver8_patch_to_axis2_modules.txt ver7 was broken. please see ver8. > StAX Filter [ Data conversion, extraction, or do something between > XMLStreamReader and StAXBuilder] > --- > > Key: AXIS2-1085 > URL: http://issues.apache.org/jira/browse/AXIS2-1085 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: core > Environment: windows > Reporter: Takahide Nogayama > Assigned To: Rich Scheuerle > Attachments: patchAXIOM_to_moduleaxiom-apisrcmainjava.txt, > patchAXIS2_to_moduleskernelsrc.txt, src_demo.zip, > StAX_filter_architecture.ppt, > ver2_patch_to_axiom_modules_axiom-api_src_main_java_org_apache_axiom_om_impl_builder.txt, > ver2_patch_to_axis2_modules_kernel_src_org_apache_axis2_transport.txt, > ver5_patch_to_axis2_modules.txt, ver6_patch_to_axis2_modules.txt, > ver7_patch_to_axis2_modules.txt, ver8_patch_to_axis2_modules.txt > > > To use this Filter in AXIS2, we have to change AXIS2 alittle. > See > http://issues.apache.org/jira/browse/WSCOMMONS-76 -- 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] Updated: (AXIS2-1085) StAX Filter [ Data conversion, extraction, or do something between XMLStreamReader and StAXBuilder]
[ http://issues.apache.org/jira/browse/AXIS2-1085?page=all ] Takahide Nogayama updated AXIS2-1085: - Attachment: ver7_patch_to_axis2_modules.txt - add java doc - add some test asserts to check that filter can get parameter from axis2.xml. > StAX Filter [ Data conversion, extraction, or do something between > XMLStreamReader and StAXBuilder] > --- > > Key: AXIS2-1085 > URL: http://issues.apache.org/jira/browse/AXIS2-1085 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: core > Environment: windows > Reporter: Takahide Nogayama > Assigned To: Rich Scheuerle > Attachments: patchAXIOM_to_moduleaxiom-apisrcmainjava.txt, > patchAXIS2_to_moduleskernelsrc.txt, src_demo.zip, > StAX_filter_architecture.ppt, > ver2_patch_to_axiom_modules_axiom-api_src_main_java_org_apache_axiom_om_impl_builder.txt, > ver2_patch_to_axis2_modules_kernel_src_org_apache_axis2_transport.txt, > ver5_patch_to_axis2_modules.txt, ver6_patch_to_axis2_modules.txt, > ver7_patch_to_axis2_modules.txt > > > To use this Filter in AXIS2, we have to change AXIS2 alittle. > See > http://issues.apache.org/jira/browse/WSCOMMONS-76 -- 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] Updated: (AXIS2-1085) StAX Filter [ Data conversion, extraction, or do something between XMLStreamReader and StAXBuilder]
[ http://issues.apache.org/jira/browse/AXIS2-1085?page=all ]
Takahide Nogayama updated AXIS2-1085:
-
Attachment: ver6_patch_to_axis2_modules.txt
JIRA might be broken now, so I send my patch by e-mail.
The filter insertion point is included by
ver4_patch_to_axis2_modules_kernel_src_org_apache_axis2_transport.txt on
WSCOMMONS-76.
The patch in this mail includes all changes (insert filter, load
configration, unit test, test-resources).
I added testcases and asserts. Please run FilterRegistryTest as Junit
test. Or do $cd modules/kernel ; maven -o
And I prepare two demo scenarios. Please run FilterDemo1 and FilterDemo2
as java application.
I will post javadoc tommorow...
I think MessageContext is better. Because only messagecontext will
probably be used.
And we can pass any object to filter by using
messageContext.{setProperty/getProperty}.
I changed the context as MessageContext in this patch.
Regards,
-
Takahide Nogayama
[EMAIL PROTECTED]
"Rich Scheuerle (JIRA)" <[EMAIL PROTECTED]> wrote on 2006/10/21 23:27:36:
---
http://www.atlassian.com/software/jira
> StAX Filter [ Data conversion, extraction, or do something between
> XMLStreamReader and StAXBuilder]
> ---
>
> Key: AXIS2-1085
> URL: http://issues.apache.org/jira/browse/AXIS2-1085
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: New Feature
> Components: core
> Environment: windows
>Reporter: Takahide Nogayama
> Assigned To: Rich Scheuerle
> Attachments: patchAXIOM_to_moduleaxiom-apisrcmainjava.txt,
> patchAXIS2_to_moduleskernelsrc.txt, src_demo.zip,
> StAX_filter_architecture.ppt,
> ver2_patch_to_axiom_modules_axiom-api_src_main_java_org_apache_axiom_om_impl_builder.txt,
> ver2_patch_to_axis2_modules_kernel_src_org_apache_axis2_transport.txt,
> ver5_patch_to_axis2_modules.txt, ver6_patch_to_axis2_modules.txt
>
>
> To use this Filter in AXIS2, we have to change AXIS2 alittle.
> See
> http://issues.apache.org/jira/browse/WSCOMMONS-76
--
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] Updated: (AXIS2-1085) StAX Filter [ Data conversion, extraction, or do something between XMLStreamReader and StAXBuilder]
[ http://issues.apache.org/jira/browse/AXIS2-1085?page=all ] Takahide Nogayama updated AXIS2-1085: - Attachment: ver5_patch_to_axis2_modules.txt patch ver5 - load filter configuration from axis2.xml - test scenario is not complete. > StAX Filter [ Data conversion, extraction, or do something between > XMLStreamReader and StAXBuilder] > --- > > Key: AXIS2-1085 > URL: http://issues.apache.org/jira/browse/AXIS2-1085 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: core > Environment: windows > Reporter: Takahide Nogayama > Assigned To: Rich Scheuerle > Attachments: patchAXIOM_to_moduleaxiom-apisrcmainjava.txt, > patchAXIS2_to_moduleskernelsrc.txt, src_demo.zip, > StAX_filter_architecture.ppt, > ver2_patch_to_axiom_modules_axiom-api_src_main_java_org_apache_axiom_om_impl_builder.txt, > ver2_patch_to_axis2_modules_kernel_src_org_apache_axis2_transport.txt, > ver5_patch_to_axis2_modules.txt > > > To use this Filter in AXIS2, we have to change AXIS2 alittle. > See > http://issues.apache.org/jira/browse/WSCOMMONS-76 -- 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] Commented: (AXIS2-1085) StAX Filter [ Data conversion, extraction, or do something between XMLStreamReader and StAXBuilder]
[ http://issues.apache.org/jira/browse/AXIS2-1085?page=comments#action_12443288 ] Takahide Nogayama commented on AXIS2-1085: -- 1) Basically yes, Filter will be applied to all messages. But I think I do not need to apply a filter to the reader which reads a configuration file. how do you think? 2) I will change to read filter configuration from axis2.xml. 3) I agree the package name. 4) OK, I will prepare simple unit test. > StAX Filter [ Data conversion, extraction, or do something between > XMLStreamReader and StAXBuilder] > --- > > Key: AXIS2-1085 > URL: http://issues.apache.org/jira/browse/AXIS2-1085 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: core > Environment: windows > Reporter: Takahide Nogayama > Assigned To: Rich Scheuerle > Attachments: patchAXIOM_to_moduleaxiom-apisrcmainjava.txt, > patchAXIS2_to_moduleskernelsrc.txt, src_demo.zip, > StAX_filter_architecture.ppt, > ver2_patch_to_axiom_modules_axiom-api_src_main_java_org_apache_axiom_om_impl_builder.txt, > ver2_patch_to_axis2_modules_kernel_src_org_apache_axis2_transport.txt > > > To use this Filter in AXIS2, we have to change AXIS2 alittle. > See > http://issues.apache.org/jira/browse/WSCOMMONS-76 -- 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] Updated: (AXIS2-1085) StAX Filter [ Data conversion, extraction, or do something between XMLStreamReader and StAXBuilder]
[ http://issues.apache.org/jira/browse/AXIS2-1085?page=all ] Takahide Nogayama updated AXIS2-1085: - Attachment: ver2_patch_to_axiom_modules_axiom-api_src_main_java_org_apache_axiom_om_impl_builder.txt I changed Filter architecture to be more simple. > StAX Filter [ Data conversion, extraction, or do something between > XMLStreamReader and StAXBuilder] > --- > > Key: AXIS2-1085 > URL: http://issues.apache.org/jira/browse/AXIS2-1085 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: core > Environment: windows > Reporter: Takahide Nogayama > Attachments: patchAXIOM_to_moduleaxiom-apisrcmainjava.txt, > patchAXIS2_to_moduleskernelsrc.txt, src_demo.zip, > StAX_filter_architecture.ppt, > ver2_patch_to_axiom_modules_axiom-api_src_main_java_org_apache_axiom_om_impl_builder.txt, > ver2_patch_to_axis2_modules_kernel_src_org_apache_axis2_transport.txt > > > To use this Filter in AXIS2, we have to change AXIS2 alittle. > See > http://issues.apache.org/jira/browse/WSCOMMONS-76 -- 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] Updated: (AXIS2-1085) StAX Filter [ Data conversion, extraction, or do something between XMLStreamReader and StAXBuilder]
[ http://issues.apache.org/jira/browse/AXIS2-1085?page=all ] Takahide Nogayama updated AXIS2-1085: - Attachment: ver2_patch_to_axis2_modules_kernel_src_org_apache_axis2_transport.txt I changed Filter architecture to be more simple > StAX Filter [ Data conversion, extraction, or do something between > XMLStreamReader and StAXBuilder] > --- > > Key: AXIS2-1085 > URL: http://issues.apache.org/jira/browse/AXIS2-1085 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: core > Environment: windows > Reporter: Takahide Nogayama > Attachments: patchAXIOM_to_moduleaxiom-apisrcmainjava.txt, > patchAXIS2_to_moduleskernelsrc.txt, src_demo.zip, > StAX_filter_architecture.ppt, > ver2_patch_to_axiom_modules_axiom-api_src_main_java_org_apache_axiom_om_impl_builder.txt, > ver2_patch_to_axis2_modules_kernel_src_org_apache_axis2_transport.txt > > > To use this Filter in AXIS2, we have to change AXIS2 alittle. > See > http://issues.apache.org/jira/browse/WSCOMMONS-76 -- 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]
[AXIOM][AXIS2] StAX Filter
Hi all, I proposed new feature StAX Filter on JIRA https://issues.apache.org/jira/browse/WSCOMMONS-76 and https://issues.apache.org/jira/browse/AXIS2-1085. StAX Filter enables us to avoid fruitness traverse and creating fruitness OMElements. And we can convert XML data before creating OM. If you have any comments I would be grateful if you give me it. Thanks for your time. --- Takahide Nogayama smime.p7s Description: S/MIME Cryptographic Signature
[jira] Updated: (AXIS2-1085) StAX Filter [ Data conversion, extraction, or do something between XMLStreamReader and StAXBuilder]
[ http://issues.apache.org/jira/browse/AXIS2-1085?page=all ] Takahide Nogayama updated AXIS2-1085: - Attachment: src_demo.zip simple demo program > StAX Filter [ Data conversion, extraction, or do something between > XMLStreamReader and StAXBuilder] > --- > > Key: AXIS2-1085 > URL: http://issues.apache.org/jira/browse/AXIS2-1085 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: core > Environment: windows > Reporter: Takahide Nogayama > Attachments: patchAXIOM_to_moduleaxiom-apisrcmainjava.txt, > patchAXIS2_to_moduleskernelsrc.txt, src_demo.zip, StAX_filter_architecture.ppt > > > To use this Filter in AXIS2, we have to change AXIS2 alittle. > See > http://issues.apache.org/jira/browse/WSCOMMONS-76 -- 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-1085) StAX Filter [ Data conversion, extraction, or do something between XMLStreamReader and StAXBuilder]
StAX Filter [ Data conversion, extraction, or do something between XMLStreamReader and StAXBuilder] --- Key: AXIS2-1085 URL: http://issues.apache.org/jira/browse/AXIS2-1085 Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature Components: core Environment: windows Reporter: Takahide Nogayama Attachments: patchAXIOM_to_moduleaxiom-apisrcmainjava.txt, patchAXIS2_to_moduleskernelsrc.txt, StAX_filter_architecture.ppt To use this Filter in AXIS2, we have to change AXIS2 alittle. See http://issues.apache.org/jira/browse/WSCOMMONS-76 -- 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]
