[JBossWS] - IllegalStateException due calling wsconsume
by Cheffilet
Hi there,
i´ve one problem there, as you can see by the topic.
When i try to generate the client-stub java files by typing in the console wsconsume echo.wsdl i receiving following stack trace:
anonymous wrote :
| C:\JBossWebService\install\bin>wsconsume echo.wsdl -t
| Exception in thread "main" java.lang.IllegalStateException: Could not load provi
| der:org.jboss.ws.tools.jaxws.impl.WSContractConsumerFactoryImpl
| at org.jboss.ws.tools.jaxws.api.Locator.locate(Locator.java:55)
| at org.jboss.ws.tools.jaxws.api.WSContractConsumer.newInstance(WSContrac
| tConsumer.java:68)
| at org.jboss.ws.tools.jaxws.api.WSContractConsumer.newInstance(WSContrac
| tConsumer.java:56)
| at org.jboss.ws.tools.jaxws.command.wsconsume.importServices(wsconsume.j
| ava:170)
| at org.jboss.ws.tools.jaxws.command.wsconsume.main(wsconsume.java:76)
|
I mention, that i´ve invoking the particular wsconsume file at the JbossWebFolder/install/bin as you can downloading from the jboss homepage as well.
The rather install procedure to migrate the JBossWebService into the Application Server(4) works for me very well.
Any ideas?
Have i to insert specifiy librarys into the JAVA_HOME/lib/ext Folder or something like that?
Best regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4046761#4046761
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4046761
18 years, 11 months
[JBoss Seam] - persist without @GeneratedValue
by nicolasb
Hello
I'm a bit confused concerning this issue but I think this fits inside the seam context since i am basically following the tutorial drum line with the newest stable seam release.
i tried to create a simple entity without an @GeneratedValue notations but it doesn't seam to persist. the tables are being generated correctly but no message in thrown in stdout in opposite to a simple persistence operation with an @GeneratedValue notation.
| public class Blog implements Serializable
| {
| @Id
| private long id;
|
| public long getId() { return id;}
| public void setId(long id) { this.id = id; }
|
| }
|
In my stateless session bean i use
| Blog b = new Blog();
| b.setId(17);
| entityManager.persist(b);
|
any idea ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4046759#4046759
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4046759
18 years, 11 months
[Security & JAAS/JBoss] - JAAS : Subject not populated
by as1816
We have a problem in using JAAS during migration from Jboss-3.2.3 to JBoss-4.0.5.GA. The same approach is working in JBoss-3.2.3 version.
The reason for above I found is SecurityAssociation is not populated for JBoss-4.0.5.GA.
Ear Deployment/JAAS Configurations details:
We have two .ear deployed in the same server. First ear contains all EJBs. Second ear contains one war file through which we monitor the system. We are using customized login module and this login module is invoked properly and subject is populated.
subject.getPrivateCredentials().add(userBean);
logger.info("Adding role '" + userBean.getRole() + "'to context");
userRoles.addMember(new SimplePrincipal(userBean.getRole()));
Login module returns true. But from action class, when we call below code subject is null.
--------------------------------------------------------------------------------------
EntryUser user = EISDataHelper().getUser();
signature of getUser is as below:
public EntryUserBean getUser() throws CustodyException,
RemoteException
{
Subject subj = SecurityAssociation.getSubject();
//Here subject is null(in JBoss-4.0.5.GA), while same code is running in JBoss-3.2.3
if (subj == null)
{
logger.debug("subject is null");
return null;
}
}
--------------------------------------------------------------------------------------
Configuration for login module in login-config.xml is as below :
--------------------------------------------------------------------------------------
<application-policy name="settlement">
<login-module code="com.db.dcs.model.settlements.jboss.security.LdapDBLoginModule" flag="required">
<module-option name="validatePWD">true</module-option>
</login-module>
</application-policy>
--------------------------------------------------------------------------------------
Configuration for JAAS in conf/jboss-service.xml is as below :
--------------------------------------------------------------------------------------
<!--
====================================================================
-->
<!-- Security
-->
<!--
====================================================================
-->
jboss.security:service=XMLLoginConfig
login-config.xml
<!-- JAAS security manager and realm mapping -->
<!-- change JaasSecurityManager by JaasSecurityDomain -->
org.jboss.security.plugins.JaasSecurityDomain
<!--JaasSecurityDomain -->
jboss.security:service=JaasSecurityManager
${jboss.server.home.dir}/ssl/.keystore
gft01abc
--------------------------------------------------------------------------------------
Configuration for SSL in deploy/jbossweb-tomcat55.sar/server.xml is as below :
--------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------
Configuration for security domain in deploy/settlement-webapp.ear/settlement-webapp.war/jboss-web.xml is as below :
--------------------------------------------------------------------------------------
<jboss-web>
<security-domain>java:/jaas/settlement</security-domain>
</jboss-web>
--------------------------------------------------------------------------------------
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4046758#4046758
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4046758
18 years, 11 months
[JBoss Seam] - Re: [JBSEAM-1302]: Conversion support for selectMany for Set
by fhh
I took a closer look at the jsf implementation. The relvant bit of code is this (from com.sun.faces.renderkit.html_basic.MenuRenderer.convertSelectManyValue()):
|
| modelType = valueExpression.getType(context.getELContext());
| // Does the valueExpression resolve properly to something with
| // a type?
| if (null != modelType) {
| if (modelType.isArray()) {
| result = convertSelectManyValues(context,
| uiSelectMany,
| modelType,
| newValues);
| } else if (List.class.isAssignableFrom(modelType)) {
| result = Arrays.asList((Object[]) convertSelectManyValues(
| context,
| uiSelectMany,
| Object[].class,
| newValues));
| } else {
| throwException = true;
| }
|
|
|
So, this seems to be a limitation of JSF indeed.
What surprises me is that it would be trivival to fix. Sets must have been left out on purpose. Does anybody know why? The way the html component work, support for sets seems more natural then lists.
Regards
Felix
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4046751#4046751
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4046751
18 years, 11 months