There is an issue opened for Axis 1.5
https://issues.apache.org/jira/browse/AXIS2-4467
The 1.5.1 release seems not to have it resolved.
It is as .class in the war distribution.
On Wed, Nov 18, 2009 at 4:20 PM, Chinmoy Chakraborty wrote:
> Hi All,
>
> I am using Axis 1.5.1 but could not find
> o
please, ignore
On Fri, Oct 2, 2009 at 4:28 PM, Asen wrote:
> cpadmin
>
Here is how I am setting the date from the client:
Calendar calendar = Calendar.getInstance();
calendar.clear();
calendar.set(2009,8,16);
java.util.Date date = calendar.getTime();
On Fri, Sep 18, 2009 at 9:08 AM, Asen wrote:
> I am using axis2-1.5.
> I did not experience this erro
I am using axis2-1.5.
I did not experience this error with 1.4.1 version even though I found this
issue AXIS2-4447.
This is my incoming object(pojo) using java.util.Date
import java.util.Date;
/**
* Test pojo with xs:data
* @author asen
*/
public class PojoIn implements PojoI {
private
Hi there,
I am getting error on xs:date manipulations at the server side.
Does anyone know any solution to this problem?
Exception in thread "main" org.apache.axis2.AxisFault: date string can not
be less than 19 charactors
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils
Please ignore this.
I was missing some required .jar on the classpath.
On Thu, Aug 27, 2009 at 12:50 PM, Asen wrote:
> Hi there-
>
> When I am trying to engage "rampart" module, the module does not exist in
> the axis configuration.
> The "rahas" is loaded bu
Hi there-
When I am trying to engage "rampart" module, the module does not exist in
the axis configuration.
The "rahas" is loaded but not the "rampart".
This was not the case when I was using 1.4.1 release.
Is axis2-1.5 add the "rampart" 1.4 module into the faultModuleList and
ignoring it?
Asen-
ing these classes into a separate Maven
> artifact would indeed give users more options when assembling a custom
> WAR file. Please open a JIRA for this.
>
> Andreas
>
> On Tue, Aug 18, 2009 at 22:41, Asen wrote:
> > Hi there-
> >
> > Is there a way to get the
Hi there-
Is there a way to get the AxisAdminServlet for 1.5 release into a .jar file.
The current .war distribution comes with webapp/WEB-INF/classes and there is
the .class file,
but I really do not want to put this into my application in which I have
integrated axis.
I know that I can create my
te a class called
> >> String, but since it is in a different package than java.lang and the
> >> ADB generated code uses fully qualified class names everywhere, there
> >> is again no conflict here. For names that match a Java primitive type,
> >> ADB is smar
> is again no conflict here. For names that match a Java primitive type,
> > ADB is smart enough to add an underscore to avoid name collisions. It
> > seems that the only case that is not addressed is collision with the
> > getClass method.
> >
> > Andreas
> >
>
Excuse my jumping into this, but the same would happen if the the element
name is as
and the generated 'String' extending the
ADB binding will conflict
with the java.lang.String class.
I think this is a limitation of the ADB binding.
I have not experienced this problem when using the JiBX bindings
I agree.
If you use Axis2 client, first build your logging.mar.
If you are using your wsdl2java stubs you can do
stub._getServiceClient().engageModule("logging");
On Thu, Apr 16, 2009 at 11:33 PM, Sukma Agung Verdianto
wrote:
> I think you can engage logging module from your client if you're usin
13 matches
Mail list logo
