Jeremy Whiting

Ranch Hand
+ Follow
since Mar 05, 2008
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
2
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Jeremy Whiting

how the jBoss know that it has to consider only these jar files from the pool of jars.


The jars are added by the IDE. Searching for jar files under the modules directory.

Can I add a new jar to this jBoos runtime environment.



Trying to add additional jars to the application server is only if you intend that jar be available for all deployed applications. It is for advanced use. For setting up database driver libraries etc. See the documentation for Add an Explicit Module Dependency to a Deployment.
 https://access.redhat.com/documentation/en-us/jboss_enterprise_application_platform/6/html/development_guide/add_an_explicit_module_dependency_to_a_deployment1.


Alternatively bundle additional dependencies with your application in the War or Ear archive.
1 year ago
This forum is for JBoss/Wildfly questions. I suggest you ask this question on the Jetty Users mailing list.

https://accounts.eclipse.org/mailing-list/jetty-users

Have you tried that yet ?
1 year ago
By default remote JMX is already enabled. It is configured to work over the http management interface.
So try removing the properties you added. Then read the Wildfly 13 manual on JMX Security [1] and JMX subsystem configuration [2] for some background.
Depending on the client you want to use you may need to add client dependencies. See the bundled script
bin/jconsole.[sh|bat] for the necessary jar files.
This DZone article [3] gives a good summary.


[1] https://docs.wildfly.org/13/Admin_Guide.html#jmx-security
[2] https://docs.wildfly.org/13/Admin_Guide.html#JMX
[3] https://dzone.com/articles/remote-jmx-access-wildfly-or
1 year ago
You might find starting over and using the Wildfly 26 quickstart examples [1] will get you on the right path.
There is an example for EJB coding [2] you might find useful. Using current day apis.

Jeremy

[1] https://github.com/wildfly/quickstart/tree/26.1.1.Final
[2] https://github.com/wildfly/quickstart/tree/26.1.1.Final/ejb-in-war
1 year ago
Think what you are looking for are Global Modules

http://docs.wildfly.org/15/Developer_Guide.html#global-modules

Jeremy
2 years ago
You say this is a compile time problem. Share your problem.
What's the error ?
What's the code that's reporting the error ?

Jeremy
2 years ago

I see that with Wildfly that is no longer possible.



Hi Thomas,
As Tim mentioned the JEE api provides a UserPrincipal object. That hasn't changed in Wildfly24.

Yes in EAP6.x your code would rely on SecurityContextAssociation to access above interface.
Wildfly24 it is still possible and relies on Context Dependency Injection (CDI) to expose objects and methods you need.

Take a look at this Wildfly 24 quickstart example that uses the JEE Security api.

https://github.com/wildfly/quickstart/blob/162cf351aecaf0ef0cd4d7d03b40c53df26540da/ee-security/src/main/java/org/jboss/as/quickstarts/ee_security/SecuredServlet.java

Jeremy
2 years ago
How about approaching this from another angle.
Move the old Wildfly to a directory you create for archiving stuff. It lives here for posterity.
Then start with a fresh install of Wildfly 24. Bring across configuration and the applications you want to keep from the archive.
Does that work for you ?
2 years ago
Think I found your answer relying on JAVA_OPTS for configuration.


2 years ago

Looking at the documentation for Narayana (Transaction Manager) sub-system we see the configuration with Wildfly section.
https://www.narayana.io//docs/project/index.html#d0e3536

The docs recommend using the cli to configure the transaction sub-system. Have a read (yes v25 docs but the principles are the same) of the configuration instructions.
https://docs.wildfly.org/25/Admin_Guide.html#transaction-statistics
The section "observing all transaction statistics attributes" is relevant to making the configuration change you want. These changes will survive a server restart.

# connect to a running application server
./bin/jboss-cli.bat -c

# enable transaction statistics
/subsystem=transactions:write-attribute(name=statistics-enabled, value=true)
# list all statistics attributes
/subsystem=transactions:read-attribute-group(name=statistics, include-runtime=true)



Can you switch to using the cli rather than using JAVA_OPTS ?

2 years ago
Without more information it's difficult to diagnose what the server considered missing.
You might be tripping over an incompatibility between the blog post written for Wildfly 10. You are deploying to Wildfly 19. These things do change over time.
I suggest you instead refer to the example applications provided on Github. For the release of Wildfly being used.

examples
https://github.com/wildfly/quickstart/tree/19.1.0.Final

ssl example
https://github.com/wildfly/quickstart/tree/19.1.0.Final/helloworld-ssl

Here you have a more reliable (to succeed) example of setting up SSL. Then try re-deploying your application.
2 years ago
I don't know if it is compatible. I suggest you try building the project with jdk17 to find out.

I think you should try using the code.quarkus.io site plus the Quarkus quickstart examples to discover oauth or auth integration.

https://code.quarkus.io/?extension-search=origin:platform%20oauth
https://github.com/quarkusio?q=examples&type=all&language=&sort=
https://github.com/Commonjava/gateway Sorry, I should let the book author Davi respond to the question.
Hi Jan,
Did you turn on the deployment scanner ?

See these instructions from a prior release

https://docs.jboss.org/author/display/WFLY10/Deployment%20Scanner%20configuration.html

You can expect the EAR file be deployed.

Jeremy
2 years ago