Re: [axis2] Builder Selector Proposal

Nick, We already have an attachment API in MessageContext which can be used to access attachements. That's one end of the problem which we are trying to tackle.. In order to set that reference, the MIME processing logic needs to access the message context or otherwise. It's impossible for the bu

[jira] Commented: (AXIS2-1865) Axis2 JSPs don't compile with Weblogic 8.1 + JRockit 1.4.2

[ http://issues.apache.org/jira/browse/AXIS2-1865?page=comments#action_12458036 ] Ali Sadik Kumlali commented on AXIS2-1865: -- Hi Mauricio, I use WL 8.1 + Sun JDK 1.4.2. Although currently I don't use war distribution, I tried it before

Re: Axis2 1.1 : java2wsdl Tool FlattensObjects in Schema

Hi, This is presently a limitation with the present Java2WSDL which looks into the JavaBean compositions but not into its inheritance hierarchy to generate the type. However this enhancement is planned as there is a JIRA opened for this - http://issues.apache.org/jira/browse/AXIS2-1749 - Venka

Axis2 1.1 : java2wsdl Tool FlattensObjects in Schema

I have just attempted to use the Axis2 java2wsdl tool to generate the webservice contract. The tool appears to generate a valid wsdl file, but it flattens the java objects (includes all the JavaBean fields but discards the inheritance hierarchy) used in the operation signature. This was not the ca

Re: [AXIS2] Proposal for saving the message context

>>On Fri, 2006-12-01 at 13:56 -0600, Ann Robinson wrote: >>> Hi, Sanjiva, >>> The proposal could be committed with little risk to the rest of Axis2. >>> The save/restore of a message context is not an automatic action and >>> so it would not affect current message handling. >> >>Yes but the code th

Re: [axis2] Builder Selector Proposal

Thilina, > For the moment I thought of using the content-type and the > inputstream.. But ideally this decision will be based on how deep we > are going to use the builders. It would be nice if we can let the > builders to handle the attachment stuff too, but it's simply not > possible since Axiom

[jira] Commented: (AXIS-2096) Custom simpleType as attribute of an element causes problems when displaying deployed service's WSDL

[ http://issues.apache.org/jira/browse/AXIS-2096?page=comments#action_12457814 ] Diego Louzán commented on AXIS-2096: I'm a commiter on Apache WSRP4J and this bug is preventing us from servicing the wsdl associated with the wsrp4j producer (

[jira] Created: (AXIS2-1866) Can not generate stub or skeleton code based on xmlbeans binding

Can not generate stub or skeleton code based on xmlbeans binding Key: AXIS2-1866 URL: http://issues.apache.org/jira/browse/AXIS2-1866 Project: Apache Axis 2.0 (Axis2) Issue Typ

[jira] Commented: (AXIS2-1865) Axis2 JSPs don't compile with Weblogic 8.1 + JRockit 1.4.2

[ http://issues.apache.org/jira/browse/AXIS2-1865?page=comments#action_12457811 ] Mauricio Wodarski da Silva commented on AXIS2-1865: --- Maybe this can help: http://marc.theaimsgroup.com/?l=axis-user&m=116594062708643&w=2 > Axis

[jira] Created: (AXIS2-1865) Axis2 JSPs don't compile with Weblogic 8.1 + JRockit 1.4.2

Axis2 JSPs don't compile with Weblogic 8.1 + JRockit 1.4.2 -- Key: AXIS2-1865 URL: http://issues.apache.org/jira/browse/AXIS2-1865 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug

Re: [axis2] woden jar in Axis2 1.1

OK done in r486235. Thanks, Jeremy On 12/11/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote: please change the names in build.xml. i'll fix things if needed. thanks, dims On 12/11/06, Jeremy Hughes <[EMAIL PROTECTED]> wrote: > On 12/6/06, Dan Diephouse <[EMAIL PROTECTED]> wrote: > > Woden itse

[Axis2] Build failure - trunk

Hi Devs, I'm seeing a build failure of the axis2 trunk :-( [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec [junit] [ERROR] TEST org.apache.axis2.java.security.driver.Java2SecTest FAILED And the test report says : Testsuite: org.apache.axis2.java.security.driver.Java2Se

[jira] Commented: (AXIS2-1609) namespace to package (ns2p) code gen option does not work in Axis2 1.1 RC2

[ http://issues.apache.org/jira/browse/AXIS2-1609?page=comments#action_12457738 ] Craig S. Bosma commented on AXIS2-1609: --- I made the following change to SchemaCompiler in the adb-codegen module, replacing this line (~244):

[jira] Created: (AXIS2-1864) Axis 2 expects single custom WSDL for all services in serviceGroup

Axis 2 expects single custom WSDL for all services in serviceGroup -- Key: AXIS2-1864 URL: http://issues.apache.org/jira/browse/AXIS2-1864 Project: Apache Axis 2.0 (Axis2) Issue

[jira] Created: (AXIS2-1863) problem with org.apache.axis2.databinding.utils.ConverterUtil.convertTodateTime(String content)

problem with org.apache.axis2.databinding.utils.ConverterUtil.convertTodateTime(String content) --- Key: AXIS2-1863 URL: http://issues.apache.org/jira/browse/AXIS2-1863

[jira] Commented: (AXIS-2477) how to supress SOAPHeaderElement attributes from appearing in soap request

[ http://issues.apache.org/jira/browse/AXIS-2477?page=comments#action_12457731 ] Andy Brook commented on AXIS-2477: -- Perhaps putting the reasons for the bug may help it to be assigned. I can say that Ive got axis working fine, however, if I tr

Re: Any news on Axis2 1.1.1?

+1 .. But I assume it is only bug fixes and no changes to interfaces. I saw few projects relese versions based on our 1.1. relese 1.1.1 should not break any of these. Srinath On 12/12/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: Hi All; I think we need to move our development soon into trun

Re: [axis2] Implementing JSON support for Axis2

we may need some changes in the spot where we call the different builders (mtom/stax) to add a check for content type and invoking the JSON stuff. right? BuilderSelector ;-) ~Thilina -- dims On 12/11/06, Isuru Suriarachchi <[EMAIL PROTECTED]> wrote: > Hi all, > > Currently I'm working on imp

Re: Any news on Axis2 1.1.1?

Hi All; I think we need to move our development soon into trunk , and other thing we have done considerable amount of changes in Axis2 1.1 branch , that simply implies we need to merge 1.1 branch again to trunk. So rather than continue development in 1.1 branch we need to start working on trunk

Re: [axis2] Builder Selector Proposal

Hi Dims, +1, Please throw in an interface for someone to write a custom builder and plug it in as well. That's the tricky part.. We already have the hierachy starting from StaxBuilder. There's is an inteface called OMStaxParserWrapper, but nobodyt seem to be using it.. It'll be bit hard to plug

[jira] Assigned: (AXIS2-1843) Unnecessary AxisFault

[ http://issues.apache.org/jira/browse/AXIS2-1843?page=all ] Deepal Jayasinghe reassigned AXIS2-1843: Assignee: Deepal Jayasinghe > Unnecessary AxisFault > - > > Key: AXIS2-1843 > URL: http://is

[jira] Assigned: (AXIS2-1849) Security exception is swallowed

[ http://issues.apache.org/jira/browse/AXIS2-1849?page=all ] Deepal Jayasinghe reassigned AXIS2-1849: Assignee: Ruchith Udayanga Fernando > Security exception is swallowed > --- > > Key: AXIS2-1849 >

[jira] Assigned: (AXIS2-1857) When a option is set to _operation client it effects all operations called after that

[ http://issues.apache.org/jira/browse/AXIS2-1857?page=all ] Deepal Jayasinghe reassigned AXIS2-1857: Assignee: Deepal Jayasinghe > When a option is set to _operation client it effects all operations called > after that > ---

Re: org.apache.axis.client.ServiceFactory.getObjectInstance

Hi Fabien Service-ref is part of the JSR 109 specification. This is not implemented directly by Axis 1.X. Only J2EE 1.4 Application Server (like JOnAS) have implemented that spec (including jaxrpc-mapping-file and others ...) BTW, in order to support jaxrpc-mapping file, you need to use Apche

Re: Why it only read 28 bytes

On Tue, 2006-12-12 at 11:55 +0800, jim ma wrote: > > Can anyone shed some light on this ? > Jim, HttpCore uses 2048 byte chunks per default and as far as I know Axis2 SimpleHttpServer does not override this default behavior. http://jakarta.apache.org/httpcomponents/httpcore/jakarta-httpcore/x

Re: Simple Ease of Use

Hi Paul ; > Can I suggest we change the default message receivers to be the RPC ones? +1 , and it is good idea to do, other thing is a RPC MR can handle OMElement case as well so switching to RPC is good idea. > > That way I could just have this as my default services.xml: > > > >P