I tried this
@XmlElement(required=false, nillable=true)
@org.apache.cxf.aegis.type.java5.XmlElement(minOccurs="0",
nillable=true)
@Column(name = "BestContactNumber", length = 10)
public String getBestContactNumber() {
return this.bestContactNumber;
}
public void setBestContactNumber(String bestContactNumber) {
this.bestContactNumber = bestContactNumber;
}
But the Soap message still contains
<ns2:bestContactNumber ns3:nil="true" xmlns:ns3="
http://www.w3.org/2001/XMLSchema-instance"/>
On Fri, Apr 2, 2010 at 6:17 PM, Chris Hardin <[email protected]> wrote:
> CAn someone give me a quick education what FastInfoSet is? Also, how can I
> ensure I am using Woodstox. I have the woodstox.jar in my lib dir.
>
>
> On Wed, Mar 31, 2010 at 10:05 PM, Daniel Kulp <[email protected]> wrote:
>
>> On Wednesday 31 March 2010 4:17:07 pm Mayank Mishra wrote:
>> > Dan,
>> >
>> > Can we shorten the namespace prefix in our engine, specially in cases
>> > for WS-* messages?
>>
>> In the JAXB stuff, yea. There is some config that can specify prefixes to
>> use
>> and such.
>>
>> For WS-Security stuff, possibly not. I think WSS4J has a lot of that
>> burned
>> in.
>>
>> Dan
>>
>>
>> >
>> > With Regards,
>> > Mayank
>> >
>> > Daniel Kulp wrote:
>> > > On Wednesday 31 March 2010 9:34:27 am Chris Hardin wrote:
>> > >> Is there anything I can do to help increase performance? For example,
>> > >> are there some strategies for cutting back on the size of the SOap
>> > >> message generated? Compression? anything would be helpful. I want to
>> > >> squeeze a few micros off my calls.
>> > >>
>> > >> thanks in advance
>> > >
>> > > Couple suggestions:
>> > >
>> > > 1) As mentioned, use minOccurs=0 instead of nillable=true. For
>> messages
>> > > with a lot of "null" values, they are MUCH smaller.
>> > >
>> > > 2) Make sure you use the woodstox parser and not the JDK built in
>> parser
>> > > (for Java6). Woodstox is a LOT faster.
>> > >
>> > > 3) If you can, use Fastinfoset. For larger messages, FI can be a
>> huge
>> > > help as it makes it much smaller on the wire and much easier to parse.
>> > > (although more expensive to write)
>> > >
>> > > 4) If you cannot use FI, but are on a slower connection (aka: not
>> > > localhost or gigabit), then enable gzip.
>> > >
>> > > If you have some large base64 blobs in the message, enabling MTOM
>> would
>> > > also be important (unless using FI). Not sure if that's the case
>> > > though.
>>
>> --
>> Daniel Kulp
>> [email protected]
>> http://dankulp.com/blog
>>
>
>
