[Installation, Configuration & DEPLOYMENT] - JBoss 4.2 and JAVA6, compatibility matrix available
by groovie
Hy there,
i have the problem, we already started our development with JAVA6 using JBoss4.2.x.
Yes, i know that Java6 is not officially supported, but the project manager staff
decided to use JAVA6. Since JBoss5.x is delivered as a commercial
product (supported by Redhat/JBoss), we have to go with JBoss4.2.x
Running JAVA6 (on Linux) with JBoss issued some problems on
the free JBoss 4.2.x version, that have been solved.
Anyway, when i try to deploy my JBoss-ear file on the commercial JBoss
server 4.2.1 running JAVA6. The deployment runs without any problem,
the Web-GUI does run without any problems, but when i try to
access the Web-Service, some exceptions happend.
Seeking through the forum tells me, that i am using a wrong JAVA version.
Great, but which one i should use ???
Is the a matrix of cooperating JBoss/JAVA Versions availiabe ??
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247919#4247919
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247919
16 years, 8 months
[JBoss Messaging] - JBM / JMS / EAI / c++ / wire-protocol
by moonbird79
Hi,
i write my diploma thesis about Enterprise Application Integration and I am a little bit confused, may be you can help me:
I have a JBoss AS-5, running with JBM 1.x and 2 Queues. My task is to connect from an old c++ application to my queues as a consument. At the moment the c++ application is connected to Tibco EMS via Tibco EMS c-client API.
The Tibco c-api documentation writes, that the API is 100% JMS compatible...
So, is it possible to connect from this API to JBM ??
As far, as I understand the JMS API, JMS is ONLY a API and every vendor can implement it different, for example with differen transport protocols. So you have different broker and - if you want to connect to broker X you have to use the client api of broker X. Is this correct ?
So if this is the case, I have to use JBM c-API which will be available with JBM 2.x ? Or is it possible to use for example ActiveMQ c-client API ?
And - what about AMQP ? Would this be a better way to use ? Isn't it the main reason for this api/protocol to connect with different vendors ?
What about STOMP and OpenWire protocol ? Does JBM support this and how ?
What is the default wire-protocol of JBM ? Is is correct, that if you use different JMS vendors on client and server side, which both use the same wire-protocol , that they will connect well ?
Many, many, many thanks !!!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247918#4247918
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247918
16 years, 8 months
[JBossWS] - Two classes have the same XML type name when deploying clien
by meetoblivion
This may have more to do with how our test/dev environment is setup, but I am in the process of developing some web services to act as a facade to direct database access from our external site (mostly for writes). When I deploy both the client (war) and server (ejb jar) on the same box, I get the below errors in my stack trace:
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 3 counts of IllegalAnnotationExceptions
| Two classes have the same XML type name "{http://sweeps.services.web.coat.com/}signupProperties". Use @XmlType.name and @XmlType.namespace to assign different names to them.
| this problem is related to the following location:
| at com.coat.web.services.sweeps.SignupProperties
| at protected java.util.List com.coat.web.services.sweeps.SweepsSignup.properties
| at com.coat.web.services.sweeps.SweepsSignup
| this problem is related to the following location:
| at com.coat.web.services.sweeps.SignupProperties
| at public com.coat.web.services.sweeps.SignupProperties com.coat.web.services.sweeps.ObjectFactory.createSignupProperties()
| at com.coat.web.services.sweeps.ObjectFactory
| Two classes have the same XML type name "{http://sweeps.services.web.coat.com/}sweepsSignup". Use @XmlType.name and @XmlType.namespace to assign different names to them.
| this problem is related to the following location:
| at com.coat.web.services.sweeps.SweepsSignup
| this problem is related to the following location:
| at com.coat.web.services.sweeps.SweepsSignup
| at public com.coat.web.services.sweeps.SweepsSignup com.coat.web.services.sweeps.ObjectFactory.createSweepsSignup()
| at com.coat.web.services.sweeps.ObjectFactory
| Two classes have the same XML type name "{http://sweeps.services.web.coat.com/}SweepsException". Use @XmlType.name and @XmlType.namespace to assign different names to them.
| this problem is related to the following location:
| at com.coat.web.services.sweeps.SweepsException
| this problem is related to the following location:
| at com.coat.web.services.sweeps.SweepsException
| at public com.coat.web.services.sweeps.SweepsException com.coat.web.services.sweeps.ObjectFactory.createSweepsException()
| at com.coat.web.services.sweeps.ObjectFactory
Now, I think it's because both client and server are on the same machine. I used wsconsume to generate the WS client stubs. Is the correct work around to use a different package?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247907#4247907
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247907
16 years, 8 months