November 2011 - jboss-dev-forums - Jboss List Archives

[JBoss AS7 Development] - Exception while deploying to jbossweb-7.0.2.Final

by Julian Prabhakar

Julian Prabhakar [http://community.jboss.org/people/julian.prabhakar] created the discussion "Exception while deploying to jbossweb-7.0.2.Final" To view the discussion, visit: http://community.jboss.org/message/635657#635657 -------------------------------------------------------------- We are getting this error during deployment - FATAL [org.egov.infstr.utils.HibernateUtil] (http--127.0.0.1-8080-1) Error occurred in SessionFactory getSessionFactory: java.lang.UnsupportedOperationException: Naming context is read-only at org.jboss.as.naming.NamingContext.createSubcontext(NamingContext.java:318) at org.hibernate.service.jndi.internal.JndiServiceImpl.bind(JndiServiceImpl.java:153) [hibernate-core-4.0.0.CR5.jar:] at org.hibernate.service.jndi.internal.JndiServiceImpl.bind(JndiServiceImpl.java:110) [hibernate-core-4.0.0.CR5.jar:] at org.hibernate.internal.SessionFactoryRegistry.addSessionFactory(SessionFactoryRegistry.java:79) [hibernate-core-4.0.0.CR5.jar:] at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:439) [hibernate-core-4.0.0.CR5.jar:] at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1726) [hibernate-core-4.0.0.CR5.jar:] at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1764) [hibernate-core-4.0.0.CR5.jar:] Is this because of a JBoss issue? Pls help. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/635657#635657] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

12 years, 5 months

1
0
0 / 0

[JBoss AS7 Development] - HTTP (JSON-like) API

by Kabir Khan

Kabir Khan [http://community.jboss.org/people/kabirkhan] modified the document: "HTTP (JSON-like) API" To view the document, visit: http://community.jboss.org/docs/DOC-17344 -------------------------------------------------------------- This is a digest of http://lists.jboss.org/pipermail/jboss-as7-dev/2011-February/000491.html http://lists.jboss.org/pipermail/jboss-as7-dev/2011-February/000491.html for easier finding. In a nutshell this is another view on the management API available over the http connector installed in standalone.xml/host.xml, normally on port 9990. <management> <security-realms> <security-realm name=+"ManagementRealm"+> <authentication> <properties path=+"mgmt-users.properties"+ relative-to=+"jboss.server.config.dir"+ plain-text=+"true"+/> </authentication> </security-realm> </security-realms> <management-interfaces> <native-interface interface=+"management"+ port=+"9999"+/> * <http-interface interface=+"management"+ port=+"9990"+/>* </management-interfaces> </management> *GET requests* The GET URL form is a mapping of operation addresses, with a few supported read operations, and support for mapping top level values via query parameters. The default operation is read-resource. So in otherwords you can dump the whole management tree like so: http://localhost:9990/management?recursive http://localhost:9990/management?recursive To make the output of any GET operation easier to read you can append the "json.pretty" parameter to the end, e.g.: http://localhost:9990/management?operation=resource&recursive&json.pretty The lack of additional /'s defaults to the root node. The lack of an "operation" defaults to the read-resource operation. The "recursive" is mapped to the recursive as a boolean, a lack of an assignment defaults to "true" The attributes of the http web connector can be restrieved with: http://localhost:9990/management/subsystem/web/connector/http http://localhost:9990/management/subsystem/web/connector/http A single attribute can be retrieved by specifying the attribute operation and the attribute name: http://localhost:9990/management/subsystem/logging/console-handler/CONSOL... http://localhost:9990/management/subsystem/logging/console-handler/CONSOL... The full description of the mode can be retrieved using the read-resource-description operation like so: http://localhost:9990/domain-api?operation=resource-description&recursive... http://localhost:9990/management?operation=resource-description&recursive... *POST requests* You can also do post support for both JSON and DMR Encoded: curl -d '{"operation":"read-resource","address":[],"json.pretty":1}' http://localhost:9990/domain-api http://localhost:9990/management curl -H Content-Type:\ application/dmr-encoded -d bwAAAAMACW9wZXJhdGlvbnMADXJlYWQtcmVzb3VyY2UAB2FkZHJlc3NsAAAAAAAHcmVjdXJzZVoB http://localhost:9990/domain-api http://localhost:9990/management -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-17344] Create a new document in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

12 years, 5 months

1
0
0 / 0

[JBoss AS7 Development] - HTTP (JSON-like) API

by Kabir Khan

Kabir Khan [http://community.jboss.org/people/kabirkhan] modified the document: "HTTP (JSON-like) API" To view the document, visit: http://community.jboss.org/docs/DOC-17344 -------------------------------------------------------------- This is a digest of http://lists.jboss.org/pipermail/jboss-as7-dev/2011-February/000491.html http://lists.jboss.org/pipermail/jboss-as7-dev/2011-February/000491.html for easier finding. In a nutshell this is another view on the management API available over the http connector installed in standalone.xml/host.xml, normally on port 9990. <management> <security-realms> <security-realm name=+"ManagementRealm"+> <authentication> <properties path=+"mgmt-users.properties"+ relative-to=+"jboss.server.config.dir"+ plain-text=+"true"+/> </authentication> </security-realm> </security-realms> <management-interfaces> <native-interface interface=+"management"+ port=+"9999"+/> * <http-interface interface=+"management"+ port=+"9990"+/>* </management-interfaces> </management> The GET URL form is a mapping of operation addresses, with a few supported read operations, and support for mapping top level values via query parameters. The default operation is read-resource. So in otherwords you can dump the whole management tree like so: http://localhost:9990/management?recursive http://localhost:9990/management?recursive To make the output of any GET operation easier to read you can append the "json.pretty" parameter to the end, e.g.: http://localhost:9990/management?operation=resource&recursive&json.pretty The lack of additional /'s defaults to the root node. The lack of an "operation" defaults to the read-resource operation. The "recursive" is mapped to the recursive as a boolean, a lack of an assignment defaults to "true" The attributes of the http web connector can be restrieved with: http://localhost:9990/management/subsystem/web/connector/http http://localhost:9990/management/subsystem/web/connector/http A single attribute can be retrieved by specifying the attribute operation and the attribute name: http://localhost:9990/management/subsystem/logging/console-handler/CONSOL... http://localhost:9990/management/subsystem/logging/console-handler/CONSOL... The full description of the mode can be retrieved using the read-resource-description operation like so: http://localhost:9990/domain-api?operation=resource-description&recursive... http://localhost:9990/management?operation=resource-description&recursive... TBD Document the POST operations, e.g. to create a deployment -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-17344] Create a new document in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

12 years, 5 months

1
0
0 / 0

[JBoss AS7 Development] - JBoss AS7 - Resource loading with ClassLoader - Issue

by Julian Prabhakar

Julian Prabhakar [http://community.jboss.org/people/julian.prabhakar] created the discussion "JBoss AS7 - Resource loading with ClassLoader - Issue" To view the discussion, visit: http://community.jboss.org/message/635308#635308 -------------------------------------------------------------- Hi All, We are facing an issue with loading a .jar resource file using Thread.currentThread().getContextClassLoader().getResource("xyzmappings.jar"). This code was perfectly working in older versions of Jboss but with jboss-as-7.0.2.Final its not finding the resource (giving back null). Our .ear structure is as follows. ${JBOSS_HOME}/.../deployments/xyz.ear--| |--META-INF |--xyzadmin.war |--lib--| |--xyzjava.jar |--xyzmappings.jar (contains only hibernate hbm.xml files) Anyone know why is this happening? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/635308#635308] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

12 years, 5 months

2
2
0 / 0

[JBoss AS7 Development] - How to configure a service-ref in the environment?

by Maarten Winkels

Maarten Winkels [http://community.jboss.org/people/m.winkels] created the discussion "How to configure a service-ref in the environment?" To view the discussion, visit: http://community.jboss.org/message/634825#634825 -------------------------------------------------------------- Hi, I'm building an application that uses both internal and external webservices. This application is based on JAX-WS and is using @WebServiceRef to inject references to webservices. The location of the WSDL for the endoints are configured in th web.xml using a service-ref element. This is working great. The location of the webservices, however, differs per deployment environment. My question is how to make the endpoint (WSDL) location configurable per location. To me this seems very similar to defining a JDBC or any other resource: The application uses anamed resource that is configured in the container. I'm not finding the functionality to do this in JBoss 7, however. I have been trying a number of options: - Use a system property in the web.xml like <wsdl-file>${some.property}?wsdl</wsdl-file>. This does not seem to work. This doesn't seem to work. - Use a jboss-web.xml and do property override there. I haven't tried this yet, but looking at the source code that parses the jboss-web.xml I see nothing that will inject system properties - Configure the service-ref in Global JNDI. According to the spec the mappedName property of the @WebServiceRef annotation should link it to a globally defined resource. I cannot find a way to define global JNDI entries in JBoss AS 7, let alone configure a WebServcice EndPoint. - Use jUDDI for web service registration and lookup. I'm a little bit hesitant to use another product to connect the dots. Is this the only possible solution? Can anyone point me in the right direction? Thanks! -Maarten Winkels -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/634825#634825] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

12 years, 5 months

2
3
0 / 0

[JBoss AS7 Development] - Logging Id's

by James Perkins

James Perkins [http://community.jboss.org/people/jamezp] modified the document: "Logging Id's" To view the document, visit: http://community.jboss.org/docs/DOC-16810 -------------------------------------------------------------- Logging id ranges for JBoss AS7 i18n message interfaces. || %1,3% *Status* || | C | = | Complete | | I | = | In Progress | | W | = | Waiting Merge | || *Range* || *Subsystem * || *Status * || | *10100 - 10199* | *Transaction* | C | | *10200 - 10399 * | *Clustering** * | C | | *10400 - 10499* | *Connector** * | C | | *10500 - 10599* | * * | | | *10600 - 10699* | *Controller Client* | | | *10700 - 10799* | *Deployment Repository* | | | *10900 - 10999* | *Deployment Scanner* | | | *11000 - 11099* | *EE* | | | *11100 - 11199* | *Embedded* | | | *11200 - 11299* | *JAXRS* | | | *11300 - 11399* | *JMX* | | | *11400 - 11499* | *JPA* | C | | *11500 - 11599* | *Logging* | C | | *11600 - 11699* | *Messaging* | C | | *11700 - 11799* | *mod_cluster* | C | | *11800 - 11899* | *Naming* | C | | *11900 - 11999* | *OSGi (as plugin 00-10; service 11-99)* | C | | *12000 - 12099* | *Process Controller* | C | | *12100 - 12199* | *Protocol* | C | | *13100 - 13199* | *Security* | | | *14100 - 14399* | *Ejb3* | I | | *14400 - 14499* | *AppClient* | C | | *14500 - 14599* | *JDR* | | | *14600 - 14899* | *Controller* | C | | *14900 - 14999* | *Deployment Repository* | C | | *15000 - 15099* | *Deployment Scanner* | C | | *15100 - 15199* | *Deployment HTTP API* | C | | *15200 - 15299* | *Deployment Management* | C | -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-16810] Create a new document in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

12 years, 5 months

1
0
0 / 0

[JBoss AS7 Development] - Re: jboss7 quickstarts entitymanager injection question

by Stuart Douglas

Stuart Douglas [http://community.jboss.org/people/swd847] created the discussion "Re: jboss7 quickstarts entitymanager injection question" To view the discussion, visit: http://community.jboss.org/message/635434#635434 -------------------------------------------------------------- If there is only one persistence unit in the application you can inject it without specifying the name -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/635434#635434] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

12 years, 5 months

2
1
0 / 0

[JBoss AS7 Development] - Re: jboss7 quickstarts entitymanager injection question

by Stuart Douglas

Stuart Douglas [http://community.jboss.org/people/swd847] created the discussion "Re: jboss7 quickstarts entitymanager injection question" To view the discussion, visit: http://community.jboss.org/message/635429#635429 -------------------------------------------------------------- Persistence units (i.e. EntityManagers) are defined in persistence.xml, having a datasource present does not automatically create a corresponding EntityManager. The connection to use is specified in persistence.xml. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/635429#635429] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

12 years, 5 months

2
1
0 / 0

[JBoss AS7 Development] - jboss7 quickstarts entitymanager injection question

by robert walker

robert walker [http://community.jboss.org/people/robertwalker] created the discussion "jboss7 quickstarts entitymanager injection question" To view the discussion, visit: http://community.jboss.org/message/635427#635427 -------------------------------------------------------------- Hi all, I am looking at the examples in jboss7 quickstarts , login and kithensink (ones that hit a DB) and wondering how jb7 knows which persistence unit to inject. for example if standalone.xml defines a few datasources (like the default) ..... and say another named "MyDataDSource" .... how does jboss know which one to inject when executing code like this from login quickstart's ManagedBeanUserManager.java file @Inject private EntityManager userDatabase; No designation which PU to to inject, I was thinking there would have to be code along the idea of the snippet below @PersistenceContext(unitName = "MyDataDSource") EntityManager em; I did read the "Chapter 5. CDI + JPA + EJB + JTA + JSF: Login quickstart" but was eagerly wanting to know how jboss knows which one to inject but didn't see it, which means it's so obvious that it does not need to be stated. So I realize i should know it this but I don''t. :-( I see the the pattern suggested by CDI is resource producers, but Resources.java has // Expose an entity manager using the resource producer pattern @SuppressWarnings("unused") @PersistenceContext @Produces private EntityManager em; with no designation either can someone point me to a reesource to explain this a bit more thanks -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/635427#635427] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

12 years, 5 months

1
0
0 / 0

[JBoss AS7 Development] - how to check all the available modules on admin console?

by jaabax

jaabax [http://community.jboss.org/people/jaabax] created the discussion "how to check all the available modules on admin console?" To view the discussion, visit: http://community.jboss.org/message/635149#635149 -------------------------------------------------------------- hi folks I have created a module and I can't reference it through my application using jboss-deployment-structure.xml I got a java.lang.NoClassDefFoundError is there a place where I can check all the available modules after start the server? (to check if my newly created module is there) thanks in advance! -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/635149#635149] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

12 years, 5 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums November 2011