Yeah, but first I wanted to make sure if that is really something which is not supported or if I just couldn't find how to do it. The documentation seemed unclear to me.
On Thursday, March 8, 2018 at 7:31:51 PM UTC+1, Ron wrote: > > I’d suggest filing a ticket with the respective project. > > > > > > > > *From: *<[email protected] <javascript:>> on behalf of Frank > Rosenberger <[email protected] <javascript:>> > *Reply-To: *"[email protected] <javascript:>" < > [email protected] <javascript:>> > *Date: *Thursday, March 8, 2018 at 03:30 > *To: *Swagger <[email protected] <javascript:>> > *Subject: *JAXB annotated non-public fields > > > > I am using Swagger 3.0/Open-API in a Java project. > > I have non-bean-like DTO classes which are JAX-B-annotated. > > @XmlType > @XmlAccessorType(XmlAccessType.FIELD) > public MyDTO { > > private String myProperty; > > } > > Swagger does not pick up the property myProperty while JAX-B and Jackson > process it as expected. > > The Swagger docs talk about bean properties from time to time, but I don't > see a requirement for classes to be beans. All solutions regarding JAXB and > non-bean-like model classes I found (e.g. @ApiModelProperty) refer to older > Swagger versions. > Is there a way to have current Swagger process non-public properties > without setters/getters? > > -- > You received this message because you are subscribed to the Google Groups > "Swagger" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
