What's the quickest way to determine which version of JBossWS is in use in a WildFly installation?
I have a WildFly 10 installation, and when I search various files for version numbers pertaining to JBossWS, I see different things depending on where I look.
Examples:
{jboss-install-dir}\runtimes\jboss-eap\modules\system\layers\base\org\jboss\as\webservices\main\module.xml references jbossws-cxf-resources-5.1.3.SP1-redhat-1-wildfly1000.jar
{jboss-install-dir}\runtimes\jboss-eap\modules\system\layers\base\jboss\ws\api\main\module.xml references jbossws-api-1.0.3.Final-redhat-1.jar
{jboss-install-dir}\runtimes\jboss-eap\modules\system\layer\base\org\jboss\ws\common\main\module.xml references jbossws-common-3.1.1.Final-redhat-1.jar
Are any of these the JBossWS version, or should I be looking elsewhere? Thanks.
I think JBossWS version is the same as asking JBoss WS-CXF, since JBossWS takes apache-cxf and integrates it to Wildfly. So the answer is 5.1.3.SP1
You can also check https://access.redhat.com/articles/112673
Related
As a long-time J2EE developer, I have always been curious as to why NetBeans uses(i.e. forces you to use) the Tomcat Manager app to deploy while Eclipse seems perfectly happy/able to deploy without the manager app? Though I have googled this exhaustively over the years, I have never found even the beginning to an answer. Perhaps this is nothing more than how each product started and has never changed.
Does anyone have any insight or educated theories they would be willing to share?
[Edit] Sigh... to address shekhar's comment, I see that it is not absolutely clear that I am referring ONLY to using Tomcat. I mistakenly assumed that the title and context of my question was sufficient, but again, I am specifically referring to using Tomcat as the Servlet Container with these IDEs. Thanks.
[Edit] I don't know who down-voted this but I have researched this for a long time and found zero reason for it. As for down-voting because it might not be useful, I think that is in the eye of the beholder; also, it usefulness can only be determined based on the answer which is why I am asking.
Sounds like a good topic for Quora but anyway...
I can only speak about NetBeans. It originally used a patched version of Tomcat 3. (early NetBeans 3.x releases). Tomcat Manager was added in Tomcat 4 and it was used because it was possible to integrate easily with your Tomcat installation without knowing much details about their setup. Start/stop Tomcat can use default scripts and will pick up your settings. Deploy does not need to care about access rights and it just assumes that manager works.
I am very new to jboss app server and using jboss app server 4.1.4 and want to upgrade to any latest version like 6 or 7. What’s the best process to perform i.e. I have seen that “copy the .rar and .war files” and these can’t make right scene to work. What's the best process?
The best way to start is to get an overview over your existing application. In particular:
Which non-standard JBoss features do you use (JBoss Cache, JCA Work Manager, …)?
What "managed resources" (data sources, connection factories, …) do you use?
Which configuration changes did you make (connection pool, transaction timeout, …)?
Which classloading assumptions does your packaging make?
and then individually check how these are handled in the JBoss version you want to migrate to.
there is no one to answer this question..looks shame about it.
I'm trying to deploy my application in JBoss AS 6. Currently it is deployed in JBoss version 4.
So what are the things I need to consider when doing this?
Any help will be highly appreciated. Thanks.
You're talking about two major versions change, so, expect a lot of things to happen. Some steps that might be helpful:
Make an inventory of everything that is JBoss-specific in your project: deployment descriptors being the most common examples, but you might also be implementing some specific classes for your own use, or things like that
Make an inventory of the Java EE APIs that you are using. For instance, JPA 1.0, JSP 1.1 and so on. With those, compare with the APIs that are available for AS 6. I guess that most of your work will be centered here.
You might also want to take note of changes in the Java version (AS 4 was released during the days of Java SE 5, IIRC).
Finally, you might want to take a look at the Windup project, which is a tool that can help you migrate your applications to JBoss AS. Note, however, that it will not give you a comprehensive list of everything you need to do, but will certainly give you good hints.
One last comment: you might want to consider migrating to JBoss EAP 6, which is JBoss AS 7, or even migrating to Wildfly 8 (the successor of JBoss AS 7).
I found this great tutorial for JAAS with JBoss, but the problem is that it is an older version. In this tutorial to define application authentication policy at JBoss you need to use "login-config.xml" in this directory -> D:\jboss-4.2.3.GA\server\mmazharhassan.com\conf\login-config.xml which doesn't exist in version 7. The writer is describing also this file "mazhar-ds.xml" in this directory -> D:\jboss-4.2.3.GA\server\mmazharhassan.com\deploy\
mazhar-ds.xml.
I would like to ask you what is the difference in newer version or how do I implement this Java Authentication and Authorization Service in JBoss 7 because i can't find any good tutorial for the version 7 (or where do I find all these files).
EDIT:
I'm sorry maybe for stupid questions, but I'm complete beginner in this.. :(
You can implement a JAAS Module in the same way you did it in JBoss 4, but the configuration of it is different.
What you probably should look at, is the http://docs.jboss.org/teiid/7.2.0.Final/developer-guide/en-US/html/custom_login_modules.html
Especially, the DatabaseLoginModule might be interesting for you.
I need to use some EJBs which are deployed on JBoss version 4.x from another EJB deployed on JBoss version 3.2.x. Is this possible?
I ask because I have a third party application which uses some strange bridge's to do that and don't know why (though I haven't try to do this on my own).
This is unfortunately not possible. One of the major drawbacks of remote EJBs is that there is nothing in the specification that guarantees or even suggests any kind of interoperability between different vendors or between different EJB versions from the same vendor.
In practice I found that at least with JBoss AS it never works. Even minor upgrades break binary compatibility completely. There have been some very hacky attempts with special class loaders that are only been given access to the client libs of the target JBoss AS, but this is very tricky to get right.
I guess this "strange bridge" you are talking about is using such a trick. Kudos to whoever build that bridge for getting this to work at all.
See this topic I started on the JBoss community forum for some more details: http://community.jboss.org/message/587180