[JBoss Seam] - Re: [OT] Seam and Tomahawk - lost property?
by gavin.king＠jboss.com
anonymous wrote : Even if you had this experience in the past didn't mean that they are still true.
Fair enough, I'm willing to give you guys a chance.
anonymous wrote : And - what gives you the right to judge in such a drastic way.
What gives me the right is I'm the one people are asking for advice. If users ask you for advice, I believe it is your responsibility to tell them your honest opinion, ie, what you believe will help them have the most success on their project.
anonymous wrote : A search about "tomahawk" (using the search box in the right upper corner) brought up 6 hits, not *that* much, is it?
Ahem, the search is quite bad, there have of course been many more threads than that (probably more like 100).
anonymous wrote : Once in the past I expressed my personal feeling that Seam is too feature overloaded, immediately one of you guys campaign against me to stop saying such things. And I stopped.
I have no idea who "one of you guys" refers to, but it certainly wasn't me, and I have not heard of any such "campaign" or anything else about this episode.
anonymous wrote : I learned its your decision what you put into Seam.
Sure. And its your perfect right to critique my decisions.
anonymous wrote : So instead of forcing people not to use tomahawk redirect them to our user form
OK, I'll try that, but if we keep seeing the large number of problems we were seeing before, I'm going to have to reinstate the previous policy.
You see, in light of the bugs we've seen in the past, *someone* is going to have to test Seam+Tomahawk. I'm not going to do it because, frankly, the components offered in Tomahawk are not interesting to me and because I believe there are better alternatives. Are *you* guys going to take responsibility for this testing? If the answer is "no", then what's going to happen is that users will find the problems, and they will get frustrated with us because we don't want to take responsibility for them.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993809#3993809
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993809
19 years, 7 months
[JBoss jBPM] - Re: SuperState DB tests - the fix throws Exception when one
by gmournos
I applied the above fix but then undeploying a process definion throws Excpetions.
The test case broken is:
public void testUndeploy() {
| ProcessDefinition procDef = new ProcessDefinition("testUndeploy");
| State s = new State("testnode");
| procDef.addNode(s);
| jbpmContext.deployProcessDefinition(procDef);
| newTransaction();
| ProcessDefinition pd = jbpmContext.getGraphSession().findLatestProcessDefinition("testUndeploy");
| jbpmContext.getGraphSession().deleteProcessDefinition(pd);
| newTransaction();
| }
|
The hibernate query that creates the problem is:
Hibernate:
| update
| JBPM_NODE
| set
| PROCESSDEFINITION_=null,
| NODECOLLECTIONINDEX_=null
| where
| PROCESSDEFINITION_=?
| and (
| nodes0_.SUPERSTATE_ is null
| )
|
Finally the exception thrown is:
12:55:04,534 [main] WARN JDBCExceptionReporter - SQL Error: 904, SQLState: 42000
| 12:55:04,534 [main] ERROR JDBCExceptionReporter - ORA-00904: "NODES0_"."SUPERSTATE_": invalid identifier
|
| 12:55:04,534 [main] WARN JDBCExceptionReporter - SQL Error: 904, SQLState: 42000
| 12:55:04,550 [main] ERROR JDBCExceptionReporter - ORA-00904: "NODES0_"."SUPERSTATE_": invalid identifier
|
| 12:55:04,550 [main] ERROR AbstractFlushingEventListener - Could not synchronize database state with session
| org.hibernate.exception.SQLGrammarException: Could not execute JDBC batch update
| at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67)
| at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
| at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:249)
| at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:92)
| at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:87)
| at org.hibernate.jdbc.AbstractBatcher.prepareBatchStatement(AbstractBatcher.java:218)
| at org.hibernate.persister.collection.AbstractCollectionPersister.remove(AbstractCollectionPersister.java:1030)
| at org.hibernate.action.CollectionRemoveAction.execute(CollectionRemoveAction.java:28)
| at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248)
| at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232)
| at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:141)
| at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
| at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
| at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
| at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338)
| at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106)
| at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:162)
| at org.jbpm.svc.Services.close(Services.java:211)
| at org.jbpm.JbpmContext.close(JbpmContext.java:139)
| ....
| Caused by: java.sql.BatchUpdateException: ORA-00904: "NODES0_"."SUPERSTATE_": invalid identifier
|
| at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:367)
| at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:8739)
| at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)
| at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48)
| at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:242)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993807#3993807
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993807
19 years, 7 months
[JBoss Seam] - [OT] Seam and Tomahawk - lost property?
by imario
Hi!
I wonder about the style used in this forum when it comes to posts where user complain about the interoperability between Seam and Tomahawk.
In the past we (I) tried some stuff in Tomahawk-sandbox which might have had some influence with Seam, but this has been fixed (as far as I know).
Tomahawk itself do nothing strange with e.g. the Lifecycle, at least as far as I am aware.
A sandbox is always a dangerous thing.
Maybe there are better looking/working JSF component libraries out there , but still, there is no reason to be this negative against Tomahawk and _force_ people to NOT use it.
So, instead of ranting around here, it would be great if you (the JBoss Seam Team) could give us a hint if something went wrong so that we can fix it, or, at least, document the incompatibilities so that users do not have to spent eons of time to figure out themself.
Maybe we should sign a contract with Jboss about the effort to make our techniques better compatible.
Just as everyone do with M$ these days.
Thanks!
Ciao,
Mario
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993794#3993794
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993794
19 years, 7 months
[JBossCache] - Buddy Replication and data consistency
by mica
Hi,
Some issues which are not clear for me after reading docs:
if I execute put(fqn, key, value, option) command with autogravity option concurrently on two distinct cache instances (let say put(key, val1) on cache1 and put(key, val2) on cache2)
1) with SYNC_REPL - invokes will be ordered and as a result i'll get consistent state of the cache (so either val1 on cache1 or val2 on cache2)
or i can get a CacheException (or sth more specific?) while from one or both puts?
2) with ASYNC_REPL - i can not get any exception and eventually at some point cache will achieve consistent state or sth else can happen (exception, inconsistent state)?
3) is there any difference in behaviour while using _INVALIDATE than _REPL in cas of buddy replication?
--
thanks in advance,
mj
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993793#3993793
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993793
19 years, 7 months
[EJB/JBoss] - Re: Scheduler vs. EJB Timer Service
by torf
Hi,
we call a SLSB from a org.jboss.varia.scheduler.Scheduler implementation, and our deployment goes like this:
deploy/applications/MyApp/ contains:
- MyApp-all.ear
- MyApp-api.jar
deploy-hasingleton/applications/MyApp/MyApp-timer-service.xml:
| <?xml version="1.0" encoding="UTF-8"?>
| <server>
| <classpath codebase="deploy/applications/MyApp" archives="MyApp-api.jar"/>
| <mbean code="org.jboss.varia.scheduler.Scheduler" name=":service=Scheduler,schedule=MyApp">
| <depends>jboss.j2ee:service=EARDeployment,url='MyApp-all.ear'</depends>
| <attribute name="StartAtStartup">true</attribute>
| <attribute name="SchedulableClass">our.company.framework.timer.TimedObjectSchedulableRemote</attribute>
| <attribute name="SchedulableArguments">ejb/MySchedulerTimer</attribute>
| <attribute name="SchedulableArgumentTypes">java.lang.String</attribute>
| <attribute name="InitialStartDate">0</attribute>
| <attribute name="SchedulePeriod">60000</attribute>
| <attribute name="InitialRepetitions">-1</attribute>
| </mbean>
| </server>
|
our.company.framework.timer.TimedObjectSchedulableRemote has a String-arg constructor which is invoked with argument "ejb/MySchedulerTimer". Its perform method looks up the remote home "ejb/MySchedulerTimer" in JNDI, reflectively invokes create(), and then (non-reflectively) the SLSB business method.
our.company.framework.timer.TimedObjectSchedulableRemote is contained in server/$SERVER_CONF/lib/our-framework.jar.
Regards,
Christoph
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993792#3993792
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993792
19 years, 7 months
[JBoss Portal] - Re: 401 error on selecting dashboard....
by macjboss
OK,
Not much feedback here :) However, I have made some progress. The default portal page that I log in to contains a number of custom pages and portlets that I have deployed. If I add a security constraint to any of these pages (in the object.xml of the page definiton) where I do not have the stated security role, the page is no longer visible on login. However, in the 'pages' portlet on the default page I can still see a link to the secured page. If I click that link, I get the Http 401 error experienced when trying to open the Admin page. If I change the security setting to be a role I have in LDAP, I can see the pages again as tabs in the default page, all good.
This 401 error seems to be returned when I do not have the required role to access the page/resource, a strange error to receive, I thought this error was thrown for BASIC authentication, which I didn't know was being used. I use FORM authentication on portal login.
The problem is, I still can't access the Admin page. Now, I'd like to change the role for the Admin page in portal 2.4 to 'Authenticated' to test the security, but can't find an object.xml that defines that page? Without this, I don't know how to change the required role for the admin page.
Does anyone know where the Admin page is configured and where the security constraint is for that page? Or, does anyone know the name of the required role (probably Admin?) so I can maybe create that group in LDAP so I can log in to the admin page.
Any help would be appreciated.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993773#3993773
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993773
19 years, 7 months
[JBoss Seam] - Trinidad Problems
by dave.rogers
Despite having few problems getting tomahawk up and running it seemed like a good idea to switch to trinidad after reading, several times, that tomahawk was still in alpha and was not to be trusted. It suprised me then to discover that trinidad seems less well supported, fewer forum entries, really hard to find on the web etc.. Not only this, I can't get it to work even a bit.
I get the following error when loading up my home page (which doesn't contain any trinidad tags):
10:07:42,561 ERROR [STDERR] Dec 14, 2006 10:07:42 AM com.sun.facelets.FaceletViewHandler handleRenderException
| SEVERE: Error Rendering View[/secure/home.xhtml]
| java.lang.IllegalStateException: No RenderingContext
| at org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin(CoreRenderer.java:156)
| at org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeBegin(HtmlFormRenderer.java:54)
| at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:512)
| at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:232)
| at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239)
| at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:554)
| at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:326)
| at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:290)
| at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:213)
| at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:90)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:32)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:46)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
Here is my web.xml (simplified)
<?xml version="1.0" ?>
| <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
| version="2.4">
|
|
| <listener>
| <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>
| </listener>
|
| <listener>
| <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
| </listener>
|
| <context-param>
| <param-name>org.jboss.seam.core.init.debug</param-name>
| <param-value>true</param-value>
| </context-param>
|
| <context-param>
| <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
| <param-value>client</param-value>
| </context-param>
|
| <context-param>
| <param-name>facelets.DEVELOPMENT</param-name>
| <param-value>true</param-value>
| </context-param>
|
| <context-param>
| <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
| <param-value>.xhtml</param-value>
| </context-param>
|
|
| <!-- FaceletViewHandler configuration -->
| <context-param>
| <param-name>org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER</param-name>
| <param-value>org.jboss.seam.ui.facelet.SeamFaceletViewHandler</param-value>
| </context-param>
|
| <filter>
| <filter-name>trinidad</filter-name>
| <filter-class>org.apache.myfaces.trinidad.webapp.TrinidadFilter</filter-class>
| </filter>
|
|
| <filter>
| <filter-name>Seam Exception Filter</filter-name>
| <filter-class>org.jboss.seam.servlet.SeamExceptionFilter</filter-class>
| </filter>
|
| <filter>
| <filter-name>Seam Redirect Filter</filter-name>
| <filter-class>org.jboss.seam.servlet.SeamRedirectFilter</filter-class>
| </filter>
|
|
| <filter-mapping>
| <filter-name>trinidad</filter-name>
| <servlet-name>faces</servlet-name>
| </filter-mapping>
|
| <filter-mapping>
| <filter-name>Seam Exception Filter</filter-name>
| <url-pattern>/*</url-pattern>
| </filter-mapping>
|
| <filter-mapping>
| <filter-name>Seam Redirect Filter</filter-name>
| <url-pattern>*.seam</url-pattern>
| </filter-mapping>
|
| <servlet>
| <servlet-name>faces</servlet-name>
| <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
| <load-on-startup>1</load-on-startup>
| </servlet>
|
|
| <servlet>
| <servlet-name>QuartzInitializer</servlet-name>
| <servlet-class>org.quartz.ee.servlet.QuartzInitializerServlet</servlet-class>
|
| <init-param>
| <param-name>config-file</param-name>
| <param-value>quartz-nrg2.properties</param-value>
| </init-param>
|
| <init-param>
| <param-name>shutdown-on-unload</param-name>
| <param-value>true</param-value>
| </init-param>
|
| <init-param>
| <param-name>start-scheduler-on-load</param-name>
| <param-value>true</param-value>
| </init-param>
| <load-on-startup>1</load-on-startup>
| </servlet>
|
| <!-- resource loader servlet -->
| <servlet>
| <servlet-name>resources</servlet-name>
| <servlet-class>org.apache.myfaces.trinidad.webapp.ResourceServlet</servlet-class>
| </servlet>
|
|
| <servlet-mapping>
| <servlet-name>resources</servlet-name>
| <url-pattern>/adf/*</url-pattern>
| </servlet-mapping>
|
| <servlet-mapping>
| <servlet-name>faces</servlet-name>
| <url-pattern>*.seam</url-pattern>
| </servlet-mapping>
|
| ..........security stuff............
|
| </web-app>
Is there a guide anywhere to getting started on Trinidad with Seam and Facelets?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993772#3993772
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993772
19 years, 7 months
[EJB/JBoss] - Procedure call(could not execute native bulk manipulation qu
by niityasir＠hotmail.com
Hi
I am calling oracle procedure in my EJB3 application. Procedure performs alot of tasks (There are several insert/update queries in it).
Query regProc=em.createNativeQuery("Call PROC_REGISTRATION(:i_ACCESS, :i_PLANID, :i_FRANCHISEEID, :i_ADDRESS, :i_BILLINGADDRESS, :out_RESPONSE)");
regProc.setParameter("i_ACCESS",BigInteger.valueOf(regOrder.getAccessLevelService().getAccessLevel()));
regProc.setParameter("i_PLANID",BigInteger.valueOf(objBillingPlan.getPlanId()));
..
..
..
regProc.setParameter("out_RESPONSE",result);
regProc.executeUpdate();
When I run my application I get following exception.
javax.ejb.EJBException: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not execute native bulk manipulation query
Kindly help me to resolve this issue.
Regrads
Yasir
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993769#3993769
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993769
19 years, 7 months
[Persistence, JBoss/CMP, Hibernate, Database] - BMP and the N+1 Problem
by tknerr
Hello,
I have a question for the BMP experts out there:
We want to realize data access to a non-standard database, thus CMP does not work and we have to write our own SQL-like code to access it. It does not support transactions.
Now, the idea was to use BMP Entity beans to realize this scenario, but then I read about the N+1 problem (http://wiki.jboss.org/wiki/Wiki.jsp?page=AvoidBMP), which makes me think that BMP is probably not a good idea and that we better use Stateless Session Beans and ValueObjects instead.
However, someone told me that there are appserver-specific configuration to tune this behaviour, i.e. avoid the N+1 problem with BMP.
So here are my questions:
1) is there a JBoss specific workaround for the N+1 problem with BMP?
- Can you point me to documentation?
2) If I consider to use BMP (even with the N+1 issue), what would be the advantage over Stateless Session Beans + ValueObjects?
- will the container give me some extra functionality which I wouldn't have with SSB + VO?
- will the container give me support for transactions (which we do not have natively) by remembering calls to ejbCreate/Remove etc. and calling them in reverse order with the same PK?
Hope you have some helpful advice for me. I'm especially curios if we could inherit some functionality from the container with the BMP approach.
Thank you and best regards,
Torben
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993763#3993763
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993763
19 years, 7 months
[JBossWS] - Differnce in Web-Service
by subramaniam.venkat
Hello,
I have a probelm in my application.
We are where using JBoss-3.2.4 and for the deploying the web-services we used to deploy the web-service.xml and the wsdl file will be generated.
Mainly for the Exception clases we had the following wsdl generated <complexType name="SoapManagementException">
| <sequence>
|
| <element name="action" nillable="true" type="xsd:string"/>
| <element name="elementName" nillable="true" type="xsd:string"/>
| <element name="faultClass" nillable="true" type="xsd:string"/>
| <element name="reason" nillable="true" type="xsd:string"/>
| <element name="rootCause" nillable="true" type="xsd:string"/>
| </sequence>
| </complexType>
Now we have ported our application to the new JBoss-4.0.3-SP1 . The code for the exception class is same and there is no change in the web-service.xml but the generated wsdl file has changed . Now there is a extra field
<complexType name="SoapManagementException">
| <sequence>
| <element name="message" nillable="true" type="xsd:string"/>
| <element name="action" nillable="true" type="xsd:string"/>
| <element name="elementName" nillable="true" type="xsd:string"/>
| <element name="faultClass" nillable="true" type="xsd:string"/>
| <element name="reason" nillable="true" type="xsd:string"/>
| <element name="rootCause" nillable="true" type="xsd:string"/>
| </sequence>
| </complexType>
The SoapManagementException extends java.lang.Exception .
But can someone tell me why is this new field introduced when deployed in the new JBoss.
Any help we will be very helpful.
Awaiting replies,
Subramaniam V
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993762#3993762
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993762
19 years, 7 months