[JBoss Web Services] - Problems with missing minOccurs=" 1" in generated wsdl
by Mats Ekström
Mats Ekström [http://community.jboss.org/people/fghj5678] created the discussion
"Problems with missing minOccurs="1" in generated wsdl"
To view the discussion, visit: http://community.jboss.org/message/561764#561764
--------------------------------------------------------------
Hi!
We are using jboss soa platform 4.3.0 CP02 and when I annotate like this:
@XmlElement(nillable=false, required=true)
public void setProducer(String producer) {
public void setProducer(String producer) {
this.producer = producer;
}
this.producer = producer;
}In the generated wsdl (from the deploy), the element producer will look like this:
<xs:element name="producer" type="xs:string"/>
Where is the minOccurs="1"???
If I instead annotate at declaration of producer I get an exception:
@XmlElement(nillable=false, required=true)
private String producer;
java.lang.IllegalStateException: Cannot build JAXB context
...
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions
Class has two properties of the same name "producer"
this problem is related to the following location:
at public java.lang.String se.tullverket.texi.archive.bl.Trans.getProducer()
at se.tullverket.texi.archive.bl.Trans
at public se.tullverket.texi.archive.bl.Trans se.tullverket.texi.archive.bl.ArchiveTO.getTrans()
at se.tullverket.texi.archive.bl.ArchiveTO
at private se.tullverket.texi.archive.bl.ArchiveTO se.tullverket.texi.archive.bl.jaxws.Archive.arg0
at se.tullverket.texi.archive.bl.jaxws.Archive
this problem is related to the following location:
at private java.lang.String se.tullverket.texi.archive.bl.Trans.producer
And if I skip the annotation it looks like this:
<xs:element minOccurs="0" name="producer" type="xs:string"/>
Any ideas?
/Mats
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/561764#561764]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 12 months
[jBPM] - Re: JBPM 3.2.5, MSSQL 2005 - blocking in JBPM_JOB table
by Alejandro Guizar
Alejandro Guizar [http://community.jboss.org/people/alex.guizar%40jboss.com] created the discussion
"Re: JBPM 3.2.5,MSSQL 2005 - blocking in JBPM_JOB table"
To view the discussion, visit: http://community.jboss.org/message/563437#563437
--------------------------------------------------------------
> Looking at how the jbpm_job table is utilized, yes, I think these specific indexes can be removed. Just to clarify. From what I have seen in *our use-case*, under normal circumstances the jbpm_job table has very few entries at any point in time. Seems like entries are added and removed constantly. That being the case, I'm not sure I can see a benefit of spending the extra time/resources maintaining indexes which are never utilized.
I'm going to explore the possibility of removing the job indexes. Can you please https://jira.jboss.org/browse/JBPM create a JIRA issue for this?
> By the way, this is as good a time to explain the use-case that is failing for us. We have a workflow with three steps synchronous steps. The first step takes a couple to a few hundred milliseconds to complete, the second step can take anywhere from 5 to 30 seconds to complete and then the last step usually takes a half a second. When I mentioned jobs earlier, I was referring to workflows contained the three steps just mentioned.
If possible, could you attach your workflow and test harness to the JIRA issue? Please remove any sensitive information you would not like to see published.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/563437#563437]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 1 month